Conversion between JSON and XML fields #207
Replies: 1 comment
-
Nevermind, I just had to look at the example XML files...
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The introduction of EPCIS 2.0 adds a new JSON format for EPCIS events, alongside with the existing XML format.
There is one point that needs clarification. This JSON is valid according to GS1:
However, its XML representation is not totally clear to me. The naive implementation would be something like this:
It's working, it's a valid XML document but I'm not sure this is the cleanest option to represent this value.
It should be an edge case, as such extension fields do not really make sense, but it's allowed so FasT&T should support it.
If anyone has a better idea, please let me know!
Beta Was this translation helpful? Give feedback.
All reactions