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

Document pattern deviation from specification #433

Merged
merged 2 commits into from
Nov 15, 2024

Conversation

s-heppner
Copy link
Collaborator

We document in the JSON and RDF schema README
files, that we deviate from the pattern in the
specification of AASd-130, due to the fact that
most schema engines test UTF-16, instead
of the used UTF-32.

For the full discussion, refer to #362

We document in the JSON and RDF schema `README`
files, that we deviate from the pattern in the
specification of AASd-130, due to the fact that
most schema engines test UTF-16, instead
of the used UTF-32.

For the full discussion, refer to #362
@s-heppner s-heppner marked this pull request as draft May 23, 2024 11:10
@s-heppner s-heppner marked this pull request as ready for review May 23, 2024 12:12
@BirgitBoss BirgitBoss requested review from BirgitBoss and mristin May 31, 2024 06:44
Copy link
Collaborator

@mristin mristin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wrote a bit longer explanation to avoid future confusion.

schemas/json/README.md Outdated Show resolved Hide resolved
Comment on lines +78 to +80
Since most RDFS engines we tested operated on UTF-16 and could not handle UTF-32, we transpiled the pattern from AASd-130, which uses UTF-32 in the specification, into UTF-16.
This is a trade-off between correctness and practicality.
See [#362](https://github.com/admin-shell-io/aas-specs/issues/362) for the details.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think that RDFS engines allow for arbitrary test to be encoded. Actually, I imagine that XML strings are used to encode text by default, so AASd-130 is meaningless (all text must conform to XML text to be ingested in RDF in the first place).

@sebbader-sap can you please have a look at this point?

@BirgitBoss BirgitBoss added the Schemas generated schemata for xml, JSON and rdf or XMI label Jun 14, 2024
@BirgitBoss BirgitBoss requested a review from sebbader-sap June 14, 2024 16:23
@s-heppner s-heppner merged commit ea938a5 into master Nov 15, 2024
2 checks passed
@s-heppner s-heppner deleted the SeHe/IDTA-01001-3-0-1_documentation branch November 15, 2024 08:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Schemas generated schemata for xml, JSON and rdf or XMI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants