Skip to content
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

XSD datatype version mismatch #395

Open
g1zzm0 opened this issue Apr 10, 2024 · 2 comments
Open

XSD datatype version mismatch #395

g1zzm0 opened this issue Apr 10, 2024 · 2 comments
Assignees
Labels
bug Something isn't working ready for approval TF proposes how to resolve the issue. Needs final approval my Workstream specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
Milestone

Comments

@g1zzm0
Copy link
Collaborator

g1zzm0 commented Apr 10, 2024

Describe the bug
The specified data types for the AAS of XSD Datatype Version 1.0 and the RDF data types (e.g. rdf:Langstring) of XSD Datatype Version 1.1 do not match.
RDF uses the referenced RDF 1.1 and therefore the XSD Datatypes version 1.1.
The datatypes defined for RDF 1.1 is https://www.w3.org/TR/rdf11-concepts/#xsd-datatypes and references the XSD Version 1.1 https://www.w3.org/TR/xmlschema11-2/#built-in-primitive-datatypes instead of the AAS Datatypes uses XSD Version 1.0 https://www.w3.org/TR/xmlschema-2/#built-in-primitive-datatypes

Where
Specification of Primitive and Simple Data Types in Version 3.0, 3.0.1 and 3.1

Screenshots
image

Additional context
No matter in which version RDF uses the XSD data types version 1.1

@g1zzm0 g1zzm0 added the bug Something isn't working label Apr 10, 2024
@BirgitBoss BirgitBoss added the specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally label Apr 12, 2024
@BirgitBoss
Copy link
Collaborator

So far the only datatype Part 1 is using from RDF is langString, all other types from RDF are not used in the metamodel.

So from metamodel point of view we need to have a look at string and AASd-130. If the string definition in XML Schema 1.0 and 1.1 differs then we need to decide whether MultiLanguageProperties have a different string constraint than "normal" Properties with type xs:string.

The impact on the serialization formats, especially RDF is not clear to me.

@BirgitBoss BirgitBoss added this to the V3.0.1 milestone Apr 12, 2024
@sebbader-sap
Copy link
Contributor

  1. RDF 1.1 references XML Schema Part 2 - Datatypes Version 1.1, indeed.
  2. However, this has no effect on the AAS RDF serialisation, and is completely unrelated to the decision that AAS relies on XML Schema version 1.0. The AAS RDF serialisation only uses the native RDF datatypes xs:string, xs:boolean, and xs:base64byte, which are already in XML Schema Part 2 - Datatypes Version 1.0

So I think we face a pretty complex situation but have a pretty easy solution: Current state is fine, no changes needed :-).

@BirgitBoss BirgitBoss added the ready for approval TF proposes how to resolve the issue. Needs final approval my Workstream label May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ready for approval TF proposes how to resolve the issue. Needs final approval my Workstream specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
Projects
None yet
Development

No branches or pull requests

3 participants