[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: About OWL syntax

• To: Didier PH Martin <martind@n...>
• Subject: Re: About OWL syntax
• From: Jonathan Borden <jonathan@o...>
• Date: Tue, 07 Oct 2003 17:33:50 -0400
• Cc: xml-dev@l...
• In-reply-to: <000801c38d0a$02704f50$c801a8c0@DIDIERHOME>
• References: <000801c38d0a$02704f50$c801a8c0@DIDIERHOME>
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030901 Thunderbird/0.2

Didier PH Martin wrote:

>Why not having the properties declared inside a class element? Something
>like:
><owl:Class rdf:ID="ConsumableThing">
>  <owl:ObjectProperty rdf:ID="madeFromFruit">
>     <rdfs:range rdf:resource="#Fruit" /> 
>  </owl:ObjectProperty>
>  .... other property definition ....
></owl:class>
>  
>
For many of the reasons you mention, the OWL XML presentation syntax 
[http://www.w3.org/TR/owl-xmlsyntax/] was developed. On the other hand 
there is also an explicit relationship between a property and the class 
of objects which contain the property called a "Restriction".

One of the constraints on the syntax for OWL is that it is based upon 
RDF/XML and ultimately on the triples that result from the RDF/XML. 
Consequently, there are often many equivalent versions of a piece of syntax.

In any case this is what you want:

<owl:Class rdf:ID="ConsumableThing">
  <owl:subClassOf>
     <owl:Restriction>
	<owl:onProperty rdf:resource="#madeFromFruit" />
     	<owl:allValuesFrom rdf:resource="#Fruit" />
     </owl:Restriction>
  </owl:subClassOf>
  .... other property definition ....
</owl:Class>

Jonathan

• Follow-Ups:
  • RE: About OWL syntax
    • From: "Didier PH Martin" <martind@n...>

• References:
  • About OWL syntax
    • From: "Didier PH Martin" <martind@n...>

• Prev by Date: Re: About OWL syntax
• Next by Date: RE: The Battle for Web Services
• Previous by thread: Re: About OWL syntax
• Next by thread: RE: About OWL syntax
• Index(es):
  • Date
  • Thread