forked from fiesta-iot/ontology
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathfiesta-iot.owl
6498 lines (4417 loc) · 288 KB
/
fiesta-iot.owl
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"?>
<!DOCTYPE rdf:RDF [
<!ENTITY iot-lite "http://purl.oclc.org/NET/UNIS/fiware/iot-lite#" >
<!ENTITY qu "http://purl.org/NET/ssnx/qu/qu#">
<!ENTITY owl "http://www.w3.org/2002/07/owl#">
<!ENTITY ns "http://creativecommons.org/ns#">
<!ENTITY fiesta-iot "http://purl.org/iot/ontology/fiesta-iot#">
<!ENTITY xsd "http://www.w3.org/2001/XMLSchema#">
<!ENTITY rdfs "http://www.w3.org/2000/01/rdf-schema#">
<!ENTITY mthreelite "http://purl.org/iot/vocab/m3-lite#">
<!ENTITY ssn "http://purl.oclc.org/NET/ssnx/ssn#">
<!ENTITY geo "http://www.w3.org/2003/01/geo/wgs84_pos#">
<!ENTITY rdf "http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<!ENTITY xml "http://www.w3.org/XML/1998/namespace">
<!ENTITY onemtom "http://www.onem2m.org/ontology/Base_Ontology/base_ontology#">
<!ENTITY dul "http://www.loa.istc.cnr.it/ontologies/DUL.owl#">
<!ENTITY time "http://www.w3.org/2006/time#">
<!ENTITY vann "http://purl.org/vocab/vann/">
<!ENTITY dc "http://purl.org/dc/elements/1.1/">
<!ENTITY dcterms "http://purl.org/dc/terms/">
<!ENTITY qudt "http://data.qudt.org/qudt/owl/1.0.0/unit.owl#" >
]>
<rdf:RDF xmlns="http://purl.org/iot/ontology/fiesta-iot#"
xml:base="http://purl.org/iot/ontology/fiesta-iot"
xmlns:iot-lite="http://purl.oclc.org/NET/UNIS/fiware/iot-lite#"
xmlns:qu="http://purl.org/NET/ssnx/qu/qu#"
xmlns:owl="http://www.w3.org/2002/07/owl#"
xmlns:ns="http://creativecommons.org/ns#"
xmlns:fiesta-iot="http://purl.org/iot/ontology/fiesta-iot#"
xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:mthreelite="http://purl.org/iot/vocab/m3-lite#"
xmlns:ssn="http://purl.oclc.org/NET/ssnx/ssn#"
xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:xml="http://www.w3.org/XML/1998/namespace"
xmlns:onemtom="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#"
xmlns:qudt="http://data.qudt.org/qudt/owl/1.0.0/unit.owl#"
xmlns:dul="http://www.loa.istc.cnr.it/ontologies/DUL.owl#"
xmlns:time="http://www.w3.org/2006/time#"
xmlns:vann="http://purl.org/vocab/vann/"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:dc="http://purl.org/dc/elements/1.1/">
<owl:Ontology rdf:about="http://purl.org/iot/ontology/fiesta-iot#">
<owl:versionInfo>3.1</owl:versionInfo>
<dc:description rdf:resource="http://ontology.fiesta-iot.eu/ontologyDocs/fiesta-iot.png"/>
<dc:description rdf:resource="http://ontology.fiesta-iot.eu/ontologyDocs/resourcegraph.png"/>
<dc:description rdf:resource="http://ontology.fiesta-iot.eu/ontologyDocs/observationgraph.png"/>
<dc:description rdf:resource="http://ontology.fiesta-iot.eu/ontologyDocs/resourceannotation.png"/>
<dc:description rdf:resource="http://ontology.fiesta-iot.eu/ontologyDocs/observationannotation.png"/>
<dc:contributor xml:lang="en">Rachit Agarwal, Inria, Paris</dc:contributor>
<dc:contributor xml:lang="en">David Gomez, UC, Santander</dc:contributor>
<dc:contributor xml:lang="en">Tarek Elsaleh, UNIS, Surrey</dc:contributor>
<dc:contributor xml:lang="en">Luis Sanchez, UC, Santander</dc:contributor>
<dc:contributor xml:lang="en">Jorge Lanza, UC, Santander</dc:contributor>
<dc:contributor xml:lang="en">Amelie Gyrard, NUIG, Galway</dc:contributor>
<dc:contributor xml:lang="en">Garvita Bajaj, Inria, Paris (Past)</dc:contributor>
<dc:description xml:lang="en">Many testbeds owning devices or applications interacting with the sensors, store their inherent observations and other related data in their own proprietary format. In other words, making a testbed independent and isolated from others that cannot directly interact with each other. Differences in the data format lead to interoperability issues between the testbeds and much work has to be done in order to ensure the compatibility. One has to understand different data formats and create the mapping between them. As a result, a testbed must understand other testbed's format and create the mapping both while sending and receiving information. One method to accomplish interoperability is through the usage of semantic-based technologies to annotate all the information shared by the platforms. Nevertheless, some of the relevant existing ontologies promise interoperability but:
- do not address the problem to describe the observation in an interoperable manner to ease further tasks, such as reasoning,
- many of them are domain-specific and cannot be applied across domains,
- they have missing concepts and do not suffice the needs of the measurements provided by the sensors, and
- many ontologies do not follow best practices making it hard to correctly interpret and reuse concepts.
In order to address the above-mentioned limitations, we provide FIESTA-IoT ontology (a unified semantic model) that follows best practices. FIESTA-IoT Ontology is a merge of concepts from various ontologies such as IoT-lite, M3-lite Taxonomy, SSN, Time and DUL (see Figure 1). The FIESTA-IoT Ontology is divided into 2 parts: resource description and observations produced. One has to follow the Figure 2 and Figure 3, respectively, for understanding what all concepts are associated with resource description and observation. Using such information testbeds can annotate their data to FIESTA-IoT specific requirements and the annotators developed can achieve FIESTA-IoT certification. For reference we provide sample annotations as figure (see Figure 4 and Figure 5) for both resource graph and observation graph.
For more details please see:
- R. Agarwal, D. Fernandez, T. Elsaleh, A. Gyrard, J. Lanza, L. Sanchez, N. Georgantas, V. Issarny, "Unified IoT Ontology to Enable Interoperability and Federation of Testbeds", 3rd IEEE WF-IoT, Reston, VA, USA, 12-14 December 2016. (https://hal.inria.fr/hal-01386917/document)
- FIESTA-IoT Consortium (R. Agarwal editor), "Deliverable D3.1.2 Semantic Models for Testbeds, Interoperability and Mobility Support, and Best Practices", project FIESTA-IoT deliverable, 2016.
- FIESTA-IoT Consortium (R. Agarwal editor), "Deliverable D3.1.1 Semantic Models for Testbeds, Interoperability and Mobility Support, and Best Practices", project FIESTA-IoT deliverable, 2016.
We further acknowledge, testbed provider such as SmartSantander, UniS, KETI, Inria, and other open call testbeds for their valuable comments. Please report any errors to [email protected].
</dc:description>
<vann:preferredNamespaceUri>http://purl.org/iot/ontology/fiesta-iot#</vann:preferredNamespaceUri>
<vann:preferredNamespacePrefix>fiesta-iot</vann:preferredNamespacePrefix>
<dc:rights>Copyright EU H2020 FIESTA-IoT</dc:rights>
<rdfs:label rdf:datatype="&xsd;string">FIESTA-IoT</rdfs:label>
<dcterms:issued rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2016-04-28</dcterms:issued>
<rdfs:comment xml:lang="en">After a thorough analysis of existing Internet of Things (IoT) related ontologies, we propose FIESTA-IoT Ontology that aims to achieve semantic interoperability among heterogeneous testbeds. The Ontology is framed within the EU H2020 FIESTA-IoT project, that aims to seamlessly support the federation of testbeds through the usage of semantic-based technologies. The FIESTA-IoT ontology takes inspiration from the well-known Noy et al. methodology for reusing and interconnecting existing ontologies. To build the ontology, we leverage a number of core concepts from various mainstream ontologies and taxonomies, such as Semantic Sensor Network (SSN), M3-lite (a lite version of M3 ontology), WGS84, IoT-lite, Time, and DUL ontology. Please report any errors to [email protected]</rdfs:comment>
<dc:title xml:lang="en">FIESTA-IoT Ontology</dc:title>
<dcterms:modified rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2017-11-27</dcterms:modified>
<dcterms:bibliographicCitation xml:lang="en">R. Agarwal, D. Fernandez, T. Elsaleh, A. Gyrard, J. Lanza, L. Sanchez, N. Georgantas, V. Issarny, "Unified IoT Ontology to Enable Interoperability and Federation of Testbeds", 3rd IEEE WF-IoT, Reston, VA, USA, 12-14 December 2016. (https://hal.inria.fr/hal-01386917/document)</dcterms:bibliographicCitation>
<dcterms:bibliographicCitation xml:lang="en">FIESTA-IoT Consortium (R. Agarwal editor), "Deliverable D3.1.2 Semantic Models for Testbeds, Interoperability and Mobility Support, and Best Practices", project FIESTA-IoT deliverable, 2016.</dcterms:bibliographicCitation>
<dcterms:bibliographicCitation xml:lang="en">FIESTA-IoT Consortium (R. Agarwal editor), "Deliverable D3.1.1 Semantic Models for Testbeds, Interoperability and Mobility Support, and Best Practices", project FIESTA-IoT deliverable, 2016.</dcterms:bibliographicCitation>
</owl:Ontology>
<!-- HISTORY
3.1 release: Last Updated: November 27 2017
- new version of m3-lite taxonomy integrated.
3.0 release: Last Updated: July 29 2017
- ssn:MeasurementProperty and its subclasses added (Accuracy, Frequency, Latency, Precision, Resolution, ResponseTime)
- hasDataValue now has xsd:string as well to support commands. The max length is set to 255.
- new version of m3-lite taxonomy integrated.
2.0 release: Last Updated: April 20 2017
- Integrate new version of M3-lite taxonomy
- more clear definitions for concepts
- added isOnline concept as in IoT-Lite
- Integrating new version of IoT-lite
- update to description with acknowledgement and reference to annotation images.
- added new datatypes like dateTime, int to dataValue.
- Fix in ontology metadata coming from LOV (having url of authors.. test failed with LODE so not updating it)
- Fix in annotation properties (some were not defined.. this before sometime threw annotation errors)
- New version tag
1.0.2 release: Last updated: Feb 10, 2017
- merge new M3-Lite changes (remove images, comments etc.)
- change to purl link
- change the has coverage cardinality
- update description and the images
- fix minor issues reported by Mengxuan Zhao
1.0.1 release: Last updated: November 23, 2016
- merge new M3-Lite changes
1.0 release: Last updated: October 28, 2016
- Add oneM2M equivalence classes
- merge new M3-Lite changes
- Change Dul:TimeInstant to use Time:Instant
0.1.1 release: Last updated: September 25, 2016
- Follow naming convention
- Add Labels wherever missing
- Integrate M3-Lite changes
0.1 release: Last updated: August 08, 2016
- fix minor bugs
- remove unused object properties, add missing mappings.
- removed classes that were not required. e.g., ssn:Situation and other super-classes that were not being used
- removed dc:identifier from the Ontology properties (earlier defined as the SSN OWL URI)
- added xsd:boolean to range of dul:hasDataValue for ObservationValue for proximity sensor
0.0.1 release: August 5,2016
-imported the latest m3-lite owl file
-removed 'some' property from the following classes where min1 was also present
- ssn:SensingDevice iot-lite:exposedBy some iot-lite:Service
- iot-lite:Entity iot-lite:hasAttribute some iot-lite:Attribute
- iot-lite:Entity iot-lite:isAssociatedWith some iot-lite:Service
- iot-lite:Service iot-lite:exposes some iot-lite:Device
0.0.0 release: April 28,2016
- initial version
-->
<!--
///////////////////////////////////////////////////////////////////////////////////////
//
// Annotation properties
//
///////////////////////////////////////////////////////////////////////////////////////
-->
<!-- http://creativecommons.org/ns#license -->
<owl:AnnotationProperty rdf:about="&ns;license"/>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#altRelative -->
<owl:AnnotationProperty rdf:about="&iot-lite;altRelative">
<rdfs:comment xml:lang="en">Relative Altitude can be used in place of an absolute altitude, especially in buildings, where it makes more sense to locate by levels or floors. For example the value "0" would indicate "ground floor", and "1" would indicate "1st floor" and so on.</rdfs:comment>
<rdfs:range rdf:resource="&xsd;string"/>
<rdfs:domain rdf:resource="&geo;Point"/>
</owl:AnnotationProperty>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#relativeLocation -->
<owl:AnnotationProperty rdf:about="&iot-lite;relativeLocation">
<rdfs:comment xml:lang="en">Relative Location is used to provide a place for where the Device is in. For example, Geonames URIs can be used to represent a place, city, area, or region. For "University of Surrey" this would be "http://sws.geonames.org/6695971/"</rdfs:comment>
<rdfs:range rdf:resource="&xsd;string"/>
<rdfs:domain rdf:resource="&geo;Point"/>
</owl:AnnotationProperty>
<!-- http://purl.org/dc/elements/1.1/creator -->
<owl:AnnotationProperty rdf:about="http://purl.org/dc/elements/1.1/creator"/>
<!-- http://purl.org/dc/terms/bibliographicCitation -->
<owl:AnnotationProperty rdf:about="http://purl.org/dc/terms/bibliographicCitation"/>
<!-- http://purl.org/dc/elements/1.1/contributor -->
<owl:AnnotationProperty rdf:about="http://purl.org/dc/elements/1.1/contributor"/>
<!-- http://purl.org/dc/terms/issued -->
<owl:AnnotationProperty rdf:about="http://purl.org/dc/terms/issued"/>
<!-- http://purl.org/dc/terms/modified -->
<owl:AnnotationProperty rdf:about="http://purl.org/dc/terms/modified"/>
<!-- http://purl.org/dc/elements/1.1/date -->
<owl:AnnotationProperty rdf:about="http://purl.org/dc/elements/1.1/date"/>
<!-- http://purl.org/dc/elements/1.1/description -->
<owl:AnnotationProperty rdf:about="http://purl.org/dc/elements/1.1/description"/>
<!-- http://purl.org/dc/elements/1.1/identifier -->
<owl:AnnotationProperty rdf:about="http://purl.org/dc/elements/1.1/identifier"/>
<!-- http://purl.org/dc/elements/1.1/rights -->
<owl:AnnotationProperty rdf:about="http://purl.org/dc/elements/1.1/rights"/>
<!-- http://purl.org/dc/elements/1.1/source -->
<owl:AnnotationProperty rdf:about="http://purl.org/dc/elements/1.1/source"/>
<!-- http://purl.org/dc/elements/1.1/title -->
<owl:AnnotationProperty rdf:about="http://purl.org/dc/elements/1.1/title"/>
<!-- http://purl.org/vocab/vann/preferredNamespacePrefix -->
<owl:AnnotationProperty rdf:about="http://purl.org/vocab/vann/preferredNamespacePrefix"/>
<!-- http://purl.org/vocab/vann/preferredNamespaceUri -->
<owl:AnnotationProperty rdf:about="http://purl.org/vocab/vann/preferredNamespaceUri"/>
<!-- http://www.loa.istc.cnr.it/ontologies/DUL.owl#mappableTo -->
<owl:AnnotationProperty rdf:about="&dul;mappableTo">
<rdfs:label xml:lang="en">mappable to</rdfs:label>
</owl:AnnotationProperty>
<!-- http://www.w3.org/2000/01/rdf-schema#comment -->
<owl:AnnotationProperty rdf:about="&rdfs;comment"/>
<!-- http://www.w3.org/2000/01/rdf-schema#isDefinedBy -->
<owl:AnnotationProperty rdf:about="&rdfs;isDefinedBy"/>
<!-- http://www.w3.org/2000/01/rdf-schema#label -->
<owl:AnnotationProperty rdf:about="&rdfs;label"/>
<!-- http://www.w3.org/2000/01/rdf-schema#seeAlso -->
<owl:AnnotationProperty rdf:about="&rdfs;seeAlso"/>
<!-- http://www.w3.org/2002/07/owl#equivalentClass -->
<owl:AnnotationProperty rdf:about="http://www.w3.org/2002/07/owl#equivalentClass"/>
<!-- http://www.w3.org/2002/07/owl#versionInfo -->
<owl:AnnotationProperty rdf:about="http://www.w3.org/2002/07/owl#versionInfo"/>
<!-- http://www.w3.org/2003/01/geo/wgs84_pos#alt -->
<owl:AnnotationProperty rdf:about="&geo;alt">
<rdfs:domain rdf:resource="&geo;Point"/>
</owl:AnnotationProperty>
<!-- http://www.w3.org/2003/01/geo/wgs84_pos#lat -->
<owl:AnnotationProperty rdf:about="&geo;lat">
<rdfs:domain rdf:resource="&geo;Point"/>
</owl:AnnotationProperty>
<!-- http://www.w3.org/2003/01/geo/wgs84_pos#long -->
<owl:AnnotationProperty rdf:about="&geo;long">
<rdfs:domain rdf:resource="&geo;Point"/>
</owl:AnnotationProperty>
<!--
///////////////////////////////////////////////////////////////////////////////////////
//
// Object Properties
//
///////////////////////////////////////////////////////////////////////////////////////
-->
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#exposedBy -->
<owl:ObjectProperty rdf:about="&iot-lite;exposedBy">
<owl:inverseOf rdf:resource="&iot-lite;exposes"/>
<rdfs:domain rdf:resource="&ssn;Device"/>
<rdfs:range rdf:resource="&iot-lite;Service"/>
<rdfs:comment xml:lang="en">A device is exposed by a service.</rdfs:comment>
<rdfs:label xml:lang="en">Exposed By</rdfs:label>
</owl:ObjectProperty>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#exposes -->
<owl:ObjectProperty rdf:about="&iot-lite;exposes">
<rdfs:domain rdf:resource="&iot-lite;Service"/>
<rdfs:range rdf:resource="&ssn;Device"/>
<rdfs:comment xml:lang="en">For service-oriented queries. The inverse of exposedBy.</rdfs:comment>
<rdfs:label xml:lang="en">Exposes</rdfs:label>
</owl:ObjectProperty>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#hasAttribute -->
<owl:ObjectProperty rdf:about="&iot-lite;hasAttribute">
<rdfs:domain rdf:resource="&iot-lite;Entity"/>
<rdfs:domain rdf:resource="&iot-lite;Object"/>
<rdfs:range rdf:resource="&iot-lite;Attribute"/>
<rdfs:comment xml:lang="en">Links the devices with their attributes.</rdfs:comment>
<rdfs:label xml:lang="en">Has Attribute</rdfs:label>
</owl:ObjectProperty>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#hasCoverage -->
<owl:ObjectProperty rdf:about="&iot-lite;hasCoverage">
<rdfs:domain rdf:resource="&ssn;Device"/>
<rdfs:range rdf:resource="&iot-lite;Coverage"/>
<rdfs:comment xml:lang="en">Links the devices with their coverages.</rdfs:comment>
<rdfs:label xml:lang="en">Has Coverage</rdfs:label>
</owl:ObjectProperty>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#hasMetadata -->
<owl:ObjectProperty rdf:about="&iot-lite;hasMetadata">
<rdfs:range rdf:resource="&iot-lite;Metadata"/>
<rdfs:comment xml:lang="en">Links any concept with metadata about that concept.</rdfs:comment>
<rdfs:label xml:lang="en">Has Metadata</rdfs:label>
</owl:ObjectProperty>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#hasQuantityKind -->
<owl:ObjectProperty rdf:about="&iot-lite;hasQuantityKind">
<owl:equivalentProperty rdf:resource="&onemtom;hasThingProperty"/>
<rdfs:domain rdf:resource="&iot-lite;Attribute"/>
<rdfs:domain rdf:resource="&ssn;Sensor"/>
<rdfs:range rdf:resource="&qu;QuantityKind"/>
<rdfs:comment xml:lang="en">Links a sensor or an attribute with the quantity kind it measures (e.g. A sensor -sensor1- measures temperature: sensor1 hasQuantityKind temperature).</rdfs:comment>
<rdfs:label xml:lang="en">Has Quantity Kind</rdfs:label>
</owl:ObjectProperty>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#hasUnit -->
<owl:ObjectProperty rdf:about="&iot-lite;hasUnit">
<owl:equivalentProperty rdf:resource="&onemtom;hasMetaData"/>
<rdfs:domain rdf:resource="&ssn;ObservationValue"/>
<rdfs:domain rdf:resource="&ssn;Sensor"/>
<rdfs:domain rdf:resource="&ssn;MeasurementProperty"/>
<rdfs:range rdf:resource="&qu;Unit"/>
<rdfs:comment>Links the sensor with the units of the quantity kind it measures (e.g. A sensor -sensor1- measures temperature in Celsius: senso1 hasUnit Celsius).</rdfs:comment>
<rdfs:label xml:lang="en">Has Unit</rdfs:label>
</owl:ObjectProperty>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#isAssociatedWith -->
<owl:ObjectProperty rdf:about="&iot-lite;isAssociatedWith">
<rdfs:domain rdf:resource="&iot-lite;Entity"/>
<rdfs:domain rdf:resource="&iot-lite;Object"/>
<rdfs:range rdf:resource="&iot-lite;Service"/>
<rdfs:comment>Defines the associations between objects and sensors (e.g. A table (object) has an attribute (temperature at the table) which is associated with a sensor (the temperature sensor of the room). </rdfs:comment>
<rdfs:label xml:lang="en">Is Associated With</rdfs:label>
</owl:ObjectProperty>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#isSubSystemOf -->
<owl:ObjectProperty rdf:about="&iot-lite;isSubSystemOf">
<owl:inverseOf rdf:resource="&ssn;hasSubSystem"/>
<rdfs:domain rdf:resource="&ssn;System"/>
<rdfs:range rdf:resource="&ssn;System"/>
<rdfs:comment xml:lang="en">This defines that a devices system is a subsystem of another system. For example, a multi-sensor device is a subsystem of a smart building testbed. This is the inverse of the SSN object property "hasSubSystem". It allows a graph to start from a subsystem. This is useful for resource-centric graphs.</rdfs:comment>
<rdfs:label xml:lang="en">Is Sub System Of</rdfs:label>
</owl:ObjectProperty>
<!-- http://purl.oclc.org/NET/ssnx/ssn#attachedSystem -->
<owl:ObjectProperty rdf:about="&ssn;attachedSystem">
<owl:inverseOf rdf:resource="&ssn;onPlatform"/>
<rdfs:domain rdf:resource="&ssn;Platform"/>
<rdfs:range rdf:resource="&ssn;System"/>
<rdfs:comment>Relation between a Platform and any Systems (e.g., Sensors) that are attached to the Platform.</rdfs:comment>
<rdfs:label xml:lang="en">Attached System</rdfs:label>
</owl:ObjectProperty>
<!-- http://purl.oclc.org/NET/ssnx/ssn#hasDeployment -->
<owl:ObjectProperty rdf:about="&ssn;hasDeployment">
<rdfs:domain rdf:resource="&ssn;System"/>
<rdfs:range rdf:resource="&ssn;Deployment"/>
<rdfs:comment>Relation between a System and a Deployment, recording that the System/Sensor was deployed in that Deployment.</rdfs:comment>
<rdfs:label xml:lang="en">Has Deployment</rdfs:label>
</owl:ObjectProperty>
<!-- http://purl.oclc.org/NET/ssnx/ssn#hasSubSystem -->
<owl:ObjectProperty rdf:about="&ssn;hasSubSystem">
<rdfs:domain rdf:resource="&ssn;System"/>
<rdfs:range rdf:resource="&ssn;System"/>
<rdfs:comment>Haspart relation between a system and its parts.</rdfs:comment>
<rdfs:label xml:lang="en">Has Sub System</rdfs:label>
</owl:ObjectProperty>
<!-- http://purl.oclc.org/NET/ssnx/ssn#hasValue -->
<owl:ObjectProperty rdf:about="&ssn;hasValue">
<rdfs:domain rdf:resource="&ssn;SensorOutput"/>
<rdfs:range rdf:resource="&ssn;ObservationValue"/>
<rdfs:label xml:lang="en">Has Value</rdfs:label>
<rdfs:comment xml:lang="en">Provides a relation between observationValue and actual value.</rdfs:comment>
</owl:ObjectProperty>
<!-- http://purl.oclc.org/NET/ssnx/ssn#madeObservation -->
<owl:ObjectProperty rdf:about="&ssn;madeObservation">
<owl:equivalentProperty rdf:resource="&onemtom;hasService"/>
<owl:inverseOf rdf:resource="&ssn;observedBy"/>
<rdfs:domain rdf:resource="&ssn;Sensor"/>
<rdfs:range rdf:resource="&ssn;Observation"/>
<rdfs:comment>Relation between a Sensor and Observations it has made.</rdfs:comment>
<rdfs:label xml:lang="en">Made Observation</rdfs:label>
</owl:ObjectProperty>
<!-- http://purl.oclc.org/NET/ssnx/ssn#observationResult -->
<owl:ObjectProperty rdf:about="&ssn;observationResult">
<rdfs:domain rdf:resource="&ssn;Observation"/>
<rdfs:range rdf:resource="&ssn;SensorOutput"/>
<dc:source>skos:closeMatch 'result' [O&M - ISO/DIS 19156]
http://portal.opengeospatial.org/files/?artifact_id=41579</dc:source>
<rdfs:comment>Relation linking an Observation (i.e., a description of the context, the Situation, in which the observation was made) and a Result, which contains a value representing the value associated with the observed Property.</rdfs:comment>
<rdfs:label xml:lang="en">Observation Result</rdfs:label>
</owl:ObjectProperty>
<!-- http://purl.oclc.org/NET/ssnx/ssn#observationSamplingTime -->
<owl:ObjectProperty rdf:about="&ssn;observationSamplingTime">
<rdfs:domain rdf:resource="&ssn;Observation"/>
<rdfs:range rdf:resource="&time;Instant"/>
<rdfs:comment>Rebadged as phenomenon time in [O&M]. The phenomenon time shall describe the time that the result applies to the property of the feature-of-interest. This is often the time of interaction by a sampling procedure or observation procedure with a real-world feature.</rdfs:comment>
<rdfs:comment>The sampling time is the time that the result applies to the feature-of-interest. This is the time usually required for geospatial analysis of the result.</rdfs:comment>
<rdfs:label xml:lang="en">Observation Sampling Time</rdfs:label>
</owl:ObjectProperty>
<!-- http://purl.oclc.org/NET/ssnx/ssn#observedBy -->
<owl:ObjectProperty rdf:about="&ssn;observedBy">
<rdfs:domain rdf:resource="&ssn;Observation"/>
<owl:inverseOf rdf:resource="&ssn;madeObservation"/>
<rdfs:range rdf:resource="&ssn;Sensor"/>
<rdfs:label xml:lang="en">observed by</rdfs:label>
<rdfs:comment xml:lang="en">Relation between a observation and it sensor.</rdfs:comment>
</owl:ObjectProperty>
<!-- http://purl.oclc.org/NET/ssnx/ssn#observedProperty -->
<owl:ObjectProperty rdf:about="&ssn;observedProperty">
<rdfs:domain rdf:resource="&ssn;Observation"/>
<rdfs:range rdf:resource="&qu;QuantityKind"/>
<dc:source>skos:exactMatch 'observedProperty' [O&M - ISO/DIS 19156]
http://portal.opengeospatial.org/files/?artifact_id=41579</dc:source>
<rdfs:comment>Relation linking an Observation to the Property that was observed. The observedProperty should be a Property (hasProperty) of the FeatureOfInterest (linked by featureOfInterest) of this observation.</rdfs:comment>
<rdfs:label>Observed Property</rdfs:label>
</owl:ObjectProperty>
<!-- http://purl.oclc.org/NET/ssnx/ssn#onPlatform -->
<owl:ObjectProperty rdf:about="&ssn;onPlatform">
<rdfs:domain rdf:resource="&ssn;System"/>
<rdfs:range rdf:resource="&ssn;Platform"/>
<rdfs:comment>Relation between a System (e.g., a Sensor) and a Platform. The relation locates the sensor relative to other described entities: i.e., the Sensor s1's location is Platform p1. More precise locations for sensors in space (relative to other entities, where attached to another entity, or in 3D space) are made using DOLCE's Regions (SpaceRegion).</rdfs:comment>
<rdfs:label>On Platform</rdfs:label>
</owl:ObjectProperty>
<!-- http://purl.org/iot/vocab/m3-lite#hasDomainOfInterest -->
<owl:ObjectProperty rdf:about="&mthreelite;hasDomainOfInterest">
<rdfs:domain rdf:resource="&ssn;Device"/>
<rdfs:range rdf:resource="&mthreelite;DomainOfInterest"/>
<rdfs:comment xml:lang="en">This property is used to classify devices by DomainOfInterest (e.g., blood pressure sensor is used in healthcare)</rdfs:comment>
<rdfs:label xml:lang="en">Has Domain Of Interest</rdfs:label>
</owl:ObjectProperty>
<!-- http://purl.org/iot/vocab/m3-lite#hasDirection -->
<owl:ObjectProperty rdf:about="&mthreelite;hasDirection">
<rdfs:domain rdf:resource="&ssn;Observation"/>
<rdfs:range>
<owl:Restriction>
<owl:onProperty rdf:resource="&mthreelite;hasDirection"/>
<owl:maxQualifiedCardinality rdf:datatype="&xsd;nonNegativeInteger">1</owl:maxQualifiedCardinality>
<owl:onClass rdf:resource="&mthreelite;Direction"/>
</owl:Restriction>
</rdfs:range>
<rdfs:comment xml:lang="en">The observations made by the sensors are affected by the direction of the sensing device. This property allows observations of the sensor to be associated to the Direction concept</rdfs:comment>
<rdfs:label xml:lang="en">Has Direction</rdfs:label>
</owl:ObjectProperty>
<!-- http://purl.org/iot/vocab/m3-lite#hasMeasurementType -->
<owl:ObjectProperty rdf:about="&mthreelite;hasMeasurementType">
<rdfs:domain rdf:resource="&ssn;Observation"/>
<rdfs:range>
<owl:Restriction>
<owl:onProperty rdf:resource="&mthreelite;hasMeasurementType"/>
<owl:maxQualifiedCardinality rdf:datatype="&xsd;nonNegativeInteger">1</owl:maxQualifiedCardinality
>
<owl:onClass rdf:resource="&mthreelite;MeasurementType"/>
</owl:Restriction>
</rdfs:range>
<rdfs:comment xml:lang="en">Each sensing device can have a different sensing mechanism which may result in different kinds of sensor data. This property links observation of the sensor to the associated MeasurementType.</rdfs:comment>
<rdfs:label xml:lang="en">Has Measurement Type</rdfs:label>
</owl:ObjectProperty>
<!-- http://purl.org/iot/vocab/m3-lite#hasSoundSource -->
<owl:ObjectProperty rdf:about="&mthreelite;hasSoundSource">
<rdfs:subPropertyOf rdf:resource="&mthreelite;hasSource"/>
<rdfs:domain rdf:resource="&mthreelite;Sound"/>
<rdfs:range rdf:resource="&mthreelite;SoundSource"/>
<rdfs:comment xml:lang="en">This property links sound to its environmental source.</rdfs:comment>
<rdfs:label xml:lang="en">Has Sound Source</rdfs:label>
</owl:ObjectProperty>
<!-- http://purl.org/iot/vocab/m3-lite#hasSource -->
<owl:ObjectProperty rdf:about="&mthreelite;hasSource">
<rdfs:domain rdf:resource="&qu;QuantityKind"/>
<rdfs:range rdf:resource="&mthreelite;Source"/>
<rdfs:comment xml:lang="en">This property links sensed phenomena to its environmental source.</rdfs:comment>
<rdfs:label xml:lang="en">Has Source</rdfs:label>
</owl:ObjectProperty>
<!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasMetaData -->
<owl:ObjectProperty rdf:about="&onemtom;hasMetaData">
<rdfs:comment>A Value of a Thing can have MetaData (like units, precision-ranges).</rdfs:comment>
<rdfs:label xml:lang="en">Has MetaData</rdfs:label>
</owl:ObjectProperty>
<!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasService -->
<owl:ObjectProperty rdf:about="&onemtom;hasService">
<rdfs:comment>The Functionalities of a Device are exposed in the network as Services of the Device</rdfs:comment>
<rdfs:label xml:lang="en">Has Service</rdfs:label>
</owl:ObjectProperty>
<!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasThingProperty -->
<owl:ObjectProperty rdf:about="&onemtom;hasThingProperty">
<rdfs:comment>A Thing may have properties that can be described by Values</rdfs:comment>
<rdfs:label xml:lang="en">Has Thing Property</rdfs:label>
</owl:ObjectProperty>
<!-- http://www.w3.org/2003/01/geo/wgs84_pos#location -->
<owl:ObjectProperty rdf:about="&geo;location">
<rdfs:range rdf:resource="&geo;Point"/>
<rdfs:comment xml:lang="en">Provides relation between object and its physical location.</rdfs:comment>
</owl:ObjectProperty>
<!-- http://purl.oclc.org/NET/ssnx/ssn#hasMeasurementCapability -->
<owl:ObjectProperty rdf:about="&ssn;hasMeasurementCapability">
<rdfs:comment>Relation from a Sensor to a MeasurementCapability describing the measurement properties of the sensor.</rdfs:comment>
<rdfs:domain rdf:resource="&ssn;Sensor"/>
<rdfs:range rdf:resource="&ssn;MeasurementCapability"/>
<rdfs:isDefinedBy>http://purl.oclc.org/NET/ssnx/ssn</rdfs:isDefinedBy>
<rdfs:label>has measurement capability</rdfs:label>
<rdfs:seeAlso>http://www.w3.org/2005/Incubator/ssn/wiki/SSN_Sensor#MeasuringCapability</rdfs:seeAlso>
</owl:ObjectProperty>
<!-- http://purl.oclc.org/NET/ssnx/ssn#hasMeasurementProperty -->
<owl:ObjectProperty rdf:about="&ssn;hasMeasurementProperty">
<rdfs:comment>Relation from a MeasurementCapability to a MeasurementProperty. For example, to an accuracy (see notes at MeasurementCapability).</rdfs:comment>
<rdfs:domain rdf:resource="&ssn;MeasurementCapability"/>
<rdfs:range rdf:resource="&ssn;MeasurementProperty"/>
<rdfs:isDefinedBy>http://purl.oclc.org/NET/ssnx/ssn</rdfs:isDefinedBy>
<rdfs:label>has measurement property</rdfs:label>
<rdfs:seeAlso>http://www.w3.org/2005/Incubator/ssn/wiki/SSN_Sensor#MeasuringCapability</rdfs:seeAlso>
</owl:ObjectProperty>
<!--
///////////////////////////////////////////////////////////////////////////////////////
//
// Data properties
//
///////////////////////////////////////////////////////////////////////////////////////
-->
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#endpoint -->
<owl:DatatypeProperty rdf:about="&iot-lite;endpoint">
<rdfs:domain rdf:resource="&iot-lite;Service"/>
<rdfs:range rdf:resource="&xsd;anyURI"/>
<rdfs:comment>Endpoint of the service. It is usually a URL where the service is available.</rdfs:comment>
<rdfs:label xml:lang="en">Endpoint</rdfs:label>
</owl:DatatypeProperty>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#id -->
<owl:DatatypeProperty rdf:about="&iot-lite;id">
<rdfs:domain rdf:resource="&iot-lite;Entity"/>
<rdfs:domain rdf:resource="&ssn;Device"/>
<rdfs:range rdf:resource="&xsd;string"/>
<rdfs:comment xml:lang="en">The ID of the Device or Entity.</rdfs:comment>
<rdfs:label xml:lang="en">ID</rdfs:label>
</owl:DatatypeProperty>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#interfaceDescription -->
<owl:DatatypeProperty rdf:about="&iot-lite;interfaceDescription">
<rdfs:domain rdf:resource="&iot-lite;Service"/>
<rdfs:range rdf:resource="&xsd;anyURI"/>
<rdfs:comment>Interface Description of the service, e.g. WADL, WSDL, NGSI9 etc.</rdfs:comment>
<rdfs:label xml:lang="en">Interface Description</rdfs:label>
</owl:DatatypeProperty>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#interfaceType -->
<owl:DatatypeProperty rdf:about="&iot-lite;interfaceType">
<rdfs:domain rdf:resource="&iot-lite;Service"/>
<rdfs:range rdf:resource="&xsd;string"/>
<rdfs:comment xml:lang="en">Defines the type of interface of the service endpoint, e.g. RESTful, NGSI-9, MQTT, CoAP etc.</rdfs:comment>
<rdfs:label xml:lang="en">Interface Type</rdfs:label>
</owl:DatatypeProperty>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#isMobile -->
<owl:DatatypeProperty rdf:about="&iot-lite;isMobile">
<rdfs:domain rdf:resource="&ssn;Platform"/>
<rdfs:range rdf:resource="&xsd;boolean"/>
<rdfs:label xml:lang="en">Is Mobile</rdfs:label>
<rdfs:comment xml:lang="en">Is the Device mobile? This can be used by an IoT management platform to enable tracking of the device's location.</rdfs:comment>
</owl:DatatypeProperty>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#isOnline -->
<owl:DatatypeProperty rdf:about="&iot-lite;isOnline">
<rdfs:domain rdf:resource="&iot-lite;Service"/>
<rdfs:range rdf:resource="&xsd;boolean"/>
<rdfs:comment xml:lang="en">Identifies if the service is online or not.</rdfs:comment>
</owl:DatatypeProperty>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#metadataType -->
<owl:DatatypeProperty rdf:about="&iot-lite;metadataType">
<rdfs:domain rdf:resource="&iot-lite;Metadata"/>
<rdfs:range rdf:resource="&xsd;string"/>
<rdfs:comment>Defines the type pf the metadata value (e.g. resolution of the sensor).</rdfs:comment>
<rdfs:label xml:lang="en">Metadata Type</rdfs:label>
</owl:DatatypeProperty>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#metadataValue -->
<owl:DatatypeProperty rdf:about="&iot-lite;metadataValue">
<rdfs:domain rdf:resource="&iot-lite;Metadata"/>
<rdfs:range rdf:resource="&xsd;string"/>
<rdfs:comment>Value of the metadata</rdfs:comment>
<rdfs:label xml:lang="en">Metadata Value</rdfs:label>
</owl:DatatypeProperty>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#radius -->
<owl:DatatypeProperty rdf:about="&iot-lite;radius">
<rdfs:domain rdf:resource="&iot-lite;Circle"/>
<rdfs:range rdf:resource="&xsd;double"/>
<rdfs:comment>Specifies the radius of a circle coverage defined by a point -the centre of the circle- and its radius.</rdfs:comment>
<rdfs:label xml:lang="en">Radius</rdfs:label>
</owl:DatatypeProperty>
<!-- http://www.loa.istc.cnr.it/ontologies/DUL.owl#hasDataValue -->
<owl:DatatypeProperty rdf:about="&dul;hasDataValue">
<rdfs:domain rdf:resource="&ssn;ObservationValue"/>
<rdfs:domain rdf:resource="&ssn;MeasurementProperty"/>
<rdfs:domain rdf:resource="&mthreelite;Direction"/>
<rdfs:range>
<rdfs:Datatype>
<owl:unionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&xsd;boolean"/>
<rdf:Description rdf:about="&xsd;dateTime"/>
<rdf:Description rdf:about="&xsd;double"/>
<rdf:Description rdf:about="&xsd;int"/>
<rdfs:Datatype>
<owl:onDatatype rdf:resource="&xsd;string"/>
<owl:withRestrictions rdf:parseType="Collection">
<rdf:Description>
<xsd:maxLength rdf:datatype="&xsd;int">255</xsd:maxLength>
</rdf:Description>
</owl:withRestrictions>
</rdfs:Datatype>
</owl:unionOf>
</rdfs:Datatype>
</rdfs:range>
<rdfs:comment>A datatype property that encodes values from a datatype for an Entity.
There are several ways to encode values in DOLCE (Ultralite):
1) Directly assert an xsd:_ value to an Entity by using hasDataValue
2) Assert a Region for an Entity by using hasRegion, and then assert an xsd:_ value to that Region, by using hasRegionDataValue
3) Assert a Quality for an Entity by using hasQuality, then assert a Region for that Quality, and assert an xsd:_ value to that Region, by using hasRegionDataValue
4) When the value is required, but not directly observed, assert a Parameter for an xsd:_ value by using hasParameterDataValue, and then associate the Parameter to an Entity by using isConstraintFor
5) When the value is required, but not directly observed, you can also assert a Parameter for a Region by using parametrizes, and then assert an xsd:_ value to that Region, by using hasRegionDataValue
The five approaches obey different requirements.
For example, a simple value can be easily asserted by using pattern (1), but if one needs to assert an interval between two values, a Region should be introduced to materialize that interval, as pattern (2) suggests.
Furthermore, if one needs to distinguish the individual Quality of a value, e.g. the particular nature of the density of a substance, pattern (3) can be used.
Patterns (4) and (5) should be used instead when a constraint or a selection is modelled, independently from the actual observation of values in the real world.</rdfs:comment>
<rdfs:label xml:lang="en">Has Data Value</rdfs:label>
</owl:DatatypeProperty>
<!-- http://www.w3.org/2006/time#inXSDDateTime -->
<owl:DatatypeProperty rdf:about="&time;inXSDDateTime">
<rdfs:domain rdf:resource="&time;Instant"/>
<rdfs:range rdf:resource="&xsd;dateTime"/>
<rdfs:comment xml:lang="en">It is the property relating Time Instant with the datetime value</rdfs:comment>
<rdfs:label xml:lang="en">In XSD DateTime</rdfs:label>
</owl:DatatypeProperty>
<!--
///////////////////////////////////////////////////////////////////////////////////////
//
// Classes
//
///////////////////////////////////////////////////////////////////////////////////////
-->
<!-- http://purl.org/iot/vocab/m3-lite#Bar -->
<owl:Class rdf:about="&mthreelite;Bar">
<rdfs:subClassOf rdf:resource="&qu;Unit"/>
<rdfs:comment xml:lang="en">Metric unit of atmospheric pressure equal to 14.50 pounds per square inch (lb/in2), 1.02 kilograms per square centimetre (kg/cm2), 29.53 inches of mercury (in Hg), or 0.9869 atmosphere.</rdfs:comment>
<rdfs:label xml:lang="en">Bar</rdfs:label>
<rdfs:seeAlso>http://qudt.org/vocab/unit#Bar</rdfs:seeAlso>
</owl:Class>
<!-- http://purl.org/iot/vocab/m3-lite#DegreeAngle -->
<owl:Class rdf:about="&mthreelite;DegreeAngle">
<rdfs:subClassOf rdf:resource="&mthreelite;Degree"/>
<rdfs:comment xml:lang="en">A plane angle unit which is equal to 1/360 of a full rotation or pi/180 rad.</rdfs:comment>
<rdfs:label xml:lang="en">Degree Angle</rdfs:label>
<rdfs:seeAlso>http://qudt.org/vocab/unit#DegreeAngle</rdfs:seeAlso>
</owl:Class>
<!-- http://purl.org/iot/vocab/m3-lite#ElectricCurrent -->
<owl:Class rdf:about="&mthreelite;ElectricCurrent">
<rdfs:subClassOf rdf:resource="&qu;QuantityKind"/>
<rdfs:comment xml:lang="en">Electric current is the flow of electric charge. It is a base quantity in the International System of Units. Electric current is electric charge divided by time. Electric Current is the flow (movement) of electric charge. The amount of electric current through some surface, e.g., a section through a copper conductor, is defined as the amount of electric charge flowing through that surface over time.</rdfs:comment>
<rdfs:label xml:lang="en">Electric Current</rdfs:label>
<rdfs:seeAlso>http://qudt.org/vocab/quantity#ElectricCurrent</rdfs:seeAlso>
</owl:Class>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#ActuatingDevice -->
<owl:Class rdf:about="&iot-lite;ActuatingDevice">
<rdfs:subClassOf rdf:resource="&ssn;Device"/>
<rdfs:comment xml:lang="en">Device that can actuate over an object or QuantityKind (e.g., switch on/off the light).</rdfs:comment>
<rdfs:label xml:lang="en">Actuating Device</rdfs:label>
</owl:Class>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#Attribute -->
<owl:Class rdf:about="&iot-lite;Attribute">
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&iot-lite;hasQuantityKind"/>
<owl:qualifiedCardinality rdf:datatype="&xsd;nonNegativeInteger">1</owl:qualifiedCardinality>
<owl:onClass rdf:resource="&qu;QuantityKind"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:comment xml:lang="en">An attribute of an IoT object that can be exposed by an IoT service (i.e. a room (IoT Object) has a temperature (Attribute), that can be exposed by a temperature sensor (IoT device).</rdfs:comment>
<rdfs:label xml:lang="en">Attribute</rdfs:label>
</owl:Class>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#Circle -->
<owl:Class rdf:about="&iot-lite;Circle">
<rdfs:subClassOf rdf:resource="&iot-lite;Coverage"/>
<rdfs:comment xml:lang="en">Circle coverage it needs the location of the sensor as the centre of the circle and the radius as a DataProperty.</rdfs:comment>
<rdfs:label xml:lang="en">Circle</rdfs:label>
</owl:Class>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#Coverage -->
<owl:Class rdf:about="&iot-lite;Coverage">
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&geo;location"/>
<owl:qualifiedCardinality rdf:datatype="&xsd;nonNegativeInteger">1</owl:qualifiedCardinality>
<owl:onClass rdf:resource="&geo;Point"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:comment xml:lang="en">The coverage of an IoT device (i.e. a temperature sensor inside a room has a coverage of that room).</rdfs:comment>
<rdfs:label xml:lang="en">Coverage</rdfs:label>
</owl:Class>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#Entity -->
<owl:Class rdf:about="&iot-lite;Entity">
<owl:equivalentClass rdf:resource="&iot-lite;Object"/>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&iot-lite;hasAttribute"/>
<owl:minQualifiedCardinality rdf:datatype="&xsd;nonNegativeInteger">1</owl:minQualifiedCardinality>
<owl:onClass rdf:resource="&iot-lite;Attribute"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&iot-lite;isAssociatedWith"/>
<owl:minQualifiedCardinality rdf:datatype="&xsd;nonNegativeInteger">1</owl:minQualifiedCardinality>
<owl:onClass rdf:resource="&iot-lite;Service"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&geo;location"/>
<owl:qualifiedCardinality rdf:datatype="&xsd;nonNegativeInteger">1</owl:qualifiedCardinality>
<owl:onClass rdf:resource="&geo;Point"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:label xml:lang="en">Entity</rdfs:label>
<rdfs:comment xml:lang="en">Any object that is relevant from a user or application perspective. (IoT-A Definition)</rdfs:comment>
</owl:Class>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#Metadata -->
<owl:Class rdf:about="&iot-lite;Metadata">
<rdfs:comment xml:lang="en">Class used to describe properties that cannot be described by QuantityKind and Units. i.e. the resolution of a sensor.</rdfs:comment>
<rdfs:label xml:lang="en">Metadata</rdfs:label>
</owl:Class>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#Object -->
<owl:Class rdf:about="&iot-lite;Object">
<rdfs:comment xml:lang="en">IoT entity</rdfs:comment>
<rdfs:label xml:lang="en">IoT Entity or Object</rdfs:label>
</owl:Class>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#Polygon -->
<owl:Class rdf:about="&iot-lite;Polygon">
<rdfs:subClassOf rdf:resource="&iot-lite;Coverage"/>
<rdfs:comment xml:lang="en">The coverage is made up by linking several points by strait lines.</rdfs:comment>
<rdfs:label xml:lang="en">Polygon</rdfs:label>
</owl:Class>
<!-- http://purl.oclc.org/NET/UNIS/fiware/iot-lite#Rectangle -->