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 issue is that practitioners tend to use the latest and greatest for their data without regard to the fact that https://rdf.ag/o/beer#term may not return a versioned ontology term that doesn't behave in the way that they expect. Some mix of url rewriting and a series of owl:sameAs statements is going to be required to ensure that the ontology that is returned is always versioned to ensure that applications get consistent results when referencing the ontology.
Currently the versioning of the ontology terms is recorded in the url https://rdf.ag/o/beer-2024-02-16#term and the latest version is https://rdf.ag/o/beer#term.
At issue is that practitioners tend to use the latest and greatest for their data without regard to the fact that https://rdf.ag/o/beer#term may not return a versioned ontology term that doesn't behave in the way that they expect. Some mix of url rewriting and a series of owl:sameAs statements is going to be required to ensure that the ontology that is returned is always versioned to ensure that applications get consistent results when referencing the ontology.
Current work in this direction: #2
The text was updated successfully, but these errors were encountered: