certificationInfo, exception, coordinateReferenceSystem

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

certificationInfo, exception, coordinateReferenceSystem #75

Closed RalphTro closed 1 year ago

RalphTro commented 1 year ago

Add these fields to the canonical property order
Prepare example(s) in .xml and .jsonld
Adjust readMe

Aravinda93 commented 1 year ago

Hi @RalphTro

We just wanted to confirm the order of these elements in the pre-hash string. Should it appear at the bottom or before extensions? If possible can you please add these elements as a part of property in the table that you have provided?

RalphTro commented 1 year ago

Hi @Aravinda93 ,

As things stand now, we most probably will insert these three fields in the property order as follows: … sensorReport (type, exception, deviceID, deviceMetadata, rawData, dataProcessingMethod, time, microorganism, chemicalSubstance, value, component, stringValue, booleanValue, hexBinaryValue, uriValue, minValue, maxValue, meanValue, sDev, percRank, percValue, uom, coordinateReferenceSystem) … …

eventTimeZoneOffset
certificationInfo
epcList – epc …

As to your question: gladly - the readMe wil be updated as part of an upcoming PR - stay tuned!

Have a nice weekend and kind regards, Ralph

Aravinda93 commented 1 year ago

Dear @RalphTro,

Thanks a lot for the confirmation on the order for these elements.

Have a nice weekend and kind regards, Aravinda

RalphTro commented 1 year ago

Sebastian/Ralph to have a look at PR 81

RalphTro commented 1 year ago

PR 81 deployed