W3C home > Mailing lists > Public > public-automotive@w3.org > June 2018

RE: [Minutes] Auto WG 2018-06-12

From: Björkengren, Ulf <ulf.bjorkengren@volvocars.com>
Date: Wed, 13 Jun 2018 08:12:36 +0000
To: "Streif, Rudolf" <rstreif@partner.jaguarlandrover.com>, T Guild <ted@w3.org>, public-automotive <public-automotive@w3.org>
Message-ID: <DB5P174MB0024F0A6100C68E06A2A06DFE07E0@DB5P174MB0024.EURP174.PROD.OUTLOOK.COM>
Hi,



The patch attached to this mail is my attempt to create a proof-of-concept of the idea to enhance VSS with the resource-element model from VIWI.

If you clone the latest from VSS GitHub (https://github.com/GENIVI/vehicle_signal_specification), you can then apply this patch.



I have added rbranch and element nodes to the Private.vspec file, copying Media Collections data from VIWI.



By following the instructions in the README file in the c_native directory, you will create a c native formatted tree containing all the legacy car VSS signals, and the new nodes on the Private branch, stored in the vss_rel_1.0.cnative file in the tools directory.

The instructions also builds a tree-parser that when executed reads the vss_rel_1.0.cnative file, and creates a double linked tree in memory, allowing traversal of the tree through commands provided to the parser.



There are some glitches in this code, I have e.g. seen some strings that are incorrectly zero terminated.



The referencing from an element to other elements, which I propose to do using the “id” property of the referenced elements, are not transferred correctly to the native tree. To fix it, I think it requires further modification in the vspec.py file, to begin with.



The child property declaration in the rbranch is done using one key per property descriptor, associated to a list of values of this property descriptor for all properties. This is different from how I showed it in the earlier mail sent to the list. I do not know if this is better, but this is how I managed to solve it when coding it.



A possible next step could be to add commands to the tree parser to add/remove element nodes, and to do (simple) queries. The tree parser UI is really bad, it could be improved a bit too.



BR

Ulf



Ulf Björkengren Ph. D.
Connectivity Strategist

M +4553562142
ulf.bjorkengren@volvocars.com<mailto:ulf.bjorkengren@volvocars.com>

VOLVO CAR CORPORATION
94014 Lund R&D Tech Center
Frederikskaj 10A
Copenhagen, Denmark
volvocars.com

From: Streif, Rudolf [mailto:rstreif@partner.jaguarlandrover.com]
Sent: den 12 juni 2018 16:48
To: T Guild <ted@w3.org>
Cc: public-automotive <public-automotive@w3.org>
Subject: Re: [Minutes] Auto WG 2018-06-12

Thank you, Ted.

Ulf and I have been discussing his proposal for VSS and bridging the gap between RSI for quite a while in email exchanges. I am on board extending VSS to support a model that allows using VSS data model and RSI data model interchangeably. VSS was intended to be simple and flexible supporting easy transformation into other data models. That's what the various converters are intended for.

Best regards,
:rjs

On Tue, Jun 12, 2018 at 7:19 AM, Ted Guild <ted@w3.org<mailto:ted@w3.org>> wrote:
https://www.w3.org/2018/06/12-auto-minutes<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2018%2F06%2F12-auto-minutes&data=02%7C01%7Culf.bjorkengren%40volvocars.com%7C1f4e392ef92a42aa0d9108d5d073a590%7C81fa766ea34948678bf4ab35e250a08f%7C0%7C0%7C636644117482390096&sdata=Bj1tYyT0aS5CSPJvXwHBIhqqmFCyCcog3fu%2B6NTKJAo%3D&reserved=0>

In particular please see and read the links from two topics both of
which we will delve into on subsequent calls.

Ulf's proposal

AGL analysis of VISS and ViWi

--
Ted Guild <ted@w3.org<mailto:ted@w3.org>>
W3C Automotive Lead
http://www.w3.org<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org&data=02%7C01%7Culf.bjorkengren%40volvocars.com%7C1f4e392ef92a42aa0d9108d5d073a590%7C81fa766ea34948678bf4ab35e250a08f%7C0%7C0%7C636644117482390096&sdata=L%2BrAFll1%2FGjfL2Q73jHukuA2N7ENO%2F4XNLToQ8tOXJs%3D&reserved=0>




--
Rudolf J Streif
System Architect
Oregon Software Technology Center

M: +1.619.631.5383
E:  rstreif@partner.jaguarlandrover.com<mailto:rstreif@partner.jaguarlandrover.com>

[https://teamtalk.jaguarlandrover.com/img/I-PACE.gif]


[http://www.jaguarlandrover.com/email/jlr.jpg]
UK: G/26/2 G02 Building 523, Engineering Centre, Gaydon, Warwick, CV35 ORR
US: 1419 NW 14th Ave, Portland, OR 97209
jaguar.com<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjaguar.com%2F&data=02%7C01%7Culf.bjorkengren%40volvocars.com%7C1f4e392ef92a42aa0d9108d5d073a590%7C81fa766ea34948678bf4ab35e250a08f%7C0%7C0%7C636644117482390096&sdata=LyIJbaeowGFiUyWSCepvsZktNIu%2FwcecRuZ9gjfATBY%3D&reserved=0> | landrover.com<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flandrover.com%2F&data=02%7C01%7Culf.bjorkengren%40volvocars.com%7C1f4e392ef92a42aa0d9108d5d073a590%7C81fa766ea34948678bf4ab35e250a08f%7C0%7C0%7C636644117482390096&sdata=QV%2Fi2sK%2F2YM5xd5L1RNpc5DMFSE8iKlukiSZLYOHPh8%3D&reserved=0>

Jaguar Land Rover Limited, Abbey Road, Whitley, Coventry CV3 4LF, UK
Registered in England No: 1672070

CONFIDENTIALITY NOTICE: This e-mail message including
attachments, is intended only for the person to whom it is addressed &
may contain confidential information. Any unauthorised 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.

Received on Wednesday, 13 June 2018 08:14:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:06:05 UTC