W3C home > Mailing lists > Public > public-owl-wg@w3.org > August 2008

Re: changes to Syntax document to implement the resolution of ISSUE-104

From: Peter F. Patel-Schneider <pfps@research.bell-labs.com>
Date: Mon, 18 Aug 2008 08:24:50 -0400 (EDT)
Message-Id: <20080818.082450.257383173.pfps@research.bell-labs.com>
To: public-owl-wg@w3.org

From: Peter F. Patel-Schneider <pfps@research.bell-labs.com>
Subject: changes to Syntax document to implement the resolution of ISSUE-104
Date: Wed, 13 Aug 2008 14:40:40 -0400 (EDT)

> I have edited the syntax document as per the resolution of ISSUE-104 in
> the teleconference today.
> 
> The diff is
> http://www.w3.org/2007/OWL/wiki/index.php?title=Syntax&diff=11052&oldid=11051
> 
> peter

You may notice that "reserved vocabulary" still exists in the Syntax
document.  There is a difference between "reserved vocabulary" and
"disallowed vocabulary" that needs to be maintained in the document to
prevent changes to the syntax of OWL 2.


The document states:

URIs from the rdf, rdfs, xsd, and owl namespaces constitute the reserved
vocabulary of OWL 2. As described in the following sections, the URIs
from the reserved vocabulary that are listed in Table 2 have special
treatment in OWL 2. All other URIs from the reserved vocabulary
constitute the disallowed vocabulary of OWL 2 and are not to be used in
OWL 2 ontologies. 

Later in the document:

URIs used to identify object properties must not be in the reserved
vocabulary, apart from owl:TopObjectProperty and
owl:BottomObjectProperty, which are available in OWL 2 as built-in
object properties with a predefined semantics.  

If instead this was something like:

URIs used to identify object properties must not be in the disallowed
vocabulary.  There are two built-in object properties with a predefined
semantics in OWL 2, namely owl:TopObjectProperty and
owl:BottomObjectProperty.

Then preventing the use of owl:TopObjectProperty as a data property
would require quite a bit more wording, which would probably be much
less clear.  

This issue affects most other entity types.

peter
Received on Monday, 18 August 2008 12:25:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 18 August 2008 12:25:56 GMT