W3C home > Mailing lists > Public > public-owl-comments@w3.org > November 2010

Inconsistency - Manchester Syntax - Datatype Restrictions

From: Bernd Neumayr <neumayr@dke.uni-linz.ac.at>
Date: Wed, 17 Nov 2010 14:19:38 +0100
Message-ID: <4CE3D66A.6010103@dke.uni-linz.ac.at>
To: public-owl-comments@w3.org
Hi,

I've just noticed an inconsistency in the "OWL 2 Manchester Syntax" 
document.

Section 3 "Quick Reference" contains:

    Datatype: NegInt
       Annotations: ...
       EquivalentTo: integer[< 0]

which intuitively means that the value space of NegInt contains all 
integers less than 0. However, in Section 4.2 "Formal Description for 
Mapping to OWL 2 Function-Style Syntax" the following transformations 
are prescribed:

    <=  xsd:minInclusive
    <   xsd:minExclusive
    >=  xsd:maxInclusive
    >   xsd:maxExclusive

Then, according to http://www.w3.org/TR/xmlschema-2/, the value space of 
NegInt in the above example contains all integers greater than 0!

Intuitively, the transformations should be (this is also how Protégé 4.1 
transforms from Manchester Syntax):

    <=  xsd:maxInclusive
    <   xsd:maxExclusive
    >=  xsd:minInclusive
    >   xsd:minExclusive

If my intuition is correct, then the first example in Section 7 
"Advanced Use of Datatypes" in the "OWL 2 primer" document should also 
be corrected:

IS:

    Datatype: personAge
      EquivalentTo: integer[<= 0 , >= 150]

SHOULD BE:

    Datatype: personAge
      EquivalentTo: integer[>= 0 , <= 150]


Best regards,

Bernd

-- 
______________________________________________________________________
Dr. Bernd Neumayr
Postdoctoral Research Fellow
+43 70 2468-9417
http://www.dke.jku.at/staff/bneumayr.html

Institut für Wirtschaftsinformatik - Data & Knowledge Engineering
Johannes Kepler Universität Linz, Altenberger Strasse 69, A-4040 Linz
Received on Thursday, 18 November 2010 10:56:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 18 November 2010 10:56:57 GMT