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

[Task] data types xs: or xsd: #275

Open
BirgitBoss opened this issue Nov 6, 2023 · 0 comments
Open

[Task] data types xs: or xsd: #275

BirgitBoss opened this issue Nov 6, 2023 · 0 comments
Labels
acknowledged Has been viewed by one of the maintainers and is ready for further work, discussion or other steps.

Comments

@BirgitBoss
Copy link
Contributor

Is your task related to a problem? Please describe.
Since the Asset Administration Shell is using prefix xs for xsd data types, I changed the namespace within the Movement example from
@Prefix xsd: http://www.w3.org/2001/XMLSchema#
to
@Prefix xs: http://www.w3.org/2001/XMLSchema#
and also changed all usage of xsd:

When uploading the changed file I get the following information:

SAME_Prefix_XS_XSD

However, when looking in https://eclipse-esmf.github.io/samm-specification/snapshot/namespaces.html there is no explanation that for data types the prefix xsd: shall be used.

Describe the solution you'd like
either

  • either update semantic aspect meta model documentation (as a minimum not allowed prefixes like xsd: and rdf: shall be listed besides those containing samm)
    or (preferred)
  • allow any suffix for data types as long as the value is identical to http://www.w3.org/2001/XMLSchema#
@chris-volk chris-volk transferred this issue from eclipse-esmf/esmf-aspect-model-editor Jan 11, 2024
@chris-volk chris-volk added the acknowledged Has been viewed by one of the maintainers and is ready for further work, discussion or other steps. label Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
acknowledged Has been viewed by one of the maintainers and is ready for further work, discussion or other steps.
Projects
None yet
Development

No branches or pull requests

2 participants