Re: Schema.org External Enumerations mechanism

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.htmlallows 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

Steph.