-
since the inclusion of the dl normalisation, the hashing generator depends on the gtin package which pulls in quite a few more dependencies, one of them being deprecated.
Upgrading the gtin package…
-
@RalphTro @Echsecutor
Hello,
We came across a scenario where Hash-id generated for XML event and its converted JSON/JSON-LD event is different so we wanted to confirm if it needs to be the same…
-
Dear @RalphTro
Hope you are doing great and having nice summer :)
We have a quick question regarding the order of elements for User-Extensions while creating the pre-hash string.
Just for e…
-
Hi,
First of all, thanks a lot for you open source implementation. It is super useful.
I tested your algorithm, and compared it to ours (https://github.com/evrythng/epcis2.js#generating-a-hashed-…
-
In the sensor report xml version, there seems to be different versions of `gs1` namespaces.
For example in
```
```
the component prefix `gs1` should be expanded to `xmlns:gs1="https://ref.gs1…
-
I have suddenly realized what "traceability" means in this context.
What needs are not satisfied by the existing [PROV-O (Provenance Ontology and related documents)](https://www.w3.org/TR/prov-over…
-
Dear @Aravinda93 ,
Please add support for the field '`certificationInfo`'. The latter is applicable for all EPCIS event types (see EPCIS 2.0, section 7.4.1) and expects a URI.
In the Create Tes…
-
Dear @Echsecutor ,
I just found an interesting case (in branch bare_string_normalisation', where bare strings are *not* expanded to their full URI.
In addition, 'ObjectEvent' is not appended af…
-
Hi,
I compared again the outputs of our algorithms and I think you forgot a few rules that are listed in the official algorithm (in the cbv standard).
For example, you don't order pre-hash strin…
-