-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
16287 lines (13076 loc) · 899 KB
/
index.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>
<head>
<style>
code[class*=language-],pre[class*=language-]{color:#000;background:0 0;text-shadow:0 1px #fff;font-family:Consolas,Monaco,'Andale Mono','Ubuntu Mono',monospace;font-size:1em;text-align:left;white-space:pre;word-spacing:normal;word-break:normal;word-wrap:normal;line-height:1.5;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-hyphens:none;-moz-hyphens:none;-ms-hyphens:none;hyphens:none}code[class*=language-] ::-moz-selection,code[class*=language-]::-moz-selection,pre[class*=language-] ::-moz-selection,pre[class*=language-]::-moz-selection{text-shadow:none;background:#b3d4fc}code[class*=language-] ::selection,code[class*=language-]::selection,pre[class*=language-] ::selection,pre[class*=language-]::selection{text-shadow:none;background:#b3d4fc}@media print{code[class*=language-],pre[class*=language-]{text-shadow:none}}pre[class*=language-]{padding:1em;margin:.5em 0;overflow:auto}:not(pre)>code[class*=language-],pre[class*=language-]{background:#f5f2f0}:not(pre)>code[class*=language-]{padding:.1em;border-radius:.3em;white-space:normal}.token.cdata,.token.comment,.token.doctype,.token.prolog{color:#708090}.token.punctuation{color:#999}.token.namespace{opacity:.7}.token.boolean,.token.constant,.token.deleted,.token.number,.token.property,.token.symbol,.token.tag{color:#905}.token.attr-name,.token.builtin,.token.char,.token.inserted,.token.selector,.token.string{color:#690}.language-css .token.string,.style .token.string,.token.entity,.token.operator,.token.url{color:#9a6e3a;background:hsla(0,0%,100%,.5)}.token.atrule,.token.attr-value,.token.keyword{color:#07a}.token.class-name,.token.function{color:#dd4a68}.token.important,.token.regex,.token.variable{color:#e90}.token.bold,.token.important{font-weight:700}.token.italic{font-style:italic}.token.entity{cursor:help}
code[class*="language-"],
pre[class*="language-"] {
color: black;
background: none;
text-shadow: 0 1px white;
font-family: Consolas, Monaco, 'Andale Mono', 'Ubuntu Mono', monospace;
font-size: 0.8rem; /* 1em */
text-align: left;
white-space: pre;
word-spacing: normal;
word-break: normal;
word-wrap: normal;
line-height: 1.5;
}
/* from: https://www.w3schools.com/howto/howto_css_cards.asp */
.card {
box-shadow: 0 4px 8px 0 rgba(0,0,0,0.2);
transition: 0.3s;
border-radius: 5px; /* 5px rounded corners */
}
/* On mouse-over, add a deeper shadow */
.card:hover {
box-shadow: 0 8px 16px 0 rgba(0,0,0,0.2);
}
/* Add some padding inside the card container */
.container {
padding: 2px 16px;
}
</style>
</head>
<body>
<h1>Docs</h1>
<input type="text" id="search" placeholder="Search" />
<div class="card" data-concept="ns4:purpose">
<h3><a href="#ns4:purpose" id="ns4:purpose">ns4:purpose</a></h3>
<p>URI: <a href="pub:purpose">pub:purpose</a></p>
<pre><code class="language-turtle">
@prefix ns1: <http://sample.org/doc#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
<pub:purpose> ns1:title "PURPOSE" ;
rdfs:comment "The purpose of this standard is to define formal knowledge concepts and a methodology to apply them to create interoperable, machine-readable semantic frameworks for representing building automation and control data, and other building system information." .
</code></pre>
</div>
<div class="card" data-concept="ns4:scope">
<h3><a href="#ns4:scope" id="ns4:scope">ns4:scope</a></h3>
<p>URI: <a href="pub:scope">pub:scope</a></p>
<pre><code class="language-turtle">
@prefix ns1: <http://sample.org/doc#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
<pub:scope> ns1:title "SCOPE" ;
rdfs:comment """This standard provides a comprehensive way to apply semantic formalisms to represent the context of building system data and relationships between the associated building mechanical system components so that software applications can find and understand the information in an automated way. It is intended to facilitate the development and implementation of building analytics tools and enterprise knowledge applications that can implement many building system functions, including:
(a) automated fault detection and diagnostics,
(b) building system commissioning,
(c) digital twins,
(d) optimization of energy use, and
(e) smart grid interactions.
""" .
</code></pre>
</div>
<div class="card" data-concept="ns4:definitions">
<h3><a href="#ns4:definitions" id="ns4:definitions">ns4:definitions</a></h3>
<p>URI: <a href="pub:definitions">pub:definitions</a></p>
<pre><code class="language-turtle">
@prefix ns1: <http://sample.org/doc#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
<pub:definitions> ns1:subclauses ( <pub:definitions-terms> <pub:abbrev> ) ;
ns1:title "DEFINITIONS" .
</code></pre>
</div>
<div class="card" data-concept="ns4:definitions-terms">
<h3><a href="#ns4:definitions-terms" id="ns4:definitions-terms">ns4:definitions-terms</a></h3>
<p>URI: <a href="pub:definitions-terms">pub:definitions-terms</a></p>
<pre><code class="language-turtle">
@prefix ns1: <http://sample.org/doc#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
<pub:definitions-terms> ns1:title "Terms Defined for this Standard" ;
rdfs:comment """
**Connectable:** an abstract class that represents a thing (Equipment or DomainSpace) that can be connected via ConnectionPoints and Connections.
**Connection:** the modeling construct used to represent a physical thing (e.g., pipe, duct, orconductor) that is used to convey some Medium (e.g., water, air, or electricity) between two Connectable things.
**ConnectionPoint:** an abstract modeling construct used to represent the fact that one Connectable thing can be connected to another Connectable thing using a Connection. It is the abstract representation of the flange, wire terminal, or other physical feature where a connection is made.
Domain: a categorization of building service or specialization used to characterize equipment or spaces in a building. Example domains include HVAC, lighting, and plumbing.
**DomainSpace:** a portion or the entirety of a PhysicalSpace that is associated with a Domain, such as lighting, HVAC, or physical security. DomainSpaces can be combined to form a Zone.
**Duct:** a subclass of Connection that is used to transport air such as supply, return, and exhaust in HVAC (Heating, Ventilation, and Air Conditioning) systems.
**Conductor:** a subclass of Connection that represents one or more wires used to convey electricity.
**Equipment:** the modeling construct used to represent a device designed to accomplish a specific task. Examples include a pump, fan, heat exchanger, luminaire, temperature sensor, or flow meter. A piece of equipment can contain another piece of equipment. For example, an air handling unit can contain a cooling coil.
**PhysicalSpace:** an architectural concept that represents a room, a collection of rooms such as a floor, a part of a room, or any physical space that might not even be thought of as a room, such as a patio.
**Pipe:** a subclass of Connection that is used primarily to transport liquids and gases such as water, sewage, natural gas, and compressed air.
**System:** a logical grouping (collection) of Equipment for some functional purpose. Examples of possible systems include an air distribution system, or a hot water system. Systems can contain other Systems. A System does not participate in Connections.
**Zone:** a collection of DomainSpaces of a specific domain that are grouped together from the perspective of building services or controls.
""" .
</code></pre>
</div>
<div class="card" data-concept="ns4:abbrev">
<h3><a href="#ns4:abbrev" id="ns4:abbrev">ns4:abbrev</a></h3>
<p>URI: <a href="pub:abbrev">pub:abbrev</a></p>
<pre><code class="language-turtle">
@prefix ns1: <http://sample.org/doc#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
<pub:abbrev> ns1:title "Abbreviations and Acronyms Used in this Standard" ;
rdfs:comment """
IFC Industry Foundation Class
RDF Resource Description Framework
SHACL Shapes Constraint Language
SPARQL SPARQL Protocol and RDF Query Language
Turtle Terse RDF Triple Language
W3C Worldwide Web Consortium
""" .
</code></pre>
</div>
<div class="card" data-concept="ns4:conceptual-framework">
<h3><a href="#ns4:conceptual-framework" id="ns4:conceptual-framework">ns4:conceptual-framework</a></h3>
<p>URI: <a href="pub:conceptual-framework">pub:conceptual-framework</a></p>
<pre><code class="language-turtle">
@prefix ns1: <http://sample.org/doc#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
<pub:conceptual-framework> ns1:subclauses ( <pub:Conform-Constraints> <pub:Implicit-Info> <pub:Text-Serialization> <pub:Units> <pub:Namespace> <http://data.ashrae.org/standard223#Class> <http://data.ashrae.org/standard223#Concept> <http://data.ashrae.org/standard223#SymmetricProperty> <http://data.ashrae.org/standard223#inverseOf> <http://data.ashrae.org/standard223#abstract> ) ;
ns1:title "CONCEPTUAL FRAMEWORK FOR SEMANTIC MODELING OF BUILDING SYSTEMS AND DATA" ;
rdfs:comment """
This standard defines modeling constructs for use in creating a machine-readable representation of building systems, the building spaces that they serve,
and the measurement and control points used to provide a safe and comfortable environment for the building occupants. The standard can be considered a
toolkit of semantic building blocks and rules for using them to create a semantic model of a particular building or campus of buildings. The resulting model provides
a way for software applications to determine the relationships between the mechanical equipment in the building (i.e., AHU 1 gets chilled water from CH 3
and provides conditioned air to VAV Boxes 12 through 15 serving rooms on the third floor) and the meaning of measurements that are available
(i.e., T16 is a temperature sensor measuring the temperature of the air stream exiting AHU 1).
The model does not directly contain telemetric data about the real-time operation or past operation of the building systems. It does provide information
about the meaning or context of that data and defines external references that are used to point to a source of the data values, thus enablling analytics
applications to find them. If the data source is a BACnet building automation and control system, the external reference contains the necessary information
for analytic software to learn which BACnet device, object and property corresponds to the desired piece of information. This enables construction of a BACnet
message used to read the value.
These capabilities are achieved by applying concepts, standards, and query tools developed and deployed for information and data science applications outside the building domain. A primary commercial driver for developing these standards and tools is the Semantic Web, an extension of the World Wide Web that was created to make the semantic meaning of data accessible from the Internet machine readable.
This standard uses Resource Description Framework (RDF) (W3C) and its extended schema (RDFS) to represent the semantic ideas in the model. RDF is a general method for representing semantic ideas as of a triple. A triple consists of a subject, a predicate, and either a literal or an object. For example:
Jane hasFriend Dave
Jane hasSupervisor Mary
In this example Jane is the subject of both triples, there are two different predicates, hasFriend and hasSupervisor, and there are two different objects,
Dave and Mary. The number of triples is expanded as needed to capture the desired information. The collection of triples represents a directed
multi-graph that can be searched or queried to answer questions or to infer information that may not be explicit in the graph. Figure 4-1 is a graph that
corresponds to this example.
This standard defines subjects, predicates, and objects relevant to the building space that are used to build a multi-graph representing a specific
building or group of buildings. A compelling advantage of this graph-based approach is the ability to combine semantic graphs derived from complementary
semantic models that apply to the same building. This makes it possible to take advantage of the combined information from distinct domains. For example, a
RealEstateCore model that captures how spaces are assigned to different tenants in a building linked to the spaces represented in a Standard 223 model
results in a semantic model containing the combined information. In a similar way, it is possible to link information from a computerized maintenance
management system or an asset management system to the semantic graph of a Standard 223 model by adding a triple that binds a piece of equipment to its
representation in the other system..
A model constructed from this standard describes the topology of the equipment and spaces in a building but not the geometric details. Linking a
Standard 223 model with an RDF representation of a building information model would add that geometric information.
Another advantage of using RDF to model building systems is that a query language standard, SPARQL (W3C SPARQL), exists and tools that implement SPARQL
are readily available. A building analytics tool developer needs only to create a library of queries relevant to their application, and use these queries
to interrogate any Standard 223 conformant model to find what they need from that building for their application.
Using RDF also provides a way to build conformance constraints into this standard in a way that enables conformance to be algorithmically verified.
This is done by using a different W3C standard, Shapes Constraints Language (SHACL) (W3C SHACL). SHACL defines a way to constrain the construction of RDF
graphs through the application of custom developed rules called shapes. The normative constraints described in this standard are formalized in
SHACL shapes. The description of each concept defined in this standard includes a table that lists related conformance constraints defined by these
SHACL shapes. Readily available SHACL reasoners check whether or not a particular model instance conforms to the shapes defined in this standard.
SHACL is also used in this standard to derive implicit information. The triples generated from this inference process enhance the ability to make useful
queries without the burden of a modeler crafting each predicate that might be useful in common searches. The goal is to make model development easier without sacrificing the utility application
developers need to find what they are looking for. The description of each concept defined in this standard with related inference rules includes a
table that lists the relevant SHACL shapes that apply the inferencing.
The Terse RDF Triple Language (W3C Turtle) defines a textual syntax to represent and exchange RDF models.
Because this standard includes references to measurements of physical properties, it is necessary to provide a model representation of units of measure
as well as what those units are quantifying (e.g., temperature, power, etc.). This standard builds upon the "Quantities, Units, Dimensions and
Types" (QUDT) ontology which is the leading open-source model expressed in RDF/SHACL. The QUDT model is documented at https://qudt.org. The key
concepts used here are the classes qudt:Unit and qudt:QuantityKind.
The normative content of this standard is documented in an RDF model textualized using Turtle (see `pub:AnnexA`). All models conforming to this standard shall be textualized using Turtle.
Because it is anticipated that models conforming to this standard will be combined with other semantic models, it is necessary to define a namespace for the
concepts defined by this standard to avoid any possible ambiguities that might arise from the same name being used in the complementary model. In this standard
and all conforming models, the prefix “s223:” shall be used in the name of each concept (class and property) defined by this standard, e.g., s223:Equipment.
The prefix “s223:” is reserved for this standard. Users who extend this standard with additional concept definitions shall use a different prefix for their concepts. The
use of different prefixes for different models allows the combination of models without ambiguity, and makes it possible to enforce a closed-world assumption
for concepts that use the "s223:" prefix, namely allowing the use of a property with a given class only if a SHACL shape has been defined for that use (see `s223:Concept`). The
closed-world assumption is a fundamental principle of semantic modeling that states that if a concept is not defined
in the model, then it is not part of the model. This principle is essential for the development of semantic models that can be used to make inferences about the
real world. Managing the use of the "s223:" prefix also makes it possible to test for strict conformance to the standard.
The concepts and properties mentioned below were designed to aid in standard development using RDF and SHACL exclusively and avoiding any dependence on OWL axioms.
This approach was chosen to avoid some of the shortcomings of using OWL in industrial settings, such as the open world assumption, the many flavors of OWL and their
support, and the sometimes counterintuitive implications of OWL reasoning for non-ontologists. (For example, if an instance satisfies the OWL axioms for a class, then
it is inferred to be an instance of that class). The use of SHACL shapes to define constraints and inferencing rules is a more intuitive way to define intended
model behavior and to verify conformance to the standard. The two most-used OWL inferences, supporting symmetric and inverse properties, are redefined in this standard
using SHACL rules.
""" .
</code></pre>
</div>
<div class="card" data-concept="ns4:Conform-Constraints">
<h3><a href="#ns4:Conform-Constraints" id="ns4:Conform-Constraints">ns4:Conform-Constraints</a></h3>
<p>URI: <a href="pub:Conform-Constraints">pub:Conform-Constraints</a></p>
<pre><code class="language-turtle">
@prefix ns1: <http://sample.org/doc#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
<pub:Conform-Constraints> ns1:title "Conformance Constraints and Validation" ;
rdfs:comment """ Using RDF also provides a way to build conformance constraints into this standard in a way that enables conformance to be algorithmically
verified. This is done by using a different W3C standard, Shapes Constraints Language (SHACL) (W3C SHACL). SHACL defines a way to constrain how RDF graphs
can be constructed through the application of custom developed rules called shapes. The normative constraints described in this standard are formalized in
SHACL shapes. The description of each concept defined in this standard includes a table that lists related conformance constraints defined by these SHACL
shapes. Readily available SHACL reasoners can use the shapes defined in this standard to determine if a particular model instance violates conformance to the standard.
When a SHACL reasoner is applied to a model, discrepancies from the conformance constraints result in a message from the reasoner with one of three levels
of severity (sh:severity).
A message with a severity sh:Info means that a model construct is incomplete.
A message with a severity sh:Warning means that a model construct is used in an unexpected way.
A message with a severity sh:Violation means a model construct is invalid and does not comply with the standard.
The concepts and properties defined in `s223:Class` through `s223:abstract` were designed to aid in standard development using RDF and SHACL exclusively and
avoiding any dependence on OWL
axioms. This approach was chosen to avoid some of the shortcomings of using OWL in industrial settings, such as the open world assumption, the many flavors
of OWL and their support, and the sometimes counterintuitive implications of OWL reasoning for non-ontologists. (For example, if an instance satisfies the
OWL axioms for a class, then it is inferred to be an instance of that class). The use of SHACL shapes to define constraints and inferencing rules is a more
intuitive way to define intended model behavior and to verify conformance to the standard. The two most-used OWL inferences, supporting symmetric and inverse
properties, are redefined in this standard using SHACL rules.
""" .
</code></pre>
</div>
<div class="card" data-concept="ns4:Implicit-Info">
<h3><a href="#ns4:Implicit-Info" id="ns4:Implicit-Info">ns4:Implicit-Info</a></h3>
<p>URI: <a href="pub:Implicit-Info">pub:Implicit-Info</a></p>
<pre><code class="language-turtle">
@prefix ns1: <http://sample.org/doc#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
<pub:Implicit-Info> ns1:title "Deriving Implicit Information from Inference Rules" ;
rdfs:comment """ SHACL is also used in this standard to derive implicit information via a process called inferencing. Inference rules are used to define
how new triples are generated. The triples generated from this inference process enhance the ability to make useful queries without the burden of a modeler
crafting each one. The goal is to make model development easier without sacrificing the utility application developers need to find what they are looking
for. The description of each concept defined in this standard with related inference rules includes a table that lists the relevant SHACL shapes that specify
the inferencing. """ .
</code></pre>
</div>
<div class="card" data-concept="ns4:Text-Serialization">
<h3><a href="#ns4:Text-Serialization" id="ns4:Text-Serialization">ns4:Text-Serialization</a></h3>
<p>URI: <a href="pub:Text-Serialization">pub:Text-Serialization</a></p>
<pre><code class="language-turtle">
@prefix ns1: <http://sample.org/doc#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
<pub:Text-Serialization> ns1:title "Textual Serialization" ;
rdfs:comment """ The Terse RDF Triple Language (W3C Turtle) defines a textual syntax to represent and exchange RDF models.
The normative content of this standard is documented in an RDF model textualized using Turtle (see Clause 15). All models conforming to this standard shall
be textualized using Turtle.
""" .
</code></pre>
</div>
<div class="card" data-concept="ns4:Units">
<h3><a href="#ns4:Units" id="ns4:Units">ns4:Units</a></h3>
<p>URI: <a href="pub:Units">pub:Units</a></p>
<pre><code class="language-turtle">
@prefix ns1: <http://sample.org/doc#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
<pub:Units> ns1:title "Units of Measure" ;
rdfs:comment """ Because this standard includes references to measurements of physical properties, it is necessary to provide a model representation of
units of measure as well as what those units are quantifying (e.g. temperature, power, etc.). This standard builds upon the “Quantities, Units, Dimensions
and Types” (QUDT) ontology which is the leading open-source model expressed in RDF/SHACL. The QUDT model is documented at https://qudt.org. The key concepts
used here are the classes qudt:Unit and qudt:QuantityKind. The 223 standard is compatible with Version 2.1.41 of QUDT and is expected to be compatible with
all newer versions as well.""" .
</code></pre>
</div>
<div class="card" data-concept="ns4:Namespace">
<h3><a href="#ns4:Namespace" id="ns4:Namespace">ns4:Namespace</a></h3>
<p>URI: <a href="pub:Namespace">pub:Namespace</a></p>
<pre><code class="language-turtle">
@prefix ns1: <http://sample.org/doc#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
<pub:Namespace> ns1:title "Namespace" ;
rdfs:comment """ Because it is anticipated that models conforming to this standard will be combined with other semantic models, it is necessary to define
a namespace for the concepts defined by this standard to avoid any possible ambiguities that might arise from a similar name used in the complementary model.
In this standard and all conforming models, the prefix “s223:” shall be used in the name of each concept (class and property) defined by this standard,
e.g., s223:Equipment.
""" .
</code></pre>
</div>
<div class="card" data-concept="ns1:Class">
<h3><a href="#ns1:Class" id="ns1:Class">Class</a></h3>
<p>URI: <a href="http://data.ashrae.org/standard223#Class">http://data.ashrae.org/standard223#Class</a></p>
<pre><code class="language-turtle">
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix sh: <http://www.w3.org/ns/shacl#> .
<http://data.ashrae.org/standard223#Class> a rdfs:Class,
sh:NodeShape ;
rdfs:label "Class" ;
rdfs:comment "This is a modeling construct. All classes defined in the 223 standard are instances of s223:Class rather than owl:Class." ;
rdfs:subClassOf rdfs:Class .
</code></pre>
</div>
<div class="card" data-concept="ns1:Concept">
<h3><a href="#ns1:Concept" id="ns1:Concept">Concept</a></h3>
<p>URI: <a href="http://data.ashrae.org/standard223#Concept">http://data.ashrae.org/standard223#Concept</a></p>
<pre><code class="language-turtle">
@prefix ns1: <http://data.ashrae.org/standard223#> .
@prefix ns2: <http://sample.org/doc#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix sh: <http://www.w3.org/ns/shacl#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
ns1:Concept a ns1:Class,
sh:NodeShape ;
rdfs:label "Concept" ;
ns1:abstract true ;
ns2:subclauses ( ns1:hasProperty ) ;
rdfs:comment "All classes defined in the 223 standard are subclasses of s223:Concept." ;
rdfs:subClassOf rdfs:Resource ;
sh:property [ rdfs:comment "Incompatible Medium. Case1: An entity with a pure medium and an associated property with a pure medium." ;
sh:name "Test for compatible declared Medium" ;
sh:path ns1:hasMedium ;
sh:sparql [ a sh:SPARQLConstraint ;
rdfs:comment "Incompatible Medium. Case 1: Two pure mediums." ;
sh:message "s223: {$this} hasMedium of {?m1}, but is associated with property {?prop} that has ofMedium of {?m2}." ;
sh:prefixes <http://data.ashrae.org/standard223/1.0/validation/model> ;
sh:select """
SELECT $this ?m1 ?prop ?m2
WHERE {
$this s223:hasMedium ?m1 .
$this ?p ?prop .
?prop a/rdfs:subClassOf* s223:Property .
?prop s223:ofMedium ?m2 .
FILTER (?m1 != ?m2 ) .
FILTER NOT EXISTS {?m1 s223:composedOf ?c1} .
FILTER NOT EXISTS {?m2 s223:composedOf ?c2}
FILTER (NOT EXISTS {?m2 rdfs:subClassOf* ?m1}) .
FILTER (NOT EXISTS {?m1 rdfs:subClassOf* ?m2}) .
}
""" ] ],
[ rdfs:comment "Incompatible Medium. Case3: An entity with constituents and an associated property with a pure medium." ;
sh:name "Test for compatible declared Medium" ;
sh:path ns1:hasMedium ;
sh:sparql [ a sh:SPARQLConstraint ;
rdfs:comment "Incompatible Medium. Case 3: A medium with constituents and an associated property with a pure medium." ;
sh:message "s223: {$this} hasMedium of {?m2}, but is associated with property {?prop} that has ofMedium of {?m1}." ;
sh:prefixes <http://data.ashrae.org/standard223/1.0/validation/model> ;
sh:select """
SELECT $this ?m1 ?prop ?m2
WHERE {
$this s223:hasMedium ?m2 .
$this ?p ?prop .
?prop a/rdfs:subClassOf* s223:Property .
?prop s223:ofMedium ?m1 .
?m2 s223:composedOf/s223:ofConstituent ?s2 .
FILTER NOT EXISTS {?m1 s223:composedOf ?c1} .
FILTER NOT EXISTS {
?m2 s223:composedOf/s223:ofConstituent ?s12 .
{?s12 rdfs:subClassOf* ?m1} UNION {?m1 rdfs:subClassOf* ?s12} .
}
}
""" ] ],
[ rdfs:comment "Ensure that any instance that is declared to be an instance of an abstract class must also be declared an instance of at least one subClass of that abstract class." ;
sh:path ns1:abstract ;
sh:sparql [ a sh:SPARQLConstraint ;
rdfs:comment "Ensure that any instance that is declared to be an instance of an abstract class must also be declared an instance of at least one subClass of that abstract class" ;
sh:message "s223: {$this} cannot be declared an instance of only abstract class {?class}." ;
sh:prefixes <http://data.ashrae.org/standard223/1.0/validation/model> ;
sh:select """
SELECT DISTINCT $this ?class
WHERE {
?class s223:abstract true .
$this a ?class .
OPTIONAL {
?otherClass rdfs:subClassOf+ ?class .
$this a ?otherClass .
FILTER (?class != ?otherClass) .
}
FILTER (!bound (?otherClass)) .
}
""" ] ],
[ rdfs:comment "Incompatible Medium. Case2: An entity with a pure medium and an associated property with constituents." ;
sh:name "Test for compatible declared Medium" ;
sh:path ns1:hasMedium ;
sh:sparql [ a sh:SPARQLConstraint ;
rdfs:comment "Incompatible Medium. Case 2: A pure medium and an associated property with constituents." ;
sh:message "s223: {$this} hasMedium of {?m1}, but is associated with property {?prop} that has ofMedium of {?m2}." ;
sh:prefixes <http://data.ashrae.org/standard223/1.0/validation/model> ;
sh:select """
SELECT $this ?m1 ?prop ?m2
WHERE {
$this s223:hasMedium ?m1 .
$this ?p ?prop .
?prop a/rdfs:subClassOf* s223:Property .
?prop s223:ofMedium ?m2 .
?m2 s223:composedOf/s223:ofConstituent ?s2 .
FILTER NOT EXISTS {?m1 s223:composedOf ?c1} .
FILTER NOT EXISTS {
?m2 s223:composedOf/s223:ofConstituent ?s12 .
{?s12 rdfs:subClassOf* ?m1} UNION {?m1 rdfs:subClassOf* ?s12} .
}
}
""" ] ],
[ rdfs:comment "If the relation hasProperty is present, it must associate the concept with a Property." ;
sh:class ns1:Property ;
sh:message "s223: If the relation hasProperty is present, it must associate the concept with a Property." ;
sh:path ns1:hasProperty ],
[ rdfs:comment "A Concept must be associated with at least one label using the relation label." ;
sh:message "s223: A Concept must be associated with at least one label using the relation label." ;
sh:minCount 1 ;
sh:path rdfs:label ;
sh:severity sh:Warning ],
[ rdfs:comment "Incompatible Medium. Case4: An entity with constituents and an associated property with constituents." ;
sh:name "Test for compatible declared Medium" ;
sh:path ns1:hasMedium ;
sh:sparql [ a sh:SPARQLConstraint ;
rdfs:comment "Incompatible Medium. Case 4: A medium with constituents and an associated property with constituents." ;
sh:message "s223: {$this} hasMedium of {?m1}, but is associated with property {?prop} that has ofMedium of {?m2}." ;
sh:prefixes <http://data.ashrae.org/standard223/1.0/validation/model> ;
sh:select """
SELECT $this ?m1 ?prop ?m2
WHERE {
$this s223:hasMedium ?m1 .
$this ?p ?prop .
?prop a/rdfs:subClassOf* s223:Property .
?prop s223:ofMedium ?m2 .
?m1 s223:composedOf/s223:ofConstituent ?s1 .
?m2 s223:composedOf/s223:ofConstituent ?s2 .
FILTER NOT EXISTS {
?m1 s223:composedOf/s223:ofConstituent ?s11 .
?m2 s223:composedOf/s223:ofConstituent ?s12 .
FILTER (?s11 = ?s12) .
}
FILTER NOT EXISTS {
?m1 s223:composedOf/s223:ofConstituent ?s21 .
?m2 s223:composedOf/s223:ofConstituent ?s22 .
{?s22 rdfs:subClassOf* ?s21} UNION {?s21 rdfs:subClassOf* ?s22} .
}
}
""" ] ] ;
sh:rule [ a sh:SPARQLRule ;
rdfs:comment "Add an rdfs:label if it is missing." ;
sh:construct """
CONSTRUCT {$this rdfs:label ?newLabel .}
WHERE {
FILTER (NOT EXISTS {$this rdfs:label ?something}) .
BIND(REPLACE(STR($this), "^.*/([^/]*)$", "$1") AS ?localNameWithoutHash)
BIND(REPLACE(?localNameWithoutHash, "^.*#(.*)$", "$1") AS ?localName)
BIND(REPLACE(?localName, "-", " ", "i") AS ?newLabel)
}
""" ;
sh:name "AddLabelFromLocalName" ;
sh:prefixes <http://data.ashrae.org/standard223/1.0/inference/model-rules> ] .
</code></pre>
</div>
<div class="card" data-concept="ns1:hasProperty">
<h3><a href="#ns1:hasProperty" id="ns1:hasProperty">has Property</a></h3>
<p>URI: <a href="http://data.ashrae.org/standard223#hasProperty">http://data.ashrae.org/standard223#hasProperty</a></p>
<pre><code class="language-turtle">
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
<http://data.ashrae.org/standard223#hasProperty> a rdf:Property ;
rdfs:label "has Property" ;
rdfs:comment "The relation hasProperty is used to associate any 223 Concept with a Property." .
</code></pre>
</div>
<div class="card" data-concept="ns1:SymmetricProperty">
<h3><a href="#ns1:SymmetricProperty" id="ns1:SymmetricProperty">Symmetric property</a></h3>
<p>URI: <a href="http://data.ashrae.org/standard223#SymmetricProperty">http://data.ashrae.org/standard223#SymmetricProperty</a></p>
<pre><code class="language-turtle">
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix sh: <http://www.w3.org/ns/shacl#> .
<http://data.ashrae.org/standard223#SymmetricProperty> a rdfs:Class,
sh:NodeShape ;
rdfs:label "Symmetric property" ;
rdfs:comment "A SymmetricProperty is modeling construct used to define symmetric behavior for certain properties in the standard such as cnx and connected." ;
rdfs:subClassOf rdf:Property .
</code></pre>
</div>
<div class="card" data-concept="ns1:inverseOf">
<h3><a href="#ns1:inverseOf" id="ns1:inverseOf">inverse of</a></h3>
<p>URI: <a href="http://data.ashrae.org/standard223#inverseOf">http://data.ashrae.org/standard223#inverseOf</a></p>
<pre><code class="language-turtle">
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
<http://data.ashrae.org/standard223#inverseOf> a rdf:Property ;
rdfs:label "inverse of" ;
rdfs:comment "The relation inverseOf is a modeling construct to associate relations that are inverses of one another, such as connectedTo and connectedFrom." .
</code></pre>
</div>
<div class="card" data-concept="ns1:abstract">
<h3><a href="#ns1:abstract" id="ns1:abstract">abstract</a></h3>
<p>URI: <a href="http://data.ashrae.org/standard223#abstract">http://data.ashrae.org/standard223#abstract</a></p>
<pre><code class="language-turtle">
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
<http://data.ashrae.org/standard223#abstract> a rdf:Property ;
rdfs:label "abstract" ;
rdfs:comment "If the relation abstract has a value of true, the associated class cannot be instantiated. " ;
rdfs:range xsd:boolean .
</code></pre>
</div>
<div class="card" data-concept="ns4:equipment">
<h3><a href="#ns4:equipment" id="ns4:equipment">ns4:equipment</a></h3>
<p>URI: <a href="pub:equipment">pub:equipment</a></p>
<pre><code class="language-turtle">
@prefix ns1: <http://sample.org/doc#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
<pub:equipment> ns1:subclauses ( <http://data.ashrae.org/standard223#Equipment> <pub:equipment-containment> <http://data.ashrae.org/standard223#contains> <http://data.ashrae.org/standard223#hasRole> <http://data.ashrae.org/standard223#hasPhysicalLocation> <http://data.ashrae.org/standard223#Sensor> <http://data.ashrae.org/standard223#Actuator> <http://data.ashrae.org/standard223#Controller> ) ;
ns1:title "EQUIPMENT" ;
rdfs:comment """This clause is the top level of the hierarchical structure of the portion of the model that represents the characteristics and features of physical equipment that make up the building systems being modeled. Equipment can be connected to other Equipment or DomainSpaces (See `pub:connectedness`). Equipment can optionally contain other pieces of equipment, providing a way to represent its constituent parts within the model (see `pub:equipment-containment`). Equipment can also be grouped together to define a System (see `pub:system`).
""" .
</code></pre>
</div>
<div class="card" data-concept="ns1:Equipment">
<h3><a href="#ns1:Equipment" id="ns1:Equipment">Equipment</a></h3>
<p>URI: <a href="http://data.ashrae.org/standard223#Equipment">http://data.ashrae.org/standard223#Equipment</a></p>
<pre><code class="language-turtle">
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix sh: <http://www.w3.org/ns/shacl#> .
<http://data.ashrae.org/standard223#Equipment> a <http://data.ashrae.org/standard223#Class>,
sh:NodeShape ;
rdfs:label "Equipment" ;
rdfs:comment """
Equipment is the modeling construct used to represent a device designed to accomplish a specific task,
or a complex device that contains component pieces of Equipment. This is distinct from a System, which is a logical grouping or collection of Equipment.
Equipment can have ConnectionPoints and participate
in the flow of one or more kinds of Medium. Examples of possible equipment include a Pump, Fan, HeatExchanger, Luminaire,
TemperatureSensor, or FlowSensor.
In common usage terms like equipment and system have a variety of ambituous and possibly conflicting interpretations. A semantic model
is an attempt to eliminate such ambiguities and conflicts. If the thing being modeled has a need for ConnectionPoints it must be modeled as Equipment and not a System.
Thus, a complex example like a chlled water plant is modeled as Equipment because it has connection points for distributing chilled water. The same chilled water plant
may be part of a logical grouping of pumps, valves, filters, and other things modeled as a chilled water System.
The graphical depiction of Equipment used in this standard is a rounded cornered rectangle as show in Figure 5-1.
""" ;
rdfs:subClassOf <http://data.ashrae.org/standard223#Connectable> ;
sh:property [ rdfs:comment "Disallow contained equipment from having external incoming connections." ;
sh:path <http://data.ashrae.org/standard223#connectedFrom> ;
sh:sparql [ a sh:SPARQLConstraint ;
rdfs:comment "Disallow contained equipment from having external incoming connections." ;
sh:message "s223: {$this} should not have a connection from external equipment {?otherDev} because {?container} contains {$this}." ;
sh:prefixes <http://data.ashrae.org/standard223/1.0/validation/model> ;
sh:select """
SELECT $this ?container ?otherDev
WHERE {
$this s223:connectedFrom ?otherDev .
$this ^s223:contains ?container .
?container a/rdfs:subClassOf* s223:Equipment .
FILTER NOT EXISTS {?container s223:contains ?otherDev .}
}
""" ] ],
[ rdfs:comment "Disallow contained equipment from having external outgoing connections." ;
sh:path <http://data.ashrae.org/standard223#connectedTo> ;
sh:sparql [ a sh:SPARQLConstraint ;
rdfs:comment "Disallow contained equipment from having external outgoing connections." ;
sh:message "s223: {$this} should not have a connection to external equipment {?otherDev} because {?container} contains {$this}." ;
sh:prefixes <http://data.ashrae.org/standard223/1.0/validation/model> ;
sh:select """
SELECT $this ?container ?otherDev
WHERE {
$this s223:connectedTo ?otherDev .
$this ^s223:contains ?container .
?container a/rdfs:subClassOf* s223:Equipment .
FILTER NOT EXISTS {?container s223:contains ?otherDev .}
}
""" ] ],
[ rdfs:comment "Warning about a subClass of Equipment of type A containing something that is in the same subClass branch." ;
sh:path <http://data.ashrae.org/standard223#contains> ;
sh:severity sh:Warning ;
sh:sparql [ a sh:SPARQLConstraint ;
rdfs:comment "Warning about a subClass of Equipment of type A containing something that is in the same subClass branch." ;
sh:message "s223: {$this}, of type {?type1}, contains {?subEquip} of type {?type2}, that could result in double-counting items in the class hierarchy of {?type1}." ;
sh:prefixes <http://data.ashrae.org/standard223/1.0/validation/model> ;
sh:select """
SELECT $this ?subEquip ?type1 ?type2
WHERE {
FILTER NOT EXISTS {$this a s223:Equipment} .
$this s223:contains+ ?subEquip .
FILTER NOT EXISTS {?subEquip a s223:Equipment} .
$this a ?type1 .
?subEquip a ?type2 .
{
?type2 rdfs:subClassOf* ?type1 .
}
UNION
{
?type1 rdfs:subClassOf* ?type2 .
}
}
""" ] ],
[ rdfs:comment "If the relation hasPhysicalLocation is present it must associate the Equipment with a PhysicalSpace." ;
sh:class <http://data.ashrae.org/standard223#PhysicalSpace> ;
sh:message "s223: If the relation hasPhysicalLocation is present it must associate the Equipment with a PhysicalSpace." ;
sh:path <http://data.ashrae.org/standard223#hasPhysicalLocation> ],
[ rdfs:comment "If the relation executes is present it must associate the Equipment with a Function." ;
sh:class <http://data.ashrae.org/standard223#Function> ;
sh:message "s223: If the relation executes is present it must associate the Equipment with a Function." ;
sh:path <http://data.ashrae.org/standard223#executes> ],
[ rdfs:comment "If the relation hasRole is present it must associate the Equipment with a EnumerationKind-Role." ;
sh:class <http://data.ashrae.org/standard223#EnumerationKind-Role> ;
sh:message "s223: If the relation hasRole is present it must associate the Equipment with a EnumerationKind-Role." ;
sh:path <http://data.ashrae.org/standard223#hasRole> ],
[ rdfs:comment """If the relation actuatedByProperty is present it must associate the Equipment with a ActuatableProperty.
Note that any Equipment may use this relation, not just Actuator.""" ;
sh:class <http://data.ashrae.org/standard223#ActuatableProperty> ;
sh:message """If the relation actuatedByProperty is present it must associate the Equipment with a ActuatableProperty.
Note that any Equipment may use this relation, not just Actuator.""" ;
sh:path <http://data.ashrae.org/standard223#actuatedByProperty> ],
[ a sh:PropertyShape ;
rdfs:comment "If the relation contains is present it must associate the Equipment with either Equipment or Junction." ;
sh:message "s223: If the relation contains is present it must associate the Equipment with either Equipment or Junction." ;
sh:name "device contains shape" ;
sh:or ( [ sh:class <http://data.ashrae.org/standard223#Equipment> ] [ sh:class <http://data.ashrae.org/standard223#Junction> ] ) ;
sh:path <http://data.ashrae.org/standard223#contains> ] ;
sh:rule [ a sh:SPARQLRule ;
rdfs:comment "For equipment containing another piece of equipment, use the mapsTo relation to infer a Medium from the contained equipment." ;
sh:construct """
CONSTRUCT {
?parentCp s223:hasMedium ?medium .
}
WHERE {
$this s223:hasConnectionPoint ?cp .
?cp s223:mapsTo ?parentCp .
?cp s223:connectsThrough ?connection .
?cp s223:hasMedium ?medium .
FILTER NOT EXISTS {?parentCp s223:hasMedium ?something} .
}
""" ;
sh:prefixes <http://data.ashrae.org/standard223/1.0/inference/model-rules> ],
[ a sh:SPARQLRule ;
rdfs:comment "For equipment contained within another piece of equipment use the mapsTo relation to infer a Medium from the containing equipment." ;
sh:construct """
CONSTRUCT {
?childCp s223:hasMedium ?medium .
}
WHERE {
$this s223:hasConnectionPoint ?cp .
?childCp s223:mapsTo ?cp .
?cp s223:connectsThrough ?connection .
?cp s223:hasMedium ?medium .
FILTER NOT EXISTS {?childCp s223:hasMedium ?something} .
}
""" ;
sh:prefixes <http://data.ashrae.org/standard223/1.0/inference/model-rules> ] .
</code></pre>
</div>
<div class="card" data-concept="ns4:equipment-containment">
<h3><a href="#ns4:equipment-containment" id="ns4:equipment-containment">ns4:equipment-containment</a></h3>
<p>URI: <a href="pub:equipment-containment">pub:equipment-containment</a></p>
<pre><code class="language-turtle">
@prefix ns1: <http://sample.org/doc#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
<pub:equipment-containment> ns1:title "Equipment Containment" ;
rdfs:comment "A piece of equipment can only contain other pieces of equipment. For example, a fan can be contained by an air handling unit. The relation contains is used to describe a piece of equipment containing another piece of equipment (see `s223:contains`). The relationship mapsTo relates a ConnectionPoint of a contained equipment to the ConnectionPoint of a containing equipment (see `s223:mapsTo`). For example, the inlet to a heating coil contained in a fan coil unit may map to the inlet of the fan coil unit. Any air connection to the fan coil unit inlet is supplying air to the inlet of the heating coil as well. Multiple pieces of equipment contained by the same piece of equipment may connect to each other, however, they may not connect to equipment that are not also contained. To indicate how a contained piece of equipment connects to an external piece of equipment, the relationship mapsTo is used. MapsTo will relate the connection point of a contained equipment to the connection point of the containing equipment, then the connection point of the containing equipment may connect to the external equipment." .
</code></pre>
</div>
<div class="card" data-concept="ns1:contains">
<h3><a href="#ns1:contains" id="ns1:contains">contains</a></h3>
<p>URI: <a href="http://data.ashrae.org/standard223#contains">http://data.ashrae.org/standard223#contains</a></p>
<pre><code class="language-turtle">
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
<http://data.ashrae.org/standard223#contains> a rdf:Property ;
rdfs:label "contains" ;
rdfs:comment "The relation contains is used to associate a PhysicalSpace with its component PhysicalSpaces or a piece of Equipment with its component pieces of Equipment." .
</code></pre>
</div>
<div class="card" data-concept="ns1:hasRole">
<h3><a href="#ns1:hasRole" id="ns1:hasRole">hasRole</a></h3>
<p>URI: <a href="http://data.ashrae.org/standard223#hasRole">http://data.ashrae.org/standard223#hasRole</a></p>
<pre><code class="language-turtle">
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
<http://data.ashrae.org/standard223#hasRole> a rdf:Property ;
rdfs:label "hasRole" ;
rdfs:comment "The relation hasRole is used to indicate the role of an Equipment, Connection, ConnectionPoint, or System within a building (e.g., a heating coil will be associated with Role-Heating). Possible values are defined in EnumerationKind-Role (see `s223:EnumerationKind-Role`)." .
</code></pre>
</div>
<div class="card" data-concept="ns1:hasPhysicalLocation">
<h3><a href="#ns1:hasPhysicalLocation" id="ns1:hasPhysicalLocation">has Physical Location</a></h3>
<p>URI: <a href="http://data.ashrae.org/standard223#hasPhysicalLocation">http://data.ashrae.org/standard223#hasPhysicalLocation</a></p>
<pre><code class="language-turtle">
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
<http://data.ashrae.org/standard223#hasPhysicalLocation> a rdf:Property ;
rdfs:label "has Physical Location" ;
rdfs:comment "The relation hasPhysicalLocation is used to indicate the PhysicalSpace (see `s223:PhysicalSpace`) where a piece of Equipment (see `s223:Equipment`) is located. The physical location of a piece of equipment is not necessarily the same as the location affected by the operation of the equipment. For example, an air handler may physically be on the roof, but its effect is to provide conditioned air to a Zone or DomainSpace within the building. By following the path of Connections, it can be determined what other equipment or spaces are possibly impacted by the equipment." .
</code></pre>
</div>
<div class="card" data-concept="ns1:Sensor">
<h3><a href="#ns1:Sensor" id="ns1:Sensor">Sensor</a></h3>
<p>URI: <a href="http://data.ashrae.org/standard223#Sensor">http://data.ashrae.org/standard223#Sensor</a></p>
<pre><code class="language-turtle">
@prefix ns1: <http://sample.org/doc#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix sh: <http://www.w3.org/ns/shacl#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
<http://data.ashrae.org/standard223#Sensor> a <http://data.ashrae.org/standard223#Class>,
sh:NodeShape ;
rdfs:label "Sensor" ;
ns1:subclauses ( <http://data.ashrae.org/standard223#FlowSensor> <http://data.ashrae.org/standard223#HumiditySensor> <http://data.ashrae.org/standard223#PressureSensor> <http://data.ashrae.org/standard223#TemperatureSensor> <http://data.ashrae.org/standard223#ConcentrationSensor> <http://data.ashrae.org/standard223#LightSensor> <http://data.ashrae.org/standard223#ParticulateSensor> <http://data.ashrae.org/standard223#OccupancySensor> <http://data.ashrae.org/standard223#hasMeasurementResolution> <http://data.ashrae.org/standard223#observes> <http://data.ashrae.org/standard223#hasObservationLocation> <http://data.ashrae.org/standard223#hasReferenceLocation> ) ;
rdfs:comment "A Sensor observes an ObservableProperty (see `s223:ObservableProperty`) which may be quantifiable (see `s223:QuantifiableObservableProperty`), such as a temperature, flowrate, or concentration, or Enumerable (see `s223:EnumeratedObservableProperty`), such as an alarm state or occupancy state." ;
rdfs:subClassOf <http://data.ashrae.org/standard223#Equipment> ;
sh:property [ rdfs:comment "A Sensor must be associated with exactly one location using the relation hasObservationLocation." ;
sh:maxCount 1 ;
sh:message "s223: A Sensor must be associated with exactly one location using the relation hasObservationLocation." ;
sh:minCount 1 ;
sh:path <http://data.ashrae.org/standard223#hasObservationLocation> ],
[ rdfs:comment "s223: If the observed Property has isDeltaQuantity true, the Sensor must have a hasReferenceLocation relation." ;
sh:path <http://data.ashrae.org/standard223#observes> ;
sh:sparql [ a sh:SPARQLConstraint ;
rdfs:comment "s223: If the observed Property has isDeltaQuantity true, the Sensor must have a hasReferenceLocation relation." ;
sh:message "s223: Sensor {$this} has Property {?x} with isDeltaQuantity true, but the Sensor lacks a reference location." ;
sh:prefixes <http://data.ashrae.org/standard223/1.0/validation/model> ;
sh:select """
SELECT $this ?x
WHERE {
$this s223:observes/qudt:isDeltaQuantity true .
$this s223:observes ?x .
?x a/rdfs:subClassOf* s223:QuantifiableProperty .
FILTER NOT EXISTS {$this s223:hasReferenceLocation ?y}
}
""" ] ],
[ rdfs:comment "If a Sensor measures a differential property, it must be associated with exactly 1 of Connectable, Connection, or ConnectionPoint using the relation hasReferenceLocation." ;
sh:maxCount 1 ;
sh:message "s223: If a Sensor measures a differential property, it must be associated with exactly 1 of Connectable, Connection, or ConnectionPoint using the relation hasReferenceLocation." ;
sh:path <http://data.ashrae.org/standard223#hasReferenceLocation> ],
[ rdfs:comment "s223: If the hasReferenceLocation relation exists, the observed Property must have isDeltaQuantity true." ;
sh:path <http://data.ashrae.org/standard223#observes> ;
sh:sparql [ a sh:SPARQLConstraint ;
rdfs:comment "s223: If the hasReferenceLocation relation exists, the observed Property must have isDeltaQuantity true." ;
sh:message "s223: Sensor {$this} has a reference location, but its Property lacks isDeltaQuantity true." ;
sh:prefixes <http://data.ashrae.org/standard223/1.0/validation/model> ;
sh:select """
SELECT $this
WHERE {
$this s223:hasReferenceLocation ?y .
$this s223:observes ?x .
?x a/rdfs:subClassOf* s223:QuantifiableProperty .
FILTER NOT EXISTS {$this s223:observes/qudt:isDeltaQuantity true}
}
""" ] ],
[ rdfs:comment "A Sensor must be associated with exactly one ObservableProperty using the relation observes." ;
sh:class <http://data.ashrae.org/standard223#ObservableProperty> ;
sh:maxCount 1 ;
sh:message "s223: A Sensor must be associated with exactly one ObservableProperty using the relation observes." ;
sh:minCount 1 ;
sh:path <http://data.ashrae.org/standard223#observes> ],
[ rdfs:comment "If the relation hasMeasurementResolution is present it must associate a Sensor with a QuantifiableProperty." ;
sh:class <http://data.ashrae.org/standard223#QuantifiableProperty> ;
sh:message "s223: If the relation hasMeasurementResolution is present it must associate a Sensor with a QuantifiableProperty." ;
sh:path <http://data.ashrae.org/standard223#hasMeasurementResolution> ] ;
sh:rule [ a sh:SPARQLRule ;
rdfs:comment "Infer the hasObservationLocation relation for a Sensor from the Property that it is observing, only if that property is associated with a single entity." ;
sh:construct """
CONSTRUCT {$this s223:hasObservationLocation ?something .}
WHERE {
{
SELECT ?prop (COUNT (DISTINCT ?measurementLocation) AS ?count) $this
WHERE {
FILTER (NOT EXISTS {$this s223:hasObservationLocation ?anything}) .
$this s223:observes ?prop .
?measurementLocation s223:hasProperty ?prop .
}
GROUP BY ?prop $this
}
FILTER (?count = 1) .
?something s223:hasProperty ?prop .
{?something a/rdfs:subClassOf* s223:Connectable}
UNION
{?something a/rdfs:subClassOf* s223:Connection}
UNION
{?something a/rdfs:subClassOf* s223:ConnectionPoint}
}
""" ;
sh:name "InferredMeasurementLocation" ;
sh:prefixes <http://data.ashrae.org/standard223/1.0/inference/model-rules> ] .
</code></pre>
</div>
<div class="card" data-concept="ns1:FlowSensor">
<h3><a href="#ns1:FlowSensor" id="ns1:FlowSensor">Flow sensor</a></h3>
<p>URI: <a href="http://data.ashrae.org/standard223#FlowSensor">http://data.ashrae.org/standard223#FlowSensor</a></p>
<pre><code class="language-turtle">
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix sh: <http://www.w3.org/ns/shacl#> .
<http://data.ashrae.org/standard223#FlowSensor> a <http://data.ashrae.org/standard223#Class>,
sh:NodeShape ;
rdfs:label "Flow sensor" ;
rdfs:comment "A FlowSensor is a specialization of a Sensor that produces an ObservableProperty that is quantifiable and represents a flow measurement." ;
rdfs:subClassOf <http://data.ashrae.org/standard223#Sensor> .
</code></pre>
</div>
<div class="card" data-concept="ns1:HumiditySensor">
<h3><a href="#ns1:HumiditySensor" id="ns1:HumiditySensor">Humidity sensor</a></h3>
<p>URI: <a href="http://data.ashrae.org/standard223#HumiditySensor">http://data.ashrae.org/standard223#HumiditySensor</a></p>
<pre><code class="language-turtle">
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix sh: <http://www.w3.org/ns/shacl#> .
<http://data.ashrae.org/standard223#HumiditySensor> a <http://data.ashrae.org/standard223#Class>,
sh:NodeShape ;
rdfs:label "Humidity sensor" ;
rdfs:comment "A HumiditySensor is a specialization of a Sensor that observes a QuantifiableObservableProperty that represents a humidity measurement. " ;
rdfs:subClassOf <http://data.ashrae.org/standard223#Sensor> ;
sh:property [ rdfs:comment "A HumiditySensor must be defined in terms of the QuantityKind that is being measured, which must be either RelativeHumidity or AbsoluteHumidity." ;
sh:class <http://data.ashrae.org/standard223#QuantifiableObservableProperty> ;
sh:message "s223: A HumiditySensor must observe a QuantifiableObservableProperty that hasQuantityKind of either RelativeHumidity or AbsoluteHumidity." ;
sh:node [ sh:property [ sh:or ( [ sh:hasValue <http://qudt.org/vocab/quantitykind/RelativeHumidity> ] [ sh:hasValue <http://qudt.org/vocab/quantitykind/AbsoluteHumidity> ] ) ;
sh:path <http://qudt.org/schema/qudt/hasQuantityKind> ] ] ;
sh:path <http://data.ashrae.org/standard223#observes> ] .
</code></pre>
</div>
<div class="card" data-concept="ns1:PressureSensor">
<h3><a href="#ns1:PressureSensor" id="ns1:PressureSensor">Pressure sensor</a></h3>
<p>URI: <a href="http://data.ashrae.org/standard223#PressureSensor">http://data.ashrae.org/standard223#PressureSensor</a></p>
<pre><code class="language-turtle">
@prefix ns1: <http://sample.org/doc#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix sh: <http://www.w3.org/ns/shacl#> .
<http://data.ashrae.org/standard223#PressureSensor> a <http://data.ashrae.org/standard223#Class>,
sh:NodeShape ;
rdfs:label "Pressure sensor" ;
ns1:subclauses ( <http://data.ashrae.org/standard223#GaugePressureSensor> ) ;
rdfs:comment """
There are three primary use cases for measuring pressure in building environments.
- The first use case involves measuring absolute pressure, which is essential in applications like weather stations
where atmospheric pressure readings are required.
- The second use case pertains to measuring differential pressure. This is crucial in HVAC systems, for instance,
where it's necessary to measure the pressure drop across filters in ducts or compare the pressure between different
rooms and hallways to ensure proper airflow and contamination control.
- The third use case is measuring gauge pressure, which indicates pressure relative to atmospheric pressure.
This is commonly used in applications such as monitoring compressed gas cylinders. In this scenario, a gauge
reading of zero signifies that the measured pressure is equal to the atmospheric pressure, not a vacuum.
Modeling a sensor that measures each of these can be performed as follows: