Consider readPoint/bizLocation "id" attribute in JSON/JSON-LD

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

Consider readPoint/bizLocation "id" attribute in JSON/JSON-LD #24

Closed RalphTro closed 4 years ago

RalphTro commented 4 years ago

As of the latest discussion in the EPCIS/CBV 2.0 group, readPoint/bizLocation ID, when expressed in JSON/JSON-LD, now looks as follows: "readPoint": {"id": "urn:epc:id:sgln:0614141.07346.1234"},

Previously, we envisioned the following data structure: "readPoint": "urn:epc:id:sgln:0614141.07346.1234",

ToDo: check/adjust algorithm

Echsecutor commented 4 years ago

AFAIK all emxamples are already in

        "readPoint": {"id": "urn:epc:id:sgln:4012345.00011.987"},

format and all tests are green. -> anything todo?

Echsecutor commented 4 years ago

ah, I found an old version in expected_equal/ReferenceEventHashAlgorithm.json and adapted this one. tests still green ;)

RalphTro commented 4 years ago

If the addition of the 'id' attribute in *.jsonld formatted events still yields the same hash values, that's great! No more todo then... thanks!