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#attr-itemid Complete: http://www.whatwg.org/c#attr-itemid Comment: Why is itemid a valid URL potentially surrounded by spaces? Posted from: 81.234.240.242 User agent: Opera/9.80 (X11; Linux x86_64; U; Edition Next; en) Presto/2.9.186 Version/12.00
Something that caught my attention while reading http://www.jenitennison.com/blog/node/164 - "The itemid cant just be empty: the . is the shortest URI you can use to reference the page itself." I thought that itemid="" would mean the same thing, but it appears that itemId is resolved differently from most other URL attributes because it is a "valid URL potentially surrounded by spaces". Is there a reason why itemid is not just a "valid URL" like most other URL properties?
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: It isn't resolved any differently from others as far as I can tell.
That could be an Opera bug, but the main question is: Is there a reason why itemid is not just a "valid URL" like most other URL properties? "valid URL potentially surrounded by spaces" seems to be something odd needed for legacy compat, not something to deliberately introduce. If it *is* deliberate, why is itemtype not the same?
This was changed in http://html5.org/tools/web-apps-tracker?from=4991&to=4992 to resolve http://www.w3.org/Bugs/Public/show_bug.cgi?id=9354 Given that, things seem to make a bit more sense. itemtype is relfected as a string, while itemid is reflected as a URL and resolved. Closing as invalid again.