W3C home > Mailing lists > Public > public-owl-wg@w3.org > October 2007

ISSUE-28 (multiple facets): REPORTED: Multiple facet restrictions per data range

From: OWL <sysbot+tracker@w3.org>
Date: Thu, 25 Oct 2007 07:25:09 +0000 (GMT)
To: public-owl-wg@w3.org
Message-Id: <20071025072509.2E01C5F751@stu.w3.org>


ISSUE-28 (multiple facets): REPORTED: Multiple facet restrictions per data range

http://www.w3.org/2007/OWL/tracker/issues/

Raised by: Bijan Parsia
On product: 

Reported by bparsia, Mar 29, 2007

See:
    <http://lists.w3.org/Archives/Public/public-owl-dev/2007JanMar/0127.html>

The current OWL 1.1 specification only allows one facet restriction per data range. This makes it 
cumbersome (and unintuitive) to specify ranges such as integer between 30 and 50. t should be 
possible to specify multiple facet restrictions for a data range



Comment 1 by bparsia, Mar 29, 2007

See also:
   <http://lists.w3.org/Archives/Public/public-owl-dev/2006OctDec/0129.html>

Delete comment
Comment 2 by pfpschneider, Oct 11, 2007

The lack of multiple facet restrictions is in line with the move from the frame-like
syntax.  If you want to allow DatatypeRestriction(xsd:integer minInclusive 30
maxInclusive 50) in addition to DatatypeRestriction(DatatypeRestriction(xsd:integer
minInclusive 30) maxInclusive 50) then you should also probably argue for
Restriction(foo minCardinality(30) maxCardinality(50)) in addition or instead of
ObjectIntersectionOf(ObjectMinCardinality(foo 30) ObjectMaxCardinality(foo 50))
Received on Thursday, 25 October 2007 07:25:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:13:26 GMT