W3C home > Mailing lists > Public > www-webont-wg@w3.org > November 2002

Re: proposal: Structured Datatypes

From: Jonathan Borden <jonathan@openhealth.org>
Date: Wed, 6 Nov 2002 23:13:13 -0500
Message-ID: <008e01c28613$fe4a7bb0$7c674544@ne.mediaone.net>
To: "Peter F. Patel-Schneider" <pfps@research.bell-labs.com>
Cc: <connolly@w3.org>, <www-webont-wg@w3.org>

Peter F. Patel-Schneider wrote:

in response to my statement:
> >
> > That is the whole point of this. Given the above datatype, and if the
> > property is defined as functional the following entailment would hold:
> >
> > ex:foo ex:DTprop "<a>010</a><b>aaa</b>"^^rdfs:XMLLiteral
> > ex:bar ex:DTprop "<a>00010</a><b>aaa</b>"^^rdfs:XMLLiteral
> >
> > =>
> >
> > ex:foo owl:sameIndividialAs ex:bar
>
> "<a>010</a><b>aaa</b>"^^rdfs:XMLLiteral and
> "<a>00010</a><b>aaa</b>"^^rdfs:XMLLiteral denote different elements of the
> RDF domain of discourse.  Thus ex:foo owl:sameIndividialAs ex:bar would
not
> follow.

what about:

_:x owl:dtvalue "<a>010</a><b>aaa</b>"^^rdfs:XMLLiteral .
_:y owl:dtvalue "<a>00010</a><b>aaa</b>"^^rdfs:XMLLiteral

_:x rdf:type ex:xType .
_:y rdf:type ex:xType .

=>

_:x owl:sameIndividualAs _:y .

It seems to me that there must be some way to allow that type of entailment
(I might not have the details correct but hopefully you understand where I
am trying to go). Perhaps not in which case this issue just may be too
difficult for this WG to tackle.

Jonathan
Received on Wednesday, 6 November 2002 23:32:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:57:55 GMT