/
wot-ig-2019.html
630 lines (562 loc) · 32 KB
/
wot-ig-2019.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
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8" />
<title>Web of Things Interest 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>
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;
}
<!-- additional style -->
span.caption {
display: block;
text-align: center;
font-style: italic;
}
section {
clear: both;
}
div.summary {
clear: both;
margin-top: 0.5em;
margin-left: 20%;
margin-right: 20%;
padding: 0.5em;
background: rgb(240,240,255);
border: solid 1px black;
}
#relationships {
float:right;
margin-left: 0.6em;
width:40%;
min-width:250px;
max-width:936px;
}
#deliverables dt {
font-weight: bold;
margin-top: 0.5em;
}
.info {
background-color: #ddd;
margin-top: 1em;
padding: 15px;
border: 1px solid transparent;
border-radius: 4px;
}
</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 Disclosures</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">Web of Things Interest Group Charter</h1>
<p class="mission">
The <strong>mission</strong> of the <a href="https://www.w3.org/WoT/IG/">Web of Things Interest Group</a> is to counter the fragmentation of the
Internet of Things by complementing available standards through Web technology capable of
interconnecting existing Internet of Things platforms, devices, gateways, and cloud services.
We aim to reduce costs through the global reach of Web standards, to enable open markets of services, and to unleash the power of the network effect.
As a W3C Interest Group, we are seeking to build a deeper understanding of the Web of Things by investigating consumer, industrial, environmental,
energy management, and smart city scenarios.
This is intended to identify demand for further standards-track work within W3C working groups and to better align with the established W3C liaisons.
</p>
<div class="noprint">
<p class="join"><a href="https://www.w3.org/2004/01/pp-impl/75874/join">Join the Web of Things Interest Group</a>.</p>
</div>
<section id="details">
<table class="summary-table">
<tr id="Duration">
<th>
Start date
</th>
<td>
22 October 2019
</td>
</tr>
<tr>
<th>
End date
</th>
<td>
30 June 2021
</td>
</tr>
<tr>
<th>Charter extension</th>
<td>See <a href="#history">Change History</a>.
</td>
</tr>
<tr>
<th>
Chairs
</th>
<td>
Michael McCool (Intel) and
Sebastian Kaebisch (Siemens)
</td>
</tr>
<tr>
<th>
Team Contacts
</th>
<td>
<a href="mailto:ashimura@w3.org">Kazuyuki Ashimura</a> (0.1 <abbr title="Full-Time Equivalent">FTE</abbr>),
<a href="mailto:dsr@w3.org">Dave Raggett</a> (0.1 <abbr title="Full-Time Equivalent">FTE</abbr>)
</td>
</tr>
<tr>
<th>
Meeting Schedule
</th>
<td>
<strong>Teleconferences:</strong> weekly with additional topic-specific calls as appropriate.<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="intro" class="scope">
<h2>Introduction</h2>
<p>
The Internet of Things (IoT) suffers from a lack of interoperability across platforms.
As a result developers are faced with data silos, high integration and maintenance costs, and limited market potential.
Existing IoT standards address only limited ecosystems and do not provide interoperability across domains.
The current IoT is like the Internet before the World Wide Web, with competing incompatible hypertext systems.
The W3C is applying lessons learned from the World Wide Web to the Internet of Things to create the Web of Things.
</p>
<p>
To achieve this goal for cross-platform and cross-domain interoperability,
the <a href="https://www.w3.org/WoT/WG/">Web of Things Working Group</a> is developing a first set of standardized building blocks.
The core idea is based upon rich metadata that describes the data and possible interactions (i.e., affordances) exposed to applications,
and the communications and security requirements for platforms to communicate effectively.
The central documents are the <a href="https://www.w3.org/TR/wot-architecture/">WoT Architecture</a> and <a href="https://www.w3.org/TR/wot-thing-description/">WoT Thing Description</a> with its <i>Properties, Actions, Events</i> interaction model.
</p>
<p>
The <a href="https://www.w3.org/WoT/WG/">Web of Things Interest Group</a> continues its work to support the WoT Working Group and to explore opportunities for new standards-track work within W3C.
The priority in this third charter period is gaining additional practical experience with the in-development building blocks in the field
to enable open markets of services on the scale of the Web.
To achieve this goal, the Interest Group is seeking to broaden the range of participants to provide the necessary skills and resources for real-world application scenarios in different verticals.
</p>
</section>
<section id="scope" class="scope">
<h2>Scope</h2>
<div class="summary">
<p style="text-align:center;font-weight:bold;">Scope Summary</p>
<ul>
<li>Support the Web of Things Working Group</li>
<li>Organize and run interoperability and testing events,
including events for specific vertical industries, to evaluate
the current working assumptions in regard to the Web of Things</li>
<li>Reach out and collaborate with interested organizations, industry specific and infrastructure vendors, and communities in support of the Interest Group's mission</li>
<li>Explore areas and identify work that is ready for transfer to the W3C Recommendation Track</li>
</ul>
</div>
<p>
<a href="wot-ig-2019-relationship.png"><img id="relationships" src="wot-ig-2019-relationship.png" alt="relationship between WoT IG and WG" /></a>
The Web of Things Interest Group (WoT IG) is a forum for discussion of ideas relating to the Web of Things
and is intended to complement the role of the Web of Things Working Group (WoT WG).
In particular, the WoT IG will propose new work items based upon new requirements, use cases,
and discussions with IoT developer communities,
standards development organizations,
industry alliances,
and vertical industry solution and infrastructure providers.
Conversely, the WoT IG will consider new topics that are submitted to it by the WoT WG.
</p>
<p>
An important activity is the operation of PlugFests to collect interoperability implementation experience
and to validate the current working assumptions of the potential building blocks discussed in the Web of Things Interest Group.
These events enable developers to get together to test their implementations and facilitates networking between partners and experts.
The Interest Group will seek to encourage work on open source projects and community evaluation of the Web of Things.
In more detail, PlugFests allow participants to:
</p>
<ul>
<li>assist with preparing implementation reports for WoT WG Candidate Recommendations</li>
<li>test-drive upcoming or proposed technologies for the W3C Recommendation Track</li>
<li>identify and test-drive upcoming or proposed technologies as they apply to the collection of technologies required to address specific industry and user community needs</li>
<li>take part in interoperability experiments across implementations for ideas at different levels of maturity</li>
<li>reach out to other communities and new members through an OpenDay for non-members, which usually includes a demo track</li>
<li>ensure interoperability between WoT technologies and assistive technologies used by people with disabilities</li>
</ul>
<p>
The Interest Group will identify requirements for standardization in two ways: first, by exploring use cases and requirements for concrete consumer, industrial,
environmental, energy management, and smart cities application scenarios, and second, through examining the requirements for integrating a broad range of IoT platforms into the Web of Things.
The exploration tasks that the Interest Group will undertake may include:
</p>
<ul>
<li>use cases and requirements for different application scenarios and user communities</li>
<li>lifecycle management of Things</li>
<li>Thing Template format and mechanisms</li>
<li>clarify relationship with the concept of Digital Twins</li>
<li>out-of-the-box device onboarding to cloud services</li>
<li>WoT Scripting API and possible simplifications</li>
<li>hypermedia-driven interactions for complex/multi-step Actions and Events</li>
<li>community-driven, bottom-up vocabulary to enable semantic interoperability</li>
<li>Concrete protocol bindings (e.g. for HTTP, WebSockets, CoAP)</li>
</ul>
<p>
Further ideas for topics are expected from discussions and expert presentations of IoT projects,
including for example,
Graph Data,
Edge Computing,
Machine Learning.
The Interest Group will incubate work items for the Web of Things until they are ready for transfer to the W3C Recommendation Track,
either in existing Working Groups, such as the WoT WG, or in new Working Groups.
</p>
<p>
The use case and requirement documents developed by the Interest Group should represent the needs of an international set of users.
Users may be either working wholly in a non-Latin script, or in an environment where different actors are using different languages.
Any requirements and use cases arising from investigation of international use should,
of course, then be reflected in the experience and/or implementation reports for identified building blocks and any primer,
best practice, or test case documents.
</p>
<section id="section-out-of-scope">
<h3 id="out-of-scope">Out of Scope</h3>
<p>
The technical development of standards is not in scope for the Interest Group.
Identified Recommendation Track opportunities will be handed over to appropriate W3C groups if such a group exists, or within a dedicated Community Group or Business Group when incubation is needed.
</p>
</section>
</section>
<section id="deliverables">
<h2>Deliverables</h2>
<p>
The primary deliverables of the WoT Interest Group are IG Notes that identify use cases and requirements for existing and/or new WoT building blocks (i.e., technical specifications).
The IG Notes may contain the consensus of first implementation experiences gained by the group (e.g., during PlugFests).
The group will also maintain a public list of identified WoT building blocks that it is tracking and investigating.
</p>
<section id="normative">
<h3>Normative Specifications</h3>
<p>
The Interest Group will not deliver any normative specifications.
</p>
</section>
<section 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>experience and/or implementation reports for identified building blocks;</li>
<li>primer, best practice, or test case documents (including security) to support WoT developers when designing applications and/or Things.</li>
</ul>
</section>
<section id="timeline">
<h3>Timeline</h3>
<p>
The IG will, during its lifetime, undertake different activities that may proceed in parallel.
No specific timeline has been identified at this point,
but the various activities are intended to be running for short periods of time (2-12 months),
with the possibility of running a few iterations of them.
</p>
</section>
</section>
<section id="coordination">
<h2>Coordination</h2>
<p>For all deliverables, this Interest 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/2019/Process-20190301/#RecsWD" title="First Public Working Draft">FPWD</a> and <a href="https://www.w3.org/2019/Process-20190301/#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/2019/Process-20190301/#WGCharter">W3C Process Document</a>:</p>
<section>
<h3 id="w3c-coordination">W3C Groups</h3>
<dl>
<dt><a href="https://www.w3.org/WoT/WG/">Web of Things Working Group</a></dt>
<dd>For collaboration as outlined in <a href="#scope"></a>.</dd>
<dt><a href="https://www.w3.org/2018/json-ld-wg/">JSON-LD Working Group</a></dt>
<dd>For collaboration on JSON-LD features and WoT use cases.</dd>
<dt><a href="https://www.w3.org/community/exi-next/">Efficient Extensible Interchange Community Group</a></dt>
<dd>In relation to efficient interchange for Thing Descriptions.</dd>
<dt><a href="https://www.w3.org/auto/">Web and Automotive Business & Working Groups</a></dt>
<dd>For collaboration on technologies and requirements relating to connected cars and the Web of Things.</dd>
<dt><a href="https://www.w3.org/das/">Device and Sensors Working Group</a></dt>
<dd>For coordination on APIs for sensors and actuators.</dd>
<dt><a href="https://www.w3.org/WAI/APA/">Accessible Platform Architectures Working Group</a></dt>
<dd>For coordination on development of use cases and requirements, and impact of Web of Things technologies on accessibility for users with disabilities.</dd>
<dt><a href="https://www.w3.org/Privacy/">Privacy Interest Group</a></dt>
<dd>For collaboration on privacy considerations for the Web of Things.</dd>
<dt><a href="https://www.w3.org/International/">Internationalization Interest Group</a></dt>
<dd>For collaboration on internationalization considerations for the Web of Things.</dd>
<dt><a href="https://www.w3.org/web-networks/">Web & Networks Interest Group</a></dt>
<dd>For collaboration on networking technologies on the edge and in the cloud when exposing interactions between Things.</dd>
</dl>
</section>
<section>
<h3 id="external-coordination">External Organizations</h3>
<p>
To succeed in establishing inter-platform standards,
W3C needs to coordinate with IoT alliances and standards development organizations.
The following list provides examples of organizations with which the Interest Group has already had significant coordination during the period of the first charter. A <a href="https://www.w3.org/WoT/IG/wiki/How_does_W3C_compare_to_other_organizations">longer list</a> is available on the Interest Group wiki.
</p>
<dl>
<dt><a href="https://datatracker.ietf.org/doc/charter-irtf-t2trg/">IRTF Thing to Thing Research Group</a></dt>
<dd>For coordination of matters of mutual interest in relation to the Web of Things.</dd>
<dt><a href="http://openconnectivity.org">Open Connectivity Foundation</a></dt>
<dd>For collaboration on integrating OCF based platforms within the Web of Things, including platform metadata and approaches for enabling semantic interoperability, and end to end security across platforms.</dd>
<dt><a href="https://echonet.jp/english/">ECHONET Consortium</a></dt>
<dd>For collaboration on integrating ECHONET Consortium based platforms within the Web of Things, including platform metadata and approaches for enabling semantic interoperability, and end to end security across platforms.</dd>
<dt><a href="http://www.iiconsortium.org">Industrial Internet Consortium</a></dt>
<dd>For collaboration on a testbed and gathering user requirements for the Web of Things.</dd>
<dt><a href="https://opcfoundation.org">OPC Foundation</a></dt>
<dd>For collaboration on semantic interoperability in terms of information model, protocol binding, and security.</dd>
<dt><a href="https://www.plattform-i40.de/I40/Navigation/EN/Home/home.html">Plattform Industrie 4.0</a></dt>
<dd>For collaboration on use cases and requirements for smart manufacturing, including semantic interoperability and end to end security across platforms.</dd>
<dt><a href="http://www.onem2m.org">oneM2M</a></dt>
<dd>For collaboration on integrating M2M based platforms within the Web of Things, including platform metadata and approaches for enabling semantic interoperability, and end to end security across platforms.</dd>
<dt><a href="https://www.etsi.org">ETSI</a></dt>
<dd>For collaboration on IoT, M2M, security, and semantic interoperability.</dd>
<dt><a href="https://www.omaspecworks.org">OMA SpecWorks</a></dt>
<dd>For collaboration on integrating LWM2M based platforms with the Web of Things.</dd>
<dt><a href="https://www.opengeospatial.org/">Open Geospatial Consortium</a></dt>
<dd>For coordination on the OGC SensorThings API and location metadata.</dd>
<dt><a href="http://www.gsma.com">GSMA</a></dt>
<dd>For coordination in respect to the interests of Network Operators.</dd>
<dt><a href="https://www.eclass.eu/en.html">eCl@ss</a></dt>
<dd>For collaboration and coordination of the technical realization of the use of eCl@ss in the W3C Thing Description.</dd>
<dt><a href="https://aioti.eu/">AIOTI WG03</a></dt>
<dd>For coordination with the Alliance for Internet of Things Innovation, Working Group 3 (standardisation), in respect to use cases, requirements, and semantic interoperability.</dd>
</dl>
</section>
</section>
<section class="participation">
<h2 id="participation">
Participation
</h2>
<p>
To be successful, this Interest 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, Editors, and Test Leads are expected to contribute half of a working day per week towards the (Working|Interest) 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 Interest Group are conducted in <a href="https://www.w3.org/2019/Process-20190301/#confidentiality-levels">public</a>. 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.</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/WoT/IG/">Web of Things Interest Group home page.</a></p>
<p>Most Web of Things Interest 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:public-wot-ig@w3.org">public-wot-ig@w3.org</a> (<a href="http://lists.w3.org/Archives/Public/public-wot-ig/">archive</a>). The public is invited to post messages to this list.</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 and 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 Interest 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 Disclosures</h2>
<p>
The Interest Group provides an opportunity to
share perspectives on the topic addressed by this charter. W3C reminds
Interest Group participants of their obligation to comply with patent
disclosure obligations as set out in <a href="https://www.w3.org/Consortium/Patent-Policy/#sec-Disclosure">Section 6</a> of the W3C Patent Policy.
While the Interest Group does not
produce Recommendation-track documents, when Interest Group
participants review Recommendation-track specifications from Working
Groups, the patent disclosure obligations do apply. 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 Interest Group will use the <a href="https://www.w3.org/Consortium/Legal/copyright-software">W3C Software and 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/#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>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 href="https://www.w3.org/2014/12/wot-ig-charter.html">Initial Charter</a>
</th>
<td>
21 January 2015
</td>
<td>
31 March 2016
</td>
<td>
</td>
</tr>
<tr>
<th>
<a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2016AprJun/0038.html">Charter Extension</a>
</th>
<td>
1 April 2016
</td>
<td>
31 July 2016
</td>
<td>
<ul>
<li>Extended for rechartering process to complete</li>
</ul>
</td>
</tr>
<tr>
<th>
<a href="https://www.w3.org/2016/07/wot-ig-charter.html">Rechartered</a>
</th>
<td>
1 August 2016
</td>
<td>
31 December 2018
</td>
<td>
<ul>
<li>Clarified relation to chartered WoT Working Group</li>
<li>Changed scope to explore role of semantic technologies</li>
</ul>
</td>
</tr>
<tr>
<th>
<a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2019JanMar/0018.html">Charter Extension</a>
</th>
<td>
1 January 2019
</td>
<td>
30 June 2019
</td>
<td>
<ul>
<li>Matthias Kovatsch changed his affiliation and re-appointed as co-Chair.</li>
<li>Yongjing Zhang stepped down as co-Chair.</li>
</ul>
</td>
</tr>
<tr>
<th>
<!--a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2016AprJun/0038.html"-->Charter Extension<!--/a-->
</th>
<td>
1 July 2019
</td>
<td>
31 December 2019
</td>
<td>
<ul>
<li>Extended for rechartering process to complete</li>
</ul>
</td>
</tr>
<tr>
<th>
<a href="https://www.w3.org/2019/07/wot-ig-2019.html">Rechartered</a>
</th>
<td>
22 October 2019
</td>
<td>
30 June 2021
</td>
<td>
<ul>
<li>Simplified scope and deliverables to enable a broader set of Participants</li>
<li>Updated coordination groups</li>
</ul>
</td>
</tr>
</tbody>
</table>
</section>
</section>
</main>
<hr />
<footer>
<address>
<a href="mailto:ashimura@w3.org">Kazuyuki Ashimura</a>,
<a href="mailto:dsr@w3.org">Dave Raggett</a>
</address>
<p class="copyright">
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
2019
<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>