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/microdata.html Multipage: http://www.whatwg.org/C#names:-the-itemprop-attribute Complete: http://www.whatwg.org/c#names:-the-itemprop-attribute Comment: Microdata: validity contraints to catch missing attributes Posted from: 81.234.240.242 User agent: Opera/9.80 (X11; Linux x86_64; U; Edition Next; en) Presto/2.9.220 Version/12.00
To help catch authoring errors like the one in bug 14595, we could improve the validity constraints related to itemprop a bit. Specifically, if itemprop appears of any of the following attributes, require that the attribute is present: meta: content audio, embed, iframe, img, source, track, or video: src a, area, or link: href object: data data: value (Matching how itemValue works.) If one deliberately wants an empty value, one can simply use e.g. <data itemprop="prop" value=""> instead of <data itemprop="prop">.
Sorry, it was late when I filed this bug, value="" is already required for <data>. Here's a pruned list of things that currently doesn't give a warning in validtor.nu but should, under the assumption that it's the spec's fault: <audio itemprop=x><source src=a></audio> <embed itemprop=x> <iframe itemprop=x></iframe> <video itemprop=x><source src=a></video> <a itemprop=x></a> <map name=n><area itemprop=x></map> <object itemprop=x type=text/plain></object>
cc'ing hsivonen for sanity check, but assuming he doesn't see a problem with this, I'll add a conformance requirement to the section that defines itemprop.
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: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments.
Fixed in http://html5.org/r/6851