W3C home > Mailing lists > Public > public-vocabs@w3.org > September 2013

Re: Proposal: Audiobook

From: Karen Coyle <kcoyle@kcoyle.net>
Date: Wed, 25 Sep 2013 05:54:41 -0700
Message-ID: <5242DD11.9050508@kcoyle.net>
To: public-vocabs@w3.org

I realize that you've asked Dan and Guha, but I've been thinking about 
this same question (your a) b)). Without getting overly philosophical, I 
think we have a difference between "essence of the thing" - that is, 
what you need to describe it as "it" - and situational or functional 
description. Audiobook needs /Book and /Audiobook to describe it 'qua' 
audiobook, but situationally could also be a product. Since conceivably 
one could describe an audiobook apart from its being a product, then 
product isn't a necessary aspect of audiobook.

This fits in to some faceted classification models where there is a 
primary facet that is the essence of the thing, and then additional 
facets for those "accidental" or "situational" aspects that apply to 
particular instances. In classification these tend to be "universals" 
(place, time, etc.). They can be applied to any "thing" in the 
vocabulary. In the case of schema.org I could imagine using both 
/Product and /Accessibility as facets, allowing them to be used wherever 
they are relevant. There has been some discussion of terms for 
measurements, and that, too, is a likely candidate as a facet.

In a more structured vocabulary, facets would be aspects that would 
never stand alone, since they modify other concepts. That isn't the case 
today for /Product, but schema.org isn't strict so I don't see that as 
an issue.


On 9/25/13 12:40 AM, Martin Hepp wrote:
> Hi Karen,
> good that we have consensus.
> Dan, Guha: I think the issue of whether multi-type entities should be solved
> a) at markup time or
> b) in the vocabulary
> is of generic relevance - do you have an opinion on that?
> I think that for types that are not disjoint but also only loosely related (like an AudioBook used as a Product), it is much cleaner and flexible to recommend using both types at markup time.
> This also decouples the evolution of such needs / use cases from the evolution of the schema.org spec - site owners do not have to wait for an update to schema.org, and search engines can learn from the appearance of new patterns.
> Martin
> On Sep 24, 2013, at 9:07 PM, Karen Coyle wrote:
>> On 9/24/13 11:40 AM, Martin Hepp wrote:
>>> Hi Karen,
>>> as already posted earlier today:
>>> Simply use the offers property from Product or the itemOffered property from offer and make the AudioBook (or other object) of type AudioBook AND Product.
>> Yes, thanks, Martin. I saw that on your reply to Dan and that seems to be exactly what we need.
>> kc
>> --
>> Karen Coyle
>> kcoyle@kcoyle.net http://kcoyle.net
>> m: 1-510-435-8234
>> skype: kcoylenet
> --------------------------------------------------------
> 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/

Karen Coyle
kcoyle@kcoyle.net http://kcoyle.net
m: 1-510-435-8234
skype: kcoylenet
Received on Wednesday, 25 September 2013 12:55:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:29:31 UTC