search

RalphTro / epcis-event-hash-generator

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).
MIT License
8 stars 4 forks source link

Added XML (and its JSON/JSON-LD eq.) with CURIEs #79

Closed RalphTro closed 1 year ago

RalphTro commented 1 year ago

The xml-serialised event contains CURIEs in the bizStep, disposition and exception/type fields. The corresponding JSON/JSON-LD file expresses these values in bare string notation. In the end though, both events should arrive at the identical hash.

dakbhavesh commented 1 year ago

Dear @RalphTro, Can we please close this PR as examples are already part of the main branch?

Link to example: https://github.com/RalphTro/epcis-event-hash-generator/blob/master/tests/examples/CertificationInfoAndSensorReportWithCRS.jsonld

RalphTro commented 1 year ago

Dear @dakbhavesh , In principle, I'd agree with that, especially as to certification info (which was recently under discussion in the MSWG anyway). The only thing I would keep is an XML example with CURIEs in e.g. the bizStep field, see e.g. https://github.com/RalphTro/epcis-event-hash-generator/pull/79/commits/a4702de7181ef76f5633f4b9f6246e40e00785e3 (i.e. WITHOUT the certificatinInfo field) What do you think?