ALGORITHM and SOFTWARE PROTOTYPE to uniquely identify/validate the integrity of any EPCIS event through a common, syntax-agnostic approach based on hashing. Takes an EPCIS Document (formatted in either XML or JSON-LD) and returns the corresponding hash value(s).
(7) Quantitative values MUST NOT have trailing zeros (for instance, a quantity of one must be expressed as '1', not '1.0').
(8) All timestamps MUST be expressed in UTC. Thereby, the zero UTC offset MUST be expressed with the capital letter 'Z'.
(9) All timestamps MUST be expressed at millisecond precision. If an EPCIS event lacks the latter, it MUST be padded with zeros, i.e. YYYY-MM-DDTHH:MM:SS.000Z.
(7) Quantitative values MUST NOT have trailing zeros (for instance, a quantity of one must be expressed as '1', not '1.0').
(8) All timestamps MUST be expressed in UTC. Thereby, the zero UTC offset MUST be expressed with the capital letter 'Z'.
(9) All timestamps MUST be expressed at millisecond precision. If an EPCIS event lacks the latter, it MUST be padded with zeros, i.e. YYYY-MM-DDTHH:MM:SS.000Z.