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

Re: Datatype Defaulting in OWL

From: Sean B. Palmer <sean@miscoranda.com>
Date: Thu, 22 Nov 2007 09:07:21 +0000
Message-ID: <b6bb4d890711220107q7c4b5075xa631892641cf7aff@mail.gmail.com>
To: "Bijan Parsia" <bparsia@cs.man.ac.uk>
Cc: "SW-forum Web" <semantic-web@w3.org>, "public-owl-wg Group WG" <public-owl-wg@w3.org>

On Nov 22, 2007 8:51 AM, Bijan Parsia <bparsia@cs.man.ac.uk> wrote:

> > So, either one needs a kind of macro, or some sort of type coercion.
>
> Can you GRDDL RDF/XML? If so, you could add a type decoration
> transform.

Yes, you can. That's clever!

This is helping me to restate my goal, too... I think what I want is a
way to say that the range of a property is xsd:string UNION
xsd:integer, but that instances of xsd:string may be transformed
through some atoi-ish type coercion (possibly via GRDDL?) to
xsd:integer. The aeq route seems to be kinda getting at this, but
might be different.

So in the GRDDL case, the way to specify this would be to say that all
documents in which my property, e.g. numberOfFish, appears may be
transformed using the GRDDL transform... but that means that we need
another new thing: a way to say "all documents in which this property
appears".

And there are further complications in that you have to mandate the
RDF/XML serialisation to apply the GRDDL transform, and so on.

-- 
Sean B. Palmer, http://inamidst.com/sbp/
Received on Thursday, 22 November 2007 09:07:30 GMT

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