W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > August 2010

Re: ISSUE-29: Re: When is equal and when is it nonequal (eg, the IRI interface)

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Mon, 02 Aug 2010 22:50:45 -0400
Message-ID: <4C578405.3020306@digitalbazaar.com>
To: W3C RDFa WG <public-rdfa-wg@w3.org>
On 08/01/2010 10:20 PM, Nathan wrote:
> Now - apologies in advance for this...
> What's the use-case for having the origin/source?


> What's the use-case for having store.createIRI(iri,origin);?
>  (and all related)

That's a bug in the API, it should've read:


'info' is an attempt to generalize the storage of developer-specified
information along with the IRI. It would allow developers to use a
single attribute as a point of extension if it is desired. This would
allow innovation outside of the core RDF triples and outside of the RDFa

> If you have some use-case(s), can they be handled by functions like
> document.getElementsBySubject(type) or not?

Not as far as the community has discovered thus far. There needs to be a
way for developers to understand where triples originated in the
document. It makes it very easy to modify the DOM based on the data it
contains. One can easily imagine highlighting foaf:name values in a
page, or placing phone dialing icons beside vcard:tel numbers. Without a
link from the RDF data back to the DOM, doing this in a way that is
deterministic is difficult.

If we can figure out a better way to do this, that would be wonderful.
The mechanism Toby outlined (placing the info object on the RDFTriple)
is one such possibility.

> ps: hope I didn't come across as rude at all - if so, it wasn't intended!

Spirited and impassioned discussion is always welcome on this mailing
list as long as it is respectful of all involved. :)

-- manu

Manu Sporny (skype: msporny, twitter: manusporny)
President/CEO - Digital Bazaar, Inc.
blog: WebApp Security - A jQuery Javascript-native SSL/TLS library
Received on Tuesday, 3 August 2010 02:51:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:19:48 UTC