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

Keep ontology and profile URLs stable #57

Open
VladimirAlexiev opened this issue Sep 15, 2024 · 2 comments
Open

Keep ontology and profile URLs stable #57

VladimirAlexiev opened this issue Sep 15, 2024 · 2 comments
Assignees
Labels
urlpolicy Considerations about URL/namespace/folder/filename design/carving

Comments

@VladimirAlexiev
Copy link
Collaborator

The URLs that @griddigit-ci cited in #56
(http://cim.ucaiug.io/grid/Dynamics/1.0, http://cim.ucaiug.io/grid/StandardInterconnections/1.0)
made me think about this:

The latest version of an ontology and profile should always be available at the same URL.

  • Keeping ontology and profile URLs stable makes life much easier for ontology users (both data providers and consumers).
  • It allows data conforming to older releases to coexist peacefully with data conforming to newer releases
  • Usually ontology versions are backward compatible (i.e. the newer version extends the older version).
    • Since CIM UML is developed through a rigorous process, I hope that the meaning of terms doesn't change between releases (is this true?)
    • You should never delete terms: only mark them owl:deprecated.
  • An ontology should also have a versioned URL and we should keep and publish older versions:
    but instance data is recommended to use un-versioned URLs.
@VladimirAlexiev VladimirAlexiev added the urlpolicy Considerations about URL/namespace/folder/filename design/carving label Sep 15, 2024
@VladimirAlexiev
Copy link
Collaborator Author

ENTSO-E document RDF-Syntax User Guide v1.0 (2024-01-17) section 3. "Combining different CIM versions" describes difficulties related to exchange of semantic data that uses versioned terms, and concludes:

Starting with CIM18, the CIM international standard development community agreed to keep the URI of the canonical CIM stable between different versions of CIM. This means that if a class is defined in CIM vocabulary its URI will not change. Semantic versioning is applied on profile level and different packages in CIM in order to be able to describe and explain CIM evolution.

@Sveino
Copy link
Owner

Sveino commented Sep 17, 2024

Yes, after a lot of work we managed to get the community to agree to use persistent URLs. We are now in the very difficult transition period. We also need to manged to implement solution that support that the URL should without version resolves to the current version. We would also need to implement support for future version (alfa version) for testing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
urlpolicy Considerations about URL/namespace/folder/filename design/carving
Projects
None yet
Development

No branches or pull requests

2 participants