- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Thu, 11 Nov 2010 11:59:24 +0100
- To: Gregg Kellogg <gregg@kellogg-assoc.com>
- CC: Toby Inkster <tai@g5n.co.uk>, "public-rdfa-wg@w3.org" <public-rdfa-wg@w3.org>
On 10.11.2010 20:04, Gregg Kellogg wrote: > One mechanism I've considered is to create a jQuery library that implements designed-in profiles through DOM re-writing. This way, I can remove dependencies on externally loading a profile I'm aware of, as an author, and it also allows me to address other issues of 1.0 vs. 1.1. It isn't a generalizable solution, but as an App writer, where I know the profiles I depend on, and have some control over the HTML markup, it seems like a reasonable solution. > > I'm not aware of any JavaScript RDFa parsers that are up-to-date with RDFa 1.1 LC. That being the case, I'd end up re-writing CURIES and Terms in RDFa properties as necessary to be 1.0 compliant, but I'd rather not have to do that. > > Gregg > ... The implementations I'm concerned with are simple HTML filters that try to extract additional metadata while parsing the document. Those would not benefit at all by any kind of Javascript library. Best regards, Julian
Received on Thursday, 11 November 2010 11:00:08 UTC