| |
|
|
Associations |
|
Type: |
|
Occurrence: |
|
|
|
xsd:choice |
|
|
0 |
.. |
unbounded |
|
|
|
|
Description: |
Retrospective semantics:
• An event described by bizStep (and any other fields) took place with respect to each EPC in epcList at eventTime at location readPoint.
• (If action is ADD) The EPCs in epcList were commissioned (issued for the first time).
• (If action is DELETE) The EPCs in epcList were decommissioned (retired from future use).
• (If action is ADD and a non-empty bizTransactionList is specified) An association exists between the business transactions enumerated in bizTransactionList and the EPCs in epcList.
• (If action is OBSERVE and a non-empty bizTransactionList is specified) This event took place within the context of the business transactions enumerated in bizTransactionList.
• (If action is DELETE and a non-empty bizTransactionList is specified) This event took place within the context of the business transactions enumerated in bizTransactionList.
Prospective semantics:
• (If action is ADD) The EPCs in epcList may appear in subsequent events.
• (If action is DELETE) The EPCs in epcList should not appear in subsequent events.
• (If disposition is specified) The business condition of the objects associated with the EPCs in epcList is as described by disposition.
• (If disposition is omitted) The business condition of the objects associated with the EPCs in epcList is unchanged.
• (If bizLocation is specified) The physical objects associated with the EPCs in epcList are at business location bizLocation.
• (If bizLocation is omitted) The business location of the physical objects associated with the EPCs in epcList is unknown.
• (If action is ADD and a non-empty bizTransactionList is specified) An association exists between the business transactions enumerated in bizTransactionList and the EPCs in epcList. |
|
|
|
|
|
Description: |
The Action field of an AggregationEvent describes the event’s relationship to the lifecycle of the aggregation. Specifically:
ADD - The EPCs named in the child list have been aggregated to the parent during this event. This includes situations where the aggregation is created for the first time, as well as when new children are added to an existing aggregate.
OBSERVE - The event represents neither adding nor removing children from the aggregation. The observation may be incomplete: there may be children that are part of the aggregation but not observed during this event and therefore not included in the childEPCs field of the AggregationEvent; likewise, the parent identity may not be observed or known during this event and therefore the parentID field be omitted from the AggregationEvent.
DELETE - The EPCs named in the child list have been disaggregated from the parent during this event. This includes situations where a subset of children are removed from the aggregation, as well as when the entire aggregation is dismantled. The list of child EPCs may be omitted from the AggregationEvent, which means that all children have been disaggregated. (This permits dissaggregation when the event capture software does not know the identities of all the children.)
Retrospective semantics:
• An event described by bizStep (and any other fields) took place involving containing entity parentID and the contained EPCs in childEPCs, at eventTime and location readPoint.
• (If action is ADD) The EPCs in childEPCs were aggregated to containing entity parentID.
• (If action is DELETE and childEPCs is non-empty) The EPCs in childEPCs were disaggregated from parentID.
• (If action is DELETE and childEPCs is empty) All contained EPCs have been disaggregated from containing entity parentID.
• (If action is ADD and a non-empty bizTransactionList is specified) An association exists between the business transactions enumerated in bizTransactionList, the EPCs in childEPCs, and containing entity parentID.
• (If action is OBSERVE and a non-empty bizTransactionList is specified) This event took place within the context of the business transactions enumerated in bizTransactionList.
• (If action is DELETE and a non-empty bizTransactionList is specified) This event took place within the context of the business transactions enumerated in bizTransactionList.
Prospective semantics:
• (If action is ADD) An aggregation exists between containing entity parentID and the contained EPCs in childEPCs.
• (If action is DELETE and childEPCs is non-empty) An aggregation no longer exists between containing entity parentID and the contained EPCs in childEPCs.
• (If action is DELETE and childEPCs is empty) An aggregation no longer exists between containing entity parentID and any contained EPCs.
• (If disposition is specified) The business condition of the objects associated with the EPCs in parentID and childEPCs is as described by disposition.
• (If disposition is omitted) The business condition of the objects associated with the EPCs in parentID and childEPCs is unchanged.
• (If bizLocation is specified) The physical objects associated with the EPCs in parentID and childEPCs are at business location bizLocation.
• (If bizLocation is omitted) The business location of the physical objects associated with the EPCs in parentID and childEPCs is unknown.
• (If action is ADD and a non-empty bizTransactionList is specified) An association exists between the business transactions enumerated in bizTransactionList, the EPCs in childEPCs, and containing entity parentID (if specified). |
|
|
|
|
|
Description: |
Quantity Event captures an event that takes place with respect to a specified quantity of object class. |
|
|
|
|
|
Description: |
The Action field of a TransactionEvent describes the event’s relationship to the lifecycle of the transaction. Specifically:
ADD - The EPCs named in the event have been associated to the business transaction(s) during this event. This includes situations where the transaction(s) is created for the first time, as well as when new EPCs are added to an existing transaction(s).
OBSERVE - The EPCs named in the event have been confirmed as continuing to be associated to the business transaction(s) during this event.
A TransactionEvent with action OBSERVE is quite similar to an ObjectEvent that includes a non-empty bizTransactionList field. When an end user group agrees to use both kinds of events, the group should
clearly define when each should be used. An example where a TransactionEvent with action OBSERVE might be appropriate is an international shipment with transaction ID xxx moving through a port, and there’s a desire to record the EPCs that were observed at that point in handling that transaction.
Subsequent queries will concentrate on querying the transaction ID to find the EPCs, not on the EPCs to find the transaction ID.
DELETE The EPCs named in the event have been disassociated from the business transaction(s) during this event. This includes situations where a subset of EPCs are disassociated from the business
transaction(s), as well as when the entire business transaction(s) has ended. As a convenience, the list of EPCs may be omitted from the TransactionEvent, which means that all EPCs have been
disassociated.
Retrospective semantics:
• An event described by bizStep (and any other fields) took place involving the business transactions enumerated in bizTransactionList, the EPCs in epcList, and containing entity parentID (if specified), at eventTime and location readPoint.
• (If action is ADD) The EPCs in epcList and containing entity parentID (if specified) were associated to the business transactions enumerated in bizTransactionList.
• (If action is DELETE and epcList is non-empty) The EPCs in epcList and containing entity parentID (if specified) were disassociated from the business transactions enumerated in bizTransactionList.
• (If action is DELETE, epcList is empty, and parentID is omitted) All EPCs have been disassociated from the business transactions enumerated in bizTransactionList.
Prospective semantics:
• (If action is ADD) An association exists between the business transactions enumerated in bizTransactionList, the EPCs in epcList, and containing entity parentID (if specified).
• (If action is DELETE and epcList is non-empty) An association no longer exists between the business transactions enumerated in bizTransactionList, the EPCs in epcList, and containing entity parentID (if specified).
• (If action is DELETE, epcList is empty, and parentID is omitted) An association no longer exists between the business transactions enumerated in bizTransactionList and any EPCs.
• (If disposition is specified) The business condition of the objects associated with the EPCs in epcList and containing entity parentID (if specified) is as described by disposition.
• (If disposition is omitted) The business condition of the objects associated with the EPCs in epcList and containing entity parentID (if specified) is unchanged.
• (If bizLocation is specified) The physical objects associated with the EPCs in epcList and containing entity parentID (if specified) are at business location bizLocation.
• (If bizLocation is omitted) The business location of the physical objects associated with the EPCs in epcList and containing entity parentID (if specified) is unknown. |
|
|
|
extension |
epcis:EPCISEventListExtensionType |
|
1 |
.. |
1 |
|
|
|
