EPC Implementer > EPCIS > Query   
 
EPCglobal-epcis-query-1_0
Previous element    
Next element
 
ComplexType epcisq:QueryParam
 
Diagram
 
 
  
Definition: Pedefined Queries for EPCIS 1.0

In EPCIS 1.0, no query language is provided by which a client may express an arbitrary query for data. Instead, an EPCIS 1.0 implementation shall provide predefined queries, which a client may invoke using the poll and subscribe methods of the EPCIS Query Control Interface. Each poll or subscribe call may include parameters via the params argument. The predefined queries each have a large number of optional parameters; by appropriate choice of parameters a client can achieve a variety of effects.

An implementation of EPCIS is free to use any internal representation for data it wishes, and implement these predefined queries using any database or query technology it chooses, so long as the results seen by a client are consistent with this specification.

Simple Event Query

This query is invoked by specifying the string SimpleEventQuery as the queryName argument to poll or subscribe. The result is a QueryResults instance whose body contains a (possibly empty) list of EPCISEvent instances. Unless constrained by the eventType parameter, each element of the result list could be of any event type; i.e., ObjectEvent, AggregationEvent, QuantityEvent, TransactionEvent, or any extension event type that is a subclass of EPCISEvent.

The SimpleEventQuery shall be available via both poll and subscribe; that is, an implementation shall not raise SubscribeNotPermittedException when SimpleEventQuery is specified as the queryName argument to subscribe.

The SimpleEventQuery is defined to return a set of events that matches the criteria specified in the query parameters. When returning events that were captured via the EPCIS Capture Interface, each event that is selected to be returned shall be identical to the originally captured event, subject to the provisions of authorization, the inclusion of the recordTime field, and any necessary conversions to and from an abstract internal representation. For any event field defined to hold an unordered list, however, an EPCIS implementation need not preserve the order.
   
Associations Type:  Occurrence: 
 
xsd:sequence 1 .. 1
name xsd:string 1 .. 1
Description:  If multiple parameters are specified an event must satisfy all criteria in order to be included in the result set. In other words, if each parameter is considered to be a predicate, all such predicates are implicitly conjoined as though by an AND operator. For example, if a given call to poll specifies a value for both the EQ_bizStep and EQ_disposition parameters, then an event must match one of the specified bizStep values AND match one of the specified disposition values in order to be included in the result.

On the other hand, for those parameters whose value is a list, an event must match at least one of the elements of the list in order to be included in the result set. In other
words, if each element of the list is considered to be a predicate, all such predicates for a given list are implicitly disjoined as though by an OR operator. For example, if the value of the EQ_bizStep parameter is a two element list (“bs1”, “bs2”), then an event is included if its bizStep field contains the value bs1 OR its bizStep field contains the value bs2.
value xsd:anyType 1 .. 1
 
  Date Of Publication: 01.04.2008  
  Copyright © GS1 Germany 2008. All rights reserved Optimised for 1024 x 768 pixel