-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non-compliant XSD using matches_xs_any_uri #317
Comments
Since the PathType does not follow RFC 8089 anymore, but the `matches_xs_any_URI()` method produces non-compliant XSD (see #317), as a temporary fix to allow compliant XSD schema generation, we remove the invariant completely.
@s-heppner we actually use it in the verification function for matching XSD types. We also test it: aas-core-meta/tests/test_v3.py Line 125 in a311624
|
Can you please provide more info on the XSD schema and how you run it? XSD engines are also often broken. |
I've seen the tests, sadly I don't have time to further dig into this issue right now. This is the CI workflow in question. Here's the complete stacktrace:
|
I hope the title of #316 is not correct: the type stays str but the regEx ist changed to anyUri |
@s-heppner wrote:
The issue is with the XSD engine. It probably uses UTF-16 instead of UTF-32 to represent the strings. Hence, characters above the Basic Multilingual Plsne can not be represented. Let's sync on the phone how to proceed. |
Having an invariant with
matches_xs_any_uri()
produces non-compliant XSD schema:This comes from admin-shell-io/aas-specs#357 with commit a5b36a12.
In order to fix #316, we need a correct uri schema validation.
As a note:
matches_xs_any_uri()
has been in aas-core since v3.0RC02, however it was never used.The text was updated successfully, but these errors were encountered: