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 10141 - itemscope is long and not very descriptive. how about just scope and prop.
Summary: itemscope is long and not very descriptive. how about just scope and prop.
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-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: 2010-07-13 02:29 UTC by contributor
Modified: 2010-10-05 13:03 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-07-13 02:29:40 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/complete.html#the-basic-syntax

Comment:
itemscope is long and not very descriptive.  how about just scope and prop.

Posted from: 68.32.157.249
Comment 1 Andreas Kuckartz 2010-07-13 19:36:57 UTC 
There are several "item..." attributes which form the set of attributes used for microdata. It would not be obvious that an attribute named "scope" belongs to that set. "prop" would be even worse because the "property" attribute is used by RDFa.
Comment 2 Ian 'Hixie' Hickson 2010-09-08 00:37:45 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: see comment 1. Also, these attributes are already implemented in various places and changing it now would cause too much disruption (indeed it would likely just be ignored).