W3C home > Mailing lists > Public > public-vocabs@w3.org > April 2012

Re: Schema.org External Enumerations mechanism

From: Stéphane Corlosquet <scorlosquet@gmail.com>
Date: Wed, 25 Apr 2012 10:48:57 -0400
Message-ID: <CAGR+nnEWLq_BSJ7DFTwUobqEHfWO7Zj6wNOZ-EwnqfD4qU8Hqw@mail.gmail.com>
To: Dan Brickley <danbri@danbri.org>
Cc: jean delahousse <delahousse.jean@gmail.com>, Guha <guha@google.com>, Danny Ayers <danny.ayers@gmail.com>, public-vocabs@w3.org, Daniel Dulitz <daniel@google.com>, ivan@w3.org
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.

Steph.


>
> and http://www.jenitennison.com/blog/node/161
>
> (these also show some hacks and partially usable approaches, e.g.
> using properties called 'type' or itemref, but also why this is a hard
> problem given microdata's current design)
>
> Dan
>
>
Received on Wednesday, 25 April 2012 14:49:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 May 2012 06:49:02 GMT