Skip to content

2.4. Preconstructed Descriptors

yushakareem edited this page Dec 16, 2019 · 9 revisions

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.

In the package owloop/Descriptor/utility:

  • classDescriptor/ package contains the following Java-classes:
    • FullClassDescriptor: an example of a descriptor which implements 6 expressions (i.e., Equivalent, Disjoint, Sub, Super, Instance, Definition). - HierarchicalClassDescriptor: an example of a descriptor which implements 2 expressions (i.e., Sub, Super). - InstanceClassDescriptor: an example of a descriptor which implements 1 expression (i.e., Instance).
      • dataPropertyDescriptor/ package contains the following Java-classes:
        • FullDataPropertyDescriptor: an example of a descriptor which implements 6 expressions (i.e., Equivalent, Disjoint, Sub, Super, Domain, Range).
        • HierarchicalDataPropertyDescriptor: an example of a descriptor which implements 2 expressions (i.e., Sub, Super).
      • individualDescriptor/ package contains the following Java-classes:
        • FullIndividualDescriptor: an example of a descriptor which implements 5 expressions (i.e., Equivalent, Disjoint, Type, ObjectLink, DataLink).
        • TypeIndividualDescriptor: an example of a descriptor which implements 1 expression (i.e., Type).
      • objectPropertyDescriptor/ package contains the following Java-classes:
        • FullObjectPropertyDescriptor: an example of a descriptor which implements 7 expressions (i.e., Equivalent, Disjoint, Sub, Super, Domain, Range, Inverse).
        • HierarchicalObjectPropertyDescriptor: an example of a descriptor which implements 2 expressions (i.e., Sub, Super).
Clone this wiki locally