W3C home > Mailing lists > Public > public-rdf-in-xhtml-tf@w3.org > September 2009

Re: Request to publish HTML+RDFa (draft 3) as FPWD

From: Toby Inkster <tai@g5n.co.uk>
Date: Tue, 22 Sep 2009 22:09:43 +0100
Message-Id: <469D9A39-F93A-4240-B254-8B376137249F@g5n.co.uk>
Cc: Shane McCarron <shane@aptest.com>, Henri Sivonen <hsivonen@iki.fi>, Mark Birbeck <mark.birbeck@webbackplane.com>, HTMLWG WG <public-html@w3.org>, RDFa mailing list <public-rdf-in-xhtml-tf@w3.org>
To: Jonas Sicking <jonas@sicking.cc>
On 22 Sep 2009, at 21:50, Jonas Sicking wrote:
> On Tue, Sep 22, 2009 at 1:43 PM, Jonas Sicking <jonas@sicking.cc>  
> wrote:
> >Sure, but if you have a DOM, what do you do? One solution is  
> certainly
>> to say that "If you have a DOM, there is no way to extract RDFa  
>> data".
>> This is certainly a possibility, but it does mean that it's  
>> impossible
>> to
> ... to build a RDFa implementation in javascript, as javascript is
> handed a DOM. I don't know if javascript implementations of RDFa is
> something that's considered important.

I know of at least three Javascript implementations of RDFa parsers  
that each use the DOM:

* The Operator add-on for Firefox
* Jeni Tennison's rdfQuery library, based on jQuery
* Ben Adida's implementation

If, as you say, RDFa implementations "can't" use the DOM, it appears  
this is more of a "theoretical can't" rather than a "practical can't".

Toby A Inkster
Received on Tuesday, 22 September 2009 21:10:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:02:05 UTC