W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2011

[Bug 13150] New: Behavior of multiple @itemid values in the same document

From: <bugzilla@jessica.w3.org>
Date: Tue, 05 Jul 2011 16:35:52 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-13150-2486@http.www.w3.org/Bugs/Public/>

           Summary: Behavior of multiple @itemid values in the same
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML Microdata (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: msporny@digitalbazaar.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,

Logging this bug at the request of Philip Jägenstedt:

When you use the same @itemid on the page, and you retrieve data using the
Microdata DOM API, is the expected behavior that:

1) All properties for the same @itemid are merged with two separate items on
the page.
2) All properties and types for the same @itemid are merged.
3) What happens when somebody does a getItems() and uses one of the itemtypes -
are all properties returned?

With RDFa and RDF in general, all things w/ the same "@itemid" (aka: "@about")
would be merged into a single object with multiple types when retrieved via the
RDFa API. This is, in fact, what happens with RDF output for Philip's Microdata
parser. However, the JSON output creates two objects with non-overlapping
properties. What is the proper behavior?

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 5 July 2011 16:35:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:55 UTC