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

API Refactor Meeting

From: Paul Boyes <pb@opencar.com>
Date: Wed, 15 Jul 2015 21:53:41 +0000
To: 이원석 <wonsuk.lee@etri.re.kr>, Rees Kevron <kevron.m.rees@intel.com>, Dave Jensen <david@jensen47.com>, Qing An <anqing.aq@alibaba-inc.com>, "Gavigan, Kevin" <kgavigan@jaguarlandrover.com>, Adam Crofts <acrofts1@jaguarlandrover.com>, 박종선(Justin Park) <jongseon.park@lge.com>
CC: public-automotive <public-automotive@w3.org>, Adam Abramski <adam.m.abramski@intel.com>, T Undecl <ted@w3.org>, Kazuyuki Ashimura <ashimura@w3.org>
Message-ID: <69FDE891-1819-419B-8853-1A111BF69930@opencar.com>
Yesterday we had a good discussion of Issue #37 (https://github.com/w3c/automotive/issues/37).  Thanks to everyone who attending and provided input.  In summary there are essentially 3 API styles presented.   One being the style currently in the spec.  The primary question to the group is should we refactor to one of the new API styles or stick with what we have.  No conclusion was reached in the meeting.  However the following action items are on the table to continue our analysis/discussion:

—Run the issue by the Technical Architecture Group (I have reached out to them) and get their opinion.
—Get feedback from JLR as they have been involved with implementing the current spec (I have reached out to them).
—Create a document that summarizes the issue providing pros and cons for each style (Dave Jensen and Kevron Rees will start this document) and work with editors to get into GitHub.
—Search other specs for examples and provide feedback (This is a challenge to the whole group.)

Please let me know if you have any questions or comments.  We can discuss in next weeks phone meeting.


Paul J. Boyes
Mobile:   206-276-9675
Skype:  pauljboyes

Received on Wednesday, 15 July 2015 21:54:13 UTC

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