This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13338 - itemprop token should not contain . or : even with itemtype=""
Summary: itemprop token should not contain . or : even with itemtype=""
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML Microdata (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-23 20:46 UTC by contributor
Modified: 2011-08-04 05:05 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2011-07-23 20:46:50 UTC 
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
Comment 1 Philip Jägenstedt 2011-07-23 20:51:34 UTC 
"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.
Comment 2 Ian 'Hixie' Hickson 2011-08-02 06:32:06 UTC 
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.
Comment 3 Philip Jägenstedt 2011-08-02 09:41:49 UTC 
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.
Comment 4 Michael[tm] Smith 2011-08-04 05:05:33 UTC 
mass-move component to LC1