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

Re: additionalType property, vs extending Microdata syntax for multiple types

From: Martin Hepp <martin.hepp@ebusiness-unibw.org>
Date: Mon, 18 Jun 2012 23:34:26 +0200
Cc: Alexander Botero-Lowry <alexbl@google.com>, Dan Brickley <danbri@danbri.org>, "public-vocabs@w3.org" <public-vocabs@w3.org>, Peter Mika <pmika@yahoo-inc.com>, Jeni Tennison <jeni@jenitennison.com>, Ivan Herman <ivan@w3.org>, Guha <guha@google.com>
Message-Id: <5A2A3EC9-440F-4FE0-841D-E37C96E5D3FB@ebusiness-unibw.org>
To: Stéphane Corlosquet <scorlosquet@gmail.com>
Hi Stephane,

On Jun 18, 2012, at 11:13 PM, Stéphane Corlosquet wrote:
> I think this is OK but we need to be explicit that for this to work the primary type (itemtype) needs to be a part of schema.org or the additionalType predicate needs to be fully qualified.

OK, but this can be a one-liner in the spec.

> I'd like to see some markup example of what this discussion would lead to. Is there a page in the wiki? In particular, the "primary" vocabulary defined via @itemtype seems important. I agree with Alexander, looks like it might be better to recommend schema.org as primary vocab to avoid confusion.
> Other gotchas to be noted for microdata authors:
> - if properties of the external vocabulary need to be used, they need to be full URIs.
> - unlike the itemtype attribute which can contain multiple types, only one type can be defined at a time in each additionalType element. When specifying multiple additionalTypes for a data item, add an element for each additional type, e.g. 
>       <meta itemprop="additionalType" content="http://purl.org/goodrelations/v1#additionalType1"/>
>       <meta itemprop="additionalType" content="http://purl.org/goodrelations/v1#additionalType2"/>
Same here - useful comment that can be easily implemented via a one-liner in the spec.

Note 1: There are cases where both the primary and the secondary types come from schema.org. But that will work just fine.

Note 2: As far as I understand the MD spec, even the usage of external properties via fully qualified URIs must be permitted in the MD processing rules of the respective MD vocabulary. So while standard MD parsers will typically tolerate all possible external properties via fully qualified URIs, this has to be defined in the MD processing rules and is thus a vocabulary-specific MD feature.


martin hepp
e-business & web science research group
universitaet der bundeswehr muenchen

e-mail:  hepp@ebusiness-unibw.org
phone:   +49-(0)89-6004-4217
fax:     +49-(0)89-6004-4620
www:     http://www.unibw.de/ebusiness/ (group)
         http://www.heppnetz.de/ (personal)
skype:   mfhepp 
twitter: mfhepp

Check out GoodRelations for E-Commerce on the Web of Linked Data!
* Project Main Page: http://purl.org/goodrelations/
Received on Monday, 18 June 2012 21:34:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:48:46 UTC