|
Description: |
The Action field of a TransactionEvent describes the events 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 theres 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. |
|
|