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] Aasx2AspectModel ECLASS now has a defined URI representation of IRDIs #596

Open
BirgitBoss opened this issue Jun 18, 2024 · 0 comments
Labels
acknowledged Has been viewed by one of the maintainers and is ready for further work, discussion or other steps. task

Comments

@BirgitBoss
Copy link
Contributor

BirgitBoss commented Jun 18, 2024

Is your task related to a problem? Please describe.
The AAS allows IRDI as values for ConceptDescription/id and HasSemantics/semanticId etc.
In Catena-X a proprietary translation was defined, soemthing like "urn:irdi:0173-1-01-AAC063-019" and used in the "see" attribute
Now at least ECLASS defined a URI representation:

https://eclass.eu/fileadmin/Redaktion/pdf-Dateien/Wiki/ECLASS-Technical-Specification-110_RDF_Spec_Part_1_V1.0.0.pdf
Chapter 4.4 IRDI as URIs

Example:
For instance, the IRDI 0173-1#01-AAC063#019 is converted into 0173-1-01-AAC063-019.
The “Temperature transmitter” Classification Class with IRDI 0173-1#01-AAC063#022 in ECLASS
14.0 would have the following URI:
◼ https://eclass-cdp.com/rdf/v1/eclass14-0/0173-1-01-AAC063-022
◼ eclass14-0:0173-1-01-AAC063-022.

Describe the solution you'd like
If the SMT contains an IRDI starting with "0173" then use the URI representation as defined by ECLASS instead.

@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 Jun 21, 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. task
Projects
None yet
Development

No branches or pull requests

2 participants