Setting Up Namespaces <rdf:RDF xmlns:rdf =" syntax-ns#" xmlns:rdfs=" schema#" xmlns:xsd =" xmlns:daml=" xmlns:dex =" xmlns:exd =" dt#" xmlns =" ex#"

Housekeeping $Id: daml+oil-ex.daml,v /03/27 21:24:04 horrocks Exp $ An example ontology, with data types taken from XML Schema followed by

Defining Classes Animal This class of animals is illustrative of a number of ontological idioms.

Defining Classes cont.1 It perfectly admissible for a class to have multiple superclasses: A Man is a Male Person...and a Woman is a Female Person.

Defining Properties

Defining Properties cont.1 shoesize is a DatatypeProperty whose range is xsd:decimal. shoesize is also a UniqueProperty (can only have one shoesize)

Defining Property Restrictions

Defining Property Restrictions cont.1 1

Defining Property Restrictions cont.2 Animals have exactly two parents, ie: If x is an animal, then it has exactly 2 parents (but it is NOT the case that anything that has 2 parents is an animal). Such an assertion "

Defining Properties cont.1 age is a DatatypeProperty whose range is xsd:decimal. age is also a UniqueProperty (can only have one age)

Defining Properties cont.2 rdf:about=" il-ex.daml#Animal"

Defining Properties cont.3

Defining Properties cont.4

Notations for properties

Notations for properties cont.1 If x's parent is y, then y is x's child. This is defined using the inverseOf tag. The hasAncestor and descendent properties are transitive versions of the hasParent and hasChild properties. hasAncestor

Notations for properties cont.2 Sometimes, we like to refer to mothers using the synonym mom. The tag samePropertyAs allows us to establish this synonymy:

Notations for classes no car is a person

Notations for classes cont.1 An even more compact idiom is to state that a whole set of classes are all pairwise disjoint. Rather than stating the individual disjointness relations, this can be stated for a set of classes in a single statement:

Notations for classes cont.2 We can also identify a Class with the disjoint union of a set of other classes. In this case, we identify the Class Person with the disjoint union of the Classes Man and Woman. every person is a man or a woman

Notations for classes cont.3 We have already seen that we can construct a new class by taking the complementOf another class. In the same way, we can construct classes out of the intersection of other classes:

Notations for classes cont.4 Similarly, we can construct a class as the unionOf a set of classes:

Notations for classes cont.5 Just as for properties, a mechanism exists for declaring synonyms for classes:

Using User-defined Datatypes = 59 --> Then we could reference elements of this file in DAML+OIL restrictions,

Defining individuals We can also define individual objects in a class, e.g., Adam, a person of age 13 and shoesize 9.5: Adam Adam is a person.

Defining individuals cont.1 A Person has a property called hasHeight, which is a Height. (hasHeight is a Property, or relation; Height is a Class, or kind of thing.)

Defining individuals cont.2 Height is a Class described by an explicitly enumerated set. We can describe this set using the oneOf element. Like disjointUnionOf, oneOf uses the RDF-extending parsetype="daml:collection".

Defining individuals cont.3 Finally, TallThing is exactly the class of things whose hasHeight has the value tall:

Defining individuals cont.4 shirtsize is a DatatypeProperty whose range is clothingsize. associatedData is a DatatypeProperty without a range restriction.

Defining individuals cont.5 BigFoots (BigFeet?) are exactly those persons whose shosize is over12.

Defining individuals cont.6 Persons have at most 1 item of associatedData 1

Defining individuals cont.7 Now we can (try to) create several individuals