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

Re: Redefine and reuse?

From: Karen Coyle <kcoyle@kcoyle.net>
Date: Wed, 24 Jul 2013 06:15:47 -0700
Message-ID: <51EFD383.2090507@kcoyle.net>
To: public-vocabs@w3.org
This is a great example that allows us to get back to the original 
question, which I think is one for this group. When one encounters a 
property or class that one would like to use in a way that is "not 
exactly as initially meant" - what is the preferred approach?

We could:
1) use it, and rely on documentation to clarify our community's use
2) redefine it, so that it fits better into our use case
3) create a super-property or class and a new subproperty or class
4) create a new, unrelated property within our own community space

If there is no overall preference, then does this group want to 
entertain ad hoc suggestions for changes to definitions of properties 
and classes?

kc

On 7/24/13 12:59 AM, Martin Hepp wrote:
> The serialNumber is in theory meant as a unique item identifier assigned at production or market entrance time, like the serial number of a digital camera, the Vehicle Identification Number of a car, etc.
>
> A library-specific identifier (like shelf locator ID) is not really a serial number. I do not see major problems with using serialNumber this way, but it is not exactly as initially meant.
>
> Martin
>
> On Jul 24, 2013, at 9:37 AM, Owen Stephens wrote:
>
>> Hi Karen,
>>
>> How would you see serialNumber mentioned by Wes mapping against library item identifiers?
>>
>> Owen
>>
>> Owen Stephens
>> Owen Stephens Consulting
>> Web: http://www.ostephens.com
>> Email: owen@ostephens.com
>> Telephone: 0121 288 6936
>>
>> On 24 Jul 2013, at 00:15, Karen Coyle <kcoyle@kcoyle.net> wrote:
>>
>>> Wes, I admit that some of this was a bit cryptic - were you suggesting the properties below as a solution? We have looked carefully at the full range of schema.org, in particular /Product and /Offer and are aware of these. They do not, unfortunately, satisfy our use case. Should "/Offer" be expanded to be more than "offer for sale" then the concept of a "merchant-specific identifier for a product or service" fits even though the actual term "Stock Keeping Unit (SKU)" is not used in the library community. None of the others represent a local number for an individual item (not product, but single item).
>>>
>>> Thanks,
>>> kc
>>>
>>> On 7/23/13 2:45 PM, Wes Turner wrote:
>>>> Need:
>>>>
>>>>   * lookup/index books by a unique (local?) SKU number
>>>>
>>>> WorldCat
>>>> ----------
>>>>
>>>> WorldCat OCLC supports RDF as RDF/XML, JSON, Turtle, Triples
>>>> http://redd.it.com/1fm5z3/#cabsejm
>>>>
>>>> (e.g Harry Potter as Turtle)
>>>> http://www.worldcat.org/oclc/41266045.ttl
>>>>
>>>> [... semantic web books]
>>>> http://redd.it/1g7ehd/#caj4d3ni
>>>>
>>>>
>>>> Schema.org
>>>> ------------
>>>> * http://schema.org/docs/full.html
>>>> * http://schema.rdfs.org/all.ttl
>>>>
>>>>
>>>> schema:Thing > schema:CreativeWork > schema:Book
>>>>
>>>>     /isbn -- string literal. ISBN-(10 &&|| 13 ?) number.
>>>>
>>>>     [/sku -- string literal. SKU number] -> schema:Product/sku
>>>>
>>>> schema:Thing > schema:Product
>>>>
>>>>     /gtin13 -- ISBN-13 / EAN UCC-13 / 0UPC-12
>>>>     /gtin14 -- GTIN-14
>>>>     /gtin8  -- EAN UCC-8
>>>>
>>>>     /productID -- The product identifier, such as ISBN.
>>>>                   For example: <meta
>>>>                       itemprop='productID'
>>>>                       content='isbn:123-456-789'/>.
>>>>
>>>>     /sku -- The Stock Keeping Unit (SKU),
>>>>             i.e. a merchant-specific identifier for a product or service,
>>>>             or the product to which the offer refers.
>>>>
>>>>
>>>> schema:Thing > schema:Product > schema:IndividualProduct
>>>>
>>>>      /serialNumber -- The serial number or any alphanumeric identifier
>>>>                       of a particular product.
>>>>                       When attached to an offer, it is a shortcut for
>>>>                       the serial number of the product included in the offer.
>>>>
>>>>
>>>
>>> --
>>> Karen Coyle
>>> kcoyle@kcoyle.net http://kcoyle.net
>>> ph: 1-510-540-7596
>>> 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
ph: 1-510-540-7596
m: 1-510-435-8234
skype: kcoylenet
Received on Wednesday, 24 July 2013 13:16:16 UTC

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