For example, this could be production or assembly that results in output which is used for further production or for sale (repackaging, labeling etc). The important distinction is that the ownership of event objects does not change during the event.
visibility
property to an attribute of a VocabularyElement
in the EPCISMasterData
section. The data marked as permissioned will be visible only to the data creator and the parties the data creator marks as whitelisted via the API. More information on permissioned data is available at Vertex Data permissioningโvisibility="permissioned.show_attribute"
. Example:visibility="permissioned.hide_attribute"
. Example:
Objects - Use case entities (products, locations, vehicles, people, โฆ ) Relations - Relations between use case entities (INSTANCE_OF, BELONGS_TO, โฆ ) Metadata - Data about dataset (integrity hashes, data creator, signature, transpilation data, โฆ.)Example: Assuming that use case request is to connect products with factories there they are produced. Entities of the use case are Product and Producer. These entities are represented as objects in OT-JSON format. Product can have relation PRODUCED_BY with producer that produces it and the producer can have relation HAS_PRODUCED with the product. Product and producer have unique identifiers Product1, Producer1 respectively.
Every OT-JSON entity (Object) is identified with at least one unique identifier. An identifier is represented as a non-empty string. Entities can have multiple identifiers along with the unique one. For example: EAN13, LOT number and time of some event. Data can be connected by arbitrary relations. A user can define own relations that can be used with others defined by standard. Relations are directed from one entity to another. It is possible to create multiple relations between two objects in both directions.
Version of OT-JSON document Dataset creation timestamp Dataset title Dataset tags Related datasets Validation schemas Data validation information Data creator Transpilation information
datasetID
, which is generated as a hash of the @graph
section of the dataset, and is used to verify data integrity of the datasetrootHash
, which is generated as a hash of the @graph
section along with the dataset creator, and is used for verifying the dataset creatorsignature
, which is generated as a signed hash of the entire dataset, and is used to verify the creator and integrity of a dataset off chain.datasetID
for OT-JSON 1.1 is generated out of the @graph
section after sorting every object and array, including the the @graph
array, without changing the order of any array inside of a properties object.rootHash
for OT-JSON 1.1 is generated out of the @graph
section in the same was as it is for the datasetID
.signature
for OT-JSON 1.1 is generated out of the dataset when the datasetHeader
is attached, after sorting the dataset in the same way it was done for datasetID
and rootHash
.datasetID
for OT-JSON 1.1 is generated out of the @graph
section after sorting every object in the the @graph
array, without changing the order of any array.rootHash
for OT-JSON 1.1 is generated out of the @graph
section in the same was as it is for the datasetID
.signature
for OT-JSON 1.1 is generated out of the dataset when the datasetHeader
is attached.datasetID
for OT-JSON 1.0 is generated out of the @graph
section after sorting every object and array, including the @graph
array.rootHash
for OT-JSON 1.0 is generated out of the @graph
section after sorting the relations and identifiers of each element, and sorting the @graph
array by each array element @id
.signature
for OT-JSON 1.0 is generated out of the dataset after first sorting the relations and identifiers of each element, and sorting the @graph
array by each array element @id
, and then sorting every object in the dataset.