| untp-dte: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. |
| untp-dte:AssociationEvent | The association event represents the assembly of child sub-components to create a parent assembled item. For example a desktop computer assembled from power supply, hard drive, and motherboard. The association event is very similar in structure to the aggregation event but is used for physical assembly. An association event may represent a bill of materials used to assemble a product whilst an aggregation event may represent a packing list or items for transport. |
| untp-dte:bizStepCode | BusinessStep is a vocabulary whose elements denote steps in business processes. An example is an identifier that denotes “shipping.” The business step field of an event specifies the business context of an event: what business process step was taking place that caused the event to be captured? |
| untp-dte:DigitalTraceabilityEvent | An array of Traceability Events as a VC |
| untp-dte:dispositionCode | Disposition code is a vocabulary whose elements denote a business state of an object. An example is a code that denotes “recalled". The disposition field of an event specifies the business condition of the events objects, subsequent to the event. The disposition is assumed to hold true until another event indicates a change of disposition. Intervening events that do not specify a disposition field have no effect on the presumed disposition of the object. |
| untp-dte:documentTypeCode | Document type codes for trade and logistics documents supporting the event such as purchase order, invoice, shipping notification, bill of lading, etc. |
| untp-dte: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 representing all common properties of an EPCIS event. |
| untp-dte:Item | A specific serialised trade item which is an instance of a more generic product. |
| untp-dte: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 physical 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) |
| untp-dte:QuantityElement | The quantity element is used to define the quantity (eg 100 kg of a product class. Used when serialised items are not applicable. |
| untp-dte:RenderTemplate2024 | A single template format focused render method--where the content/media type decision becomes secondary (and is expressed separately).See https://github.com/w3c-ccg/vc-render-method/issues/9 |
| untp-dte:Sensor | A physical sensor that records a sensor data set. |
| untp-dte:SensorData | A data point read by a sensor. |
| untp-dte:SensorElement | A SensorElement is used to carry data related to an event that is captured one sensor such as an IoT device. Include one sensor property and an array of sensor data values. |
| untp-dte: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. |
| untp-dte: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. |
| untp-dte:UOM | UNECE Recommendation 20 Unit of Measure code list. |
| untp-dte:WebRenderingTemplate2022 | A simple (though non-standard) embedded template. |
