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 12966 - Why the { items: [item, ...] } when the object has only one property?
Summary: Why the { items: [item, ...] } when the object has only one property?
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML Microdata (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 blocker
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-06-16 06:22 UTC by contributor
Modified: 2011-08-04 05:05 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2011-06-16 06:22:35 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html
Section: http://www.whatwg.org/specs/web-apps/current-work/complete.html#json

Comment:
Why the { items: [item, ...] } when the object has only property?

Posted from: 81.234.240.242
User agent: Opera/9.80 (X11; Linux x86_64; U; Edition Next; en) Presto/2.8.158 Version/11.50
Comment 1 Philip Jägenstedt 2011-06-16 06:25:33 UTC 
Looking at the algorithm in isolation, there appears to be no good reason why an object with a property 'items' holds the array of items, instead of just serializing the array directly.

If the reason is for future extensibility or that the object-ness is somehow, a note stating this would be appreciated.
Comment 2 Ian 'Hixie' Hickson 2011-07-07 23:31:53 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 below
Rationale: Concurred with reporter's comments.
Comment 3 contributor 2011-07-07 23:32:51 UTC 
Checked in as WHATWG revision r6283.
Check-in comment: explain about json extensibility
http://html5.org/tools/web-apps-tracker?from=6282&to=6283
Comment 4 Michael[tm] Smith 2011-08-04 05:05:29 UTC 
mass-move component to LC1