Traceable Resource Definitions

The TRD allows for domain specific additions to the event model.

Entity types

The Traceable Resource Definitions (TRD) defines types of traceable objects. Any number of types may be created from three basal traceable entity types: Batch,TradeUnit and TradeUnitCluster.

  • Batch is intended to be used for modelling production stages.
  • TradeUnit can be sent between parties and is often used to model finished products or raw materials.
  • TradeUnitCluster is used to model aggregated trade units or aggregates of other trade unit clusters.

From these any number of entity types can be created. How many are needed depends on the wanted level of detail.

A simple model might have one type to model incoming raw material, one type to model the production and one type to model outgoing finished products. A more detailed model will have different types for different raw materials have multiple production steps and differentiated finished products. More types will allow more detailed models and will allow for richer third party applications.

Property types

A property is a named value attached to a traceable entity. It may be a text, date, datetime, a geolocation or a numeric value. Numeric values may also have a unit of measurement.

Extensions on Observe events will become properties on the EPCs in the event.

Localization

TRD labels and descriptions may be localized through the use of the <Text> element’s xml:lang=“xx” attribute. Any number of localized labels and descriptions may be added to the TRD, PropertyTypes and Batch/TradeUnitTypes.

When attempting to localize EntityDetails the user’s language will be used to pick the appropriate label or description. If no translation in that language exists, the system will try to show an English label. If no English label exists then the XML name of the element will be used instead.

See example TRD document.