W3C home > Mailing lists > Public > public-vocabs@w3.org > December 2014

Re: Automotive, EXIF, Property-Values

From: <mfhepp@gmail.com>
Date: Mon, 22 Dec 2014 20:46:54 +0100
Cc: Vicki Tardif Holland <vtardif@google.com>, W3C Web Schemas Task Force <public-vocabs@w3.org>
Message-Id: <39C61C45-BB85-41C7-BBE1-F35F0B7682DB@gmail.com>
To: Thad Guidry <thadguidry@gmail.com>
Hi Thad,
Good point! It should be straightforward to add such clarification to the schema:QuantitativeValue entity via schema:valueReference.

The textual definition of all or most of the properties already tries to address such issues:

E.g.

http://sdo-property-value-and-cars.appspot.com/tongueWeight

says:

The permited vertical load (TWR) of a trailer attached to the vehicle. Also referred to as Tongue Load Rating (TLR) or Vertical Load Rating (VLR).
Typical unit code(s): KGM for kilogram, LBR for pound
Note 1: You can indicate additional information in the name of the QuantitativeValue node.
Note 2: You may also link to a QualitativeValue node that provides additional information using valueReference.
Note 3: Note that you can use minValue and maxValue to indicate ranges.

So you can either use an existing URI to indicate a reference to the respective standard, as in

<div id="product" property="itemOffered" typeof="Car">
  <strong property="name">2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox</strong>
  <p property="description">2009 Volkswagen Golf V GTI MY09 Direct-Shift  (...)
  </p>
  <p><strong>Tongue Weight: </strong>
    <span property="tongueWeight" typeof="QuantitativeValue">
      <span property="value">250</span> 
      <meta property="unitCode" content="KGM">kg
      (according to <a property="valueReference" href="http://standards.sae.org/wip/j2807/">SAE J 2807 Performance Requirements for Determining Tow-Vehicle Gross Combination Weight Rating and Trailer Weight Rating)</a>
      </span>
    </span>
  </p>
..
</div>

or define a schema:QualitativeValue or schema:StructuredValue to provide this link:

<div id="product" property="itemOffered" typeof="Car">
  <strong property="name">2009 Volkswagen Golf V GTI MY09 Direct-Shift Gearbox</strong>
  <p property="description">2009 Volkswagen Golf V GTI MY09 Direct-Shift  (...)
  </p>
  <p><strong>Tongue Weight: </strong>
    <span property="tongueWeight" typeof="QuantitativeValue">
      <span property="value">250</span> 
      <meta property="unitCode" content="KGM">kg
      (according to <span property="valueReference" typeof="QualitativeValue">
        <meta property="name" content="J2807"> 
		<span property="description">SAE J 2807 Performance Requirements for Determining Tow-Vehicle Gross Combination Weight Rating and Trailer Weight Rating"</span>
		<link property="url" href="http://standards.sae.org/wip/j2807/" />
      </span>
    </span>
  </p>
..
</div>

Of course, we can also use WikiData URIs for referencing standard procedures for measuring certain characteristcs.

Does that cover your requirements?

Martin

-----------------------------------
martin hepp  http://www.heppnetz.de
mhepp@computer.org          @mfhepp







On 22 Dec 2014, at 20:05, Thad Guidry <thadguidry@gmail.com> wrote:

> RED FLAG - I have some deep concerns in one area regarding the description of weights throughout this schema proposal.
> 
> We need to be much more clear about the use of the word "permitted" in the description of weights within this Schema for the safety and protection of consumers and human life.
> 
> Of particular concern for me and consumers is the adherence of industry standards and those that are not followed closely or not at all by manufacturers.
> Manufacturer claims are sometimes not the same claim as an industry standard, such as SAE J2807  http://standards.sae.org/wip/j2807/
> 
> Here is an example of some of the issues involved: http://www.autonews.com/article/20130211/OEM03/302119913/pickup-truck-towing-standard-isnt-standard
> 
> I would like the schema to be very clear on the designation of "permitted" ... by whom ?  A manufacturer or government regulation or industry regulation ?
> 
> I would like to make this clear perhaps by having an enum to capture the "permitted by whom" while not taking sides with either the manufacturer claims or the government / industry claims.
> 
> Thoughts ?
> 
> 
> Thad
> +ThadGuidry
> 
> On Mon, Dec 22, 2014 at 10:40 AM, mfhepp@gmail.com <mfhepp@gmail.com> wrote:
> Hi Vicky:
> 
> Thanks! See inline comments.
> Martin
> -----------------------------------
> martin hepp  http://www.heppnetz.de
> mhepp@computer.org          @mfhepp
> 
> 
> On 22 Dec 2014, at 17:30, Vicki Tardif Holland <vtardif@google.com> wrote:
> 
> > Hi Martin,
> >
> > I have a couple quick questions about the new Vehicle schema.
> >
> > 1. What is the difference between tongueWeight and trailerWeight?
> 
> tongueWeight is the maximum weight your trailer hitch can handle of the downward force exerted on it by the trailer's tongue (the arm that extends from the trailer that couples with the tow vehicle's receiver) (snippet taken from http://auto.howstuffworks.com/auto-parts/towing/vehicle-towing/maneuvers/dead-weight-towed-weight1.htm). In essence, how much your trailer can push down the pulling car without lifting its wheels.
> 
> trailerWeight is the maximum weight is of a fully loaded trailer, so in essence how much the pulling vehicle + trailer hitch can pull in driving direction.
> 
> 
> > 2. Vehicle has an interiorColor property. Would you advise using the "color" property for the exterior color?
> Yes.
> 
> > 3. There is a lot of detail here. Do you have examples that can be published on schema.org to help guide users?
> 
> Yes, they are already included in
> 
> http://sdo-property-value-and-cars.appspot.com/Car
> 
> Please scroll down to examples or see here
> 
>     https://github.com/mfhepp/schemaorg/blob/property-value-and-cars/data/sdo-automobile-examples.txt
> 
> Again, thanks for looking at the proposal. Please do not hesitate to contact me if you have further questions.
> 
> Martin
> 
> 
> >
> > Cheers,
> > Vicki
> >
> >
> > Vicki Tardif Holland | Ontologist | vtardif@google.com
> >
> >
> > On Wed, Dec 17, 2014 at 5:01 AM, mfhepp@gmail.com <mfhepp@gmail.com> wrote:
> > Dear all:
> >
> > Based on many bilateral discussions, I have updated the proposal for cars and other vehicles [1] and the property-values mechanism for product feature data [2].
> >
> > A live demo is up and running at
> >
> >     http://sdo-property-value.appspot.com/
> >
> > The proposal updates schema:Car (new:http://sdo-property-value.appspot.com/Car) and schema:Vehicle (new: http://sdo-property-value.appspot.com/Vehicle). It incorporates and is aligned with the Yandex proposal for cars [3] (Yuliya and I analyzed the overlap).
> >
> > A Github fork based on sdo-venkman is available at
> >
> >     https://github.com/mfhepp/schemaorg/tree/property-value-and-cars
> >
> > I have already created a respective pull-request to https://github.com/danbri/schemaorg/tree/sdo-venkman.
> >
> > In effect, it adds the following elements:
> >
> > 1. Types for common vehicle categories
> > --------------------------------------
> >
> >     http://sdo-property-value.appspot.com/MotorizedRoadVehicle
> >     http://sdo-property-value.appspot.com/Truck
> >     http://sdo-property-value.appspot.com/Van
> >     http://sdo-property-value.appspot.com/MotorizedBicycle
> >     http://sdo-property-value.appspot.com/BusOrCoach
> >     http://sdo-property-value.appspot.com/Motorcycle
> >     http://sdo-property-value.appspot.com/Bike
> >     http://sdo-property-value.appspot.com/Watercraft
> >     http://sdo-property-value.appspot.com/Boat
> >     http://sdo-property-value.appspot.com/MotorBoat
> >     http://sdo-property-value.appspot.com/SailingBoat
> >
> > plus a few utility types for quantitative values.
> >
> > 2. Properties for common, vendor-independent car features
> > ---------------------------------------------------------
> > For a list, see here:
> >
> >     http://www.w3.org/wiki/WebSchemas/Vehicles#New_Properties
> >
> > 3. A type for exposing semi-structured product and place feature information
> > ----------------------------------------------------------------------------
> >
> >     http://sdo-property-value.appspot.com/PropertyValue
> >
> > plus three new properties for this type:
> >
> >     additionalProperty
> >     propertyID
> >     unitText
> >
> > plus slight modifications to unitCode, minValue, maxValue, value, and valueReference:
> >
> >     https://www.w3.org/wiki/WebSchemas/PropertyValuePairs#Changes_to_Existing_Elements
> >
> > 4. A mechanism for exposing standardized and vendor-specific EXIF image meta-data to schema:ImageObject
> > -------------------------------------------------------------------------------------------------------
> >
> > This happens by simply including schema:PropertyValue to the range of schema:exifData, see
> >
> >      http://sdo-property-value.appspot.com/ImageObject
> >
> > Examples for the use for EXIF meta-data are here:
> >
> >     https://www.w3.org/wiki/WebSchemas/PropertyValuePairs#ImageObject:_EXIF_Meta-data
> >
> > See also
> >     https://www.w3.org/wiki/WebSchemas/PropertyValuePairs#EXIF_Image_Meta-data
> >
> >
> > The proposal comes with a full set of examples in Microdata, RDFA, and JSON-LD; only the property-value examples are currently given in Microdata only. I can add them on other syntaxes if needed.
> >
> > I hope that this final specification addresses all issues from the previous discussions and can be agreed upon.
> >
> > Best wishes
> > Martin Hepp
> >
> >
> > [1] https://www.w3.org/wiki/WebSchemas/Vehicles
> > [2] https://www.w3.org/wiki/WebSchemas/PropertyValuePairs
> > [3] http://help.yandex.ru/webmaster/supported-schemas/review-car.xml
> >
> > -----------------------------------
> > martin hepp  http://www.heppnetz.de
> > mhepp@computer.org          @mfhepp
> >
> >
> >
> >
> >
> >
> >
> >
> >
> 
> 
> 
Received on Monday, 22 December 2014 19:47:09 UTC

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