This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
public-html-comments posting from: Brent Jacobs <brent.jacobs@gmail.com> http://www.w3.org/mid/CAJSCMeFUcZhj9zEABTmSU5T6a1BUTJuh194dZO=JBObqZ6jx4A@mail.gmail.com Dear W3C I would like to make a suggestion regarding The Basic Syntax<http://www.w3.org/TR/microdata/#the-basic-syntax>section of the HTML Microdata draft. My suggestion relates to the mark up for items containing a single property: <span itemscope><span itemprop="name">The Castle</span></span> There is a potential to reduce the amount of markup for single property items. The itemscope attribute could be placed in the same span tag as the itemprop attribute: <span itemscope itemprop="name">The Castle</span> This would reduce overhead of the additional span tag declaring the item. It is now clear that the item contains a single property. It also makes the markup neater and easier to read. As similar syntax is already used for nested items (in red), it would complimentary to define single property items in the same way. <div itemscope> <p>Name: <span itemprop="name">Amanda</span></p> <p>Band: <span itemprop="band" *itemscope*> <span itemprop="name">Jazz Band</span> ( <span itemprop="size">12</span> players)</span></p> </div> Kind regards, Brent
Sorry, but this won't work. Elements with both @itemscope and @itemprop already have a meaning - that's how you indicate that a property of some other item is an item itself. Here's an example: <div itemscope itemtype="person"> <p itemprop=name>Tab Atkins</p> <p itemprop=location itemscope itemtype="geo">Current Location: <span itemprop=lat>37</span>°, <span itemprop=long>-122</span>° </p> </div> Here, the "location" property from the "person" vocabulary is a Microdata item from the "geo" vocabulary.
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.