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 14233 - Allow items to have multiple types if they share the same vocabulary.
Summary: Allow items to have multiple types if they share the same vocabulary.
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML Microdata (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC All
: P2 blocker
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-21 20:26 UTC by Ian 'Hixie' Hickson
Modified: 2011-10-12 22:21 UTC (History)
8 users (show)

See Also:


Attachments

Description Ian 'Hixie' Hickson 2011-09-21 20:26:36 UTC
At the workshop today a number of people said that the main thing they wanted to do that they couldn't do with HTML today is mark up items with multiple types, for example marking an item as being both "a bike shop" and "a ski shop", where these types have common (or at least overlapping and non-conflicting) vocabularies.

Historically the solution has been to use an itemtype="" that specifies the type of the vocabulary, and an itemprop="" that gives the kinds. However, it seems this is unintuitive enough that people don't get it, so we should just allow compatible vocabularies to be listed in the itemtype="" attribute.
Comment 1 contributor 2011-10-12 00:16:43 UTC
Checked in as WHATWG revision r6668.
Check-in comment: Redefine itemtype='' to allow multiple types if they share the same vocabulary. This was by far the most frequently made request at the recent schema.org event
http://html5.org/tools/web-apps-tracker?from=6667&to=6668
Comment 2 Ian 'Hixie' Hickson 2011-10-12 00:16:51 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: Accepted
Change Description: see diff given above
Rationale: Concurred with reporter's comments.