-
Notifications
You must be signed in to change notification settings - Fork 13
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
Provide URIs for units as datatypes #29
Comments
@cmungall if I understand correctly, the current use of UO that has the same purl be both the class and the instance of the class is "punning", and it might not necessarily be the best practice to do this? I'm curious about the reasons for this if you don't mind explaining a bit more why it might be stranger or non-desirable.
As far as I'm aware OM, OBOE and especially QUDT are the best available other units semantic resources it would be great to sync/map with them at some point. Are you suggesting that the instances of UO classes could or should be QUDT terms (or are they properties) or equivalent to them in some way? |
Correct, this is one form of punning
it's perfectly logically valid. However, it is confusing for users. Some tooling may not explicitly take account of this. Or it may complicate the use of some tooling. See: Note also that neither OLS nor OntoBee show the axiomatization the makes each class equivalent to an enumeration of a single individual: This is not necessarily bad, the browsers show the intuitive class-only view or the URI, but this itself could potentially lead to confusing as the punning and axiomatization is opaque My proposal potentially makes things more confusing by additionally punning with datatypes. Over on the linked COB ticket we discuss the pros and cons of this model. This is not straightforward and would be good to get @leechuck @jamesaoverton and others thoughts on this and arrive at something we can all agree on
My thoughts on this are here: |
we are exploring a has-quantity property that links a characteristic instance to a literal of the form "NUMBER"^^UNIT_DATATYPE
here is an example:
This leads the owlapi to induce:
I don't know if punning class vs datatype is allowed but it's kinda weird
OBOFoundry/COB#35
cc @jamesaoverton
The text was updated successfully, but these errors were encountered: