W3C Automotive and Web Platform Business Group May 29, 2013

INTEL CONFIDENTIAL 2 SSG System Software Division Practicals Meeting Minutes  IRC - with a web browsers and we can specify the channel name "#auto" on that portal page to join the channel  Need volunteers to take notes for each topic area (primary/secondary):  Intros (?/?)  Public v Private (?/?)  IVI to Smartphone API (?/?)  Vehicle Data Web API Specs (?/?)  Scope of Spec (?/?)  Roles and Responsibilities/Process/Organization of a Spec (?/?)  Intelligent Transport (?/?)  Next Gen Web Navigation APIs (?/?)  Next Steps (?/?)

INTEL CONFIDENTIAL 3 SSG System Software Division Introductions Chairs  Andy Gryc - QNX  Adam Abramski - Intel Introductions  Name  Position  Company

INTEL CONFIDENTIAL 4 SSG System Software Division Public vs Private  Meeting agenda  Private  Public  Meeting minutes  Private  Public  Technical/Use Case conversations  Private  Public  Reports (including draft specs, test suites and draft use cases)  Private  Public  Discussion  Public - Private -

INTEL CONFIDENTIAL 5 SSG System Software Division Charter Goals  Create specs, starting with Vehicle Data  Create conformance tests to cover new specs (optional)  Provide use cases and other reports to identify add’l needed standards work & to drive successful automotive web deployments

INTEL CONFIDENTIAL 6 SSG System Software Division IVI to Smartphone API - KDDI

INTEL CONFIDENTIAL 7 SSG System Software Division Vehicle Data Web API Specs  QNX (30 min)  Tizen (30 min)  GENIVI/LGE (30 min)  Webinos – No presentation  Spec -  Previous presentation from the W3C Automotive and Web Workshop Fall 2012  Q&A - Discussion

INTEL CONFIDENTIAL 8 SSG System Software Division Sound and Vehicle Data Presentation - ACCESS

INTEL CONFIDENTIAL 9 SSG System Software Division Scope of the Spec  Spec does not include an implementation as there is proprietary issues in the protocol used by CAN and MOST data networks  What is the contentious vehicle data that should NOT be exposed in this first version of the draft spec?  What about reading vs writing vehicle data?  Discussion  Food for thought:  Which spec do we start from or do we start it from scratch or use a combination?  What about starting with OBDII since it’s a gov’t regulation?

INTEL CONFIDENTIAL 10 SSG System Software Division Roles and Responsibilities All participants are encouraged to Attend group’s formal meetings Follow and participate in mailing list (+IRC) discussions – all technical discussions should happen on the group’s mailing list(s) Review draft proposals, propose changes, fix spec bugs Editor’s responsibilities Edits the spec based on group consensus Follows group’s technical discussion and integrate proposed changes Makes sure someone in the group responds to comments submitted to the spec(s) Practicalities Each spec needs at least one active editor The group agrees on the work mode such as “commit-then-review” vs. “review-then-commit” together with the editor(s)

INTEL CONFIDENTIAL 11 SSG System Software Division Process 1.Describe the problem to solve, list use cases 2.List requirements for each use case 3.Share the use cases and requirements with the group, adjust based on feedback from the group 4.Study existing proposals, come up with new proposals, keep the proposal as simple as possible and defer “nice to haves” for later 5.Evaluate how well the proposals address the use cases and meet the requirements, choose/create/merge a proposal that the group thinks is the best fit 6.Write draft spec, tests, publish spec snapshot(s) Finally: “Some (but not all) Business Group Specifications are expected to serve as input to a Working Group.”

INTEL CONFIDENTIAL 12 SSG System Software Division Top-level Organization of a Spec Introduction – an overview of the technology Conformance – how conformance is determined in the spec E.g. “Everything in this specification is normative except for diagrams, examples, notes and sections marked non-normative. […] A user agent must also be a conforming implementation of DOM4.” Terminology – definitions of terms used E.g. “The term user credentials for the purposes of this specification means cookies, HTTP authentication, and client-side SSL certificates.” Content Normative – requirements and definitions Informative – everything else References Acknowledgements Specs should follow the patterns and style established by other specs.

INTEL CONFIDENTIAL 13 SSG System Software Division Top-level Organization of a Spec: Content (detailed) Normative Interface definition – Web APIs are defined using Web IDL, e.g.: Requirements and definitions “The XMLHttpRequest(options) constructor MUST run these steps” Use RFC2119 terms must, should, may Normative must statements should be testable Informative Everything that is not normative, e.g. use cases, code examples, diagrams Must not use RFC2119 keywords, use “can” or “is” instead [Constructor(optional XMLHttpRequestOptions options)] interface XMLHttpRequest : XMLHttpRequestEventTarget { // event handler attribute EventHandler onreadystatechange; // … };

INTEL CONFIDENTIAL 14 SSG System Software Division Examples and Tools for Specs  Draft spec should follow existing W3C specs like:  (Runtime and Security Model for Web Apps)  (Web Speech API from a W3C Community Group)  (Geolocation API)  Good tool to use as an editor of a spec: design-cookbook/ design-cookbook/  Helps to understand “how to use WebIDL to design Web APIs”  It’s not officially supported or endorsed by W3C but it’s still a good reference doc  Food for thought  Think about your interest in being an editor

INTEL CONFIDENTIAL 15 SSG System Software Division Next Gen Navigation Web APIs - Intel

INTEL CONFIDENTIAL 16 SSG System Software Division ISO Intelligent Transport Systems – Vehicle Interface - JARI

INTEL CONFIDENTIAL 17 SSG System Software Division Next Steps  Looking beyond vehicle data, what’s to tackle next?  Recommend looking at all of the papers and presentations from the W3C Automotive and Web Workshop last fall:  UI Constraints (driver safety, distraction and adjusting the GUI)  Application Security and Safety (handling different input controls)  Navigation (see W3C Geolocation API)  Voice Recognition (see W3C Web Speech API)  Audio Policy Management (addressing policy and management of multiple sinks and sources)  List of potential areas (15 of them) to focus on next:   Should we break into task forces to research various topics?  Example model we could follow:  Task force area specific Wiki pages:  Conf Calls  How often should we have them? Every 2 weeks, every month?  Next F2F? If so, where? When?  Decisions should be discussed and made online and through the distro list

INTEL CONFIDENTIAL 18 SSG System Software Division Group Photo