Re: relating IndividualProduct to Product

I'll daresay that was the plan from Apple marketing folks all along ;)

Regards,

John

On 10 Apr 2015, at 20:06, Thad Guidry <thadguidry@gmail.com> wrote:

> Yes iPhone is now a brand.
> 
> But it did not start off that way was my point.
> 
> 
> Thad
> +ThadGuidry
> 
> On Fri, Apr 10, 2015 at 1:03 PM, John Walker <john.walker@semaku.com> wrote:
> Hi Thad
> 
> One might argue iPhone to be the brand.
> 
> You may then have a hierarchy of schema:ProductModel (related via schema:isVariantOf) for example the 'base' iPhone 6 with variants of memory color etc. even those may have various manufacturing variants (different chipsets, firmware etc.).
> 
> An actual individual phone can then be related to the precise model via schema:model as mentioned by Niklas.
> 
> In some industries knowing the exact model can be very relevant due to manufacturing location which may affect export control regulations.
> 
> Regards,
> 
> John
> 
> On 10 Apr 2015, at 17:05, Thad Guidry <thadguidry@gmail.com> wrote:
> 
>> Niklas has another good approach.
>> 
>> That is where you treat "The Fairphone" as the concept of "The 1st Fairphone Model".  There might be further models later, or there may never be.
>> 
>> Before iPhone 6 there was just the iPhone (1st gen) and it's productID was actually lowercase "iphone"
>> 
>> 
>> Thad
>> +ThadGuidry
>> 
>> On Fri, Apr 10, 2015 at 10:01 AM, Thad Guidry <thadguidry@gmail.com> wrote:
>> I would suggest to use instead productID
>> 
>> but looks like we need to expand it's datatype ?
>> 
>> the productID is reserved for exactly your case (hard linking an individualProduct to a "product group" or productID...
>> however the problem is that the datatype is only text at the moment.
>> 
>> 
>> Thad
>> +ThadGuidry
>> 
>> On Fri, Apr 10, 2015 at 9:47 AM, Niklas Lindström <lindstream@gmail.com> wrote:
>> Hi,
>> 
>> You could use sdo:model to link to a sdo:ProductModel, like:
>> 
>>     {
>>       "@id": "https://www.fairphone.com/fairphone",
>>       "@type": "ProductModel",
>>       "name": "The Fairphone"
>>     }
>> 
>>     {
>>       "@id": "https://graph.wwelves.org/704e3a57-c09e-4846-b27a-d31854096572"
>>       "@type": "IndividualProduct",
>>       "model": {"@id": "https://www.fairphone.com/fairphone"},
>>       "name": "A Fairphone currently used by elf Pavlik",
>>       "serialNumber": "2092043924022"
>>     }
>> 
>> Cheers,
>> Niklas
>> 
>> 
>> On Fri, Apr 10, 2015 at 4:39 PM, ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org> wrote:
>> On 04/10/2015 04:27 PM, Thad Guidry 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.
>> >
>> > 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
>> Thanks Thad, makes sense but I still don't find answer to my question.
>> 
>> How exactly do I link an IndividualProduct
>> {
>>   "@id": "https://graph.wwelves.org/704e3a57-c09e-4846-b27a-d31854096572"
>>   "@type": "IndividualProduct",
>>   "name": "A Fairphone currently used by elf Pavlik",
>>   "serialNumber": "2092043924022"
>> }
>> 
>> to the Product
>> 
>> {
>>   "@id": "https://www.fairphone.com/fairphone",
>>   "@type": "Product",
>>   "name": "The Fairphone"
>> }
>> 
>> ?
>> 
>> 
>> >
>> >
>> >
>> > Thad
>> > +ThadGuidry <https://www.google.com/+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!
>> >>
>> >>
>> >
>> 
>> 
>> 
>> 
>> 
>