forked from w3c/automotive
-
Notifications
You must be signed in to change notification settings - Fork 0
/
charter-2018.html
582 lines (503 loc) · 28.1 KB
/
charter-2018.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8" />
<title>Automotive Working Group Charter</title>
<link rel="stylesheet" href="https://www.w3.org/2005/10/w3cdoc.css" type="text/css" media="screen" />
<link rel="stylesheet" type="text/css" href="https://www.w3.org/Guide/pubrules-style.css" />
<link rel="stylesheet" type="text/css" href="https://www.w3.org/2006/02/charter-style.css" />
<style type="text/css">
ul#navbar {
font-size: small;
}
dt.spec {
font-weight: bold;
}
dt.spec new {
background: yellow;
}
ul.out-of-scope > li {
font-weight: bold;
}
ul.out-of-scope > li > ul > li{
font-weight: normal;
}
.issue {
background: cornsilk;
font-style: italic;
}
.todo {
color: #900;
}
footer {
font-size: small;
}
</style>
</head>
<body>
<header id="header">
<aside>
<ul id="navbar">
<li><a href="#scope">Scope</a></li>
<li><a href="#deliverables">Deliverables</a></li>
<li><a href="#coordination">Coordination</a></li>
<li><a href="#participation">Participation</a></li>
<li><a href="#communication">Communication</a></li>
<li><a href="#decisions">Decision Policy</a></li>
<li><a href="#patentpolicy">Patent Policy</a></li>
<li><a href="#licensing">Licensing</a></li>
<li><a href="#about">About this Charter</a></li>
</ul>
</aside>
<p>
<a href="https://www.w3.org/"><img alt="W3C" height="48" src="https://www.w3.org/Icons/w3c_home" width="72" /></a>
</p>
</header>
<main>
<h1 id="title">Automotive Working Group Charter</h1>
<p class="mission">The <b>mission</b> of the <a href="/auto/wg/">Automotive Working Group</a> is
to develop Open Web Platform specifications for
application developers, enabling Web connectivity through in-vehicle
infotainment systems and vehicle data access protocols.</p>
<div class="noprint">
<p class="join"> <a href="https://www.w3.org/2004/01/pp-impl/76043/join">Join the Automotive Working Group</a> </p>
</div>
<p style="padding: 0.5ex; border: 1px solid green"> This proposed charter is available
on <a href="https://github.com/w3c/automotive/blob/gh-pages/charter-2018.html">GitHub</a>.
Feel free to raise <a href="https://github.com/w3c/automotive/issues">issues</a>.
</p>
<section id="details">
<table class="summary-table">
<tr id="Duration">
<th>
Start date
</th>
<td>
<i>01 May 2018</i>
</td>
</tr>
<tr id="Duration">
<th>
End date
</th>
<td>
<i>30 June 2018</i>
</td>
</tr>
<tr class="todo">
<th>Charter extension</th>
<td>See <a href="#history">Change History</a>.
</td>
</tr>
<tr>
<th>
Chairs
</th>
<td>
Paul Boyes, Invited Expert<br/>
Rudolf Streif, Jaguar Land Rover
</td>
</tr>
<tr>
<th>
Team Contacts
</th>
<td>
<a href="mailto:[email protected]">Ted Guild</a> (0.2 <abbr title="Full-Time Equivalent">FTE</abbr>)
</td>
</tr>
<tr>
<th>
Meeting Schedule
</th>
<td>
<strong>Teleconferences:</strong> 1-hour calls will be held weekly in
addition to topic-specific calls.
<br />
<strong>Face-to-face:</strong> we will meet during the W3C's annual Technical Plenary week; additional face-to-face meetings may be scheduled by consent of the participants, usually no more than 3 per year.
</td>
</tr>
</table>
</section>
<section id="scope" class="scope">
<h2>Scope</h2>
<p>This group will develop service specifications for exposing vehicle data and other information around vehicle centric functions.</p>
<p>A common pattern will be described to unify the style the different service interfaces are using.</p>
<p>The specification(s) produced by this Working Group will include security and privacy considerations.</p>
<p>Members of the Working Group should review other working groups' deliverables that are identified as being relevant to the Working Group's mission.</p>
<p>Services may include but are not limited to
<ul>
<li>Vehicle Data</li>
<ul><li>vehicle brand, model, year, fuel type, transmission type, steering wheel position, tire pressure, oil level, wiper position, lights, doors, windows and seat settings as well as navigation, trip computer data, climate control data, speed, RPMs, acceleration, gears, …</li></ul>
<li>media</li>
<ul><li>media control, track lists, …</li></ul>
<li>navigation</li>
<ul><li>route manipulation, points of interests, …</li></ul>
</ul>
</p>
<div id="section-out-of-scope">
<h3 id="out-of-scope">Out of Scope</h3>
<p> This Working Group will not define or mandate implementation details
including vehicle, network or sensor protocols for sharing data
between the vehicle data network and sensors. The vehicle data bus
network and protocols are OEM specific and vary from vehicle to
vehicle.</p>
<p>However, to facilitate interoperability among vehicle OEMs and
encourage adoption of the specifications, the group may informatively reference
existing suites of protocols, either directly in the
deliverable(s) or in a non-normative companion Note.</p>
</div>
<div>
<h3>Success Criteria</h3>
<p>In order to advance to <a href="https://www.w3.org/Consortium/Process/#RecsPR" title="Proposed Recommendation">Proposed Recommendation</a>, each specification is expected to have <a href="https://www.w3.org/Consortium/Process/#implementation-experience">at least two independent implementations</a> for every feature defined in the specification.</p>
<p>Each specification should contain a section detailing any known security or privacy implications for implementers, Web authors, and end users.</p>
<p>Testing plans for each specification, starting from the earliest drafts.</p>
</div>
</section>
<section id="deliverables">
<h2>
Deliverables
</h2>
<p>More detailed milestones and updated publication schedules are available on the <a href="https://www.w3.org/wiki/[groupname]/PubStatus">group publication status page</a>.</p>
<p>To promote interoperability, all changes made to specifications should have <a href='https://github.com/w3c/testing-how-to/#test-as-you-commit-pointer-event-whatwg-webperf'>tests</a>.</p>
<p><i>Draft state</i> indicates the state of the deliverable at the time of the charter approval. <i>Expected completion</i> indicates when the deliverable is projected to become a Recommendation, or otherwise reach a stable state.</p>
<div id="normative">
<h3>
Normative Specifications
</h3>
<p>
The Working Group will deliver the following W3C normative specifications:
</p>
<dl>
<dt id="web-foo" class="spec"><a href="https://www.w3.org/TR/vehicle-information-service/">
Vehicle Information Service Specification (VISS)</a></dt>
<dd>
<p>The Vehicle Signal Server Specification defines the semantics of exposing vehicle information through the WebSocket protocol. This specification is dependent upon the Vehicle Signal Specification, as defined by GENIVI.</p>
<p class="draft-status"><b>Draft state:</b> Candidate Recommendation</p>
<p class="milestone"><b>Expected completion:</b> <i class="todo">[Q2 2018]</i></p>
</dd>
</dl>
<dl>
<dt id="web-foo" class="spec">Restful Service Interface (RSI)</dt>
<dd>
<p>This specification expands on VISS to expose services through interfaces in a restful style.
The group will create a <b>common pattern</b> which will be used for services in the vehicle universe.
The pattern could be used for vehicle signals, media, navigation and other services for in vehicle functions.</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://www.w3.org/Submission/2016/01/">Member Submission</a></p>
<p class="milestone"><b>Expected completion:</b> <i class="todo">[Q2 2019]</i></p>
</dd>
</dl>
</dl>
<dl>
<dt id="web-foo" class="spec">typical vehicle services</dt>
<dd>
<p>The behaviour and interface of a number of services within the scope of a vehicle will be described using the pattern requested above.
Ideas for service to be described are: vehicle signals, media, navigation and other services for in vehicle functions.</p>
<p class="draft-status"><b>Draft state (for some):</b> <a href="https://www.w3.org/Submission/2016/01/">Member Submission</a></p>
<p class="milestone"><b>Expected completion:</b> <i class="todo">[Q2 2020] and earlier</i></p>
</dd>
</dl>
<!--
<dl>
<dt id="web-foo" class="spec"><a href="#">Web <i class="todo">[spec name]</i></a></dt>
<dd>
<p>This specification defines <i class="todo">[concrete description]</i>.</p>
<p class="draft-status"><b>Draft state:</b> <i class="todo">[No draft | <a href="#">Use Cases and Requirements</a> | <a href="#">Editor's Draft</a> | <a href="#">Member Submission</a> | <a href="#">Adopted from WG/CG Foo</a> | <a href="#">Working Draft</a>]</i></p>
<p class="milestone"><b>Expected completion:</b> <i class="todo">[Q1–4 yyyy]</i></p>
</dd>
</dl>
-->
<p><b>Adopted Working Draft:</b>
<dt>
<a href='https://www.w3.org/TR/vehicle-information-service/' rel='versionof'>Vehicle Information Service Specification</a>
<br>Latest publication: <a href='https://www.w3.org/TR/2018/CR-vehicle-information-service-20180213/'>13 February 2018</a></dt>
<dd>Reference Draft:
<a href='https://www.w3.org/TR/2018/CR-vehicle-information-service-20180213/'>https://www.w3.org/TR/2018/CR-vehicle-information-service-20180213//</a><br>
associated <a
href='https://lists.w3.org/Archives/Member/member-cfe/2018Mar/0001.html'>Call
for Exclusion</a> on 6 March 2018
ended on 19 March 2017<br>Produced under Working Group Charter:
http://www.w3.org/2014/automotive/charter-2016</dd>
</p>
<!--
<p><b>Adopted Working Draft:</b> The <a
href="https://www.w3.org/TR/vehicle-information-service/">Vehicle
Information Service Specification</a> [2018-02-13] which will serve as the basis for work on the deliverable.
<p><b>Reference Draft:</b> The <span class="todo">title, stable URL, and publication date of the most recent <a href='https://github.com/w3c/charter-drafts/blob/gh-pages/draft-states.md#reference-draft'>Reference Draft</a> or Candidate Recommendation</span> which triggered an Exclusion Opportunity per the Patent Process.
<span class="todo">Exclusion period <b>began</b>; Exclusion period <b>ended</b>.</span> <span class='todo'>(this <a href="https://www.w3.org/2004/01/pp-impl/charter-assistant?wgid=76043">charter assistant</a> helps in producing the list</a>. use the proper <a href='https://www.w3.org/2004/01/pp-impl/'>wgid</a>)</span>
<p>Produced under <b>Working Group Charter:</b> The <span class="todo">stable URL of the Working Group charter</span> under which the most recent Reference Draft or Candidate Recommendation was published.
</dd>
</dl></dl>
-->
</div>
<div id="ig-other-deliverables">
<h3>
Other Deliverables
</h3>
<p>
Other non-normative documents may be created such as:
</p>
<ul>
<li>Use case and requirement documents;</li>
<li>Test suite and implementation report for the specification;</li>
<li>Primer or Best Practice documents to support web developers when designing applications.</li>
</ul>
</div>
<!--
<div id="timeline">
<h3>Timeline</h3>
<p class="todo">Put here a timeline view of all deliverables.</p>
<ul class="todo">
<li>March 2018: VISS to PR</li>
<li>June 2018: VISS to REC</li>
<li>September 2018: FPWD for RSI</li>
<li>December 2018: RSI to CR</li>
<li>February 2019: RSI to PR</li>
<li>April 2019: RSI REC</li>
</ul>
</div>
-->
</section>
<section id="coordination">
<h2>Coordination</h2>
<p>For all specifications, this Working Group will seek <a href="https://www.w3.org/Guide/Charter.html#horizontal-review">horizontal review</a> for accessibility, internationalization, performance, privacy, and security with the relevant Working and Interest Groups, and with the <a href="https://www.w3.org/2001/tag/" title="Technical Architecture Group">TAG</a>. Invitation for review must be issued during each major standards-track document transition, including <a href="https://www.w3.org/Consortium/Process/#RecsWD" title="First Public Working Draft">FPWD</a> and at least 3 months before <a href="https://www.w3.org/Consortium/Process/#RecsCR" title="Candidate Recommendation">CR</a>, and should be issued when major changes occur in a specification.</p>
<p>Additional technical coordination with the following Groups will be made, per the <a href="https://www.w3.org/Consortium/Process/#WGCharter">W3C Process Document</a>:</p>
<div>
<h3 id="w3c-coordination">W3C Groups</h3>
<dl>
<dt><a href="http://www.w3.org/community/autowebplatform/">Automotive
and Web Platform Business Group</a></dt>
<dd>This group developed the initial version of the Vehicle
Information & Vehicle Data APIs and will likely continue to
explore new use cases and other automotive and web related topics. </dd>
<dt><a href="http://www.w3.org/2009/dap/">Device and Sensors Working Group</a>
</dt>
<dd>The Device and Sensors Working Group defines the Network Service
Discovery API that addresses some of the use cases that are in scope
of the Automotive Working Group.</dd>
<dt><a href="http://www.w3.org/Privacy/">Privacy Interest Group</a></dt>
<dd>The Automotive API Working Group intends to secure reviews on its
deliverables from the Privacy Interest Group to ensure they offer
the right level of protection to users.</dd>
<dt><a href="https://www.w3.org/WAI/APA/">Accessible Platform Architectures Working Group</a> </dt>
<dd>To ensure the Vehicle Information and Data APIs support
accessibility requirements, particularly with regard to
interoperability with assistive technologies, input to use
cases and inclusion in the
deliverable of guidance for implementing the group’s deliverables in
ways that support accessibility requirements. The APAWG will also
coordinate review from the <a href="http://www.w3.org/WAI/GL/mobile-a11y-tf/">Mobile
Accessibility Task Force</a>.</dd>
<dt><a href="https://www.w3.org/WebPlatform/WG/">Web Platform Working
Group</a></dt>
<dd>This group defines <a href="https://w3c.github.io/charter-html/group-charter.html#deliverables">relevant or potentially relevant specifications</a>
including <a href="http://w3c.github.io/manifest//">Manifest for Web applications</a>, <a href="http://www.w3.org/TR/webmessaging/">HTML5
Web Messaging</a>, <a
href="http://w3c.github.io/ServiceWorker/spec/service_worker/">Service
Worker</a> and <a href="http://www.w3.org/TR/websockets/">The
Web Socket API</a>.</dd>
<dt><a href="http://www.w3.org/2011/webappsec/">Web Application
Security Working Group</a></dt>
<dd>The Web Application Security Working Group is developing security
and policy mechanisms to improve the security of Web Applications
and enable secure cross-site communication.</dd>
<dt><a href="http://www.w3.org/Security/wiki/IG">Web Security Interest
Group</a></dt>
<dd>The Automotive API Working Group intends to secure reviews on its
deliverables from the Web Security Interest Group to ensure they
offer the right level of security. </dd>
</dl>
<h3 id="external-coordination">External Organizations</h3>
<dl>
<dt><a href="http://www.genivi.org/">GENIVI Alliance</a></dt>
<dd> The GENIVI Alliance is an automotive initiative that uses Linux
and open source technology to define an automotive infotainment
system that would adopt the APIs developed in this Working
Group.</dd>
<dt><a href="http://automotive.linuxfoundation.org/">Automotive Grade Linux (AGL)</a></dt>
<dd>Automotive Grade Linux is a collaborative open source
project developing a common, Linux-based software stack for
the connected car and part of The Linux Foundation.</dd>
<dt><a href="http://www.autosar.org">AUTOSAR (AUTomotive Open System ARchitecture)</a></dt>
<dd>AUTOSAR is an open and standardized automotive software
architecture, jointly developed by automobile manufacturers,
suppliers and tool developers.</dd>
<dt><a href="https://openconnectivity.org">Open Connectivity Foundation/IOTIVITY </a></dt>
<dd>The Open Connectivity Foundation (OCF) is an industry group whose stated mission
is to develop standards and certification for devices involved in the Internet of
Things (IoT) based around Constrained Application Protocol (CoAP)</dd>
<dt><a href="http://openmobilealliance.org/about-oma/work-program/omauto/">OMAUTO</a></dt>
<dd>The OMAUTO mission is to establish a venue for discussion between telecom and
automotive at a technical and industry level to establish any network, any automobile
communication</dd>
<dt><a href="http://www.sae.org">SAE</a></dt>
<dd>SAE International is a global association of more than 128,000 engineers and related technical experts in the aerospace, automotive and commercial-vehicle industries.</dd>
</dl>
</div>
</section>
<section class="participation">
<h2 id="participation">
Participation
</h2>
<p>
To be successful, this Working Group is expected to have 6 or more active participants for its duration, including representatives from the key implementors of this specification, and active Editors and Test Leads for each specification. The Chairs, specification Editors, and Test Leads are expected to contribute half of a working day per week towards the Working Group. There is no minimum requirement for other Participants.
</p>
<p>
The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in <a href='#communication'>Communication</a>.
</p>
<p>
The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a>.
</p>
</section>
<section id="communication">
<h2>
Communication
</h2>
<p id="public">
Technical discussions for this Working Group are conducted in <a href="https://www.w3.org/Consortium/Process/#confidentiality-levels">public</a>: the meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed on a public repository, and may permit direct public contribution requests.
The meetings themselves are not open to public participation, however.
</p>
<p>
Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <a href="https://www.w3.org/2014/automotive/">Automotive Working Group home page.</a>
</p>
<p>
Most Automotive Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.
</p>
<p>
This group primarily conducts its technical work on the public mailing list <a id="public-name" href="mailto:[email protected]">[email protected]</a> (<a href="http://lists.w3.org/Archives/Public/public-automotive">archive</a>)
and on <a id="public-github" href="https://github.com/w3c/automotive">GitHub issues</a>.
The public is invited to review, discuss and contribute to this work.
</p>
<p>
The group may use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a participant requests such a discussion.
</p>
</section>
<section id="decisions">
<h2>
Decision Policy
</h2>
<p>
This group will seek to make decisions through consensus and due process, per the <a href="https://www.w3.org/Consortium/Process/#Consensus"> W3C Process Document (section 3.3</a>). Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required.</p>
<p>
However, if a decision is necessary for timely progress, but consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote, and record a decision along with any objections.
</p>
<p>
To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional.
A call for consensus (CfC) will be issued for all resolutions (for example, via email and/or web-based survey), with a response period from one week to 10 working days, depending on the chair's evaluation of the group consensus on the issue.
If no objections are raised on the mailing list by the end of the response period, the resolution will be considered to have consensus as a resolution of the Working Group.
</p>
<p>
All decisions made by the group should be considered resolved unless and until new information becomes available, or unless reopened at the discretion of the Chairs or the Director.
</p>
<p>
This charter is written in accordance with the <a href="https://www.w3.org/Consortium/Process/policies#Votes">W3C Process Document (Section 3.4, Votes)</a>, and includes no voting procedures beyond what the Process Document requires.
</p>
</section>
<section id="patentpolicy">
<h2>
Patent Policy
</h2>
<p>
This Working Group operates under the <a href="https://www.w3.org/Consortium/Patent-Policy-20170801/">W3C Patent Policy</a> (Version of 5 February 2004 updated 1 August 2017). To promote the widest adoption of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis.
For more information about disclosure obligations for this group, please see the <a href="https://www.w3.org/2004/01/pp-impl/">W3C Patent Policy Implementation</a>.
</p>
</section>
<section id="licensing">
<h2>Licensing</h2>
<p>This Working Group will use the <a href="https://www.w3.org/Consortium/Legal/copyright-documents">W3C Document license</a> for all its deliverables.</p>
</section>
<section id="about">
<h2>
About this Charter
</h2>
<p>
This charter has been created according to <a href="https://www.w3.org/Consortium/Process/groups#GAGeneral">section 5.2</a> of the <a href="https://www.w3.org/Consortium/Process">Process Document</a>. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.
</p>
<section id="history">
<h3>
Charter History
</h3>
<p class="issue"><b>Note:</b>Display this table and update it when appropriate. Requirements for charter extension history are documented in the <a href="https://www.w3.org/Guide/Charter#extension">Charter Guidebook (section 4)</a>.</p>
<p>The following table lists details of all changes from the initial charter, per the <a href="https://www.w3.org/Consortium/Process/#CharterReview">W3C Process Document (section 5.2.3)</a>:</p>
<table class="history">
<tbody>
<tr>
<th>
Charter Period
</th>
<th>
Start Date
</th>
<th>
End Date
</th>
<th>
Changes
</th>
</tr>
<tr>
<th>
<a class="todo" href="https://www.w3.org/2014/automotive/charter.html">Initial Charter</a>
</th>
<td>3 February 2015</td>
<td>31 December 2016</td>
<td>
<i class="todo">none</i>
</td>
</tr>
<tr>
<th>
<a class="todo" href="">Charter Extension</a>
</th>
<td>
<i class="todo">1 January 2017</i>
</td>
<td>
<i class="todo">30 March 2018</i>
</td>
<td>
<i class="todo">none</i>
</td>
</tr>
<tr>
<th>
<a class="todo" href="">Rechartered</a>
</th>
<td>
<i class="todo">[dd monthname yyyy]</i>
</td>
<td>
<i class="todo">[dd monthname yyyy]</i>
</td>
<td>
<p class="todo">Inclusion of <span class="new">Restful Service
Interface (RSI)</span> as an extension of Vehicle
Information Service Specification (VISS) and the
discontinuation of Vehicle Information API
Specification (VIAS).</p>
</td>
</tr>
</tbody>
</table>
</section>
</section>
</main>
<hr />
<footer>
<address>
<a href="mailto:[email protected]">Ted Guild</a>
</address>
<p class="copyright">
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©2018
<a href="https://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
(
<a href="https://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
<a href="https://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
<a href="https://www.keio.ac.jp/">Keio</a>,
<a href="http://ev.buaa.edu.cn/">Beihang</a>
), All Rights Reserved.
<abbr title="World Wide Web Consortium">W3C</abbr> <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="https://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
</p>
</footer>
</body>
</html>