- From: Niklas Lindström <lindstream@gmail.com>
- Date: Sun, 9 Dec 2012 10:35:32 +0100
- To: Manu Sporny <msporny@digitalbazaar.com>
- Cc: RDFa WG <public-rdfa-wg@w3.org>
Hi, I found a problem in the latest draft. In "3.1 Additional RDFa Processing Rules", it says to use "HTMLLiteral" from the RDF vocabulary. But according to "RDF 1.1 Concepts and Abstract Syntax: 5.2 The rdf:HTML Datatype" [1], that should be just "HTML". So replace the two occurrences of "HTMLLiteral" with "HTML". Also, I think it's great that @value is supported. IIUC, it means that @value from <input> elements also can be captured with RDFa, correct? But I wonder why @value is defined to override @content, and not vice versa? I don't recall the reasons for that. (I was expecting @content to work just like @resource overrides @href. I.e. to always override any host language specific attribute; in this case, @value.) Best regards, Niklas [1]: http://www.w3.org/TR/rdf11-concepts/#section-html On Sun, Dec 2, 2012 at 8:39 PM, Manu Sporny <msporny@digitalbazaar.com> wrote: > A new editor's draft for HTML+RDFa 1.1 has been published which > incorporates all decisions made by the newly re-chartered RDFa WG to > date. As of this moment, there are no plans to add any new features or > remove existing features from HTML+RDFa 1.1. This document is probably > the one that is going to go to Last Call, so please review it and try to > find any issues or problems: > > http://www.w3.org/2010/02/rdfa/drafts/2012/ED-rdfa-in-html-20121202/ > > You can view a diff of the changes here: > > http://www.w3.org/2010/02/rdfa/drafts/2012/ED-rdfa-in-html-20121202/diff-20120911.html > > -- manu > > -- > Manu Sporny (skype: msporny, twitter: manusporny) > Founder/CEO - Digital Bazaar, Inc. > blog: The Problem with RDF and Nuclear Power > http://manu.sporny.org/2012/nuclear-rdf/ >
Received on Sunday, 9 December 2012 09:36:31 UTC