- From: Evan Wallace <ewallace@cme.nist.gov>
- Date: Tue, 20 May 2008 18:07:38 -0400
- To: Michael Schneider <schneid@fzi.de>
- CC: OWL Working Group WG <public-owl-wg@w3.org>
Michael Schneider wrote: > Jeremy Carroll answered to Boris Motik: > > >>> >> Unfortunately, this is a "feature" and not a bug. Complements of data >>> >>ranges are included into OWL 2 mainly in order to provide >>> >> everything that is needed for reasoning >>> > > [...] > > >> >I am assuming it is possible to express the intersection of the >> >enclosing type with the complement - so that Michael's point is more >> >about usability than expressability. >> > > Good point! For example: > > IntersectionOf( > AllValuesFrom( badBodyTemperature xsd:decimal ) > AllValuesFrom( badBodyTemperature ComplementOf( > DatatypeRestriction( xsd:decimal minInclusive 35 maxExclusive 42 > )))) > > Perhaps one can introduce some syntactic sugar, or just leave the situation > as is, and add some note into the Primer instead on how to handle such > common cases. > > Cheers, > Michael > > I saw this issue was coming up for discussion on the agenda for tomorrow's telecon, and I had a couple of comments about it. 1) The fact that ComplementOf a DataRange produces an ugly collection of literal values is what I would expect. 2) But it would also be nice to have a DataIntersectionOf DataRange constructor that would allow intersecting another DataType with the ugly complemented DataRange directly. This would be analogous to the structure of ClassExpressions and thus would be quite intuitive for the user. -Evan
Received on Tuesday, 20 May 2008 22:09:13 UTC