Incorporate support for new fields

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

Incorporate support for new fields #81

Closed dakbhavesh closed 1 year ago

dakbhavesh commented 1 year ago

incorporated support for the following fields

certificationInfo
sensorReport (exception, time, component, coordinateReferenceSystem)

This PR addresses issues #75 & #78

FYI: @RalphTro , @Echsecutor

dakbhavesh commented 1 year ago

Thanks, @RalphTro for reviewing. Can you check your new example against the branch for which I created a PR.

PR Link: https://github.com/RalphTro/epcis-event-hash-generator/pull/82

In this, I have fixed the type ordering and some other issues. Hopefully, you may see the expected result

FYI: @Echsecutor, @ShaikDayan

dakbhavesh commented 1 year ago

Dear @RalphTro, I found the issue in your new files. The second occurrence of sensorElementList happens when we have user extension elements inside sensor metadata or sensor report. I will try to have a look at the issue.