-
Notifications
You must be signed in to change notification settings - Fork 43
/
static.html
6901 lines (6534 loc) · 557 KB
/
static.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
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html><html lang="en-US"><head>
<meta charset="utf-8">
<meta name="generator" content="ReSpec 34.1.1">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<style>
.issue-label{text-transform:initial}
.warning>p:first-child{margin-top:0}
.warning{padding:.5em;border-left-width:.5em;border-left-style:solid}
span.warning{padding:.1em .5em .15em}
.issue.closed span.issue-number{text-decoration:line-through}
.issue.closed span.issue-number::after{content:" (Closed)";font-size:smaller}
.warning{border-color:#f11;border-width:.2em;border-style:solid;background:#fbe9e9}
.warning-title:before{content:"⚠";font-size:1.3em;float:left;padding-right:.3em;margin-top:-.3em}
li.task-list-item{list-style:none}
input.task-list-item-checkbox{margin:0 .35em .25em -1.6em;vertical-align:middle}
.issue a.respec-gh-label{padding:5px;margin:0 2px 0 2px;font-size:10px;text-transform:none;text-decoration:none;font-weight:700;border-radius:4px;position:relative;bottom:2px;border:none;display:inline-block}
</style>
<style>
dfn{cursor:pointer}
.dfn-panel{position:absolute;z-index:35;min-width:300px;max-width:500px;padding:.5em .75em;margin-top:.6em;font-family:"Helvetica Neue",sans-serif;font-size:small;background:#fff;color:#000;box-shadow:0 1em 3em -.4em rgba(0,0,0,.3),0 0 1px 1px rgba(0,0,0,.05);border-radius:2px}
.dfn-panel:not(.docked)>.caret{position:absolute;top:-9px}
.dfn-panel:not(.docked)>.caret::after,.dfn-panel:not(.docked)>.caret::before{content:"";position:absolute;border:10px solid transparent;border-top:0;border-bottom:10px solid #fff;top:0}
.dfn-panel:not(.docked)>.caret::before{border-bottom:9px solid #a2a9b1}
.dfn-panel *{margin:0}
.dfn-panel b{display:block;color:#000;margin-top:.25em}
.dfn-panel ul a[href]{color:#333}
.dfn-panel>div{display:flex}
.dfn-panel a.self-link{font-weight:700;margin-right:auto}
.dfn-panel .marker{padding:.1em;margin-left:.5em;border-radius:.2em;text-align:center;white-space:nowrap;font-size:90%;color:#040b1c}
.dfn-panel .marker.dfn-exported{background:#d1edfd;box-shadow:0 0 0 .125em #1ca5f940}
.dfn-panel .marker.idl-block{background:#8ccbf2;box-shadow:0 0 0 .125em #0670b161}
.dfn-panel a:not(:hover){text-decoration:none!important;border-bottom:none!important}
.dfn-panel a[href]:hover{border-bottom-width:1px}
.dfn-panel ul{padding:0}
.dfn-panel li{margin-left:1em}
.dfn-panel.docked{position:fixed;left:.5em;top:unset;bottom:2em;margin:0 auto;max-width:calc(100vw - .75em * 2 - .5em - .2em * 2);max-height:30vh;overflow:auto}
</style>
<title>Web of Things (WoT) Architecture 1.1</title>
<style id="respec-mainstyle">
@keyframes pop{
0%{transform:scale(1,1)}
25%{transform:scale(1.25,1.25);opacity:.75}
100%{transform:scale(1,1)}
}
:is(h1,h2,h3,h4,h5,h6,a) abbr{border:none}
dfn{font-weight:700}
a.internalDFN{color:inherit;border-bottom:1px solid #99c;text-decoration:none}
a.externalDFN{color:inherit;border-bottom:1px dotted #ccc;text-decoration:none}
a.bibref{text-decoration:none}
.respec-offending-element:target{animation:pop .25s ease-in-out 0s 1}
.respec-offending-element,a[href].respec-offending-element{text-decoration:red wavy underline}
@supports not (text-decoration:red wavy underline){
.respec-offending-element:not(pre){display:inline-block}
.respec-offending-element{background:url(data:image/gif;base64,R0lGODdhBAADAPEAANv///8AAP///wAAACwAAAAABAADAEACBZQjmIAFADs=) bottom repeat-x}
}
#references :target{background:#eaf3ff;animation:pop .4s ease-in-out 0s 1}
cite .bibref{font-style:normal}
a[href].orcid{padding-left:4px;padding-right:4px}
a[href].orcid>svg{margin-bottom:-2px}
.toc a,.tof a{text-decoration:none}
a .figno,a .secno{color:#000}
ol.tof,ul.tof{list-style:none outside none}
.caption{margin-top:.5em;font-style:italic}
table.simple{border-spacing:0;border-collapse:collapse;border-bottom:3px solid #005a9c}
.simple th{background:#005a9c;color:#fff;padding:3px 5px;text-align:left}
.simple th a{color:#fff;padding:3px 5px;text-align:left}
.simple th[scope=row]{background:inherit;color:inherit;border-top:1px solid #ddd}
.simple td{padding:3px 10px;border-top:1px solid #ddd}
.simple tr:nth-child(even){background:#f0f6ff}
.section dd>p:first-child{margin-top:0}
.section dd>p:last-child{margin-bottom:0}
.section dd{margin-bottom:1em}
.section dl.attrs dd,.section dl.eldef dd{margin-bottom:0}
#issue-summary>ul{column-count:2}
#issue-summary li{list-style:none;display:inline-block}
details.respec-tests-details{margin-left:1em;display:inline-block;vertical-align:top}
details.respec-tests-details>*{padding-right:2em}
details.respec-tests-details[open]{z-index:999999;position:absolute;border:thin solid #cad3e2;border-radius:.3em;background-color:#fff;padding-bottom:.5em}
details.respec-tests-details[open]>summary{border-bottom:thin solid #cad3e2;padding-left:1em;margin-bottom:1em;line-height:2em}
details.respec-tests-details>ul{width:100%;margin-top:-.3em}
details.respec-tests-details>li{padding-left:1em}
.self-link:hover{opacity:1;text-decoration:none;background-color:transparent}
aside.example .marker>a.self-link{color:inherit}
.header-wrapper{display:flex;align-items:baseline}
:is(h2,h3,h4,h5,h6):not(#toc>h2,#abstract>h2,#sotd>h2,.head>h2){position:relative;left:-.5em}
:is(h2,h3,h4,h5,h6):not(#toch2)+a.self-link{color:inherit;order:-1;position:relative;left:-1.1em;font-size:1rem;opacity:.5}
:is(h2,h3,h4,h5,h6)+a.self-link::before{content:"§";text-decoration:none;color:var(--heading-text)}
:is(h2,h3)+a.self-link{top:-.2em}
:is(h4,h5,h6)+a.self-link::before{color:#000}
@media (max-width:767px){
dd{margin-left:0}
}
@media print{
.removeOnSave{display:none}
}
</style>
<style type="text/css">
a[href].internalDFN {
color: inherit;
border-bottom: 1px solid #99c;
text-decoration: none;
}
img.wot-arch-diagram {
max-width: 90%;
height: auto;
}
</style>
<meta name="description" content="The W3C Web of Things (WoT) enables
interoperability across IoT platforms and application
domains.
The goal of the WoT is to preserve and complement existing
IoT standards and solutions. The W3C WoT architecture is
designed to describe what exists, and only prescribes new mechanisms
when necessary.">
<style>
var{position:relative;cursor:pointer}
var[data-type]::after,var[data-type]::before{position:absolute;left:50%;top:-6px;opacity:0;transition:opacity .4s;pointer-events:none}
var[data-type]::before{content:"";transform:translateX(-50%);border-width:4px 6px 0 6px;border-style:solid;border-color:transparent;border-top-color:#000}
var[data-type]::after{content:attr(data-type);transform:translateX(-50%) translateY(-100%);background:#000;text-align:center;font-family:"Dank Mono","Fira Code",monospace;font-style:normal;padding:6px;border-radius:3px;color:#daca88;text-indent:0;font-weight:400}
var[data-type]:hover::after,var[data-type]:hover::before{opacity:1}
</style>
<script id="initialUserConfig" type="application/json">{
"lint": {
"check-punctuation": true,
"local-refs-exist": true,
"no-http-props": true,
"no-headingless-sections": true
},
"doJsonLd": true,
"noLegacyStyle": true,
"inlineCSS": true,
"noIDLIn": true,
"group": "wg/wot",
"specStatus": "ED",
"shortName": "wot-architecture11",
"copyrightStart": 2017,
"wgPublicList": "public-wot-wg",
"implementationReportURI": "https://w3c.github.io/wot-architecture/testing/report11.html",
"github": {
"repoURL": "https://github.com/w3c/wot-architecture",
"branch": "main"
},
"previousPublishDate": "2022-09-07",
"previousMaturity": "WD",
"editors": [
{
"name": "Michael Lagally",
"w3cid": "47166",
"company": "Oracle Corp.",
"companyURL": "https://www.oracle.com/"
},
{
"name": "Ryuichi Matsukura",
"w3cid": "64284",
"company": "Fujitsu Ltd.",
"companyURL": "https://www.fujitsu.com/"
},
{
"name": "Michael McCool",
"w3cid": "93137",
"company": "Intel Corp.",
"companyURL": "https://www.intel.com/"
},
{
"name": "Kunihiko Toumura",
"w3cid": "83488",
"company": "Hitachi, Ltd.",
"companyURL": "https://www.hitachi.com/"
}
],
"formerEditors": [
{
"name": "Kazuo Kajimoto",
"note": "when at Panasonic"
},
{
"name": "Toru Kawaguchi",
"w3cid": "79307",
"company": "Panasonic Corp.",
"companyURL": "https://www.panasonic.com/"
},
{
"name": "Matthias Kovatsch",
"company": "Huawei",
"companyURL": "https://www.huawei.com"
}
],
"otherLinks": [
{
"key": "Previous Recommendation",
"data": [
{
"value": "https://www.w3.org/TR/2020/REC-wot-architecture-20200409/",
"href": "https://www.w3.org/TR/2020/REC-wot-architecture-20200409/"
}
]
},
{
"key": "Contributors",
"data": [
{
"value": "In the GitHub repository",
"href": "https://github.com/w3c/wot-architecture/graphs/contributors"
}
]
},
{
"key": "Repository",
"data": [
{
"value": "We are on GitHub",
"href": "https://github.com/w3c/wot-architecture/"
},
{
"value": "File a bug",
"href": "https://github.com/w3c/wot-architecture/issues"
}
]
}
],
"localBiblio": {
"CoRE-RD": {
"href": "https://datatracker.ietf.org/doc/html/draft-ietf-core-resource-directory-21",
"title": "CoRE Resource Directory",
"authors": [
"M. Koster",
"C. Bormann",
"P. van der Stok",
"C. Amsuess"
],
"status": "Internet-Draft",
"publisher": "IETF",
"date": "13 June 2019"
},
"IEC-FOTF": {
"href": "https://www.iec.ch/basecamp/factory-future/",
"title": "Factory of the future",
"publisher": "IEC",
"date": "October 2015",
"id": "iec-fotf"
},
"IOT-SCHEMA-ORG": {
"href": "https://www.w3.org/community/iotschema/",
"title": "Schema Extensions for IoT Community Group",
"id": "iot-schema-org"
},
"REST": {
"href": "https://www.ics.uci.edu/~fielding/pubs/dissertation/fielding_dissertation.pdf",
"title": "REST: Architectural Styles and the Design of Network-based Software Architectures",
"authors": [
"Roy Thomas Fielding"
],
"status": "PhD thesis",
"publisher": "University of California, Irvine",
"date": "2000",
"id": "rest"
},
"SAREF": {
"href": "https://sites.google.com/site/smartappliancesproject/ontologies/reference-ontology",
"title": "Smart Appliances REFerence (SAREF) ontology",
"publisher": "ETSI",
"date": "November 2015",
"id": "saref"
},
"SOLID": {
"href": "https://solidproject.org/TR/",
"title": "Solid Technical Reports",
"publisher": "W3C Solid CG",
"date": "April 2021",
"id": "solid"
},
"HCI": {
"href": "https://www.interaction-design.org/literature/book/the-encyclopedia-of-human-computer-interaction-2nd-ed",
"title": "The Encyclopedia of Human-Computer Interaction, 2nd Ed",
"publisher": "Interaction Design Foundation",
"date": "2013",
"id": "hci"
},
"NORMAN": {
"title": "The Psychology of Everyday Things",
"authors": [
"Donald A. Norman"
],
"publisher": "Basic Books",
"date": "1988",
"id": "norman"
},
"MQTT": {
"href": "https://docs.oasis-open.org/mqtt/mqtt/v3.1.1/mqtt-v3.1.1.html",
"title": "MQTT Version 3.1.1 Plus Errata 01",
"authors": [
"Andrew Banks",
"Rahul Gupta"
],
"publisher": "OASIS Standard",
"date": "December 2015",
"id": "mqtt"
},
"OCF": {
"href": "https://openconnectivity.org/developer/specifications/",
"title": "OCF Core Specification",
"publisher": "Open Connectivity Foundation",
"status": "Version 2.0.2",
"date": "April 2019",
"id": "ocf"
},
"WOT-USE-CASES-REQUIREMENTS": {
"href": "https://www.w3.org/TR/wot-usecases/",
"title": "Web of Things (WoT) Use Cases and Requirements",
"publisher": "W3C",
"authors": [
"Michael Lagally",
"Michael McCool",
"Ryuichi Matsukura",
"Tomoaki Mizushima"
],
"status": "Editor's Draft",
"date": "Oct 2020",
"id": "wot-use-cases-requirements"
},
"LWM2M": {
"href": "https://openmobilealliance.org/release/LightweightM2M/V1_1-20180710-A/OMA-TS-LightweightM2M_Core-V1_1-20180710-A.pdf",
"title": "Lightweight Machine to Machine Technical Specification: Core",
"publisher": "OMA SpecWorks",
"status": "Approved Version: 1.1",
"date": "August 2018",
"id": "lwm2m"
},
"CoRAL": {
"href": "https://datatracker.ietf.org/doc/html/draft-ietf-core-coral/",
"title": "The Constrained RESTful Application Language (CoRAL)",
"authors": [
"Christian Amsüss",
"Thomas Fossati"
],
"publisher": "IETF",
"status": "Internet-Draft",
"date": "March 2022",
"id": "coral"
},
"WOT-PIONEERS-1": {
"href": "https://pdfs.semanticscholar.org/3ee3/a2e8ce93fbf9ba14ad54e12adaeb1f3ca392.pdf",
"title": "Mobile Service Interaction with the Web of Things",
"authors": [
"E. Rukzio, M. Paolucci",
"M. Wagner, H. Berndt",
"J. Hamard",
"A. Schmidt"
],
"publisher": "Proceedings of 13th International Conference on Telecommunications (ICT 2006), Funchal, Madeira island, Portugal",
"date": "May 2006",
"id": "wot-pioneers-1"
},
"WOT-PIONEERS-2": {
"href": "https://escholarship.org/uc/item/1786t1dm",
"title": "Putting Things to REST",
"authors": [
"Erik Wilde"
],
"publisher": "UCB iSchool Report 2007-015, UC Berkeley, Berkeley, CA, USA",
"date": "November 2007",
"id": "wot-pioneers-2"
},
"WOT-PIONEERS-3": {
"href": "https://www.vs.inf.ethz.ch/publ/papers/ostermai-poster-2008.pdf",
"title": "Poster Abstract: Dyser – Towards a Real-Time Search Engine for the Web of Things",
"authors": [
"Benedikt Ostermaier",
"B. Maryam Elahi",
"Kay Römer",
"Michael Fahrmair",
"Wolfgang Kellerer"
],
"publisher": "Proceedings of ACM SenSys 2008, Raleigh, NC, USA",
"date": "November 2008",
"id": "wot-pioneers-3"
},
"WOT-PIONEERS-4": {
"href": "https://ieeexplore.ieee.org/abstract/document/5678452",
"title": "A Resource Oriented Architecture for the Web of Things",
"authors": [
"Dominique Guinard",
"Vlad Trifa",
"Erik Wilde"
],
"publisher": "Proceedings of Internet of Things 2010 International Conference (IoT 2010). Tokyo, Japan",
"date": "November 2010",
"id": "wot-pioneers-4"
},
"Y.4409-Y.2070": {
"href": "https://www.itu.int/rec/T-REC-Y.2070-201501-I",
"title": "ITU-T Rec. Y.4409/Y.2070 (01/2015) Requirements and architecture of the home energy management system and home network services ",
"publisher": "ITU-T",
"status": "Recommendation",
"date": "January 2015",
"id": "y.4409-y.2070"
},
"ISO-IEC-2382": {
"href": "https://www.iso.org/obp/ui/#iso:std:iso-iec:2382:ed-1:v2:en",
"title": "Information technology — Vocabulary",
"publisher": "ISO",
"date": "2015",
"id": "iso-iec-2382"
},
"ISO-IEC-27000": {
"href": "https://www.iso.org/obp/ui/#iso:std:iso-iec:27000:ed-5:v1:en",
"title": "Information technology — Security techniques — Information security management systems — Overview and vocabulary",
"publisher": "ISO",
"date": "2018",
"id": "iso-iec-27000"
},
"ISO-IEC-29100": {
"href": "https://www.iso.org/obp/ui/#iso:std:iso-iec:29100:ed-1:v1:en",
"title": "Information technology — Security techniques — Privacy framework",
"publisher": "ISO",
"date": "2011",
"id": "iso-iec-29100"
},
"WOT-THING-DESCRIPTION": {
"title": "Web of Things (WoT) Thing Description 1.1",
"href": "https://www.w3.org/TR/wot-thing-description11/",
"authors": [
"Sebastian Kaebisch",
"Takuki Kamiya",
"Michael McCool",
"Victor Charpenay"
],
"publisher": "W3C",
"date": "November 2020",
"id": "wot-thing-description"
},
"WOT-DISCOVERY": {
"title": "Web of Things (WoT) Discovery",
"href": "https://www.w3.org/TR/wot-discovery/",
"authors": [
"Andrea Cimmino",
"Michael McCool",
"Farshid Tavakolizadeh",
"Kunihiko Toumura"
],
"publisher": "W3C",
"date": "November 2020",
"id": "wot-discovery"
},
"WOT-SECURITY": {
"title": "Web of Things (WoT) Security and Privacy Guidelines",
"href": "https://www.w3.org/TR/wot-security/",
"authors": [
null,
"Michael McCool",
"Elena Reshetova"
],
"publisher": "W3C",
"date": "March 2019",
"id": "wot-security"
}
},
"publishISODate": "2023-06-08T00:00:00.000Z",
"generatedSubtitle": "W3C Editor's Draft 08 June 2023"
}</script>
<link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/2021/W3C-ED"></head>
<body class="h-entry toc-inline"><div class="head">
<p class="logos"><a class="logo" href="https://www.w3.org/"><img crossorigin="" alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72">
</a></p>
<h1 id="title" class="title">Web of Things (WoT) Architecture 1.1</h1>
<p id="w3c-state"><a href="https://www.w3.org/standards/types#ED">W3C Editor's Draft</a> <time class="dt-published" datetime="2023-06-08">08 June 2023</time></p>
<details open="">
<summary>More details about this document</summary>
<dl>
<dt>This version:</dt><dd>
<a class="u-url" href="https://w3c.github.io/wot-architecture/">https://w3c.github.io/wot-architecture/</a>
</dd>
<dt>Latest published version:</dt><dd>
<a href="https://www.w3.org/TR/wot-architecture11/">https://www.w3.org/TR/wot-architecture11/</a>
</dd>
<dt>Latest editor's draft:</dt><dd><a href="https://w3c.github.io/wot-architecture/">https://w3c.github.io/wot-architecture/</a></dd>
<dt>History:</dt><dd>
<a href="https://www.w3.org/standards/history/wot-architecture11">https://www.w3.org/standards/history/wot-architecture11</a>
</dd><dd>
<a href="https://github.com/w3c/wot-architecture/commits/main">Commit history</a>
</dd>
<dt>Implementation report:</dt><dd>
<a href="https://w3c.github.io/wot-architecture/testing/report11.html">https://w3c.github.io/wot-architecture/testing/report11.html</a>
</dd>
<dt>Editors:</dt><dd class="editor p-author h-card vcard" data-editor-id="47166">
<span class="p-name fn">Michael Lagally</span> (<a class="p-org org h-org" href="https://www.oracle.com/">Oracle Corp.</a>)
</dd><dd class="editor p-author h-card vcard" data-editor-id="64284">
<span class="p-name fn">Ryuichi Matsukura</span> (<a class="p-org org h-org" href="https://www.fujitsu.com/">Fujitsu Ltd.</a>)
</dd><dd class="editor p-author h-card vcard" data-editor-id="93137">
<span class="p-name fn">Michael McCool</span> (<a class="p-org org h-org" href="https://www.intel.com/">Intel Corp.</a>)
</dd><dd class="editor p-author h-card vcard" data-editor-id="83488">
<span class="p-name fn">Kunihiko Toumura</span> (<a class="p-org org h-org" href="https://www.hitachi.com/">Hitachi, Ltd.</a>)
</dd>
<dt>
Former editors:
</dt><dd class="editor p-author h-card vcard">
<span class="p-name fn">Kazuo Kajimoto</span> (when at Panasonic)
</dd><dd class="editor p-author h-card vcard" data-editor-id="79307">
<span class="p-name fn">Toru Kawaguchi</span> (<a class="p-org org h-org" href="https://www.panasonic.com/">Panasonic Corp.</a>)
</dd><dd class="editor p-author h-card vcard">
<span class="p-name fn">Matthias Kovatsch</span> (<a class="p-org org h-org" href="https://www.huawei.com">Huawei</a>)
</dd>
<dt>Feedback:</dt><dd>
<a href="https://github.com/w3c/wot-architecture/">GitHub w3c/wot-architecture</a>
(<a href="https://github.com/w3c/wot-architecture/pulls/">pull requests</a>,
<a href="https://github.com/w3c/wot-architecture/issues/new/choose">new issue</a>,
<a href="https://github.com/w3c/wot-architecture/issues/">open issues</a>)
</dd><dd><a href="mailto:public-wot-wg@w3.org?subject=%5Bwot-architecture11%5D%20YOUR%20TOPIC%20HERE">public-wot-wg@w3.org</a> with subject line <kbd>[wot-architecture11] <em>… message topic …</em></kbd> (<a rel="discussion" href="https://lists.w3.org/Archives/Public/public-wot-wg">archives</a>)</dd>
<dt>Previous Recommendation</dt><dd>
<a href="https://www.w3.org/TR/2020/REC-wot-architecture-20200409/">https://www.w3.org/TR/2020/REC-wot-architecture-20200409/</a>
</dd><dt>Contributors</dt><dd>
<a href="https://github.com/w3c/wot-architecture/graphs/contributors">In the GitHub repository</a>
</dd><dt>Repository</dt><dd>
<a href="https://github.com/w3c/wot-architecture/">We are on GitHub</a>
</dd><dd>
<a href="https://github.com/w3c/wot-architecture/issues">File a bug</a>
</dd>
</dl>
</details>
<p class="copyright">
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
©
2017-2023
<a href="https://www.w3.org/">World Wide Web Consortium</a>.
<abbr title="World Wide Web Consortium">W3C</abbr><sup>®</sup>
<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 rel="license" href="https://www.w3.org/Consortium/Legal/2015/copyright-software-and-document" title="W3C Software and Document Notice and License">permissive document license</a> rules apply.
</p>
<hr title="Separator for header">
</div>
<section id="abstract" class="introductory"><h2>Abstract</h2>
<p>The <abbr title="World Wide Web Consortium">W3C</abbr> Web of Things (WoT) enables
interoperability across IoT platforms and application
domains.
The goal of the WoT is to preserve and complement existing
IoT standards and solutions. The <abbr title="World Wide Web Consortium">W3C</abbr> WoT architecture is
designed to describe what exists, and only prescribes new mechanisms
when necessary.
</p>
<p>This <em>WoT Architecture</em> specification describes the abstract
architecture for the <abbr title="World Wide Web Consortium">W3C</abbr> Web of Things.
This abstract architecture is based on
requirements that were derived from use cases for
multiple application domains.
Several modular building blocks were identified whose detailed
specifications are given in other documents.
This document describes how these building blocks are related and work together.
The WoT abstract architecture defines a basic conceptual
framework that can be mapped onto a variety of concrete deployment scenarios,
several examples of which are given.
However, the abstract architecture described in this specification does not
itself define concrete mechanisms or prescribe any concrete implementation.
</p>
</section>
<section id="sotd" class="introductory"><h2>Status of This Document</h2><p><em>This section describes the status of this
document at the time of its publication. A list of current <abbr title="World Wide Web Consortium">W3C</abbr>
publications and the latest revision of this technical report can be found
in the <a href="https://www.w3.org/TR/"><abbr title="World Wide Web Consortium">W3C</abbr> technical reports index</a> at
https://www.w3.org/TR/.</em></p>
<p>
This document describes an abstract architecture.
However, there is an
<a href="https://w3c.github.io/wot-architecture/testing/report11.html">Implementation Report</a>
that describes a set of concrete implementations
following the <abbr title="World Wide Web Consortium">W3C</abbr> Web of Things architecture.
It also references the other implementation
reports for the various WoT building blocks.
</p>
<p class="at-risk">At-risk assertions are marked with yellow highlighting.</p>
<p>
This document was published by the <a href="https://www.w3.org/groups/wg/wot">Web of Things Working Group</a> as
an Editor's Draft.
</p><p>Publication as an Editor's Draft does not
imply endorsement by <abbr title="World Wide Web Consortium">W3C</abbr> and its Members. </p><p>
This is a draft document and may be updated, replaced or obsoleted by other
documents at any time. It is inappropriate to cite this document as other
than work in progress.
</p><p>
This document was produced by a group
operating under the
<a href="https://www.w3.org/Consortium/Patent-Policy/"><abbr title="World Wide Web Consortium">W3C</abbr> Patent
Policy</a>.
<abbr title="World Wide Web Consortium">W3C</abbr> maintains a
<a rel="disclosure" href="https://www.w3.org/groups/wg/wot/ipr">public list of any patent disclosures</a>
made in connection with the deliverables of
the group; that page also includes
instructions for disclosing a patent. An individual who has actual
knowledge of a patent which the individual believes contains
<a href="https://www.w3.org/Consortium/Patent-Policy/#def-essential">Essential Claim(s)</a>
must disclose the information in accordance with
<a href="https://www.w3.org/Consortium/Patent-Policy/#sec-Disclosure">section 6 of the <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
</p><p>
This document is governed by the
<a id="w3c_process_revision" href="https://www.w3.org/2021/Process-20211102/">2 November 2021 <abbr title="World Wide Web Consortium">W3C</abbr> Process Document</a>.
</p></section><nav id="toc"><h2 class="introductory" id="table-of-contents">Table of Contents</h2><ol class="toc"><li class="tocline"><a class="tocxref" href="#abstract">Abstract</a></li><li class="tocline"><a class="tocxref" href="#sotd">Status of This Document</a></li><li class="tocline"><a class="tocxref" href="#introduction"><bdi class="secno">1. </bdi>Introduction</a></li><li class="tocline"><a class="tocxref" href="#conformance"><bdi class="secno">2. </bdi>Conformance</a></li><li class="tocline"><a class="tocxref" href="#terminology"><bdi class="secno">3. </bdi>Terminology</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#device-categories"><bdi class="secno">3.1 </bdi>Device Categories</a></li></ol></li><li class="tocline"><a class="tocxref" href="#sec-application-domains"><bdi class="secno">4. </bdi>Application Domains</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#consumer-use-cases"><bdi class="secno">4.1 </bdi>Consumer</a></li><li class="tocline"><a class="tocxref" href="#industrial-iot-usecases"><bdi class="secno">4.2 </bdi>Industrial</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#example-smart-factory"><bdi class="secno">4.2.1 </bdi>Example: Smart Factory</a></li></ol></li><li class="tocline"><a class="tocxref" href="#transportationlogistics"><bdi class="secno">4.3 </bdi>Transportation
& Logistics</a></li><li class="tocline"><a class="tocxref" href="#utilities"><bdi class="secno">4.4 </bdi>Utilities</a></li><li class="tocline"><a class="tocxref" href="#oilandgas"><bdi class="secno">4.5 </bdi>Oil and Gas</a></li><li class="tocline"><a class="tocxref" href="#insurance"><bdi class="secno">4.6 </bdi>Insurance</a></li><li class="tocline"><a class="tocxref" href="#engineering-and-construction"><bdi class="secno">4.7 </bdi>Engineering
and Construction</a></li><li class="tocline"><a class="tocxref" href="#agriculture"><bdi class="secno">4.8 </bdi>Agriculture</a></li><li class="tocline"><a class="tocxref" href="#healthcare"><bdi class="secno">4.9 </bdi>Healthcare</a></li><li class="tocline"><a class="tocxref" href="#environmentmonitoring"><bdi class="secno">4.10 </bdi>Environment
Monitoring</a></li><li class="tocline"><a class="tocxref" href="#smartcities"><bdi class="secno">4.11 </bdi>Smart Cities</a></li><li class="tocline"><a class="tocxref" href="#smartbuildings"><bdi class="secno">4.12 </bdi>Smart Buildings</a></li><li class="tocline"><a class="tocxref" href="#connectedcar"><bdi class="secno">4.13 </bdi>Connected Car</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#connectedcar-example"><bdi class="secno">4.13.1 </bdi>Connected Car
Example</a></li></ol></li></ol></li><li class="tocline"><a class="tocxref" href="#sec-common-deployment-patterns"><bdi class="secno">5. </bdi>Common Deployment Patterns</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#telemetry"><bdi class="secno">5.1 </bdi>Telemetry</a></li><li class="tocline"><a class="tocxref" href="#device-controllers"><bdi class="secno">5.2 </bdi>Device Controllers</a></li><li class="tocline"><a class="tocxref" href="#thing-to-thing"><bdi class="secno">5.3 </bdi>Thing-to-Thing</a></li><li class="tocline"><a class="tocxref" href="#remote-access"><bdi class="secno">5.4 </bdi>Remote Access</a></li><li class="tocline"><a class="tocxref" href="#smart-home-gateways"><bdi class="secno">5.5 </bdi>Smart Home Gateways</a></li><li class="tocline"><a class="tocxref" href="#edge-devices"><bdi class="secno">5.6 </bdi>Edge Devices</a></li><li class="tocline"><a class="tocxref" href="#digital-twins"><bdi class="secno">5.7 </bdi>Digital Twins</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#cloud-connected-devices"><bdi class="secno">5.7.1 </bdi>Cloud Connected Devices</a></li><li class="tocline"><a class="tocxref" href="#orchestration"><bdi class="secno">5.7.2 </bdi>Orchestration</a></li><li class="tocline"><a class="tocxref" href="#legacy-devices"><bdi class="secno">5.7.3 </bdi>Legacy Devices</a></li></ol></li><li class="tocline"><a class="tocxref" href="#multi-cloud"><bdi class="secno">5.8 </bdi>Multi-Cloud</a></li><li class="tocline"><a class="tocxref" href="#virtual-thing"><bdi class="secno">5.9 </bdi>Virtual Things</a></li><li class="tocline"><a class="tocxref" href="#sec-cross-domain-collaboration"><bdi class="secno">5.10 </bdi>Cross-domain Collaboration</a></li><li class="tocline"><a class="tocxref" href="#sec-system-integration"><bdi class="secno">5.11 </bdi>System Integration</a></li></ol></li><li class="tocline"><a class="tocxref" href="#sec-wot-architecture"><bdi class="secno">6. </bdi>Abstract WoT System Architecture</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#sec-architecture-overview"><bdi class="secno">6.1 </bdi>Fundamental Concepts</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#metadata"><bdi class="secno">6.1.1 </bdi>Metadata</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#metadata-thing-descriptions"><bdi class="secno">6.1.1.1 </bdi>Thing Descriptions</a></li><li class="tocline"><a class="tocxref" href="#metadata-thing-models"><bdi class="secno">6.1.1.2 </bdi>Thing Models</a></li></ol></li><li class="tocline"><a class="tocxref" href="#links"><bdi class="secno">6.1.2 </bdi>Links</a></li><li class="tocline"><a class="tocxref" href="#intermediaries"><bdi class="secno">6.1.3 </bdi>Intermediaries</a></li></ol></li><li class="tocline"><a class="tocxref" href="#sec-affordances"><bdi class="secno">6.2 </bdi>Affordances</a></li><li class="tocline"><a class="tocxref" href="#sec-web-thing"><bdi class="secno">6.3 </bdi>Web Thing</a></li><li class="tocline"><a class="tocxref" href="#lifecycle"><bdi class="secno">6.4 </bdi>Lifecycle</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#simple-system-lifecycle"><bdi class="secno">6.4.1 </bdi>Simple System Lifecycle</a></li><li class="tocline"><a class="tocxref" href="#system-lifecycle-no-directory"><bdi class="secno">6.4.2 </bdi>System Lifecycle with Registration</a></li><li class="tocline"><a class="tocxref" href="#thing-lifecycle"><bdi class="secno">6.4.3 </bdi>Thing Lifecycle</a></li></ol></li><li class="tocline"><a class="tocxref" href="#sec-interaction-model"><bdi class="secno">6.5 </bdi>Interaction Model</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#properties"><bdi class="secno">6.5.1 </bdi>Properties</a></li><li class="tocline"><a class="tocxref" href="#actions"><bdi class="secno">6.5.2 </bdi>Actions</a></li><li class="tocline"><a class="tocxref" href="#events"><bdi class="secno">6.5.3 </bdi>Events</a></li></ol></li><li class="tocline"><a class="tocxref" href="#sec-hypermedia-controls"><bdi class="secno">6.6 </bdi>Hypermedia Controls</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#sec-hypermedia-links"><bdi class="secno">6.6.1 </bdi>Links</a></li><li class="tocline"><a class="tocxref" href="#sec-hypermedia-forms"><bdi class="secno">6.6.2 </bdi>Forms</a></li></ol></li><li class="tocline"><a class="tocxref" href="#sec-protocol-bindings"><bdi class="secno">6.7 </bdi>Protocol Bindings</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#hypermedia-driven"><bdi class="secno">6.7.1 </bdi>Hypermedia-driven</a></li><li class="tocline"><a class="tocxref" href="#sec-arch-URIs"><bdi class="secno">6.7.2 </bdi>URIs</a></li></ol></li><li class="tocline"><a class="tocxref" href="#media-types"><bdi class="secno">6.8 </bdi>Media Types</a></li><li class="tocline"><a class="tocxref" href="#sec-i18n"><bdi class="secno">6.9 </bdi>Internationalization</a></li><li class="tocline"><a class="tocxref" href="#sec-wot-servient-architecture-high-level"><bdi class="secno">6.10 </bdi>WoT System Components and their Interconnectivity</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#direct-communication"><bdi class="secno">6.10.1 </bdi>Direct Communication</a></li><li class="tocline"><a class="tocxref" href="#indirect-communication"><bdi class="secno">6.10.2 </bdi>Indirect Communication</a></li></ol></li></ol></li><li class="tocline"><a class="tocxref" href="#sec-building-blocks"><bdi class="secno">7. </bdi>WoT Building Blocks</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#sec-thing-description"><bdi class="secno">7.1 </bdi>WoT Thing Description</a></li><li class="tocline"><a class="tocxref" href="#sec-thing-model"><bdi class="secno">7.2 </bdi>Thing Model</a></li><li class="tocline"><a class="tocxref" href="#wot-profiles"><bdi class="secno">7.3 </bdi>Profiles</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#profile-description-methodology"><bdi class="secno">7.3.1 </bdi>Profiling Methodology</a></li></ol></li><li class="tocline"><a class="tocxref" href="#sec-discovery"><bdi class="secno">7.4 </bdi>WoT Discovery</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#sec-discovery-introductions"><bdi class="secno">7.4.1 </bdi>Introduction Mechanisms</a></li><li class="tocline"><a class="tocxref" href="#sec-discovery-exploration"><bdi class="secno">7.4.2 </bdi>Exploration Mechanisms</a></li></ol></li><li class="tocline"><a class="tocxref" href="#sec-binding-templates"><bdi class="secno">7.5 </bdi>WoT Binding Templates</a></li><li class="tocline"><a class="tocxref" href="#sec-scripting-api"><bdi class="secno">7.6 </bdi>WoT Scripting API</a></li><li class="tocline"><a class="tocxref" href="#sec-security-guidelines"><bdi class="secno">7.7 </bdi>WoT Security and Privacy Guidelines</a></li></ol></li><li class="tocline"><a class="tocxref" href="#sec-servient-implementation"><bdi class="secno">8. </bdi>Abstract Servient Architecture</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#behavior-implementation"><bdi class="secno">8.1 </bdi>Behavior Implementation</a></li><li class="tocline"><a class="tocxref" href="#wot-runtime"><bdi class="secno">8.2 </bdi>WoT Runtime</a></li><li class="tocline"><a class="tocxref" href="#wot-scripting-api"><bdi class="secno">8.3 </bdi>WoT Scripting API</a></li><li class="tocline"><a class="tocxref" href="#expose-consumed-thing"><bdi class="secno">8.4 </bdi>Exposed Thing and Consumed Thing Abstractions</a></li><li class="tocline"><a class="tocxref" href="#private-security-data"><bdi class="secno">8.5 </bdi>Private Security Data</a></li><li class="tocline"><a class="tocxref" href="#protocol-stack-implementation"><bdi class="secno">8.6 </bdi>Protocol Stack Implementation</a></li><li class="tocline"><a class="tocxref" href="#system-api"><bdi class="secno">8.7 </bdi>System API</a></li><li class="tocline"><a class="tocxref" href="#alt-servient-impl"><bdi class="secno">8.8 </bdi>Alternative Servient and WoT Implementations</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#native-impl"><bdi class="secno">8.8.1 </bdi>Native WoT API</a></li><li class="tocline"><a class="tocxref" href="#existing-impl"><bdi class="secno">8.8.2 </bdi>Thing Description for Existing Devices</a></li></ol></li></ol></li><li class="tocline"><a class="tocxref" href="#sec-deployment-scenario"><bdi class="secno">9. </bdi>Example WoT Deployments</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#sec-client-server-roles"><bdi class="secno">9.1 </bdi>Thing and Consumer Roles</a></li><li class="tocline"><a class="tocxref" href="#sec-topologies-deployment-scenarios"><bdi class="secno">9.2 </bdi>Topology of WoT Systems and Deployment Scenarios</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#sec-deployment-app-dev"><bdi class="secno">9.2.1 </bdi>Consumer and Thing on the Same Network</a></li><li class="tocline"><a class="tocxref" href="#sec-deployment-intermediaries"><bdi class="secno">9.2.2 </bdi>Consumer and Thing Connected via Intermediaries</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#sec-deployment-app-proxy-dev"><bdi class="secno">9.2.2.1 </bdi>Intermediary Acting as a Proxy</a></li><li class="tocline"><a class="tocxref" href="#sec-deployment-digital-twin"><bdi class="secno">9.2.2.2 </bdi>Intermediary Acting as a Digital Twin</a></li></ol></li><li class="tocline"><a class="tocxref" href="#sec-deployment-cloud"><bdi class="secno">9.2.3 </bdi>Devices in a Local Network Controlled from a Cloud Service</a></li><li class="tocline"><a class="tocxref" href="#sec-deployment-discovery-with-directory"><bdi class="secno">9.2.4 </bdi>Discovery Using a Thing Description Directory</a></li><li class="tocline"><a class="tocxref" href="#sec-deployment-service-to-service"><bdi class="secno">9.2.5 </bdi>Service-to-Service Connections Across Multiple Domains</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#sec-deployment-service-to-service-synchronized"><bdi class="secno">9.2.5.1 </bdi>Connection Through Thing Description Directory Synchronization</a></li><li class="tocline"><a class="tocxref" href="#sec-deployment-service-sync-proxy"><bdi class="secno">9.2.5.2 </bdi>Connection Through Proxy Synchronization</a></li></ol></li></ol></li></ol></li><li class="tocline"><a class="tocxref" href="#sec-security-considerations"><bdi class="secno">10. </bdi>Security Considerations</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#sec-security-consideration-td-risks"><bdi class="secno">10.1 </bdi>WoT Thing Description Risks</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#sec-security-consideration-td-private"><bdi class="secno">10.1.1 </bdi>Thing Description Private Security Data Risk</a></li><li class="tocline"><a class="tocxref" href="#sec-security-consideration-td-cm"><bdi class="secno">10.1.2 </bdi>Thing Description Communication Metadata Risk</a></li></ol></li><li class="tocline"><a class="tocxref" href="#sec-security-consideration-scripting-risks"><bdi class="secno">10.2 </bdi>WoT Scripting API Risks</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#sec-security-consideration-cross-script"><bdi class="secno">10.2.1 </bdi>Cross-Script Security Risk</a></li><li class="tocline"><a class="tocxref" href="#sec-security-consideration-device-direct-access"><bdi class="secno">10.2.2 </bdi>Physical Device Direct Access Risk</a></li></ol></li><li class="tocline"><a class="tocxref" href="#sec-security-consideration-runtime-risks"><bdi class="secno">10.3 </bdi>WoT Runtime Risks</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#sec-security-consideration-update-provisioning"><bdi class="secno">10.3.1 </bdi>Provisioning and Update Security Risk</a></li><li class="tocline"><a class="tocxref" href="#sec-security-consideration-credentials-storage"><bdi class="secno">10.3.2 </bdi>Security Credentials Storage Risk</a></li></ol></li><li class="tocline"><a class="tocxref" href="#sec-security-consideration-trusted-environment-risks"><bdi class="secno">10.4 </bdi>Trusted Environment Risks</a></li><li class="tocline"><a class="tocxref" href="#sec-security-consideration-secure-transport"><bdi class="secno">10.5 </bdi>Secure Transport</a></li></ol></li><li class="tocline"><a class="tocxref" href="#sec-privacy-considerations"><bdi class="secno">11. </bdi>Privacy Considerations</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#sec-privacy-consideration-td-risks"><bdi class="secno">11.1 </bdi>WoT Thing Description Risks</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#sec-privacy-consideration-td-pii"><bdi class="secno">11.1.1 </bdi>Thing Description Personally Identifiable
Information Risk</a></li></ol></li><li class="tocline"><a class="tocxref" href="#arch-privacy-consideration-access-controls"><bdi class="secno">11.2 </bdi>Access to Personally Identifiable Information</a></li></ol></li><li class="tocline"><a class="tocxref" href="#sec-accessibility-considerations"><bdi class="secno">12. </bdi>Accessibility Considerations</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#sec-accessibility-considerations-greenfield"><bdi class="secno">12.1 </bdi>Greenfield WoT Systems</a></li><li class="tocline"><a class="tocxref" href="#sec-accessibility-considerations-brownfield"><bdi class="secno">12.2 </bdi>Brownfield WoT Systems</a></li></ol></li><li class="tocline"><a class="tocxref" href="#changes"><bdi class="secno">A. </bdi>Recent Specification Changes</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#changes-from-cr"><bdi class="secno">A.1 </bdi>Changes from 19 January 2023 Candidate Recommendation</a></li><li class="tocline"><a class="tocxref" href="#changes-from-wd-2022-09-07"><bdi class="secno">A.2 </bdi>Changes from the WD published September 7, 2022</a></li><li class="tocline"><a class="tocxref" href="#changes-from-fpwd-1.1"><bdi class="secno">A.3 </bdi>Changes in WD published September 7, 2022 from the FPWD version</a></li><li class="tocline"><a class="tocxref" href="#changes-in-fpwd-1.1-from-recommendation-1.0"><bdi class="secno">A.4 </bdi>Changes in the FPWD from the 1.0 version of [<cite><span class="formerLink" data-link-type="biblio" title="Web of Things (WoT) Architecture">wot-architecture</span></cite>]</a></li></ol></li><li class="tocline"><a class="tocxref" href="#acknowledgements"><bdi class="secno">B. </bdi>Acknowledgments</a></li><li class="tocline"><a class="tocxref" href="#references"><bdi class="secno">C. </bdi>References</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#normative-references"><bdi class="secno">C.1 </bdi>Normative references</a></li><li class="tocline"><a class="tocxref" href="#informative-references"><bdi class="secno">C.2 </bdi>Informative references</a></li></ol></li></ol></nav>
<section id="introduction" class="informative"><div class="header-wrapper"><h2 id="x1-introduction"><bdi class="secno">1. </bdi>Introduction</h2><a class="self-link" href="#introduction" aria-label="Permalink for Section 1."></a></div><p><em>This section is non-normative.</em></p>
<p>The goals of the <em>Web of Things</em> (WoT) are to improve the interoperability
and usability of the Internet of Things (IoT). Through a collaboration
involving many stakeholders over many years, several building
blocks have been identified that help address these challenges.
</p>
<p>A set of over 30 WoT <em>use cases</em> were contributed by stakeholders from multiple industries for various
application domains.
These have been collected and were published in the <em>WoT Use Cases and Requirements</em>
<a href="https://www.w3.org/TR/wot-usecases/">https://www.w3.org/TR/wot-usecases/</a> document.
</p>
<p>
The collection of use cases is classified into two categories:
</p>
<ul>
<li>Horizontal use cases that address multiple domains</li>
<li>Domain specific (vertical) use cases for a single application domain</li>
</ul>
<p>These use cases and requirements drive the creation and further evolution
of the <abbr title="World Wide Web Consortium">W3C</abbr> WoT specification family.</p>
<p>The WoT architecture specification is focused on the scope of <abbr title="World Wide Web Consortium">W3C</abbr> WoT standardization,
which can be broken down into these building blocks as well as the abstract
architecture that defines how they are related.
</p><p>
The architecture document serves multiple purposes:
</p>
<p>
The building blocks are defined and described in detail in separate specifications.
In addition to defining the abstract architecture and its terminology and
conceptual framework,
this specification also serves as an introduction to the WoT building blocks,
and explains their interworking:</p>
<ul>
<li>The <em>Web of Things (WoT) Thing Description</em> [<cite><a class="bibref" data-link-type="biblio" href="#bib-wot-thing-description" title="Web of Things (WoT) Thing Description 1.1">WOT-THING-DESCRIPTION</a></cite>]
normatively provides a machine-readable
data format for describing the metadata and network-facing interfaces of Things.
It is based upon the fundamental concepts introduced in this document, such as
interaction affordances.
</li>
<li>The <em>Web of Things (WoT) Binding Templates</em> [<cite><a class="bibref" data-link-type="biblio" href="#bib-wot-binding-templates" title="Web of Things (WoT) Binding Templates">WOT-BINDING-TEMPLATES</a></cite>]
provides informational guidelines on how to define network-facing interfaces in Things for
particular protocols and IoT ecosystems, which we call Protocol Bindings.
The document also provides examples for a number of existing IoT
ecosystems and standards.
</li>
<li>The <em>Web of Things (WoT) Discovery</em> [<cite><a class="bibref" data-link-type="biblio" href="#bib-wot-discovery" title="Web of Things (WoT) Discovery">WOT-DISCOVERY</a></cite>]
specification defines a distribution mechanism for WoT metadata
(<a href="#dfn-thing-description" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-thing-description-1">Thing Descriptions</a>).
The WoT Discovery process uses existing mechanisms for first
contact, but provides for access control before serving detailed metadata.
It includes support for directories and self-description.
</li>
<li>The <em>Web of Things (WoT) Scripting API</em> [<cite><a class="bibref" data-link-type="biblio" href="#bib-wot-scripting-api" title="Web of Things (WoT) Scripting API">WOT-SCRIPTING-API</a></cite>],
which is optional, enables the implementation of
the application logic of a Thing using a common JavaScript API
similar to the Web browser APIs. This simplifies IoT application
development and enables portability across vendors and devices.
</li>
<li>The <em>Web of Things (WoT) Security and Privacy Guidelines</em> [<cite><a class="bibref" data-link-type="biblio" href="#bib-wot-security" title="Web of Things (WoT) Security and Privacy Guidelines">WOT-SECURITY</a></cite>]
represent a cross-cutting building block.
This informational document provides guidelines for the secure implementation and
configuration of Things,
and discusses issues which should be considered in any systems implementing <abbr title="World Wide Web Consortium">W3C</abbr> WoT.
However, it should be emphasized that
security and privacy can only be fully evaluated in the context
of a complete set of concrete mechanisms for a specific implementation,
which goes beyond the scope of the WoT abstract architecture.
This is especially
true when the WoT architecture is used descriptively for pre-existing systems,
since the <abbr title="World Wide Web Consortium">W3C</abbr> WoT cannot constrain the behavior of such systems, it can only
describe them.
In this document we also discuss privacy and security risks and their mitigation
at a high level in sections <a href="#sec-security-considerations" class="sec-ref"><bdi class="secno">10. </bdi>Security Considerations</a>
and <a href="#sec-privacy-considerations" class="sec-ref"><bdi class="secno">11. </bdi>Privacy Considerations</a>.
</li>
</ul>
<p>This specification also covers non-normative architectural aspects
and conditions for the deployment of WoT systems.
These guidelines are described in the context of example deployment scenarios,
although this specification does not require specific concrete
implementations.
</p>
<p>This specification serves as an umbrella for <abbr title="World Wide Web Consortium">W3C</abbr> WoT
specifications and defines the basics such as terminology
and the underlying abstract architecture of the <abbr title="World Wide Web Consortium">W3C</abbr> Web of
Things. In summary, the purpose of this specification is to
provide:</p>
<ul>
<li>a set of application domains in <a href="#sec-application-domains" class="sec-ref"><bdi class="secno">4. </bdi>Application Domains</a>
that were considered to identify use cases for the <abbr title="World Wide Web Consortium">W3C</abbr> WoT Architecture,
</li>
<li>a set of common deployment patterns in
<a href="#sec-common-deployment-patterns" class="sec-ref"><bdi class="secno">5. </bdi>Common Deployment Patterns</a>,
</li>
<li>a definition of the abstract architecture in
<a href="#sec-wot-architecture" class="sec-ref"><bdi class="secno">6. </bdi>Abstract WoT System Architecture</a>,
</li>
<li>an overview of a set of WoT building blocks
and their interplay in <a href="#sec-building-blocks" class="sec-ref"><bdi class="secno">7. </bdi>WoT Building Blocks</a>,
</li>
<li>an informative guideline on how to map the abstract architecture to
concrete implementations in
<a href="#sec-servient-implementation" class="sec-ref"><bdi class="secno">8. </bdi>Abstract Servient Architecture</a>,
</li>
<li>informative examples of deployment scenarios in
<a href="#sec-deployment-scenario" class="sec-ref"><bdi class="secno">9. </bdi>Example WoT Deployments</a>,
</li>
<li>and a set of high level
security and privacy considerations to be aware of when
implementing a system based on the <abbr title="World Wide Web Consortium">W3C</abbr> WoT architecture in
<a href="#sec-security-considerations" class="sec-ref"><bdi class="secno">10. </bdi>Security Considerations</a> and
<a href="#sec-privacy-considerations" class="sec-ref"><bdi class="secno">11. </bdi>Privacy Considerations</a>, respectively.
</li>
</ul>
<p>Additional requirements, use cases, conceptual features and new building blocks
are collected in future versions of the <em>WoT Use Cases and Requirement </em>
<a href="https://www.w3.org/TR/wot-usecases/">https://www.w3.org/TR/wot-usecases/</a> document.
</p>
</section>
<section id="conformance"><div class="header-wrapper"><h2 id="x2-conformance"><bdi class="secno">2. </bdi>Conformance</h2><a class="self-link" href="#conformance" aria-label="Permalink for Section 2."></a></div><p>As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.</p><p>
The key words <em class="rfc2119">MAY</em>, <em class="rfc2119">MUST</em>, <em class="rfc2119">MUST NOT</em>, <em class="rfc2119">SHOULD</em>, and <em class="rfc2119">SHOULD NOT</em> in this document
are to be interpreted as described in
<a href="https://datatracker.ietf.org/doc/html/bcp14">BCP 14</a>
[<cite><a class="bibref" data-link-type="biblio" href="#bib-rfc2119" title="Key words for use in RFCs to Indicate Requirement Levels">RFC2119</a></cite>] [<cite><a class="bibref" data-link-type="biblio" href="#bib-rfc8174" title="Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words">RFC8174</a></cite>]
when, and only when, they appear in all capitals, as shown here.
</p></section>
<section id="terminology" class="informative"><div class="header-wrapper"><h2 id="x3-terminology"><bdi class="secno">3. </bdi>Terminology</h2><a class="self-link" href="#terminology" aria-label="Permalink for Section 3."></a></div><p><em>This section is non-normative.</em></p>
<p>This specification uses the following terms as defined here.
The WoT prefix is used to avoid ambiguity for terms that are
(re)defined specifically for Web of Things concepts.</p>
<p>
In case of a conflict of a definition with terminology used in another
WoT document, the definition of the WoT Architecture takes precedence.
</p>
<dl>
<dt>
<dfn data-plurals="actions" id="dfn-action" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Action</dfn>
</dt>
<dd>An Interaction Affordance that allows to invoke a
function of the Thing, which manipulates state
(e.g., toggling a lamp on or off)
or triggers a process on the Thing (e.g., dim a lamp over time).</dd>
<dt>
<dfn data-lt="WoT Anonymous Thing Description|Anonymous TD" class="lint-ignore" id="dfn-wot-anonymous-thing-description" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Anonymous TD</dfn>
</dt>
<dd>A Thing Description without a user-defined identifier (<code>id</code> attribute).</dd>
<dt>
<dfn id="dfn-connected-device" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Connected Device</dfn>
</dt>
<dd>
A synonym for <a href="#dfn-device" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-device-1">Device</a>.</dd>
<dt>
<dfn data-lt="WoT Binding Templates|Binding Templates" data-plurals="binding template" id="dfn-wot-binding-templates" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Binding
Templates</dfn>
</dt>
<dd>
A re-usable collection of blueprints that enable a Thing Description
to be used with a specific protocol, data payload format or an IoT
platform that combine both of them in specific ways. This is done through
additional descriptive vocabularies, Thing Models and examples that aim
to guide the implementers of Things and Consumers alike. </dd>
<dt>
<dfn data-plurals="consumed things" id="dfn-consumed-thing" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Consumed Thing</dfn>
</dt>
<dd>A software abstraction that represents a remote
Thing used by the local application. The abstraction might be
created by a native WoT Runtime, or instantiated
as an object through the WoT Scripting API.</dd>
<dt>
<dfn data-plurals="content types" id="dfn-content-type" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Content Type</dfn>
</dt>
<dd>Identifier for the format of the message body.
Also known as media type and MIME type [<cite><a class="bibref" data-link-type="biblio" href="#bib-rfc2046" title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">RFC2046</a></cite>]. </dd>
<dt>
<dfn class="lint-ignore" id="dfn-consuming-a-thing" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Consuming a Thing</dfn>
</dt>
<dd>To parse and process a TD document and from it create a Consumed
Thing software abstraction as interface for the application in the local
runtime environment.</dd>
<dt>
<dfn data-plurals="consumers" id="dfn-consumer" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Consumer</dfn>
</dt>
<dd>An entity that can process WoT Thing Descriptions
(including its JSON-based representation format)
and interact with Things (i.e., consume Things).</dd>
<dt>
<dfn data-plurals="data schemas" id="dfn-data-schema" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Data Schema</dfn>
</dt>
<dd>A data schema describes the information model and the related payload structure
and corresponding data items that are passed between <a href="#dfn-thing" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-thing-1">Things</a>
and <a href="#dfn-consumer" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-consumer-1">Consumers</a> during interactions.</dd>
<dt>
<dfn data-plurals="devices" id="dfn-device" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Device</dfn>
</dt>
<dd>A Device is a physical entity that has a network interface.
Devices can be described by a <a href="#dfn-thing-description" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-thing-description-2">Thing Description</a> and are a kind of <a href="#dfn-thing" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-thing-2">Thing</a>.
A synonym for <a href="#dfn-connected-device" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-connected-device-1">Connected Device</a>.
Compare with <a href="#dfn-service" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-service-1">Service</a>.</dd>
<dt>
<dfn data-plurals="digital twins" id="dfn-digital-twin" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Digital Twin</dfn>
</dt>
<dd>A digital twin is type of <a href="#dfn-virtual-thing" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-virtual-thing-1">Virtual Thing</a>
that resides on a cloud or edge node.
Digital Twins may be used to represent and provide
a network interface for
real-world devices which may not be continuously online
(see also <a href="#dfn-shadow" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-shadow-1">Shadows</a>),
may be able to run simulations of new applications and services
before they get deployed to the real devices,
may be able to maintain a history of past state or behaviour,
and may be able to predict future state or behaviour.
Digital Twins typically have more functionality than
simple <a href="#dfn-shadow" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-shadow-2">Shadows</a>.
</dd>
<dt>
<dfn class="lint-ignore" id="dfn-directory" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Directory</dfn>
</dt>
<dd>A <a href="#dfn-service" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-service-2">Service</a> that maintains a set of data or metadata describing other <a href="#dfn-service" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-service-3">Services</a>
or <a href="#dfn-thing" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-thing-3">Things</a>. An example would be a <a href="#dfn-wot-thing-description-directory" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-wot-thing-description-directory-1">WoT Thing Description Directory</a>.</dd>
<dt><dfn data-lt="WoT Discovery|Discovery" id="dfn-wot-discovery" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Discovery</dfn>
</dt><dd>Mechanisms defined by WoT for distributing and accessing
<a href="#dfn-wot-thing-description" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-wot-thing-description-1">WoT Thing Descriptions</a> on the network,
either locally or remotely.</dd>
<dt>
<dfn data-lt="WoT Discoverer|Discoverer" class="lint-ignore" id="dfn-wot-discoverer" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Discoverer</dfn>
</dt>
<dd>An entity which acts as a client of a WoT Discovery process to discover
and fetch a <a href="#dfn-thing-description" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-thing-description-3">Thing Description</a>,
e.g. by being introduced to and searching a
<a href="#dfn-wot-thing-description-directory" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-wot-thing-description-directory-2">Thing Description Directory</a> exploration service or by
fetching a <a href="#dfn-thing-description" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-thing-description-4">Thing Description</a> directly from
the well-known endpoint on a Thing.
</dd>
<dt>
<dfn data-plurals="domain-specific vocabularies" id="dfn-domain-specific-vocabulary" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Domain-specific Vocabulary</dfn>
</dt>
<dd>Linked Data vocabulary that can be used in the WoT
Thing Description, but is not defined by <abbr title="World Wide Web Consortium">W3C</abbr> WoT.</dd>
<dt>
<dfn id="dfn-edge-device" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Edge Device</dfn>
</dt>
<dd>A device that provides an entry point into
enterprise or service provider core networks. Examples
include hubs, gateways, routers, switches, multiplexers, and a
variety of other access devices.</dd>
<dt>
<dfn data-lt="WoT Enriched Thing Description|Enriched TD" class="lint-ignore" id="dfn-wot-enriched-thing-description" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Enriched TD</dfn>
</dt>
<dd>A Thing Description embedded with additional attributes
for bookkeeping and discovery.</dd>
<dt>
<dfn data-plurals="events" id="dfn-event" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Event</dfn>
</dt>
<dd>An Interaction Affordance that describes an event source,
which asynchronously pushes event data to Consumers
(e.g., overheating alerts).</dd>
<dt>
<dfn data-lt="WoT Exploration|Exploration" id="dfn-wot-exploration" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Exploration</dfn>
</dt>
<dd>A discovery mechanism that provides access to detailed metadata in the
form of one or more Thing Descriptions. Exploration mechanisms are in
general protected by security mechanism and are accessible only to authorized users.
</dd>
<dt>
<dfn data-plurals="exposed things" id="dfn-exposed-thing" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Exposed Thing</dfn>
</dt>
<dd>A software abstraction that represents a locally hosted Thing
that can be accessed over the network by remote Consumers.
The abstraction might be created by a native WoT Runtime,
or instantiated as an object through the WoT Scripting API.</dd>
<dt>
<dfn class="lint-ignore" id="dfn-exposing-a-thing" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Exposing a Thing</dfn>
</dt>
<dd>To create an Exposed Thing software abstraction in the
local runtime environment to manage the state of a Thing
and interface with the behavior implementation.</dd>
<dt>
<dfn data-plurals="hypermedia controls" id="dfn-hypermedia-control" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Hypermedia Control</dfn>
</dt>
<dd>A serialization of a Protocol Binding in hypermedia, that is,
either a Web link [<cite><a class="bibref" data-link-type="biblio" href="#bib-rfc8288" title="Web Linking">RFC8288</a></cite>] for navigation or a Web form for
performing other operations. Forms can be seen as request templates
provided by the Thing to be completed and sent by the Consumer.</dd>
<dt>
<dfn data-plurals="interaction affordances" id="dfn-interaction-affordance" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Interaction Affordance</dfn>
</dt>
<dd>
Metadata of a Thing that shows and describes the possible choices to Consumers,
thereby suggesting how Consumers may interact with the Thing.
There are many types of potential affordances, but
<abbr title="World Wide Web Consortium">W3C</abbr> WoT defines three types of Interaction Affordances:
Properties, Actions, and Events.
A fourth Interaction Affordance is navigation, which is already available on the Web through linking.</dd>
<dt>
<dfn id="dfn-interaction-model" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Interaction Model</dfn>
</dt>
<dd>An intermediate abstraction that formalizes and narrows the
mapping from application intent to concrete protocol operations.
In <abbr title="World Wide Web Consortium">W3C</abbr> WoT, the defined set of Interaction Affordances constitutes the Interaction Model.</dd>
<dt>
<dfn data-plurals="intermediaries" id="dfn-intermediary" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Intermediary</dfn>
</dt>
<dd>An entity between Consumers and Things that can proxy, augment, or compose Things
and republish a WoT Thing Description that points to the WoT Interface on the Intermediary instead of the
original Thing.
For Consumers, an Intermediary may be indistinguishable from a Thing, following the Layered System constraint of
REST.</dd>
<dt>
<dfn data-lt="WoT Introduction|Introduction" id="dfn-wot-introduction" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Introduction</dfn>
</dt>
<dd>A "first contact" discovery mechanism, whose result is a URL that
references an exploration mechanism. Introduction mechanisms themselves
should not directly provide metadata, and in general are designed to be
open.
</dd>
<dt>
<dfn data-plurals="iot platforms" id="dfn-iot-platform" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">IoT Platform</dfn>
</dt>
<dd>A specific IoT ecosystem such as OCF, oneM2M, or
Mozilla Project Things with its own specifications for
application-facing APIs, data model, and protocols or
protocol configurations.</dd>
<dt>
<dfn class="lint-ignore" id="dfn-metadata" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Metadata</dfn>
</dt>
<dd>Data that provides a description of an entity's abstract characteristics.
For example, a <a href="#dfn-thing-description" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-thing-description-5">Thing Description</a> is Metadata for a <a href="#dfn-thing" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-thing-4">Thing</a>.</dd>
<dt>
<dfn data-lt="Personally Identifiable Information|Personally Identifiable Information (PII)" id="dfn-personally-identifiable-information" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Personally Identifiable Information (PII)</dfn>
</dt>
<dd>
Any information that can be used to identify the natural person to whom such information relates,
or is or might be directly or indirectly linked to a natural person.
We use the same definition as [<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-iec-29100" title="Information technology — Security techniques — Privacy framework">ISO-IEC-29100</a></cite>].
</dd>
<dt>
<dfn class="lint-ignore" id="dfn-orchestration" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Orchestration</dfn>
</dt>
<dd>
The automation of the behavior of a collection of things.
Orchestration is combining individual things with rules or services
into a new service or virtual <a href="#dfn-thing" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-thing-5">Thing</a>.
</dd>
<dt>
<dfn id="dfn-partial-td" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Partial TD</dfn>
</dt>
<dd>
A <a href="#dfn-partial-td" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-partial-td-1">Partial TD</a> is an object that follows the same hierarchical structure of the <a href="#dfn-td" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-td-1">TD</a> information model,
but it is not required to contain all the mandatory elements.
<p>
Note: An example for the usage of a <a href="#dfn-partial-td" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-partial-td-2">Partial TD</a> is in <a href="#dfn-wot-scripting-api" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-wot-scripting-api-1">WoT Scripting API</a>,
where it is used as input for the creation of <a href="#dfn-exposed-thing" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-exposed-thing-1">Exposed Things</a>.
</p></dd>
<dt>
<dfn class="lint-ignore" id="dfn-privacy" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Privacy</dfn>
</dt>
<dd>Freedom from intrusion into the private life or affairs of an individual when that intrusion results from
undue or illegal gathering and use of data about that individual.
We use the same definition as [<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-iec-2382" title="Information technology — Vocabulary">ISO-IEC-2382</a></cite>].
See also <a href="#dfn-personally-identifiable-information" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-personally-identifiable-information-1">Personally Identifiable Information</a> and <a href="#dfn-security" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-security-1">Security</a>,
as well as other related definitions in [<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-iec-29100" title="Information technology — Security techniques — Privacy framework">ISO-IEC-29100</a></cite>].
</dd>
<dt>
<dfn id="dfn-private-security-data" tabindex="0" aria-haspopup="dialog" data-dfn-type="dfn">Private Security Data</dfn>
</dt>
<dd>
Private Security Data is that component of a Thing's <a href="#dfn-security-configuration" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-security-configuration-1">Security Configuration</a> that is
kept secret and is not shared with other devices or users. An example would be private keys in a PKI
system. Ideally such data is stored in a separate memory inaccessible to the application