html5 and the open web platform for automotive - w3.org · develop vehicle api spec until end of...
TRANSCRIPT
HTML5 and The Open
Web Platform for
Automotive
Dr. Philipp Hoschka<[email protected]>
W3C Deputy Director
This project is funded by the European Union through the
Seventh Framework Programme (FP7/2010-2012) under
grant Webinos
W3C • Mission: Leading the Web to its Full Potential
• Directed by Web inventor Tim Berners-Lee since 1994
• 20+ years track record of success
• Standards: HTML5, Web APIs, XML, Web Services, RDF, VoiceXML, ...
• Consortium with ~380 members
• International organization (Europe, US, Japan, China)
W3C Value Proposition
• “One Web”: Desktop, Mobile, TV,
Automotive, …
• Neutral forum for collaboration across
industries, ecosystems and communities
• Royalty-free patent policy
• Active, expert staff participating in work
• 380 members: Broad industry and academic
participation
Business Case for HTML5
• HTML5: From Web Pages to Web Applications
• Overcome Fragmentation
• Cross OS: No native code for different
appstores, platforms, …
• Cross device: Financial Times HTML5 only,
dropped iphone app
• More developers, less costly to develop
The Open Web Platform
Why Automotive in W3C?
• Whole Web ecosystem represented
• IT (Adobe, Apple, Gemalto, Google, HP, IBM, Microsoft, Mozilla, IBM, …)
• Mobile (ATT, Vodafone, Orange, KDDI, …)
• TV (BBC, Bloomberg, NBC, Netflix, SkyTV, …)
• …
• Mobile, TV, … history of ecosystem-only standard effort failures outside W3C
• Web developers watch W3C
• Royalty-free standards
Automotive and W3C:
History • Started with Webinos Project
• Presentation to Genivi General Assembly – Paris, April 2012
• Held Workshop in Rome on November 2012 to hear from Industry
• Launched W3C Automotive & Web Platform Business Group in February 2013
• Genivi joined W3C
• First meeting hosted by Genivi in Barcelona – April 2013
• Second meeting hosted by Automotive Linux Summit in Tokyo – May 2013
W3C Automotive and Web
Business Group Chairs
Adam Abramski (Intel)
Andy Gryc (QNX)
86 individuals
39+ companies
7th largest group out of 129 W3C business and
community groups
Members
Group Work Items • Develop Vehicle API spec until end of 2013
• Maintain repository of ongoing W3C work relevant to Automotive (16)
• Offline Applications, Authentication, Web Application Security, …
• Contacts, Messaging, Telephony, Speech…
• Multimedia, Navigation, Notifications, Flow Control …
• Emerging topics
IVI/Phone Interface (Booths: Ixonos, Obigo, …)
Navigation
Application Security and Safety
Voice Recognition, Speech, Text to Speech, …
Vehicle API Spec Existing specs considered
GENIVI
Tizen/Intel
QNX
Webinos
Vehicle data
Vehicle type, fuel type, speedometer, …
250+ data points (Genivi)
What vehicle data that should be exposed in this first version of the draft spec?
What about reading (get) vs writing (set) vehicle data?
Automotive W3C Standard
Roadmap • Business Group
• No standards
• Report on Vehicle API specification
• Reports on other topics: Gap analysis, …
• Non W3C members can join for small fee
• Working Group
• Does actual standards (HTML5 etc.)
• Participation requires full W3C membership
Summary
• Web technology is strategic for Automotive
• W3C automotive activity has just started
• Vehicle API focus (Target Dec 2013)
• Upcoming: Vehicle/Mobile Interface, Navigation, Speech, …
• Early days - Great time to get involved!
Background Material
HTML5 Roadmap
Specification FPWD LC CR PR Rec
HTML5 N/A 2011 Q2 2012 Q4 2014 Q4 2014 Q4
HTML 5.1 2012 Q4 2014 Q3 2015 Q1 2016 Q4 2016 Q4
First Public Working Draft
↓
Last Call Working Draft
↓
Candidate Recommendation
↓
Proposed Recommendation
↓
Recommendation
Other Relevant Work W3C Runtime and Security Model for Web Apps
http://www.w3.org/TR/2013/WD-runtime-20130321/
W3C Geolocation API
http://www.w3.org/TR/2012/PR-geolocation-API-20120510/
Web Speech API
https://dvcs.w3.org/hg/speech-api/raw-file/9a0075d25326/speechapi.html
…
Charter • Goals
Create specs, starting with Vehicle Data
Create conformance tests to cover new specs
Provide use cases and other reports to identify add’l needed standards work & to drive successful automotive web deployments
Reference http://www.w3.org/community/autowebpl
atform/automotive-and-web-platform-business-group-charter