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

Re: Multiple types from different vocabularies (ACTION-7)

From: Gregg Kellogg <gregg@kellogg-assoc.com>
Date: Mon, 10 Oct 2011 15:43:46 -0400
To: Jeni Tennison <jeni@jenitennison.com>
CC: Martin Hepp <martin.hepp@ebusiness-unibw.org>, Evan Sandhaus <sandhes@nytimes.com>, Edward O'Connor <eoconnor@apple.com>, Philip Jägenstedt <philip@foolip.org>, "public-html-data-tf@w3.org" <public-html-data-tf@w3.org>
Message-ID: <2AB8D5EC-EFDC-446B-9E54-FF0084E7D09F@greggkellogg.net>
On Oct 10, 2011, at 12:23 PM, Jeni Tennison wrote:

> Martin, Evan, Ted, Philip, all,
> 
> After the schema.org workshop, Hixie opened a bug on supporting multiple item types in microdata [1], if they share the same vocabulary. I'm hoping to get some input to see whether we want to make any comment on that bug.
> 
> Martin / Evan: What you are aiming to do with GoodRelations / rNews and schema.org? Are you recommending people just use the appropriate schema.org types, just the more specialised types from GoodRelations / rNews, or use both at the same time?
> 
> Ted / Philip: Do you have any feeling about whether browsers might end up natively supporting the microdata vocabularies from the WHATWG HTML spec [2] (eg to give better integration with people's address books or calendars) or are they likely to support equivalent types/properties from the schema.org vocabulary, or do nothing natively with embedded data?
> 
> Anyone else have any thoughts about multiple types? It seems to me that if our general argument is that consumers should state what they consume and publishers should produce data in multiple formats to match those requirements [3][4], then we're encouraging people to publish with multiple vocabularies, which implies multiple types coming from different vocabularies.

If the content model for @itemtype was something like DOMTokenList instead of DOMString, it would could allow multiple values. I actually updated my implementation to allow for this, using the first listed type to resolve non-URI @itemprop names.

# If the _item_ has an @itemtype attribute, split on spaces, with the order preserved but with duplicates removed (leaving only the first occurance of each type)
# For each _type_ extracted from @itemtype which is an absolute URI, generate the following triple:

	subject: _subject_
	predicate: http://www.w3.org/1999/02/22-rdf-syntax-ns#type
	object: _type_

# Set _type_ to the first type from @itemtype which is an absolute URI, if there is one, otherwise to _fallback type_ if not empty.
...

> Thanks,
> 
> Jeni 
> 
> [1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=14233
> [2] http://www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html#mdvocabs 
> [3] http://lists.w3.org/Archives/Public/public-html-data-tf/2011Oct/0024.html
> [4] http://lists.w3.org/Archives/Public/public-html-data-tf/2011Oct/0025.html
> -- 
> Jeni Tennison
> http://www.jenitennison.com
> 
> 
Received on Monday, 10 October 2011 19:44:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 10 October 2011 19:44:24 GMT