- From: <mfhepp@gmail.com>
- Date: Sun, 12 Apr 2015 17:40:30 +0200
- To: jean-delahousse <delahousse.jean@gmail.com>
- Cc: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>, W3C Web Schemas Task Force <public-vocabs@w3.org>
Using the new Car type is fine, but it is ambigous about whether you describe a certain car, some identical cars, or a car model. If you want to make explit that you are talking of an actual car, use a multi-typed instance of schema:Car and schema:IndividualProduct. ----------------------------------- martin hepp http://www.heppnetz.de mhepp@computer.org @mfhepp > On 12 Apr 2015, at 16:16, jean-delahousse <delahousse.jean@gmail.com> wrote: > > Hello, > I am still quite confuse. In my use case I have the dealer point of view describing used cars in adds. > My idea was to use schema:Car, and hope the extension you proposed at http://sdo-property-value-and-cars.appspot.com/Car could be so I would be able to give more information about the mileage, the engine... of this individual used car. > I understand you propose to use IndividualProduct, but then how will I be able to use the very useful properties and class I find in http://sdo-property-value-and-cars.appspot.com/Car ? > By the way, thanks for your great work on car ontologies... > > Jean > > Jean Delahousse > Independent Consultant > Semantic web, taxonomies, ontologies, Linked Open Data > delahousse.jean@gmail.com > mob +33 6 01 22 48 55 > http://jean-delahousse.net > skype jean.delahousse > > 2015-04-12 15:28 GMT+02:00 mfhepp@gmail.com <mfhepp@gmail.com>: > An individual car (e.g. a used car on ebay is a schema:IndividualProduct. In an offer of new cars on a dealer page, these cars are typically a schema:SomeProducts. On the manufacturers' pages, a car model description is typically a schema:ProductModel. > > If you do not know or cannot say which of these three types a product is, you can use schema:Product. > > Martin > > ----------------------------------- > martin hepp http://www.heppnetz.de > mhepp@computer.org @mfhepp > > > > > > > > > On 12 Apr 2015, at 14:59, Jean delahousse <delahousse.jean@gmail.com> wrote: > > > > Hello > > Would you consider Vehicle to be an individualProduct? If you describe a used car would you use individualProduct or Vehicle ? > > Jean > > > > > > Jean Delahousse > > > > Independent Consultant > > Semantic technologies, LinkedIn Open Data > > delahousse.jean@gmail.com > > mob +33 6 01 22 48 55 > > http://jean-delahousse.net > > skype jean.delahousse > > > > Le 10 avr. 2015 à 15:52, ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org> a écrit : > > > >> 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 Sunday, 12 April 2015 15:41:01 UTC