-
Notifications
You must be signed in to change notification settings - Fork 5
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
reference previous version (owl:priorVersion) #91
Comments
@graybeal comments? |
I kinda have an issue with this one... why? Because I feel it it down to the author to explicitly define the |
You may be right to want to drop this, but I don't find your arguments compelling, because it isn't the user creating the new ontology, it's COR. The user does a bunch of things with COR's UI and poof! an ontology comes out the other side. The user typically has no idea what an ontology is, what semantic versioning is, what it means to skip a version, or when "versioning" even started. But the COR system knows all those things. COR provides a nice interface that let's the user do things. If it references the previous version, it could let the user and others do more things later, like track changes over time and see the history of the entity back to its creation. All of it automatically, without the user having to manually remember and appropriately make the appropriate changes (which will hardly ever happen, let alone happen consistently. So it's trying to make the ontology into a maore FAIR artifact, with actual provenance. But we've come a long way from COR's original vision, almost entirely changes for the good. I'll have to build my fortune for a long time before I can make it into the strange beast I had originally envisioned. ;-) |
In old system: mmisw/mmiorr#381
The text was updated successfully, but these errors were encountered: