Re: Schema.org External Enumerations mechanism

On Apr 25, 2012, at 10:47 AM, Stéphane Corlosquet wrote:

> Adrian,
> 
> On Wed, Apr 25, 2012 at 10:56 AM, Adrian Giurca <giurca@tu-cottbus.de> wrote:
> Hello,
> 
> On 4/25/2012 4:48 PM, Stéphane Corlosquet wrote:
>> 
>> 
>> On Wed, Apr 25, 2012 at 10:30 AM, Dan Brickley <danbri@danbri.org> wrote:
>> On 25 April 2012 16:04, jean delahousse <delahousse.jean@gmail.com> wrote:
>> > Hello,
>> >
>> > Just to be sure, you say it is not possible to express this :
>> >
>> >  <p vocab="http://schema.org/" resource="#manu"
>> > typeof="Person wiki:Programmer"> .
>> >
>> > whith microdata as microdata does not support multiple types ?
>> >
>> > It is too bad because it exactly answers the needs a) to use high level
>> > classes inside schema.org to have a shared classification, b) to be able to
>> > use any external vocabularies to get a more detailed or more domain oriented
>> > description.
>> 
>> That's my understanding, e.g. per
>> http://openspring.net/blog/2011/06/10/microdata-multiple-vocabularies
>> 
>> It should be clarified that after the schema.org workshop last Sept, hixie changed microdata to support multiple types as long as they belong to the same microdata vocabulary. The example above remains unfeasible in microdata though since it uses types from multiple vocabs.
> Can you share a link, because  http://www.w3.org/TR/html5/microdata.html allows for multiple properties (the value of @itemprop is a list of tokens) but not for types (@itemtype is an absoulte  URL )
> 
> I guess this change hasn't made it to w3.org yet. You can see it here though: http://www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html#item-types

It's here in W3C space as of 3/29: http://www.w3.org/TR/2012/WD-microdata-20120329/#item-types.

It's interesting to note, that even though the microdata content model does not allow for this, following the processing rules specified in the Microdata to RDF note would end up producing triples with types from multiple vocabularies anyway. It's just not officially part of the microdata spec, and wouldn't have the expected results in the JSON representation.

See the processing rules at http://www.w3.org/TR/2012/WD-microdata-rdf-20120112/#generate-the-triples.

Gregg

> Steph.
>

Received on Wednesday, 25 April 2012 18:21:10 UTC