You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, the repository contains multiple serializations of the same ontology.
All but one can be removed, and instructions included on how to convert from one format to the other. Alternatively, these files could be included as assets attached to releases: https://help.github.com/en/github/administering-a-repository/creating-releases
The text was updated successfully, but these errors were encountered:
I would propose that the Publication's Office publishes this ontology, just like other models, schemas, ontologies and and authority lists. This way it will be accesible in Cellar with dereferenceable URIs.
To do so, when the time is right and the release is ready on github, simply send a request to this functional mailbox: [email protected] .
Well, we have the data.europa.eu/yfw reserved for use by this ontology, so we have a bit of flexibility on the place it gets published. While I agree that it should be dereferenceable, my main worry here is that is no longer clear what is the canonical version.
I would like to go to 1 file containing all information without duplication. Other representation should be derived from this file.
that is very good. I would advise on using the namespace in a way that it can be extended in the future for example by adding a segment or two to point to the ontology: "data.europa.eu/yfw/segment1/segment2#"
At the moment, the repository contains multiple serializations of the same ontology.
All but one can be removed, and instructions included on how to convert from one format to the other. Alternatively, these files could be included as assets attached to releases:
https://help.github.com/en/github/administering-a-repository/creating-releases
The text was updated successfully, but these errors were encountered: