Re: @itemid and URL properties in schema.org

On Fri, 04 Nov 2011 20:31:27 +0100, Jason Douglas  
<jasondouglas@google.com> wrote:

>    - As few concepts as possible.  As Guha commented on a previous  
> thread,
>    we've generally found that the more syntactical options given to
>    webmasters, the higher the error rate.  Not including itemid in the  
> docs
>    meant we only had to talk about itemscope, itemtype, itemprop (and  
> itemref).
>    - itemid as an attribute is a bit awkward in real-world markup as
>    there's no way to re-use the URL value of an existing anchor, which  
> is a
>    very common use case.  You end up having to repeat the URL.

[...]

> So to throw a strawman out there, maybe we could:
>
>    1. State on schema.org that Thing/url is equivalent to itemid and  
> either
>    is accepted.

If the goal is to have as few concepts as possible and itemid would be  
equivalent to Thing/url, why not just outright disallow itemid? Otherwise,  
you have two ways to express the same thing and also need to define  
exactly how to process it. For example, is

<span itemscope itemtype="http://schema.org/Thing"  
itemid="http://url.to/a/thing">
   <link itemprop="url" href="http://url.to/b/thing">
</span>

equivalent to

<span itemscope itemtype="http://schema.org/Thing">
   <link itemprop="url" href="http://url.to/a/thing">
   <!-- itemid overrides all url properties, as if they did not exist -->
</span>

,

<span itemscope itemtype="http://schema.org/Thing">
   <link itemprop="url" href="http://url.to/a/thing">
   <!-- itemid considered the first url property -->
   <link itemprop="url" href="http://url.to/b/thing">
</span>

or

<span itemscope itemtype="http://schema.org/Thing">
   <link itemprop="url" href="http://url.to/b/thing">
   <link itemprop="url" href="http://url.to/a/thing">
   <!-- itemid considered the last url property -->
</span>

?

-- 
Philip Jägenstedt
Core Developer
Opera Software

Received on Saturday, 5 November 2011 18:47:34 UTC