2.4. Preconstructed Descriptors

To have control over the amount of synchronization that happens between the internal-state of a descriptor and an ontology, a developer can utilize descriptors that implement one or more expressions. OWLOOP API provides some preconstructed descriptors that implement different number of expressions.

• conceptDescriptor/: contains the following classes:
  • FullConceptDescriptor: an example of a compound descriptor which implements 6 expressions (i.e., Equivalent, Disjoint, Sub, Super, Instance, Definition).
  • HierarchicalConceptDescriptor: an example of a compound descriptor which implements 2 expressions (i.e., Sub, Super).
  • InstanceConceptDescriptor: an example of a simple descriptor which implements 1 expression (i.e., Instance).
  • dataPropertyDescriptor/: contains the following classes:
  • FullDataPropertyDescriptor: an example of a compound descriptor which implements 6 expressions (i.e., Equivalent, Disjoint, Sub, Super, Domain, Range).
  • HierarchicalDataPropertyDescriptor: an example of a compound descriptor which implements 2 expressions (i.e., Sub, Super).
• individualDescriptor/: contains the following classes:
  • FullIndividualDescriptor: an example of a compound descriptor which implements 5 expressions (i.e., Equivalent, Disjoint, Type, ObjectLink, DataLink).
  • TypeIndividualDescriptor: an example of a simple descriptor which implements 1 expression (i.e., Type).
• objectPropertyDescriptor/: contains the following classes:
  • FullObjectPropertyDescriptor: an example of a compound descriptor which implements 7 expressions (i.e., Equivalent, Disjoint, Sub, Super, Domain, Range, Inverse).
  • HierarchicalObjectPropertyDescriptor: an example of a compound descriptor which implements 2 expressions (i.e., Sub, Super).