W3C home > Mailing lists > Public > public-html-data-tf@w3.org > November 2011

Re: @itemid and URL properties in schema.org

From: Philip Jägenstedt <philipj@opera.com>
Date: Sat, 05 Nov 2011 19:51:38 +0100
To: public-html-data-tf@w3.org
Message-ID: <op.v4hlcckusr6mfa@localhost.localdomain>
On Sat, 05 Nov 2011 18:28:48 +0100, Jason Douglas  
<jasondouglas@google.com> wrote:

> On Fri, Nov 4, 2011 at 11:50 PM, Jeni Tennison  
> <jeni@jenitennison.com>wrote:
>> On 4 Nov 2011, at 21:28, Daniel Dulitz wrote:
>> > On Fri, Nov 4, 2011 at 14:17, Jeni Tennison <jeni@jenitennison.com>
>> wrote:
>> >> I'd love to know whether there are any consumers of schema.org markup
>> that are or plan to aggregate data across different sites to create a  
>> view
>> of information about the same thing, and indeed whether there are any
>> publishers who are generating schema.org markup with common @itemids or
>> urls…
>> >
>> > One could imagine that consumers like search engines might do  
>> something
>> like you describe. :-)
>> One could *imagine* so, yes :) I suppose I was fishing a bit because of
>> course if a search engine *was* doing that then it would picking up
>> information in different languages about those things, and it would  
>> want to
>> preserve the language of the information so that they could present
>> something useful back to the users. And that would be a good example for
>> Hixie on the bug on microdata language handling [1]...
> In as much as Hixie's response is it's "up to the vocabulary" and what  
> most
> everyone seems to want is the same -- use the existing DOM mechanisms, so
> overall page language with @lang for overriding specific nodes -- should  
> we
> just state that's what schema.org processors will do (I know of at least
> one implementer who had that expectation :-)?

The spec currently says: "It's important to note that there is no  
relationship between the microdata and the content of the document where  
the microdata is marked up."

To curry the extracted microdata with extra information from the DOM would  
be in violation of this, so if you want to use lang="" it'd be best to  
push for a spec change, IMHO.

Philip Jägenstedt
Core Developer
Opera Software
Received on Saturday, 5 November 2011 18:52:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:08:25 UTC