[Bug 13007] should (resolved) itemid be unique within a document?

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13007

--- Comment #10 from Manu Sporny <msporny@digitalbazaar.com> 2011-06-21 20:39:34 UTC ---
(In reply to comment #9)
> This is a completely separate issue from what Philip was talking about.

It's related - it's not completely separate. I submitted the original bug to
Philip wondering how someone could specify that something is both a Web Page
and a Blog.

> If you want multiple sets of properties to be reflected in a single Microdata
> item, mark up one of the sets as an item and use @itemref to refer to the rest.
> There's no need to do magic coalescing here.

If you do this:

<span itemref="foo" itemscope itemtype="http://schema.org/WebPage">
   <span itemprop="name">My Website and Blog</span>
</span>

<span itemref="foo" itemscope itemtype="http://schema.org/BlogPost"> 
   <a itemprop="url" href="http://example.org/post-4">permalink</a>
</span>

Then this is the JSON result per Philip's implementation:

{
  "items": [
    {
      "type": "http://schema.org/WebPage",
      "properties": {
        "name": [
          "My Website and Blog"
        ]
      }
    },
    {
      "type": "http://schema.org/Blog",
      "properties": {
        "url": [
          "http://example.org/blog"
        ]
      }
    }
  ]
}

Not only that, but the RDF is strange as well. At least with @itemid, the RDF
seems sensible, but the JSON is strange.

What am I missing?

-- 
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, 21 June 2011 20:39:40 UTC