I think the answer is yes - but need to think a bit about what the model is about. I guess it is about the instrument but the particular way it is about it needs to be written.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Maybe model number is harder to define than serial number. Whatever the result is the relation should be the same. Serial number seems to have a more clear-cut definition (according to wikipedia), so maybe we should address this prior to model number? The last time I tried to represent this in OWL I used a datatype property.
Maybe using something like "Nominal Number" which according to wikipedia are numerals used for identification only. The (alpha)numerical value is irrelevant, and they do not indicate quantity, rank, or any other measurement.[http://en.wikipedia.org/wiki/Nominal_number]. If we used this, both model_number and serial_number would be sub-classes(-properties) of Nominal number.
The following definition conflates what a serial number is with what it is used for - identification. Maybe we have to do the same as currently a string could not play the role of identifier....
Serial Number [http://en.wikipedia.org/wiki/Serial_number]
A serial number is a unique number assigned for identification which varies from its successor or predecessor by a fixed discrete integer value. Common usage has expanded the term to refer to any unique alphanumeric identifier for one of a large set of objects, however in data processing and allied fields in computer science. Not every numerical identifier is a serial number; identifying numbers which are not serial numbers are sometimes called nominal numbers.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am not sure if we need a specific relation towards each of the _identifier subclasses though. Maybe using something like model_number (subproperty of is_about) device? What about specifically_denotes?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It would be interesting to determine, if the is_about relation could handle this, or that has_model number could be a sub-property of this?
I think the answer is yes - but need to think a bit about what the model is about. I guess it is about the instrument but the particular way it is about it needs to be written.
Maybe model number is harder to define than serial number. Whatever the result is the relation should be the same. Serial number seems to have a more clear-cut definition (according to wikipedia), so maybe we should address this prior to model number? The last time I tried to represent this in OWL I used a datatype property.
Maybe using something like "Nominal Number" which according to wikipedia are numerals used for identification only. The (alpha)numerical value is irrelevant, and they do not indicate quantity, rank, or any other measurement.[http://en.wikipedia.org/wiki/Nominal_number]. If we used this, both model_number and serial_number would be sub-classes(-properties) of Nominal number.
Maybe something like
is_about
-(child)has_nominal_number
--(child)has_serial_number
--(child has_model_number
The following definition conflates what a serial number is with what it is used for - identification. Maybe we have to do the same as currently a string could not play the role of identifier....
Serial Number [http://en.wikipedia.org/wiki/Serial_number]
A serial number is a unique number assigned for identification which varies from its successor or predecessor by a fixed discrete integer value. Common usage has expanded the term to refer to any unique alphanumeric identifier for one of a large set of objects, however in data processing and allied fields in computer science. Not every numerical identifier is a serial number; identifying numbers which are not serial numbers are sometimes called nominal numbers.
Not clear yet that we should have specific relations for this or whether the information is carried by the instance of model number.
BTW, note the is_about goes from information -> thing whereas has_model_number goes from thing -> information.
Also note that serial numbers are not necessarily numbers, despite the name. They can have letters in them, or be opaque, but unique, encodings.
This is still required, domain obviously device
range would be model number (IAO_0000017)
I am not sure if we need a specific relation towards each of the _identifier subclasses though. Maybe using something like model_number (subproperty of is_about) device? What about specifically_denotes?
Discussed on July 6, 2015 call. Now have model number http://purl.obolibrary.org/obo/IAO_0000017
and generic denotes relations
http://purl.obolibrary.org/obo/IAO_0000219
Assume this is now taken care of so if don't hear back to the contrary, we will close.