XSD error 'EventListType': The content model is not determinist

[VladimirAlexiev]

I'm not much of an expert on XSD but I tried to validate one of the XML examples (slightly renamed) and got this error:

xmllint --schema ../XSD/EPCglobal-epcis-2_0.xsd Example-TransactionEvents-2020_07_03y.xml
complex type 'EventListType': The content model is not determinist.
WXS schema ../XSD/EPCglobal-epcis-2_0.xsd failed to compile

@CraigRe @RalphTro who's our XSD expert?

Loosely related to #279

[sboeckelmann]

I am volunteering to look into XSD issues and offer support.

[CraigRe]

Needs eyeballing and validation checks by @CraigRe @mgh128 @sboeckelmann and @RalphTro .
Make sure to validate all example files against schema prior to CommRev, @VladimirAlexiev recommends using a makefile script to see the source of validation errors at a glance.

@sboeckelmann will also ask @RalphTro if we can run existing (1.x) production data against 2.0 schema, to make sure we are not adding backward incompatibility.

[sboeckelmann]

@RalphTro, @CraigRe, @mgh128
please check #283

This should be addressing the most pressuring issues with validation.
I will have another look at the XSDs and try to get clearance for checking against existing production data within the next couple of days.

[CraigRe]

Linked to #283

[VladimirAlexiev]

At the Jun 15 telco:

• there is hope Issues/286 #295 (removal of nested extension envelopes) will alleviate this
• @shalika-singh (@shalikasingh) said we shouldn't worry too much and should accept non-determinism in the XSD, because that's only a problem in xmllint but not in other commonly used XSD validators. Shalika, please elaborate and correct this if I misstated.

[shalikasingh]

Hi @VladimirAlexiev,

Its right that xmllint has a limitation of not being able to parse non-deterministic XSD, whereas using API of javax.xml.validation.*, I was able to parse non-deterministic EPCIS XSD and validate events against it.

Fortunately, we don't have to worry about the non-deterministic behavior of XSD anymore as the modified version of XSD submitted by @sboeckelmann as PR: #295 is a deterministic one.

[mgh128]

Thanks to updated XSD from Sven (PR #303 ), I think this issue can now be closed.

[sboeckelmann]

I have update the XSL/README a bit - but it’s still work in progress. Sorry, but I won’t be able to finish it up before today’s call. Just to notify and provide a quick preview: https://github.com/sboeckelmann/EPCIS/tree/master/XSL#readme In my opinion, it might be useful to give some hints for different programming languages. What do you think?

…

Am 08.11.2021 um 21:15 schrieb Mark Harrison ***@***.***>: Thanks to updated XSD from Sven (PR #303 <#303> ), I think this issue can now be closed. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#280 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE72UTSLVDQYXMFPIAUN7JDULAVUZANCNFSM45COAOWA>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[mgh128]

Hi Sven, Thanks for making further updates. I agree that it's a very good idea to provide guidance about how to use this in various programming languages, I'm also suggesting that we extend the introduction section to EPCIS to explain the new features, data formats, interfaces, etc. and have prepared three diagrams to help explain these. One of these includes your XSLT transformation to bridge the gap between XML and JSON/JSON-LD - and I hope that this extended intro section can then refer to the availability of the helpful XSLT artefact you have contributed. Best wishes Mark

…

On Tue, Nov 9, 2021 at 12:42 PM sboeckelmann ***@***.***> wrote: I have update the XSL/README a bit - but it’s still work in progress. Sorry, but I won’t be able to finish it up before today’s call. Just to notify and provide a quick preview: https://github.com/sboeckelmann/EPCIS/tree/master/XSL#readme In my opinion, it might be useful to give some hints for different programming languages. What do you think? > Am 08.11.2021 um 21:15 schrieb Mark Harrison ***@***.***>: > > > Thanks to updated XSD from Sven (PR #303 < #303> ), I think this issue can now be closed. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub < #280 (comment)>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AE72UTSLVDQYXMFPIAUN7JDULAVUZANCNFSM45COAOWA >. > Triage notifications on the go with GitHub Mobile for iOS < https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android < https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#280 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSXRL5I7T4QMNUIKGKJWC3ULEJJRANCNFSM45COAOWA> .