W3C home > Mailing lists > Public > public-lod@w3.org > November 2010

Re: isDefinedBy and isDescribedBy, Tale of two missing predicates

From: Tore Eriksson <tore.eriksson@po.rd.taisho.co.jp>
Date: Tue, 09 Nov 2010 08:18:20 +0900
To: Toby Inkster <tai@g5n.co.uk>
Cc: public-lod@w3.org
Message-Id: <20101109081819.8BA0.9D98B4E7@po.rd.taisho.co.jp>
> On Fri, 5 Nov 2010 15:53:34 +0000
> Ian Davis <lists@iandavis.com> wrote:
> 
> > Suppose I assign the ID 'mars' to represent the planet mars in my RDFa
> > document. I can then refer to it using http://example.com/foo#mars.
> > What does it mean when my javascript calls
> > document.getElementById('mars')? Should I expect now to manipulate the
> > planet mars?

Toby Inkster wrote: 
> If you are using the URI <http://example.com/foo#mars> to represent a
> planet, then you should not use the same URI to represent an HTML
> element, as it's likely that the set of HTML elements and the set of
> planets are disjoint. (In Aug 2006 the IAU finally settled on a
> definition of planets that at least seems to exclude HTML elements from
> being planets in their own right.)
> 
> Given that the planet Mars and your HTML element are in disjoint sets,
> they must be separate entities so must not share a URI.

Or you could consider, as was suggested recently, that the HTML element
is a _representation_ of the planet Mars. Then
document.getElementById('mars') would only manipulate the representation,
not the resource. Whether an HTML fragment is an adequate representation
for a planet is another debate though...

Tore Eriksson

_______________________________________________________________
Tore Eriksson [tore.eriksson at po.rd.taisho.co.jp]
Received on Monday, 8 November 2010 23:19:04 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 31 March 2013 14:24:30 UTC