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

Re: relating IndividualProduct to Product

From: <mfhepp@gmail.com>
Date: Mon, 13 Apr 2015 11:36:47 +0200
Cc: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>, W3C Web Schemas Task Force <public-vocabs@w3.org>
Message-Id: <B149472D-6804-41AD-A2D3-3C8DF6CF4C7D@gmail.com>
To: Thad Guidry <thadguidry@gmail.com>
On 10 Apr 2015, at 16:27, Thad Guidry <thadguidry@gmail.com> wrote:
> I would explain it as:
> http://schema.org/Product  is really "Product Category Offered".  You could also think "Product Class Offered" or "Product Group Offered" if it helps.

To be precise, schema:Product is a type for an entity that is one of the following 

a) a product model (datasheet, abstract ideal, ...), 
b) a specific, identifiable product (my iPhone 5), or 
c) a bag of not individually identifiable products.

and for which you cannot or do not want to specify whether it is a), b), or c).

Note that a), b), and c) are disjoint, so schema:Product should not be used to conflate e.g. a product and its make and model. If you expose information about a model and about some individual products, it is better to use two independent entities and link them properly using schema:model.


> beneath that you might have 5 laptops that you are offering to sell as a product... so each one....is an  http://schema.org/IndividualProduct
> Fairphone is definitely a http://schema.org/Product   each individual one (with it's unique IMEI code) is a http://schema.org/IndividualProduct
> You can also say:
> http://schema.org/IndividualProduct can be registered by users using their IMEI, Serial #, etc... something that uniquely ties that individual product to that customer.
> Only put things that are individually unique for a particular IMEI, Serial #, etc... against the http://schema.org/IndividualProduct 
> One thing that you can put against that http://schema.org/IndividualProduct  is actually a chipset firmware version ... because sometimes some folks get version A1 and later on in production the rest of the users might be getting version A2, etc... if you have that kind of data...that would go under http://schema.org/IndividualProduct  rather than saying ALL your Fairphones have version A2 by putting ia firmware version under http://schema.org/Product 
> Thad
> +ThadGuidry
> On Fri, Apr 10, 2015 at 8:52 AM, ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org> wrote:
> Hello,
> Looking at
> * http://schema.org/Product
>   "Any offered product or service. For example: a pair of shoes; a
> concert ticket; the rental of a car; a haircut; or an episode of a TV
> show streamed online."
> * http://schema.org/IndividualProduct
>   "A single, identifiable product instance (e.g. a laptop with a
> particular serial number)."
> I struggle to understand how I can specify for IndividualProduct just
> URI of the relevant Product. For example
> {
>   "@id": "https://www.fairphone.com/fairphone",
>   "@type": "Product",
>   "name": "The Fairphone"
> }
> {
>   "@id": "https://graph.wwelves.org/704e3a57-c09e-4846-b27a-d31854096572"
>   "@type": "IndividualProduct",
>   "name": "A Fairphone currently used by elf Pavlik",
>   "serialNumber": "2092043924022"
> }
> I understand that I could *duplicate* all the values of properties from
> * https://www.fairphone.com/fairphone
> on
> * https://graph.wwelves.org/704e3a57-c09e-4846-b27a-d31854096572
> But I would prefer to just reference it by URI and if needed embed
> information about Product resource in document describing
> IndividualProduct resource. And the generic data about Product would
> keep https://www.fairphone.com/fairphone as its subject.
> Thank you for help with understanding how to do that, or pointing out
> flaws in my approach.
> Cheers!
Received on Monday, 13 April 2015 09:37:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:49:40 UTC