This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-semantics.html Multipage: http://www.whatwg.org/C#the-data-element Complete: http://www.whatwg.org/c#the-data-element Comment: Consider replacing <data value> with a global attribute itemvalue="" Posted from: 94.234.170.60 by simonp@opera.com User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.15 Safari/535.7
Indeed, it makes sense to have an attribute (to use with any element) instead of separate <data> element that has nothing sense other than containing a value. By the way, in general, this bug has something in common with bug 13057 related to replacing DEL/INS elements to more usable attributes.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: <data value> is not only about microdata. Even if it was, one of the things that we learnt when studying microdata early on is that people get really confused with global attributes and in particular with bimodal behaviour. With itemscope="" we already have that, and it's one of the most confusing parts of the microdata part of HTML.
(In reply to comment #2) > Even if it was, one of the things that we learnt when studying microdata early > on is that people get really confused with global attributes and in particular > with bimodal behaviour. With itemscope="" we already have that, and it's one of > the most confusing parts of the microdata part of HTML. We already _have_ 'itemscope' and 'itemprop' attrs anyway, so there is no reasons why 'itempropvalue' (not 'itemvalue' as original summary proposes) attribute could be more confusing than existing 'itemscope' and 'itemprop' ones. On the contrary, 'itempropvalue' attr could be consistent supplement to them.