OWL, how can I find out if something should be a class or an instance?

I am trying to build an ontology to represent properties (assets), the property must have a type, such as a villa or apartment ...

My question is that I do not know if villas and apartments should be occupations or authorities. How can I know ?

I mean a class called Propertyand a relation called isTypeOf, and a class called PropertyTypethat has two instances of apartmentand villa. is this correct please? or should I do apartmentand villahow are classes that are a subclass of a class PropertyType?

+4
source share
2 answers

I think you combine two differences here, which you can argue separately:

  • When should a subclass be used and when should property references be used?
  • When should discrimination be presented at the TBox level (subclasses) and when at the ABox level (property values, instances)?

(1) more or less coincides with the old question inheritance or delegation. And the answers are also more or less the same: use inheritance when discrimination is an integral property of the objects represented, when this discrimination property is central to your knowledge model and when the discrimination property does not have an independent reason for existence.

, , / "" (.. ). : , PropertyType, PropertyType, Property. , " ", , .

(2) .

:

  • , , , , , ( LuxuryApartment Garden, Villa ..).
  • , , , , . , .
  • , , , , .

, , .

-

Apartment Villa , , . , , Property, Villa, :

(∃ hasPropertyFeature . Garden) ⊑ Villa

hasPropertyType, -

(∃ hasPropertyFeature . Garden) ⊑ (∃ hasPropertyType . "villa"^^xsd:string)

, . , , .. .

Contra

hasPropertyType .

townHouse , TBox townHouse. ( ), - TBox, .

- - , ; . .

+3

RDF, RDFS OWL t-box. OWL DL Logic, Set Theory, , .

, , / , (), SKOS, , .

SKOS, ConceptSchemes, , / ConceptScheme. , OWL

+1

All Articles