W3C home > Mailing lists > Public > public-vocabs@w3.org > November 2011

Re: @itemid and URL properties in schema.org

From: Toby Inkster <tai@g5n.co.uk>
Date: Wed, 9 Nov 2011 13:29:34 +0000
To: Peter Mika <pmika@yahoo-inc.com>
Cc: Gregg Kellogg <gregg@kellogg-assoc.com>, Jeni Tennison <jeni@jenitennison.com>, "public-vocabs@w3.org" <public-vocabs@w3.org>, HTML Data Task Force WG <public-html-data-tf@w3.org>
Message-ID: <20111109132934.1eb51aac@miranda.g5n.co.uk>
On Sun, 06 Nov 2011 15:13:03 +0100
Peter Mika <pmika@yahoo-inc.com> wrote:

> In OWL, the only way to express this constraint is to use a
> datatype-property: using an object property would allow any resource
> (including bnodes) as value.

Just use an object property, and accept the fact that OWL isn't
capable of expressing every possible constraint.

<http://tobyinkster.co.uk/#i> foaf:homepage [] . # deal with it! ;-)

Setting a property's rdfs:range to owl:NamedIndividual is at least an
*indication* that you intend a property not to be used with bnode
values. Whatsmore, it will allow DL tools to whine about it.

-- 
Toby A Inkster
<mailto:mail@tobyinkster.co.uk>
<http://tobyinkster.co.uk>
Received on Wednesday, 9 November 2011 13:28:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 May 2012 06:48:57 GMT