W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > December 2012

Re: New Editor's Draft for HTML+RDFa 1.1

From: Ivan Herman <ivan@w3.org>
Date: Wed, 12 Dec 2012 06:06:47 -0500
Cc: Niklas Lindström <lindstream@gmail.com>, RDFa WG <public-rdfa-wg@w3.org>, Jeni Tennison <jeni@jenitennison.com>
Message-Id: <BBE0BADD-0D53-4D48-9F0E-7DA4C8800E72@w3.org>
To: Manu Sporny <msporny@digitalbazaar.com>

On Dec 11, 2012, at 21:02 , Manu Sporny wrote:

> cc: Jeni (who originally raised one of the sub-issues in this e-mail)
> 
> On 12/09/2012 04:35 AM, Niklas Lindström wrote:
>> 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".
> 
> Fixed in the latest Editor's Draft, will have a pubrules-ready WD later
> tonight.
> 
>> 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.)
> 
> Here's the issue that led to the feature:
> 
> http://www.w3.org/2010/02/rdfa/track/issues/113
> 
> The original e-mail by Jeni Tennison:
> 
> http://lists.w3.org/Archives/Public/public-rdfa-wg/2011Oct/0126.html
> 
> and the resolution:
> 
> http://www.w3.org/2010/02/rdfa/meetings/2011-11-17#resolution_3
> 
> It is troubling that @value overrides @content... seems like a bad thing
> to do. Can anybody on the list remember why @value overrides @content?
> 

Because we never thought of it:-) I am serious. Looking back at the issue mailings, this specific question never came up.


> Also keep in mind that the side-effect of adding support for @value is
> that @value is also used on the INPUT and LI elements in HTML5, which I
> don't think was intended when we added this feature. I'm personally fine
> with leaving the feature in there, and changing it so that @content
> overrides @value if it exists.

I agree.

Ivan


> 
> -- 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/
> 


----
Ivan Herman, W3C Semantic Web Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
FOAF: http://www.ivan-herman.net/foaf.rdf







Received on Wednesday, 12 December 2012 11:07:32 UTC

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