...
- Answer to Q1 is kind or type
- Answer to Q2 is yes, there are different properties that you care about for the purpose of the ontology?
- Answer to Q3 is yes, same people governing
- Answer to Q4 is no, the bucket will be subject or object in a triple
- Answer to Q5 is: no, just a few
...
- Answer to Q1 is descriptive attribute
- Answer t oQ2 is, no, properties are mostly the same
- Answer to Q3 is no, different people will be governing
- Answer to Q4 is yes, the bucket will be subject or object in a triple
- Answer to Q5 is: yes, lots of Buckets in a single Classifier.
Take an example in healthcare:
- you an think of it as a kind or type of condition
- there probably are different properties for different diseases, but that will not be needed for healthcare delivery, it would matter more in a scientific context studying diseases.
- the people building a healthcare delivery ontology will not be governing the set of diseases out there.
- a disease will probably be used as a code in a diagnosis field.
- there are (tens of?) thousands of diseases out there.
Of course there are gray areas, and some criteria are more important that others.
...
We link the two in this way. We make CarLoan equivalent to the restriction: [isClassifiedBy value loan:_LoanReason_Car] in Manchester Syntax. Of course, this is not ideal for two reasons.
- we are representing the same information in two different ways (mostly to avoid OWL Full)
- hasValue restrictions cause inference delays during ontology development
Ideally, you don't have to do it both ways, and you can deprecate the URIs used for the other way.
...