-
Notifications
You must be signed in to change notification settings - Fork 38
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
Implement proper versioning in ids namespaces #570
Comments
FYI: If we update the base-URI in line 7 to include a version number, we must also do this for the base-prefix in line 1. |
@sebplorenz for the implementation of versioning in the ontology we followed the best practices according to this guideline Could you please indicate me what do you think about this approach? Or do you think we still need to include the |
@lcomet I'm not an ontology expert, but I thought that this
should be
Shouldn't it? |
@sebplorenz Thank you for your reply. @JohannesLipp Do you have any comments about this issue? The problem here, I think, is that in the different components of the ontology, e.g. Participant.ttl has no information about the specific version. That information is in resulting the Ontology after importing all the components of the model, i.e https://github.com/International-Data-Spaces-Association/InformationModel/blob/develop/Ontology.ttl, and which is independent of the documentation. |
OK. That means, as a "user" of the Infomodel I create an SD of a Participant (with the latest changes), with a reference
in my participant SD, right? |
After a discussion with @PHochmann and @clange , we agreed on the following:
|
The correct version number is often missing for ids or idsc namespace in the .ttl files.
E.g. the Participant.ttl has been changed several times recently but still refers to the default namespace, as can be seen here:
InformationModel/model/participant/Participant.ttl
Line 8 in 5293315
Expected behaviour: a specific version of the model should be referenced in the namespace of the .ttl files when they are updated.
The text was updated successfully, but these errors were encountered: