This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section: http://www.whatwg.org/specs/web-apps/current-work/#values Comment: Please add a rule that the property value for a PARAM element should be its VALUE attribute Posted from: 70.144.137.248
Use case: adding microdata properties to an OBJECT element where the property value is given in one of the child PARAM elements. <section> <h1>Mark Pilgrim</h1> <OBJECT classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0" WIDTH="550" HEIGHT="400"> <PARAM NAME=movie VALUE="photoViewer.swf"> <PARAM NAME=file VALUE="http://www.example.com/photo.jpg"> </OBJECT> </section> could become <section itemscope itemtype="http://data-vocabulary.org/Person"> <h1 itemprop="name">Mark Pilgrim</h1> <OBJECT classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0" WIDTH="550" HEIGHT="400"> <PARAM NAME=movie VALUE="photoViewer.swf"> <PARAM itemprop="photo" NAME=file VALUE="http://www.example.com/photo.jpg"> </OBJECT> </section> And then you would get two properties in the http://data-vocabulary.org/Person vocabulary: name=Mark Pilgrim photo=http://www.example.com/photo.jpg
How do you distinguish between a string and a URL (for e.g. converting to RDF)?
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: I considered doing as you suggest. However, since there's no way to know if the value is meant to be a URL or not, I couldn't add <param> to the list of URL property elements, and that would have meant that the example above would in fact still be non-conforming, since you're not allowed to put a URL into the value of an element with itemprop that isn't a URL property element. So it wouldn't really help.