| traceabilityEvents:ActionCode | |
| traceabilityEvents:AggregationEvent | Aggregation represents an event that happened to one or more objects that are physically aggregated together (physically constrained to be in the same place at the same time, as when cases are aggregated to a pallet). This event is also used to represent de-aggregation (eg unpacking) when businessStepCode is unpacking. |
| traceabilityEvents:BusinessPartner | The contant details of the party - used for counter party verification callbacks. |
| traceabilityEvents:BusinessStepCode | |
| traceabilityEvents:CertificationInfo | Details of a self asssessed or independently verified set of sustainability claims about a product or an establishment. |
| traceabilityEvents:DispositionCode | |
| traceabilityEvents:Document | A Secure binary document store. |
| traceabilityEvents:DocumentTypeCode | |
| traceabilityEvents:Event | This abstract event structure provides a common language to describe supply chain events such as shipments, inspections, manufacturing processes, etc. There are four types of EPCIS event but this is an abstract class represenitng all common properties of an EPCIS event. |
| traceabilityEvents:Item | A specific trade item /product code which could be either a product serial number or a consignment identifier |
| traceabilityEvents:ObjectEvent | Object represents an event that happened to one or more physical or digital objects - such as an inspection or certification of a product or shipment. The physucal objects may be identified either as specific items (eg a unique consignment number) or as a quantified amount of a product class (eg 100Kg of cotton yarn) |
| traceabilityEvents:Party | A trade party |
| traceabilityEvents:QuantityElement | The quantity elment is used to define the quantities (eg 100), units of measure (eg Kg) and product class (eg GTIN or other class identifier) of products that are inputs or outputs or the subject of supply chain events. |
| traceabilityEvents:TradeTransaction | A trade transaction between two parties such as an invoice, purchase order, or shipping notificaiotn. |
| traceabilityEvents:TransactionEvent | Transaction represents an event in which one or more objects become associated or disassociated with one or more identified business transactions - such as the purchase / shipment of goods between buyer and seller. |
| traceabilityEvents:TransformationEvent | Transformation represents an event in which input objects are fully or partially consumed and output objects are produced, such that any of the input objects may have contributed to all of the output objects - for example consuming bales of cotton to produce yarn. |
| traceabilityEvents:VerificationCallback | Data structure for a call-back verification service. consumer provides an event structre to be verified, service returns that structure for the same event as known to the verifier together with a uniqu verificationID, date time stamp, and outcome |
| traceabilityEvents:VerificationOutcome | |
| traceabilityEvents:verificationRole | |
