W3C home > Mailing lists > Public > public-automotive@w3.org > November 2015

RE: Yet another standard for vehicle sensor data

From: Konopelko, Pavel (P.) <pkonopel@visteon.com>
Date: Tue, 3 Nov 2015 14:16:03 +0000
To: Philipp Hoschka <ph@w3.org>, Paul Boyes <pb@opencar.com>
CC: PHILIPPE COLLIOT <philippe.colliot@mpsa.com>, Adam Abramski <adam.m.abramski@intel.com>, "lbs (eg-lbs@mail.genivi.org)" <eg-lbs@mail.genivi.org>, "public-automotive@w3.org" <public-automotive@w3.org>, "public-autowebplatform@w3.org" <public-autowebplatform@w3.org>
Message-ID: <HE1PR06MB1210E79AF283FEEFB0DBC5DBC52B0@HE1PR06MB1210.eurprd06.prod.outlook.com>
Philipp,

Philipp Hoschka wrote on 2015-11-02:
> The specification being worked on seems to be here
> https://lts.cms.here.com/static-cloud-
> content/Company_Site/2015_06/Vehicle_Sensor_Data_Cloud_Ingestion_Interfa
> ce_Specification.pdf
> 
> Interesting work and we should definitely reach out - having said that,
> at list after a quick look, work seems somewhat orthogonal to API spec
> since it's about communication between the vehicle and the "cloud"
> ("analytic processing backend")
> 
> Quoting from "General Considerations"
> 
> Vehicles driving on the road are equipped with a magnitude of sensors.
> These Sensor Data may be transferred over any kind of technology from
> the vehicle to an Analytic Processing Backend. Between individual
> vehicles and the Analytic Processing Backend, an OEM-, or System
> Vendor- Backend may be located as a proxy. The Sensor Data Interface
> Specification defines the content of Sensor Data Messages and their
> encoding format as they are submitted to the Analytic Processing
> Backend. However, the specification 	may be used between other
> components as well. Sensor Data are submitted as messages with various
> type of content.

Here's specification does add a different dimension.  However, the section 2 includes also definitions of various vehicle attributes.  For example, the section 2.7.3 Light State of the document cited above overlaps in its scope with the section 6.12 LightStatus Interface [1] of the Vehicle Data.  Both define different types of exterior lighting (e.g., fog, hazard, high beam, etc.), but do this in slightly different ways.  Where the W3C draft only defines 'fog' attribute, Here's document defines 'FOGLAMP_FRONT' and 'FOGLAMP_REAR'.


Regards,
--Pavel Konopelko

[1] http://www.w3.org/2014/automotive/data_spec.html#lightstatus-interface

> On 11/2/2015 7:42 PM, Paul Boyes wrote:
> 
> 
> 	Pavel,
> 
> 	Thanks for posting this.  I believe this work is definitely
> related to the LBS and W3C Vehicle Info APIs.  It would seem we should
> engage them at very least to find out what they are doing.  Does anyone
> on the list have contacts related to this?
> 
> 
> 	Paul J. Boyes
> 	--------------------------------
> 	Mobile:   206-276-9675
> 	Skype:  pauljboyes
> 
> 
> 
> 
> 
> 		On Nov 2, 2015, at 2:09 AM, Konopelko, Pavel (P.)
> <pkonopel@visteon.com> wrote:
> 
> 		Philippe, Adam,
> 
> 		I just stumbled across this [1]:
> 
> 		"Representatives from electronic map provider HERE and
> companies active along the automotive value chain have met in Auburn
> Hills (USA) to push their joint activities to create a global interface
> format for vehicle sensor data. Such a standard would speed the
> development of automated driving worldwide.
> 
> 		Among the participants were representatives of carmakers Fiat
> Chrysler, Ford and General Motors, traffic data provider Inrix and
> navigation system manufacturer TomTom as well as tier one supplier
> Robert Bosch GmbH. The wide spectrum of participants highlights the
> significance of an industrywide collaboration in the area of digital
> mobility data, said HERE in a press release. The meeting in Auburn Hills
> followed up to an initial meeting in Berlin in July where 16 companies
> participated."
> 
> 		I wonder if this activity is or could potentially be related to the
> work that both GENIVI LBS EG and W3C already do in this area.
> 
> 
> 
> 		Regards,
> 		--Pavel Konopelko
> 
> 		[1] http://www.automotive-eetimes.com/en/standardisation-
> of-vehicle-data-makes-progress.html?cmp_id=7&news_id=222904516
> <http://www.automotive-eetimes.com/en/standardisation-of-vehicle-data-
> makes-progress.html?cmp_id=7&news_id=222904516>
> 
> 		--
> 		Visteon Innovation & Technology GmbH
> 		Sitz der Gesellschaft: Kerpen
> 		Registergericht: Köln HRB 71036
> 		Geschäftsführung:  Christian Feltgen, Radboud Vaessen,
> Andrea Eichelberg
> 
> 		CONFIDENTIALITY NOTICE: This e-mail message including attachments, if
> any, is intended only for the person or entity to which it is addressed
> and may contain confidential and /or privileged material. Any
> unauthorized review, use, disclosure or distribution is prohibited. If
> you are not the intended recipient, please contact the sender by reply
> e-mail and destroy all copies of the original message. If you are the
> intended recipient but do not wish to receive communications through
> this medium, please so advise the sender immediately.
> 
> 
> 
> 
> 
>
Received on Tuesday, 3 November 2015 14:16:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 24 October 2017 18:52:44 UTC