Defining Complementary Classes and Their Instances

Top

We now wish to define that the PrintManual class is complementary to the WebPage class. Do this as follows:

1.	In the Classes Overview, click the Detail View button of PrintManual.

2.	In the Detail View of PrintManual, right-click the PrintManual class box and select Add complementOf.

3.	Right-click the complementOf connector, click Add Class from the context menu, and select doc:WebPage.

The Detail View should look like this:

ss_tut_odl_printmanual_2

Now create instances for the PrintManual class as follows:

1.	In the Instances Overview, click the Add New button to create an entry for a new instance. Name the instance doc:XMLSpyEnterpriseUserManualENPDF.

2.	In the Detail View of the doc:XMLSpyEnterpriseUserManualENPDF instance, expand the rdf:type predicate box, double-click in the Resource Object box to pop up a down arrow on the right of the Resource Object box, and select doc:PrintManual.

3.	Right-click the Instance box, click Add Predicate from the context menu, and select dc:format.

4.	Right-click the predicate box, click Add Resource Object from the context menu, and select doc:PDF.

5.	Right-click the Instance box, click Add Predicate from the context menu, and select dc:language.

6.	Right-click the predicate box, click Add Resource Object from the context menu, and select doc:EN.

7.	Right-click the Instance box, click Add Predicate from the context menu, and select dc:date.

Right-click the predicate box, click Add Literal Object from the context menu, and type 2006-10-03 in the newly created Literal Object box. Select the datatype toggle (by clicking DT in the bottom half of the

icon). Then click the down arrow of the combo box to display a dropdown list of available XML Schema datatypes, and select xsd:date.

The Detail View should look like this:

ss_tut_odl_inst_spyumanenpdf

Create and define an instance called doc:XMLSpyEnterpriseUserManualDEPDF similarly, with the difference that the dc:language predicate should take doc:DE. as its object.

That's it!

You have built up your skills to use the more advanced descriptive constructs offered by OWL DL and have become more familiar with the interface, features and mechanisms of SemanticWorks.

Top