-
Notifications
You must be signed in to change notification settings - Fork 28
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
adapter.xml: Update XSD to v3.0 #161
Conversation
This commit remanes `valueDataType_t` from the XSD to `valueDataType`. Furthermore, it adds a missing `<reference>` tag around the `refersTo` References of `Extension`.
The current order of the elements in `SubmodelElementList` was wrong. This updates the order.
Version 3.0 of the spec removes the attribute `kind` from `SubmodelElement`s. While we already implemented this, it was still missing in the XSD Schema, as well as the examples. This commit fixes that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aside the comment to the Extension
serialization, this also currently doesn't adjust the XML deserialization for Extension.refers_to
. This went unnoticed because Extensions aren't compared by the AASDataChecker
, hence also my message on Zulip. Maybe the AASDataChecker
should compare Extensions so we can properly test our SDK?
Currently, the XML deserialization missed the `<aas:refersTo>` wrapper around the single references inside `Extension.refers_to`. This commit fixes that.
97439a8
to
6071934
Compare
The deserialization is fixed in 6071934 |
346522e
to
58f4597
Compare
Currently, `Extension.refers_to` is declared as a `Iterable[Reference]`. This implies, that we can not necessarily check, whether or not the attribute is empty or not. This creates a problem with the XML serialization, since the `<aas.refersTo>` element should only appear if there is at least one `Reference` inside. This commit changes the `Extension.refers_to` to be a set of `Reference`s, as well as adapting a more clear check whether or not the attribute is empty in `adapter.xml.xml_serialization`.
58f4597
to
daa770f
Compare
LGTM 👍 |
This implements the missing changes to the XSD schema from the specification v3.0.
However, as noted in #72, we did not include the regex patterns for the
File
.Since this is quite a lot, I suggest looking at the single commits for the review.