-
Notifications
You must be signed in to change notification settings - Fork 13
/
Copy pathxep-0000-IoT-Interoperability.xml
6485 lines (6479 loc) · 209 KB
/
xep-0000-IoT-Interoperability.xml
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
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE xep SYSTEM 'xep.dtd' [
<!ENTITY % ents SYSTEM 'xep.ent'>
%ents;
]>
<!-- TODO: byte codes for identification + xml file with interface data. + version numbers -->
<!-- TODO: Another XEP: Billing interfaces. Tariffs. Prepayment. -->
<!-- TODO: Standardized Short field names (2 characters) for memory constrained devices. -->
<!-- TODO: Better anchor points. -->
<!-- TODO: FIX: nodeId optional, inte required. -->
<!-- TODO: getInterfaces-fråga med nodeId (concentrator-fallet) -->
<!-- TODO: XMPP.IoT.Security.Alarm får inte användas av de andra alarm-interfacen. En enhet kan ha flera olika alarm. Fältnamnet måste identifiera alarmtypen. -->
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
<!--
© Clayster 2013-2014
Author: Peter Waher
-->
<xep>
<header>
<title>Internet of Things - Interoperability</title>
<abstract>This specification provides interoperability guidelines for sensors and actuators in Internet of Things based on XMPP.</abstract>
&LEGALNOTICE;
<number>xxxx</number>
<status>ProtoXEP</status>
<type>Standards Track</type>
<sig>Standards</sig>
<approver>Council</approver>
<dependencies>
<spec>XEP-0001</spec>
<spec>XEP-0030</spec>
<spec>XEP-0323</spec>
<spec>XEP-0324</spec>
<spec>XEP-0325</spec>
<spec>XEP-0326</spec>
</dependencies>
<supersedes/>
<supersededby/>
<shortname>NOT_YET_ASSIGNED</shortname>
<author>
<firstname>Peter</firstname>
<surname>Waher</surname>
<email>peter.waher@clayster.com</email>
<jid>peter.waher@jabber.org</jid>
<uri>http://www.linkedin.com/in/peterwaher</uri>
</author>
<revision>
<version>0.0.1</version>
<date>2013-04-04</date>
<initials>pw</initials>
<remark>
<p>First draft.</p>
</remark>
</revision>
</header>
<section1 topic='Introduction' anchor='intro'>
<p>
There are multiple XEP's controlling how different parties exchange information between each other across the XMPP-based sensor network. However, to achieve
interoperability between products of different manufacturers, common rules need to be adhered to by all parties involved, so data and information can be freely
interchanged and understood throughout the network. This document defines such interoperability rules.
</p>
<p>
Internet of Things contains many different architectures and use cases. For this reason, the IoT standards have been divided into multiple XEPs according to the following table:
</p>
<table caption='Internet of Things XEPs'>
<tr>
<th>XEP</th>
<th>Description</th>
</tr>
<tr>
<td>xep-0000-IoT-BatteryPoweredSensors</td>
<td>Defines how to handle the peculiars related to battery powered devices, and other devices intermittently available on the network.</td>
</tr>
<tr>
<td>xep-0000-IoT-Events</td>
<td>Defines how sensors send events, how event subscription, hysteresis levels, etc., are configured.</td>
</tr>
<tr>
<td>xep-0000-IoT-Interoperability</td>
<td>This specification. Defines guidelines for how to achieve interoperability in Internet of Things, publishing interoperability interfaces for different types of devices.</td>
</tr>
<tr>
<td>xep-0000-IoT-Multicast</td>
<td>Defines how sensor data can be multicast in efficient ways.</td>
</tr>
<tr>
<td>xep-0000-IoT-PubSub</td>
<td>Defines how efficient publication of sensor data can be made in Internet of Things.</td>
</tr>
<tr>
<td>xep-0000-IoT-Chat</td>
<td>Defines how human-to-machine interfaces should be constructed using chat messages to be user friendly, automatable and consistent with other IoT extensions and possible underlying architecture.</td>
</tr>
<tr>
<td>XEP-0322</td>
<td>
Defines how to EXI can be used in XMPP to achieve efficient compression of data. Albeit not a sensor network specific XEP, this XEP should be considered
in all sensor network implementations where memory and packet size is an issue.
</td>
</tr>
<tr>
<td>XEP-0323</td>
<td>
Provides the underlying architecture, basic operations and data structures for sensor data communication over XMPP networks.
It includes a hardware abstraction model, removing any technical detail implemented in underlying technologies. This XEP is used by all other sensor network XEPs.
</td>
</tr>
<tr>
<td>XEP-0324</td>
<td>Defines how provisioning, the management of access privileges, etc., can be efficiently and easily implemented.</td>
</tr>
<tr>
<td>XEP-0325</td>
<td>Defines how to control actuators and other devices in Internet of Things.</td>
</tr>
<tr>
<td>XEP-0326</td>
<td>Defines how to handle architectures containing concentrators or servers handling multiple sensors.</td>
</tr>
<tr>
<td>XEP-0331</td>
<td>Defines extensions for how color parameters can be handled, based on &xep0004;</td>
</tr>
<tr>
<td>XEP-0336</td>
<td>Defines extensions for how dynamic forms can be created, based on &xep0004;, &xep0122;, &xep0137; and &xep0141;.</td>
</tr>
<tr>
<td>XEP-0347</td>
<td>Defines the peculiars of sensor discovery in sensor networks. Apart from discovering sensors by JID, it also defines how to discover sensors based on location, etc.</td>
</tr>
</table>
</section1>
<section1 topic='Glossary' anchor='glossary'>
<p>The following table lists common terms and corresponding descriptions.</p>
<dl>
<di>
<dt>Actuator</dt>
<dd>Device containing at least one configurable property or output that can and should be controlled by some other entity or device.</dd>
</di>
<di>
<dt>Computed Value</dt>
<dd>A value that is computed instead of measured.</dd>
</di>
<di>
<dt>Concentrator</dt>
<dd>Device managing a set of devices which it publishes on the XMPP network.</dd>
</di>
<di>
<dt>Field</dt>
<dd>
One item of sensor data. Contains information about: Node, Field Name, Value, Precision, Unit, Value Type, Status, Timestamp, Localization information, etc.
Fields should be unique within the triple (Node ID, Field Name, Timestamp).
</dd>
</di>
<di>
<dt>Field Name</dt>
<dd>Name of a field of sensor data. Examples: Energy, Volume, Flow, Power, etc.</dd>
</di>
<di>
<dt>Field Type</dt>
<dd>What type of value the field represents. Examples: Momentary Value, Status Value, Identification Value, Calculated Value, Peak Value, Historical Value, etc.</dd>
</di>
<di>
<dt>Historical Value</dt>
<dd>A value stored in memory from a previous timestamp.</dd>
</di>
<di>
<dt>Identification Value</dt>
<dd>A value that can be used for identification. (Serial numbers, meter IDs, locations, names, etc.)</dd>
</di>
<di>
<dt>Localization information</dt>
<dd>Optional information for a field, allowing the sensor to control how the information should be presented to human viewers.</dd>
</di>
<di>
<dt>Meter</dt>
<dd>A device possible containing multiple sensors, used in metering applications. Examples: Electricity meter, Water Meter, Heat Meter, Cooling Meter, etc.</dd>
</di>
<di>
<dt>Momentary Value</dt>
<dd>A momentary value represents a value measured at the time of the read-out.</dd>
</di>
<di>
<dt>Node</dt>
<dd>
Graphs contain nodes and edges between nodes. In Internet of Things, sensors, actuators, meters, devices, gatewats, etc., are often depicted as nodes whereas links between sensors (friendships)
are depicted as edges. In abstract terms, it's easier to talk about a Node, rather than list different possible node types (sensors, actuators, meters, devices, gateways, etc.).
Each Node has a Node ID.
</dd>
</di>
<di>
<dt>Node ID</dt>
<dd>
An ID uniquely identifying a node within its corresponding context. If a globally unique ID is desired, an architecture should be used using a universally accepted
ID scheme.
</dd>
</di>
<di>
<dt>Parameter</dt>
<dd>
Readable and/or writable property on a node/device. The XEP-0326 &xep0326; deals with reading and writing parameters
on nodes/devices. Fields are not parameters, and parameters are not fields.
</dd>
</di>
<di>
<dt>Peak Value</dt>
<dd>A maximum or minimum value during a given period.</dd>
</di>
<di>
<dt>Precision</dt>
<dd>
In physics, precision determines the number of digits of precision. In sensor networks however, this definition is not easily applicable. Instead, precision
determines, for example, the number of decimals of precision, or power of precision. Example: 123.200 MWh contains 3 decimals of precision. All entities parsing and
delivering field information in sensor networks should always retain the number of decimals in a message.
</dd>
</di>
<di>
<dt>Sensor</dt>
<dd>
Device measuring at least one digital value (0 or 1) or analog value (value with precision and physical unit). Examples: Temperature sensor, pressure sensor, etc.
Sensor values are reported as fields during read-out. Each sensor has a unique Node ID.
</dd>
</di>
<di>
<dt>SN</dt>
<dd>Sensor Network. A network consisting, but not limited to sensors, where transport and use of sensor data is of primary concern. A sensor network may contain actuators, network applications, monitors, services, etc.</dd>
</di>
<di>
<dt>Status Value</dt>
<dd>A value displaying status information about something.</dd>
</di>
<di>
<dt>Timestamp</dt>
<dd>Timestamp of value, when the value was sampled or recorded.</dd>
</di>
<di>
<dt>Token</dt>
<dd>
A client, device or user can get a token from a provisioning server. These tokens can be included in requests to other entities in the network, so these entities can validate
access rights with the provisioning server.
</dd>
</di>
<di>
<dt>Unit</dt>
<dd>Physical unit of value. Example: MWh, l/s, etc.</dd>
</di>
<di>
<dt>Value</dt>
<dd>A field value.</dd>
</di>
<di>
<dt>Value Status</dt>
<dd>Status of field value. Contains important status information for Quality of Service purposes. Examples: Ok, Error, Warning, Time Shifted, Missing, Signed, etc.</dd>
</di>
<di>
<dt>Value Type</dt>
<dd>Can be numeric, string, boolean, Date & Time, Time Span or Enumeration.</dd>
</di>
<di>
<dt>WSN</dt>
<dd>Wireless Sensor Network, a sensor network including wireless devices.</dd>
</di>
<di>
<dt>XMPP Client</dt>
<dd>Application connected to an XMPP network, having a JID. Note that sensors, as well as applications requesting sensor data can be XMPP clients.</dd>
</di>
</dl>
</section1>
<section1 topic='Use Cases' anchor='usecases'>
<p>
The basic tool for creating interoperability in large networks where many different devices from many different manufacturers needs to interoperate, is to
create recognized interfaces with well defined attributes. Each interface represents a contract that the device promises to uphold. It consists of mandatory
and optional parts. If the device implements any optional funcionality, it must implement them as defined by the corresponding interface.
</p>
<p>
Interfaces are categorized, grouped and named using a sequence of parts separated using period (.) characters. The interfaces in this document all begin with
"<strong>XMPP.</strong>". Any manufacturer is free to create their own interfaces, however these must start with a name they control, for instance the name of
the company.
</p>
<p>
The next part name in the name of interfaces listed in this document is "<strong>IoT.</strong>" meaning interfaces related to Internet of Things - i.e. communication
as specified in the XEPs listed in the <link url='#intro'>Introduction</link>. Here companies creating their own interfaces are free to choose any grouping
they desire. If the subgroup is not equal to "<strong>IoT.</strong>" and the root is "<strong>XMPP.</strong>", then a corresponding XEP will define the interfaces
for that subgroup of interfaces. This document thus defines all interfaces starting with "<strong>XMPP.IoT.</strong>".
</p>
<p>
Note also that devices are free to add any number of fields, control parameters, units, etc., as they desire. The interfaces listed here only define a minimum
of the former, to facilitate interopability. They also list optional extensions that should be adhered to, if used, for the same reasons.
</p>
<p>
<strong>Important:</strong> The author(s) encourage active participation in defining new interfaces or enhancing existing interfaces within the XMPP namespace,
all in an effort to create as large a communicty as possible that can agree on a set of interoperable interfaces that can be used to interchange information in
XMPP networks. For more information, please see <link url='#newinterfaces'>Extending the Interoperability Document</link>.
</p>
<section2 topic='Getting supported interfaces'>
<p>
The following example shows how a client can get the interfaces supported by a device:
</p>
<example caption='Getting supported interfaces'>
<![CDATA[
<iq type='get'
from='master@clayster.com/amr'
to='weatherstation@clayster.com'
id='1'>
<getInterfaces xmlns='urn:xmpp:iot:interoperability'/>
</iq>
<iq type='result'
from='weatherstation@clayster.com'
to='master@clayster.com/amr'
id='1'>
<getInterfacesResponse xmlns='urn:xmpp:iot:interoperability'>
<interface name='XMPP.IoT.Sensor.DewPoint'/>
<interface name='XMPP.IoT.Sensor.RainRate'/>
<interface name='XMPP.IoT.Sensor.WindDirection'/>
<interface name='XMPP.IoT.Sensor.WindSpeed'/>
<interface name='XMPP.IoT.Sensor.Humidity'/>
<interface name='XMPP.IoT.Sensor.SolarRadiation'/>
<interface name='XMPP.IoT.Sensor.Temperature'/>
<interface name='XMPP.IoT.Sensor.DewPoint.History'/>
<interface name='XMPP.IoT.Sensor.RainRate.History'/>
<interface name='XMPP.IoT.Sensor.WindDirection.History'/>
<interface name='XMPP.IoT.Sensor.WindSpeed.History'/>
<interface name='XMPP.IoT.Sensor.Humidity.History'/>
<interface name='XMPP.IoT.Sensor.SolarRadiation.History'/>
<interface name='XMPP.IoT.Sensor.Temperature.History'/>
<interface name='XMPP.IoT.Identity.Clock'/>
<interface name='XMPP.IoT.Identity.Location'/>
<interface name='XMPP.IoT.Identity.Manufacturer'/>
<interface name='XMPP.IoT.Identity.Name'/>
<interface name='XMPP.IoT.Identity.Version'/>
<interface name='XMPP.IoT.Media.Camera'/>
</getInterfacesResponse>
</iq>]]>
</example>
</section2>
<section2 topic='Interfaces' anchor='interfaces'>
<p>
The following sub-sections lists interfaces that should be adhered to by parties interested in creating interoperable devices in Internet of Things based on XMPP.
A device can implement any number of interfaces.
</p>
<section3 topic='XMPP.IoT.Sensor'>
<p>
This section contains interfaces relating to sensors measuring physical magnitudes of some sort or another.
</p>
<section4 topic='XMPP.IoT.Sensor.AnalogInput'>
<p>
Generical analog input.
</p>
<table caption='XMPP.IoT.Sensor.AnalogInput Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Analog Input</td>
<td>Required</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary input value.</td>
</tr>
<tr>
<td>Analog Input, Raw</td>
<td>Optional</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary raw binary input value.</td>
</tr>
<tr>
<td>Analog Input, Bits</td>
<td>Optional</td>
<td>status</td>
<td>numeric</td>
<td>Number of bits of precision of input value.</td>
</tr>
<tr>
<td>Analog Input, Range, Low</td>
<td>Optional</td>
<td>status</td>
<td>numeric</td>
<td>Lowest possible value.</td>
</tr>
<tr>
<td>Analog Input, Range, High</td>
<td>Optional</td>
<td>status</td>
<td>numeric</td>
<td>Highest possible value.</td>
</tr>
</table>
<p>
The input value must be reported using the correct precision and unit. Examples of units that could be used:
</p>
<ul>
<li>% - for instance 0-100 %</li>
<li>mA - for instance 4-20 mA</li>
<li>V - for instance 0-10 V</li>
</ul>
<p>
The raw value should be a unit-less integer value.
</p>
</section4>
<section4 topic='XMPP.IoT.Sensor.AnalogInputs'>
<p>
Devices containing an array of analog inputs.
</p>
<table caption='XMPP.IoT.Sensor.AnalogInputs Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Analog Input %1%</td>
<td>Required</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary input value for input number %1%.</td>
</tr>
<tr>
<td>Analog Input %1%, Raw</td>
<td>Optional</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary raw binary input value for input number %1%.</td>
</tr>
<tr>
<td>Analog Input %1%, Bits</td>
<td>Optional</td>
<td>status</td>
<td>numeric</td>
<td>Number of bits of precision of input value for input number %1%.</td>
</tr>
<tr>
<td>Analog Input %1%, Range, Low</td>
<td>Optional</td>
<td>status</td>
<td>numeric</td>
<td>Lowest possible value for input number %1%.</td>
</tr>
<tr>
<td>Analog Input %1%, Range, High</td>
<td>Optional</td>
<td>status</td>
<td>numeric</td>
<td>Highest possible value for input number %1%.</td>
</tr>
<tr>
<td>Analog Input Count</td>
<td>Optional</td>
<td>status</td>
<td>numeric</td>
<td>Number of analog inputs available on the device.</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.Current'>
<p>
Current sensors, measuring a electrical current.
</p>
<table caption='XMPP.IoT.Sensor.Current Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Current</td>
<td>Required</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary Current value.</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.DewPoint'>
<p>
Dew Point sensors, measuring current dew point in the environment.
</p>
<table caption='XMPP.IoT.Sensor.DewPoint Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Dew Point</td>
<td>Required</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary Dew Point.</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.DigitalInput'>
<p>
Generical digital input.
</p>
<table caption='XMPP.IoT.Sensor.DigitalInput Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Digital Input</td>
<td>Required</td>
<td>momentary</td>
<td>boolean</td>
<td>Momentary input value.</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.DigitalInputs'>
<p>
Devices containing an array of digital inputs.
</p>
<table caption='XMPP.IoT.Sensor.DigitalInputs Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Digital Input %1%</td>
<td>Required</td>
<td>momentary</td>
<td>boolean</td>
<td>Momentary input value for input number %1%.</td>
</tr>
<tr>
<td>Digital Input Count</td>
<td>Optional</td>
<td>status</td>
<td>numeric</td>
<td>Number of digital inputs available on the device.</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.Direction'>
<p>
Direction sensors, measuring a direction.
</p>
<table caption='XMPP.IoT.Sensor.Direction Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Direction</td>
<td>Required</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary Direction value, as an angle against true north. Value must use an angle unit.</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.Distance'>
<p>
Distance sensors, measuring physical distance.
</p>
<table caption='XMPP.IoT.Sensor.Distance Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Distance</td>
<td>Required</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary Distance value.</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.Force'>
<p>
Force sensors, measuring physical force, or tension.
</p>
<table caption='XMPP.IoT.Sensor.Force Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Force</td>
<td>Required</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary Force or tension value.</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.Frequency'>
<p>
Frequency sensors, measuring frequency.
</p>
<table caption='XMPP.IoT.Sensor.Frequency Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Frequency</td>
<td>Required</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary Frequency value.</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.Humidity'>
<p>
Humidity sensors (hygrometers), measuring a moisture content in the environment.
</p>
<table caption='XMPP.IoT.Sensor.Humidity Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Relative Humidity</td>
<td>Required</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary Relative Humidity value (in %).</td>
</tr>
<tr>
<td>Temperature</td>
<td>Optional</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary Temperature.</td>
</tr>
<tr>
<td>Dew Point</td>
<td>Optional</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary Dew Point.</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.Illuminance'>
<p>
Illuminance sensors (luxmeters), measuring a illuminance.
</p>
<table caption='XMPP.IoT.Sensor.Illuminance Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Illuminance</td>
<td>Required</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary Illuminance value.</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.Mass'>
<p>
Mass sensors, measuring physical mass.
</p>
<table caption='XMPP.IoT.Sensor.Mass Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Mass</td>
<td>Required</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary Mass value.</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.MassFlow'>
<p>
Mass flow sensors (for example air flow sensors), measuring physical mass flow.
</p>
<table caption='XMPP.IoT.Sensor.Mass Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Mass Flow</td>
<td>Required</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary Mass Flow value.</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.Pressure'>
<p>
Pressure sensors, measuring a pressure.
</p>
<table caption='XMPP.IoT.Sensor.Pressure Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Pressure</td>
<td>Required</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary Pressure value.</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.Rain'>
<p>
Rain sensors (udometers, pluviometers, ombrometers), measuring if it is raining, and how much.
</p>
<table caption='XMPP.IoT.Sensor.Rain Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Is Raining</td>
<td>Required</td>
<td>momentary</td>
<td>boolean</td>
<td>If it is raining or not.</td>
</tr>
<tr>
<td>Rain Rate</td>
<td>Optional</td>
<td>momentary</td>
<td>numeric</td>
<td>Rate of rainfall (for instance in mm/h).</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.Resistance'>
<p>
Resistance sensors, measuring a electrical resistance.
</p>
<table caption='XMPP.IoT.Sensor.Resistance Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Resistance</td>
<td>Required</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary Resistance value.</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.SolarRadiation'>
<p>
Solar radiation sensors (pyranometers), measuring solar radiation.
</p>
<table caption='XMPP.IoT.Sensor.Force Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Solar Radiation</td>
<td>Required</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary Solar Radiation value.</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.Speed'>
<p>
Speed sensors, measuring speed.
</p>
<table caption='XMPP.IoT.Sensor.Speed Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Speed</td>
<td>Required</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary Speed value.</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.Temperature'>
<p>
Temperature sensors, measuring a temperature.
</p>
<table caption='XMPP.IoT.Sensor.Temperature Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Temperature</td>
<td>Required</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary Temperature value.</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.TideLevel'>
<p>
tide level sensors, measuring the change in sea level relative to a datum.
</p>
<table caption='XMPP.IoT.Sensor.TideLevel Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Tide Level</td>
<td>Required</td>
<td>momentary</td>
<td>numeric</td>
<td>The current change in sea level relative to a datum.</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.Velocity'>
<p>
Distance sensors, measuring physical distance.
</p>
<table caption='XMPP.IoT.Sensor.Distance Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Velocity, Speed</td>
<td>Required</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary Speed value.</td>
</tr>
<tr>
<td>Velocity, Direction</td>
<td>Required</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary Direction value, as an angle against true north. Value must use an angle unit.</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.Voltage'>
<p>
Voltage sensors, measuring a electrical voltage.
</p>
<table caption='XMPP.IoT.Sensor.Voltage Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Voltage</td>
<td>Required</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary Voltage value.</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.Volume'>
<p>
Volume sensors (for example tank capacity), measuring a physical volume.
</p>
<table caption='XMPP.IoT.Sensor.Volume Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Volume</td>
<td>Required</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary Volume value.</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.Weight'>
<p>
Weight sensors, measuring weight.
</p>
<table caption='XMPP.IoT.Sensor.Weight Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Weight</td>
<td>Required</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary Weight value.</td>
</tr>
</table>
</section4>
<section4 topic='XMPP.IoT.Sensor.WindDirection'>
<p>
Wind Direction sensors, measuring where wind is blowing from.
</p>
<table caption='XMPP.IoT.Sensor.WindDirection Fields'>
<tr>
<th>Field Name</th>
<th>Use</th>
<th>Field Type</th>
<th>Value Type</th>
<th>Description</th>
</tr>
<tr>
<td>Wind, Direction</td>
<td>Optional</td>
<td>momentary</td>
<td>numeric</td>
<td>Momentary Wind Direction value, as an angle against true north. Value must use an angle unit. If value is omitted, it means
there's no wind.</td>
</tr>
<tr>