- From: Gregg Kellogg <gregg@greggkellogg.net>
- Date: Thu, 13 Dec 2012 11:22:13 -0500
- To: RDFa Working Group <public-rdfa-wg@w3.org>
I'm +1 too. Gregg Kellogg gregg@greggkellogg.net On Dec 13, 2012, at 7:36 AM, RDFa Working Group Issue Tracker <sysbot+tracker@w3.org> wrote: > ISSUE-145 (@content override @value): Should @content override @value? [RDFa 1.1 in HTML5] > > http://www.w3.org/2010/02/rdfa/track/issues/145 > > Raised by: Manu Sporny > On product: RDFa 1.1 in HTML5 > > The current HTML+RDFa 1.1 specification states: > > "In Section 7.5: Sequence, processing step 11, the HTML5 value attribute must be utilized when generating output. If value is detected, it must override content and must be processed according to the rules for content." > > This seems backwards as @content is typically used to override other literal-carrying attributes, like @value. > > The group should align how @content and @value is treated when placed on the same element with how @content is treated on every other element in RDFa 1.1. > > PROPOSAL: When both @content and @value appear on the same HTML element, the value of @content MUST be used. > > >
Received on Thursday, 13 December 2012 16:23:51 UTC