13338 2011-07-23 20:46:50 +0000 itemprop token should not contain . or : even with itemtype="" 2011-08-04 05:05:33 +0000 1 1 1 Unclassified HTML WG LC1 HTML Microdata (editor: Ian Hickson) unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#names:-the-itemprop-attribute P3 normal --- 1 contributor ian ian mike philipj public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 51410 0 contributor 2011-07-23 20:46:50 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/ Multipage: http://www.whatwg.org/C#names:-the-itemprop-attribute Complete: http://www.whatwg.org/c#names:-the-itemprop-attribute Comment: itemprop token should not contain . or : even with itemtype="" Posted from: 81.234.240.242 User agent: Opera/9.80 (X11; Linux x86_64; U; Edition Next; en) Presto/2.9.181 Version/12.00 51411 1 philipj 2011-07-23 20:51:34 +0000 "If the item is a typed item: a defined property name allowed in this situation according to the specification that defines the relevant type for the item" The spec also says "Specifications that introduce defined property names that are not absolute URLs must ensure all such property names contain no U+002E FULL STOP characters (.), no U+003A COLON characters (:), and no space characters." This is a requirement on other specifications, but it doesn't appear as if the requirement is enforced in the HTML syntax. I suggest making it such that if a token is not a valid URL, it must not contain "." or ":", even for typed items. 51948 2 ian 2011-08-02 06:32:06 +0000 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: When it's not a valid URL, the property name must be one from a vocabulary. Why would checking a subset of the syntax help? It's not like the validator can say it's valid unless it knows what the allowed property names are. 51977 3 philipj 2011-08-02 09:41:49 +0000 It can however say that it's *invalid* without knowing the vocabulary. I guess the spec doesn't disallow validators from doing, so that's fine then. 52950 4 mike 2011-08-04 05:05:33 +0000 mass-move component to LC1