18.12.2012 Views

Proceedings

Proceedings

Proceedings

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

3.5. Defining properties for classes (including its characteristics)<br />

Since a subclass inherits all super class properties, we insisted on defining properties<br />

at the level of base classes. In a first phase, we defined the properties of the object<br />

type, i.e. those serving in the correlation of individuals come through different classes.<br />

So, for example, Enterprise class is correlated of Offer and States classes through the<br />

properties hasOffer and hasState. To allow inference and in the opposite direction, we<br />

proceeded to define inverse properties (inverseOf) those declared previously, i.e.<br />

offerOf and stateOf. Graphically, links are represented by Protégé as in the Figure 2.<br />

In OWL, disclaimers second inverse properties (for example, hasOffer and offerOf)<br />

are presented below:<br />

<br />

hasOffer<br />

<br />

<br />

<br />

<br />

offerOf<br />

<br />

<br />

<br />

<br />

Figure 2. Links between classes<br />

Of course, for each class we defined and the main properties of date type: eName,<br />

eAddress (with sub property uri), eCity, eCountry for Enterprise, oName and ōdate<br />

for Offer. And, limit to only one example, we provide the code for the property OWL<br />

eAddress (destined for address postal record) and eUri (WEB address) of the<br />

Enterprise class:<br />

~ 255 ~

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!