forked from buildingSMART/IFC4.3.x-output
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathIfcProductExtension.pot
4058 lines (2901 loc) · 235 KB
/
IfcProductExtension.pot
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
# Industry Foundation Classes IFC.
# Copyright (C) 2020 buildingSMART
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2020-09-25 10:09+0200\n"
"X-Crowdin-SourceKey: msgstr\n"
"Language-Team: buildingSMART community\n"
#:IFC.xml:27286
msgid "IfcLinearElement"
msgstr "IfcLinearElement"
msgid "IfcLinearElement_DEFINITION"
msgstr ""
#:IFC.xml:27299
msgid "IfcAlignment"
msgstr "IfcAlignment"
msgid "IfcAlignment_DEFINITION"
msgstr "An alignment is used to define a reference system to position elements mainly for linear construction works, such as roads, rails, bridges, and others. The relative positioning along the alignment is defined by the linear referencing methodology. NOTE See ISO 19148 Geographic information Linear referencing for general definitions about linear referencing. A single alignment may have a horizontal alignment defined in the x y plane of the engineering coordinate system an accompanying vertical alignment, defined along the horizontal alignment in the distance along z coordinate space a relative alignment, defined as a span within another alignment and or at constant or variable offsets a 3D alignment, either computed from the horizontal and vertical alignment, or extracted from geospatial data. Alignments may be aggregated into referents [[IfcReferent]] or derivative alignments. Derivative alignments may be used to indicate dependent alignments, such as an alignment for a bridge that is relative to a parent alignment for a road, where the child [[IfcAlignment]] may have Axis set to [[IfcOffsetCurveByDistances]] that starts and ends at a span within the extent of the [[IfcAlignmentCurve]] defined at the Axis of the parent [[IfcAlignment]] . Alignments may be assigned to groups using [[IfcRelAssignsToGroup]] , where [[IfcGroup]] or subtypes may capture information common to multiple alignments. Supported representations of [[IfcAlignment]].Axis are [[IfcAlignmentCurve]] as a 3D horizontal and vertical alignment represented by their alignment segments [[IfcAlignmentCurve]] as a 2D horizontal alignment represented by its horizontal alignment segments without a vertical alignment [[IfcOffsetCurveByDistances]] as a 2D or 3D curve defined relative to an [[IfcAlignmentCurve]] or another [[IfcOffsetCurveByDistances]] [[IfcPolyline]] as a 3D alignment by a 3D polyline representation such as coming from a survey [[IfcPolyline]] as a 2D horizontal alignment by a 2D polyline representation such as in very early planning phases or as a map representation NOTE Although Axis is an [[IfcCurve]] base type, only derived types [[IfcAlignmentCurve]] , [[IfcOffsetCurveByDistances]] , and [[IfcPolyline]] are meant to be supported types. Derivative specifications Model View Definitions may expand this set to include additional curve types. bSI Documentation"
#:IFC.xml:27302
msgid "IfcAlignment_PredefinedType"
msgstr "PredefinedType"
msgid "IfcAlignment_PredefinedType_DEFINITION"
msgstr "PredefinedType"
#:IFC.xml:27317
msgid "IfcAlignmentTypeEnum"
msgstr "IfcAlignmentTypeEnum"
msgid "IfcAlignmentTypeEnum_DEFINITION"
msgstr "This enumeration defines the different types of alignments. bSI Documentation"
#:IFC.xml:27320
msgid "IfcAnnotation"
msgstr "IfcAnnotation"
msgid "IfcAnnotation_DEFINITION"
msgstr "An annotation is an information element within the geometric and spatial context of a project, that adds a note or meaning to the objects which constitutes the project model. Annotations include additional points, curves, text, dimensioning, hatching and other forms of graphical notes. It also includes virtual or symbolic representations of additional model components, not representing products or spatial structures, such as event elements, survey points, contour lines or similar. NOTE Additional presentation information often 2D such as tag number or hatching, that is directly related to a particular product representation is included within the [[IfcProductDefinitionShape]] having various [[IfcShapeRepresentation]] s of the [[IfcElement]] and its subtypes . Only those presentation information, that cannot be directly related to a single product, have to be wrapped within the [[IfcAnnotation]]. If available, the annotation should be related to the spatial context of the project, by containing the annotation within the appropriate level of the building structure site, facility, facility part or building, storey, or space . This is handled by the [[IfcRelContainedInSpatialStructure]] relationship. The [[IfcAnnotation]] can provide specific 0D, 1D, and 2D geometric items as representation of the annotation, offering annotation point, curves, and surfaces. In addition to the predefined type values in [[IfcAnnotationTypeEnum]], the following values can be used for the ObjectType with PredefinedType attribute value USERDEFINED . Annotation point is an annotation provided by a point that has additional semantic. The inherited attribute ObjectType should be used to capture the type of point annotation, some suggested values are SurveyPoint A single survey point represented by a Cartesian point. A property set may add the conditions method, accuracy, etc. to the survey point . SurveyArea A set of survey points represented by Cartesian point. These coordinates are determined relative to the coordinates of a reference point, which acts as the datum for the survey. Properties attached apply equally to all points. The difference in elevation of the survey points enables terrain to be determined. Annotation curve is an annotation provided by a curve that has additional semantic. The inherited attribute ObjectType should be used to capture the type of curve annotation, some suggested values are ContourLine A line of constant elevation typically used on geographic maps where the spacing of lines at constant intervals of elevation may be used as an indication of slope. IsoBar A line of constant pressure typically used on weather maps or to show pressure gradient in spaces, chambers or externally. IsoLux A line of constant illumination typically used to show the distribution of illumination levels and or day lighting in a space or externally. IsoTherm A line of constant temperature typically used to show the distribution and effect of heating or cooling within a space or to show temperature distribution on a geographic map. Annotation surface is an annotation provided by a surface that has additional semantic. The inherited attribute ObjectType should be used to capture the type of surface annotation, some suggested values are SurveyArea A surface patch based on survey points. bSI Documentation"
#:IFC.xml:27340
msgid "IfcAnnotation_ContainedInStructure"
msgstr "ContainedInStructure"
msgid "IfcAnnotation_ContainedInStructure_DEFINITION"
msgstr "ContainedInStructure"
#:IFC.xml:27321
msgid "IfcAnnotation_PredefinedType"
msgstr "PredefinedType"
msgid "IfcAnnotation_PredefinedType_DEFINITION"
msgstr "PredefinedType"
#:IFC.xml:27352
msgid "IfcAssemblyPlaceEnum"
msgstr "IfcAssemblyPlaceEnum"
msgid "IfcAssemblyPlaceEnum_DEFINITION"
msgstr "This enumeration defines where the assembly is intended to take place, either in a factory or on the building site. HISTORY New enumeration in IFC2x2. bSI Documentation"
#:IFC.xml:27361
msgid "IfcBridge"
msgstr "IfcBridge"
msgid "IfcBridge_DEFINITION"
msgstr "A Bridge is civil engineering works that affords passage to pedestrians, animals, vehicles, and services above obstacles or between two points at a height above ground. NOTE Definition from ISO 6707 1 2014 Civil engineering works that affords passage to pedestrians, animals, vehicles, and services above obstacles or between two points at a height above ground. bSI Documentation"
#:IFC.xml:27364
msgid "IfcBridge_PredefinedType"
msgstr "PredefinedType"
msgid "IfcBridge_PredefinedType_DEFINITION"
msgstr "PredefinedType"
#:IFC.xml:27379
msgid "IfcBridgePart"
msgstr "IfcBridgePart"
msgid "IfcBridgePart_DEFINITION"
msgstr "In a bridge, BridgePart as subtype of FacilityPart represents the parts in breakdown structure according to local practices e.g. Superstructure, Substructure, Foundation , and these can also be broken down further e.g. Substructure as whole can be COMPLEX, while each abutment and pier would be ELEMENT, and a pier can be composed of separate towers PARTIAL . bSI Documentation"
#:IFC.xml:27383
msgid "IfcBridgePartTypeEnum"
msgstr "IfcBridgePartTypeEnum"
msgid "IfcBridgePartTypeEnum_DEFINITION"
msgstr "bSI Documentation"
#:IFC.xml:27404
msgid "IfcBridgePartTypeEnum_PYLON"
msgstr "PYLON"
msgid "IfcBridgePartTypeEnum_PYLON_DEFINITION"
msgstr "PYLON"
#:IFC.xml:27400
msgid "IfcBridgePartTypeEnum_DECK_SEGMENT"
msgstr "DECK SEGMENT"
msgid "IfcBridgePartTypeEnum_DECK_SEGMENT_DEFINITION"
msgstr ""
#:IFC.xml:27396
msgid "IfcBridgePartTypeEnum_ABUTMENT"
msgstr "ABUTMENT"
msgid "IfcBridgePartTypeEnum_ABUTMENT_DEFINITION"
msgstr "ABUTMENT"
#:IFC.xml:27405
msgid "IfcBridgePartTypeEnum_SUBSTRUCTURE"
msgstr "SUBSTRUCTURE"
msgid "IfcBridgePartTypeEnum_SUBSTRUCTURE_DEFINITION"
msgstr ""
#:IFC.xml:27406
msgid "IfcBridgePartTypeEnum_SUPERSTRUCTURE"
msgstr "SUPERSTRUCTURE"
msgid "IfcBridgePartTypeEnum_SUPERSTRUCTURE_DEFINITION"
msgstr ""
#:IFC.xml:27407
msgid "IfcBridgePartTypeEnum_SURFACESTRUCTURE"
msgstr "SURFACESTRUCTURE"
msgid "IfcBridgePartTypeEnum_SURFACESTRUCTURE_DEFINITION"
msgstr ""
#:IFC.xml:27402
msgid "IfcBridgePartTypeEnum_PIER"
msgstr "PIER"
msgid "IfcBridgePartTypeEnum_PIER_DEFINITION"
msgstr "PIER"
#:IFC.xml:27403
msgid "IfcBridgePartTypeEnum_PIER_SEGMENT"
msgstr "PIER SEGMENT"
msgid "IfcBridgePartTypeEnum_PIER_SEGMENT_DEFINITION"
msgstr ""
#:IFC.xml:27398
msgid "IfcBridgePartTypeEnum_DECK"
msgstr "DECK"
msgid "IfcBridgePartTypeEnum_DECK_DEFINITION"
msgstr "DECK"
#:IFC.xml:27401
msgid "IfcBridgePartTypeEnum_FOUNDATION"
msgstr "FOUNDATION"
msgid "IfcBridgePartTypeEnum_FOUNDATION_DEFINITION"
msgstr "FOUNDATION"
#:IFC.xml:27408
msgid "IfcBridgeTypeEnum"
msgstr "IfcBridgeTypeEnum"
msgid "IfcBridgeTypeEnum_DEFINITION"
msgstr "bSI Documentation"
#:IFC.xml:27423
msgid "IfcBridgeTypeEnum_SUSPENSION"
msgstr "SUSPENSION"
msgid "IfcBridgeTypeEnum_SUSPENSION_DEFINITION"
msgstr ""
#:IFC.xml:27417
msgid "IfcBridgeTypeEnum_ARCHED"
msgstr "ARCHED"
msgid "IfcBridgeTypeEnum_ARCHED_DEFINITION"
msgstr ""
#:IFC.xml:27421
msgid "IfcBridgeTypeEnum_FRAMEWORK"
msgstr "FRAMEWORK"
msgid "IfcBridgeTypeEnum_FRAMEWORK_DEFINITION"
msgstr ""
#:IFC.xml:27419
msgid "IfcBridgeTypeEnum_CANTILEVER"
msgstr "CANTILEVER"
msgid "IfcBridgeTypeEnum_CANTILEVER_DEFINITION"
msgstr ""
#:IFC.xml:27422
msgid "IfcBridgeTypeEnum_GIRDER"
msgstr "GIRDER"
msgid "IfcBridgeTypeEnum_GIRDER_DEFINITION"
msgstr "GIRDER"
#:IFC.xml:27424
msgid "IfcBridgeTypeEnum_TRUSS"
msgstr "TRUSS"
msgid "IfcBridgeTypeEnum_TRUSS_DEFINITION"
msgstr "TRUSS"
#:IFC.xml:27418
msgid "IfcBridgeTypeEnum_CABLE_STAYED"
msgstr "CABLE STAYED"
msgid "IfcBridgeTypeEnum_CABLE_STAYED_DEFINITION"
msgstr ""
#:IFC.xml:27420
msgid "IfcBridgeTypeEnum_CULVERT"
msgstr "CULVERT"
msgid "IfcBridgeTypeEnum_CULVERT_DEFINITION"
msgstr "CULVERT"
#:IFC.xml:27425
msgid "IfcBuilding"
msgstr "IfcBuilding"
msgid "IfcBuilding_DEFINITION"
msgstr "A building represents a structure that provides shelter for its occupants or contents and stands in one place. The building is also used to provide a basic element within the spatial structure hierarchy for the components of a building project together with site, storey, and space . NOTE Definition from ISO 6707 1 Construction work that has the provision of shelter for its occupants or contents as one of its main purpose and is normally designed to stand permanently in one place. A building is if specified associated to a site. A building may span over several connected or disconnected buildings. Therefore building complex provides for a collection of buildings included in a site. A building can also be decomposed in vertical parts, where each part defines a building section. This is defined by the composition type attribute of the supertype IfcSpatialStructureElements which is interpreted as follow COMPLEX building complex ELEMENT building PARTIAL building section The [[IfcBuilding]] is used to build the spatial structure of a building that serves as the primary project breakdown and is required to be hierarchical . The spatial structure elements are linked together by using the objectified relationship [[IfcRelAggregates]]. Figure 150 shows the [[IfcBuilding]] as part of the spatial structure. It also serves as the spatial container for building and other elements. NOTE Detailed requirements on mandatory element containment and placement structure relationships are given in view definitions and implementer agreements. Building composition Figure 150 Building composition Systems, such as building service or electrical distribution systems, zonal systems, or structural analysis systems, relate to [[IfcBuilding]] by using the objectified relationship [[IfcRelReferencedInSpatialStructure]]. Figure 151 describes the heights and elevations of the [[IfcBuilding]] . It is used to provide the height above sea level of the project height datum for this building, that is, the internal height 0.00. The height 0.00 is often used as a building internal reference height and equal to the floor finish level of the ground floor. base elevation of building provided by [[IfcBuilding]].ElevationOfRefHeight, it is usually the top of construction slab. base elevation of terrain at the perimeter of the building provided by [[IfcBuilding]].ElevationOfTerrain, it is usually the minimum elevation is sloped terrain total height of building, also referred to as ridge height top of roof structure, e.g the ridge against terrain provided by BaseQuantity with Name TotalHeight eaves height of building base of roof structure, e.g the eaves against terrain provided by BaseQuantity with Name EavesHeight building elevations Figure 2 Building elevations HISTORY New entity in IFC1.0. bSI Documentation"
#:IFC.xml:407
msgid "IfcBuilding_BuildingAddress"
msgstr "BuildingAddress"
msgid "IfcBuilding_BuildingAddress_DEFINITION"
msgstr "BuildingAddress"
#:IFC.xml:27426
msgid "IfcBuilding_ElevationOfRefHeight"
msgstr "ElevationOfRefHeight"
msgid "IfcBuilding_ElevationOfRefHeight_DEFINITION"
msgstr "Elevation above sea level of the reference height used for all storey elevation measures, equals to height 0.0. It is usually the ground floor level."
#:IFC.xml:27431
msgid "IfcBuilding_ElevationOfTerrain"
msgstr "ElevationOfTerrain"
msgid "IfcBuilding_ElevationOfTerrain_DEFINITION"
msgstr "Elevation above the minimal terrain level around the foot print of the building, given in elevation above sea level."
#:IFC.xml:27445
msgid "IfcBuildingStorey"
msgstr "IfcBuildingStorey"
msgid "IfcBuildingStorey_DEFINITION"
msgstr "The building storey has an elevation and typically represents a nearly horizontal aggregation of spaces that are vertically bound. A storey is if specified associated to a building. A storey may span over several connected storeys. Therefore storey complex provides for a collection of storeys included in a building. A storey can also be decomposed in horizontical parts, where each part defines a partial storey. This is defined by the composition type attribute of the supertype IfcSpatialStructureElements which is interpreted as follow COMPLEX building storey complex ELEMENT building storey PARTIAL partial building storey EXAMPLE In split level houses, a storey is split into two or more partial storeys, each with a different elevation. It can be handled by defining a storey, which includes two or more partial storeys with the individual elevations. The [[IfcBuildingStorey]] is used to build the spatial structure of a building that serves as the primary project breakdown and is required to be hierarchical . The spatial structure elements are linked together by using the objectified relationship [[IfcRelAggregates]] . Figure 1 shows the [[IfcBuildingStorey]] as part of the s patial structure. It also serves as the spatial container for building and other elements. NOTE Detailed requirements on mandatory element containment and placement structure relationships are given in view definitions and implementer agreements. [[IfcBuildingStorey]] as part of a spatial structure .. .. .. .. .. .. figures ifcbuildingstorey spatialstructure.png Figure 1 Building storey composition Figure 2 describes the heights and elevations of the [[IfcBuildingStorey]] . elevation of storey provided by [[IfcBuildingStorey]].Elevation as a local height value relative to [[IfcBuilding]].ElevationOfRefHeight , it is usually the top of construction slab net height of storey, also referred to as total height or system height top of construction slab to top of construction slab above provided by BaseQuantity with Name GrossHeight net height of storey top of construction slab to bottom of construction slab above provided by BaseQuantity with Name NetHeight space heights .. .. .. .. .. .. figures ifcbuildingstorey heights.png Figure 2 Building storey elevations HISTORY New entity in IFC1.0 bSI Documentation"
#:IFC.xml:27446
msgid "IfcBuildingStorey_Elevation"
msgstr "Elevation"
msgid "IfcBuildingStorey_Elevation_DEFINITION"
msgstr "Elevation of the base of this storey, relative to the 0,00 internal reference height of the building. The 0.00 level is given by the absolute above sea level height by the ElevationOfRefHeight attribute given at [[IfcBuilding]] . X 0D X 0D NOTE If the geometric data is provided ObjectPlacement is specified , the Elevation value shall either not be included, or be equal to the local placement Z value."
#:IFC.xml:27455
msgid "IfcBuiltElement"
msgstr "IfcBuiltElement"
msgid "IfcBuiltElement_DEFINITION"
msgstr "The built element comprises all elements that are primarily part of the construction of a built facility, i.e., its structural and space separating system. Built elements are all physically existent and tangible things NOTE Definition from ISO 6707 1 Major functional part of a building, examples are foundation, floor, roof, wall. This [[IfcBuiltElement]] is a generalization of all elements that participate in a building system. Typical examples of [[IfcBuiltElement]] s are among others built elements within a space separation systems built elements within an enclosure system such as a facade built elements within a fenestration system built elements within a load bearing system built elements within a foundation system EXAMPLE built elements are walls, curtain wall, doors, columns, pile, and others. REMOVE The [[IfcBuiltElement]] is an abstract entity that cannot be instantiated. For arbitrary building elements, that cannot be expressed by a subtype of [[IfcBuiltElement]] , use IfcBuiltElementProxy . The [[IfcBuiltElement]] can be instantiated in the case when arbitrary built elements cannot be expressed by a subtype of [[IfcBuiltElement]]. HISTORY New entity in IFC1.0 bSI Documentation"
#:IFC.xml:27463
msgid "IfcBuiltElementType"
msgstr "IfcBuiltElementType"
msgid "IfcBuiltElementType_DEFINITION"
msgstr "The [[IfcBuiltElementType]] provides the type information for [[IfcBuiltElement]] occurrences. NOTE The product representations are defined as representation maps at the level of the supertype [[IfcTypeProduct]] , which gets assigned by an element occurrence instance through the [[IfcShapeRepresentation]].Item 1 being an [[IfcMappedItem]] . A built element type is used to define the common properties of a certain type of built element that are applied to all occurrences of that type. It is used to define a built element specification i.e. the specific product information, that is common to all occurrences of that product type . Built element types or the instantiable subtypes may be exchanged without being already assigned to occurrences. REMOVE The IfcBuildingElementType is an abstract type that cannot be instantiated. For arbitrary building element types, that cannot be expressed by a subtype of IfcBuildingElementType , use [[IfcBuildingElementProxyType]] . The [[IfcBuiltElementType]] can be instantiated in the case when arbitrary built element types cannot be expressed by a subtype of [[IfcBuiltElementType]] . Occurrences of subtypes of the IfcBuildingElementType are represented by instances of the appropriate subtypes of IfcBuildingElement . HISTORY New entity in IFC2x2. bSI Documentation"
#:IFC.xml:27466
msgid "IfcCivilElement"
msgstr "IfcCivilElement"
msgid "IfcCivilElement_DEFINITION"
msgstr "An [[IfcCivilElement]] is a generalization of all elements within a civil engineering works that cannot be represented as BuildingElements, DistributionElements or GeographicElements. Depending on the context of the construction project, included building work, such as buildings or factories, are represented as a collection of [[IfcBuiltElement]] s, distribution systems, such as piping or drainage, are represented as a collection of [[IfcDistributionElement]] s, and other geographic elements, such as trees, light posts, traffic signs etc. are represented as [[IfcGeographicElement]] s. NOTE The [[IfcCivilElement]] has been introduced as a stub for future extensions of this specification to include an object model for civil engineering works. Civil elements are typically horizontally organized using a spatial structure expressed by spatial zones, therefore [[IfcCivilElement]] is spatially contained by default within an [[IfcSpatialZone]]. HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:27472
msgid "IfcCivilElementType"
msgstr "IfcCivilElementType"
msgid "IfcCivilElementType_DEFINITION"
msgstr "An [[IfcCivilElementType]] is used to define an element specification of an element used within civil engineering works. Civil element types include for different types of element that may be used to represent information for construction works external to a building. [[IfcCivilElementType]] s may include linear elements such as sections of a roadway including carriageway pavement, verge, median, marker line, kerb etc. elements for connections and junctions including traffic roundabouts, T junctions, 4 way junctions elements for supporting structures such as piers, piles, pylons, and similar. The specification of the specific types is provided by the inherited attribute [[IfcElementType]].ElementType given as an [[IfcLabel]]. NOTE This is due to the range of choices of element type that are available and their expression in different languages. It is not considered possible to create a reasonably full list of types within an enumeration. It is suggested that selection of the relevant type be drawn from an available feature catalogue . NOTE The [[IfcCivilElementType]] has been introduced as a stub for future extensions of this specification to include an object model for civil engineering works. HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:27475
msgid "IfcDistributionElement"
msgstr "IfcDistributionElement"
msgid "IfcDistributionElement_DEFINITION"
msgstr "This [[IfcDistributionElement]] is a generalization of all elements that participate in a distribution system. Typical examples of [[IfcDistributionElement]] s are among others building service elements within a heating systems building service elements within a cooling system building service elements within a ventilation system building service elements within a plumbing system building service elements within a drainage system electrical elements elements within a communication network within a sensor monitoring network The [[IfcDistributionElement]] is further specialized in the IFC specification. Direct instantiation of [[IfcDistributionElement]] without an assigned subtype of [[IfcDistributionElementType]] provides the meaning of an distribution element proxy. HISTORY New entity in IFC1.5. .change ifc2x4 IFC4 CHANGE The entity is marked as deprecated for instantiation will be made ABSTRACT in future releases. bSI Documentation"
#:IFC.xml:27479
msgid "IfcDistributionElement_HasPorts"
msgstr "HasPorts"
msgid "IfcDistributionElement_HasPorts_DEFINITION"
msgstr "HasPorts"
#:IFC.xml:27493
msgid "IfcDistributionElementType"
msgstr "IfcDistributionElementType"
msgid "IfcDistributionElementType_DEFINITION"
msgstr "The [[IfcDistributionElementType]] defines a list of commonly shared property set definitions of an element and an optional set of product representations. It is used to define an element specification i.e. the specific product information, that is common to all occurrences of that product type . NOTE The product representations are defined as representation maps at the level of the supertype [[IfcTypeProduct]] , which gets assigned by an element occurrence instance through the [[IfcShapeRepresentation]].Item 1 being an [[IfcMappedItem]] . A distribution element type is used to define the common properties of a certain type of a distribution element that may be applied to many instances of that feature type to assign a specific style. Distribution element types or the instantiable subtypes may be exchanged without being already assigned to occurrences. The occurrences of the [[IfcDistributionElementType]] are represented by instances of [[IfcDistributionElement]] or its subtypes . HISTORY New entity in IFC2x2. .change ifc2x3 IFC2x3 CHANGE The entity has been made non abstract .change ifc2x3 IFC4 CHANGE The entity is marked as deprecated for instantiation will be made ABSTRACT in future releases. bSI Documentation"
#:IFC.xml:27496
msgid "IfcElement"
msgstr "IfcElement"
msgid "IfcElement_DEFINITION"
msgstr "An element is a generalization of all components that make up an AEC product. Elements are physically existent objects, although they might be void elements, such as holes. Elements either remain permanently in the AEC product, or only temporarily, as formwork does. Elements can be either assembled on site or pre manufactured and built in on site. EXAMPLE Examples of elements in a building construction context are walls, floors, windows and recesses. The elements can be logically contained by a spatial structure element that constitutes a certain level within a project structure hierarchy site, building, storey or space . This is done by using the [[IfcRelContainedInSpatialStructure]] relationship. An element can have material and quantity information assigned through the [[IfcRelAssociatesMaterial]] and [[IfcRelDefinesByProperties]] relationship. In addition an element can be declared to be a specific occurrence of an element type and thereby be defined by the element type properties using the [[IfcRelDefinesByType]] relationship. An element can also be defined as an element assembly that is a group of semantically and topologically related elements that form a higher level part of the AEC product. Those element assemblies are defined by virtue of the [[IfcRelAggregates]] relationship. EXAMPLE Examples for element assembly are complete Roof Structures, made by several Roof Areas, or a Stair, composed by Flights and Landings. Elements that performs the same function may be grouped by an Element Group By Function . It is realized by an instance of [[IfcGroup]] with the ObjectType ElementGroupByFunction . HISTORY New entity in IFC1.0 bSI Documentation"
#:IFC.xml:27514
msgid "IfcElement_HasProjections"
msgstr "HasProjections"
msgid "IfcElement_HasProjections_DEFINITION"
msgstr "HasProjections"
#:IFC.xml:27528
msgid "IfcElement_HasOpenings"
msgstr "HasOpenings"
msgid "IfcElement_HasOpenings_DEFINITION"
msgstr "HasOpenings"
#:IFC.xml:27542
msgid "IfcElement_IsConnectionRealization"
msgstr "IsConnectionRealization"
msgid "IfcElement_IsConnectionRealization_DEFINITION"
msgstr "IsConnectionRealization"
#:IFC.xml:27556
msgid "IfcElement_HasCoverings"
msgstr "HasCoverings"
msgid "IfcElement_HasCoverings_DEFINITION"
msgstr "HasCoverings"
#:IFC.xml:27570
msgid "IfcElement_InterferesElements"
msgstr "InterferesElements"
msgid "IfcElement_InterferesElements_DEFINITION"
msgstr "InterferesElements"
#:IFC.xml:27580
msgid "IfcElement_ConnectedFrom"
msgstr "ConnectedFrom"
msgid "IfcElement_ConnectedFrom_DEFINITION"
msgstr "ConnectedFrom"
#:IFC.xml:27594
msgid "IfcElement_ContainedInStructure"
msgstr "ContainedInStructure"
msgid "IfcElement_ContainedInStructure_DEFINITION"
msgstr "ContainedInStructure"
#:IFC.xml:27606
msgid "IfcElement_ConnectedTo"
msgstr "ConnectedTo"
msgid "IfcElement_ConnectedTo_DEFINITION"
msgstr "ConnectedTo"
#:IFC.xml:27620
msgid "IfcElement_IsInterferedByElements"
msgstr "IsInterferedByElements"
msgid "IfcElement_IsInterferedByElements_DEFINITION"
msgstr "IsInterferedByElements"
#:IFC.xml:27630
msgid "IfcElement_FillsVoids"
msgstr "FillsVoids"
msgid "IfcElement_FillsVoids_DEFINITION"
msgstr "FillsVoids"
#:IFC.xml:27644
msgid "IfcElement_ProvidesBoundaries"
msgstr "ProvidesBoundaries"
msgid "IfcElement_ProvidesBoundaries_DEFINITION"
msgstr "ProvidesBoundaries"
#:IFC.xml:27497
msgid "IfcElement_Tag"
msgstr "Tag"
msgid "IfcElement_Tag_DEFINITION"
msgstr "Tag"
#:IFC.xml:27670
msgid "IfcElementAssembly"
msgstr "IfcElementAssembly"
msgid "IfcElementAssembly_DEFINITION"
msgstr "The [[IfcElementAssembly]] represents complex element assemblies aggregated from several elements, such as discrete elements, building elements, or other elements. EXAMPLE Steel construction assemblies, such as trusses and different kinds of frames, can be represented by the [[IfcElementAssembly]] entity. Other examples include slab fields aggregated from a number of precast concrete slabs or reinforcement units made from several reinforcement bars. Also bathroom units, staircase sections and other premanufactured or precast elements are examples of the general [[IfcElementAssembly]] entity NOTE The [[IfcElementAssembly]] is a general purpose entity that is required to be decomposed. Also other subtypes of [[IfcElement]] can be decomposed. REMOVE with some dedicated entities such as [[IfcWallElementedCase]] and [[IfcSlabElementedCase]] . The assembly structure can be nested, i.e. an [[IfcElementAssembly]] could be an aggregated part within another [[IfcElementAssembly]]. NOTE View definitions and or implementer agreements may restrict the number of allowed levels of nesting. The geometry of an [[IfcElementAssembly]] is generally formed from its components, in which case it does not need to have an explicit geometric representation. In some cases it may be useful to also expose an own explicit representation of the aggregate. NOTE View definitions or implementer agreements may further constrain the applicability of certain shape representations at the [[IfcElementAssembly]] in respect of the shape representations of its parts. HISTORY New entity in IFC2x2. Informal Propositions The [[IfcElementAssembly]] shall have an aggregation relationship to the contained parts, i.e. the INV IsDecomposedBy relationship shall be utilized. bSI Documentation"
#:IFC.xml:27679
msgid "IfcElementAssembly_AssemblyPlace"
msgstr "AssemblyPlace"
msgid "IfcElementAssembly_AssemblyPlace_DEFINITION"
msgstr "A designation of where the assembly is intended to take place defined by an Enum."
#:IFC.xml:27684
msgid "IfcElementAssembly_PredefinedType"
msgstr "PredefinedType"
msgid "IfcElementAssembly_PredefinedType_DEFINITION"
msgstr "PredefinedType"
#:IFC.xml:27703
msgid "IfcElementAssemblyType"
msgstr "IfcElementAssemblyType"
msgid "IfcElementAssemblyType_DEFINITION"
msgstr "The [[IfcElementAssemblyType]] defines a list of commonly shared property set definitions of an element and an optional set of product representations. It is used to define an element specification i.e. the specific product information, that is common to all occurrences of that product type . NOTE The product representations are defined as representation maps at the level of the supertype [[IfcTypeProduct]] , which gets assigned by an element occurrence instance through the [[IfcShapeRepresentation]].Item 1 being an [[IfcMappedItem]]. An element assembly type is used to define the common properties of a certain type of an element assembly that may be applied to many instances of that type to assign a specific style. An element assembly types or the instantiable subtypes may be exchanged without being already assigned to occurrences. The occurrences of the [[IfcElementAssemblyType]] are represented by instances of [[IfcElementAssembly]]. HISTORY S New entity in IFC4. bSI Documentation"
#:IFC.xml:27708
msgid "IfcElementAssemblyType_PredefinedType"
msgstr "PredefinedType"
msgid "IfcElementAssemblyType_PredefinedType_DEFINITION"
msgstr "PredefinedType"
#:IFC.xml:27727
msgid "IfcElementAssemblyTypeEnum"
msgstr "IfcElementAssemblyTypeEnum"
msgid "IfcElementAssemblyTypeEnum_DEFINITION"
msgstr "This enumeration defines the basic configuration types for element assemblies. HISTORY New enumeration in IFC2x2. bSI Documentation"
#:IFC.xml:27771
msgid "IfcElementAssemblyTypeEnum_GIRDER"
msgstr "GIRDER"
msgid "IfcElementAssemblyTypeEnum_GIRDER_DEFINITION"
msgstr "GIRDER"
#:IFC.xml:27760
msgid "IfcElementAssemblyTypeEnum_SIGNALASSEMBLY"
msgstr "SIGNALASSEMBLY"
msgid "IfcElementAssemblyTypeEnum_SIGNALASSEMBLY_DEFINITION"
msgstr "An assembly to physically aggregate together one or more signal instances and also sign instances including any supporting structural elements such as a simple pole or a rigid frame gantry."
#:IFC.xml:27775
msgid "IfcElementAssemblyTypeEnum_RIGID_FRAME"
msgstr "RIGID FRAME"
msgid "IfcElementAssemblyTypeEnum_RIGID_FRAME_DEFINITION"
msgstr "A structure built up of beams, columns, etc. with moment resisting joints, such as gantry."
#:IFC.xml:27772
msgid "IfcElementAssemblyTypeEnum_PIER"
msgstr "PIER"
msgid "IfcElementAssemblyTypeEnum_PIER_DEFINITION"
msgstr "PIER"
#:IFC.xml:27279
msgid "IfcElementAssemblyTypeEnum_GRID"
msgstr "GRID"
msgid "IfcElementAssemblyTypeEnum_GRID_DEFINITION"
msgstr "A framework of spaced cables or bars that are parallel to or cross each other."
#:IFC.xml:27783
msgid "IfcElementAssemblyTypeEnum_TRAFFIC_CALMING_DEVICE"
msgstr "TRAFFIC CALMING DEVICE"
msgid "IfcElementAssemblyTypeEnum_TRAFFIC_CALMING_DEVICE_DEFINITION"
msgstr "A structure on the carriageway to control the speed of vehicles. NOTE Definition from ISO 6707 1 Encouragement of restrained and considerate behaviour by means such as road humps and reductions in width of the travelled way US traffic restraint, UK speed bump . NOTE Definition from PIARC Local carriageway layout staggered section, choker or physical device central island, round or flat top road hump, speed bump, rumble strips, etc. to control the speed of road vehicles."
#:IFC.xml:27779
msgid "IfcElementAssemblyTypeEnum_SLAB_FIELD"
msgstr "SLAB FIELD"
msgid "IfcElementAssemblyTypeEnum_SLAB_FIELD_DEFINITION"
msgstr "Slabs, laid out in one plane."
#:IFC.xml:27766
msgid "IfcElementAssemblyTypeEnum_ARCH"
msgstr "ARCH"
msgid "IfcElementAssemblyTypeEnum_ARCH_DEFINITION"
msgstr "A curved structure."
#:IFC.xml:27395
msgid "IfcElementAssemblyTypeEnum_TURNOUTPANEL"
msgstr "TURNOUTPANEL"
msgid "IfcElementAssemblyTypeEnum_TURNOUTPANEL_DEFINITION"
msgstr "Trackwork ensuring the support and guidance of a vehicle along any given route among various diverging or intersecting tracks. Note definition from NF EN 13232 1 2004."
#:IFC.xml:27767
msgid "IfcElementAssemblyTypeEnum_BEAM_GRID"
msgstr "BEAM GRID"
msgid "IfcElementAssemblyTypeEnum_BEAM_GRID_DEFINITION"
msgstr "Interconnected beams, located in one typically horizontal plane."
#:IFC.xml:27774
msgid "IfcElementAssemblyTypeEnum_REINFORCEMENT_UNIT"
msgstr "REINFORCEMENT UNIT"
msgid "IfcElementAssemblyTypeEnum_REINFORCEMENT_UNIT_DEFINITION"
msgstr "Assembled reinforcement elements."
#:IFC.xml:27769
msgid "IfcElementAssemblyTypeEnum_CROSS_BRACING"
msgstr "CROSS BRACING"
msgid "IfcElementAssemblyTypeEnum_CROSS_BRACING_DEFINITION"
msgstr "A Structural linear member or assembly of memebrs inside a box girder or between girders, typically on a pier, to resist lateral forces and transfer them to the support."
#:IFC.xml:27282
msgid "IfcElementAssemblyTypeEnum_SHELTER"
msgstr "SHELTER"
msgid "IfcElementAssemblyTypeEnum_SHELTER_DEFINITION"
msgstr "A structure, fairly quick to setup, move or dismantle, used to give protection, especially from the weather or intrusion."
#:IFC.xml:27357
msgid "IfcElementAssemblyTypeEnum_SUSPENSIONASSEMBLY"
msgstr "SUSPENSIONASSEMBLY"
msgid "IfcElementAssemblyTypeEnum_SUSPENSIONASSEMBLY_DEFINITION"
msgstr "A complex assembly of components used to suspend elements or cable segments."
#:IFC.xml:27377
msgid "IfcElementAssemblyTypeEnum_TRACTION_SWITCHING_ASSEMBLY"
msgstr "TRACTION SWITCHING ASSEMBLY"
msgid "IfcElementAssemblyTypeEnum_TRACTION_SWITCHING_ASSEMBLY_DEFINITION"
msgstr "A common assembly used to insure the switching function. It is composed of switches, control instruments and other components."
#:IFC.xml:27756
msgid "IfcElementAssemblyTypeEnum_MAST"
msgstr "MAST"
msgid "IfcElementAssemblyTypeEnum_MAST_DEFINITION"
msgstr "An assembly of plates, members, cables or fasteners that form a vertical structure for the support or mounting of other equipment such as lights, sonar or wireless transmitters."
#:IFC.xml:27768
msgid "IfcElementAssemblyTypeEnum_BRACED_FRAME"
msgstr "BRACED FRAME"
msgid "IfcElementAssemblyTypeEnum_BRACED_FRAME_DEFINITION"
msgstr "A rigid frame with additional bracing members."
#:IFC.xml:27399
msgid "IfcElementAssemblyTypeEnum_RAIL_MECHANICAL_EQUIPMENT_ASSEMBLY"
msgstr "RAIL MECHANICAL EQUIPMENT ASSEMBLY"
msgid "IfcElementAssemblyTypeEnum_RAIL_MECHANICAL_EQUIPMENT_ASSEMBLY_DEFINITION"
msgstr "A complex assembly made up of several components like blocking device, speed regulator, bias loaded inspector, track scale or controllable retarder."
#:IFC.xml:27781
msgid "IfcElementAssemblyTypeEnum_SUMPBUSTER"
msgstr "SUMPBUSTER"
msgid "IfcElementAssemblyTypeEnum_SUMPBUSTER_DEFINITION"
msgstr "An obstacle with oil catchment basin installed typically in a bus lane to prevent other traffic with lower ground clearance from using it. Also Sump breaker or Sump trap."
#:IFC.xml:27284
msgid "IfcElementAssemblyTypeEnum_SUPPORTINGASSEMBLY"
msgstr "SUPPORTINGASSEMBLY"
msgid "IfcElementAssemblyTypeEnum_SUPPORTINGASSEMBLY_DEFINITION"
msgstr "An assembly intends to support Overhead Contact Line System. It includes foundation, supporting elements and suspension assembly."
#:IFC.xml:27278
msgid "IfcElementAssemblyTypeEnum_ENTRANCEWORKS"
msgstr "ENTRANCEWORKS"
msgid "IfcElementAssemblyTypeEnum_ENTRANCEWORKS_DEFINITION"
msgstr "An assembly forming the support structure of a chamber lock, dock gate and associated elements, plus the containment of operational equipment."
#:IFC.xml:27780
msgid "IfcElementAssemblyTypeEnum_TRUSS"
msgstr "TRUSS"
msgid "IfcElementAssemblyTypeEnum_TRUSS_DEFINITION"
msgstr "TRUSS"
#:IFC.xml:27765
msgid "IfcElementAssemblyTypeEnum_ACCESSORY_ASSEMBLY"
msgstr "ACCESSORY ASSEMBLY"
msgid "IfcElementAssemblyTypeEnum_ACCESSORY_ASSEMBLY_DEFINITION"
msgstr "Assembled accessories or components."
#:IFC.xml:27397
msgid "IfcElementAssemblyTypeEnum_DILATATIONPANEL"
msgstr "DILATATIONPANEL"
msgid "IfcElementAssemblyTypeEnum_DILATATIONPANEL_DEFINITION"
msgstr "Device which permits longitudinal relative rail movement of two adjacent rails, while maintaining correct guidance and support. Note definition from NF EN 13232 1 2004."
#:IFC.xml:27773
msgid "IfcElementAssemblyTypeEnum_PYLON"
msgstr "PYLON"
msgid "IfcElementAssemblyTypeEnum_PYLON_DEFINITION"
msgstr "PYLON"
#:IFC.xml:27770
msgid "IfcElementAssemblyTypeEnum_DECK"
msgstr "DECK"
msgid "IfcElementAssemblyTypeEnum_DECK_DEFINITION"
msgstr "DECK"
#:IFC.xml:27382
msgid "IfcElementAssemblyTypeEnum_TRACKPANEL"
msgstr "TRACKPANEL"
msgid "IfcElementAssemblyTypeEnum_TRACKPANEL_DEFINITION"
msgstr "Trackwork ensuring the support and guidance of a vehicle along a route. It consists of assembly of rail, sleepers and fastenings."
#:IFC.xml:27764
msgid "IfcElementAssemblyTypeEnum_ABUTMENT"
msgstr "ABUTMENT"
msgid "IfcElementAssemblyTypeEnum_ABUTMENT_DEFINITION"
msgstr "ABUTMENT"
#:IFC.xml:27785
msgid "IfcElementCompositionEnum"
msgstr "IfcElementCompositionEnum"
msgid "IfcElementCompositionEnum_DEFINITION"
msgstr "This enumeration indicates the composition of a spatial structure element or proxy. HISTORY New enumeration in IFC2x bSI Documentation"
#:IFC.xml:27790
msgid "IfcElementQuantity"
msgstr "IfcElementQuantity"
msgid "IfcElementQuantity_DEFINITION"
msgstr "An [[IfcElementQuantity]] defines a set of derived measures of an element s physical property. Elements could be spatial structure elements like buildings, storeys, or spaces or building elements like walls, slabs, finishes . The [[IfcElementQuantity]] gets assigned to the element by using the [[IfcRelDefinesByProperties]] relationship. The optional MethodOfMeasurement attribute defines the code, e.g. from a standard method of measurement, which had been used to calculate the element quantity. NOTE The recognizable values for the name and the method of measurement attributes have to be agreed upon in further agreement documents, such as implementers agreements. Some of these agreements might be limited to a certain region, to which the method of measurement applies. The name attribute, given at the individual Quantities provides a recognizable semantic meaning of the element quantity. Both information is needed to establish a precise meaning for the measure value. An optional description may be assigned to each of the Quantities . All quantities assigned by a single instance of [[IfcElementQuantity]] are deemed to have been generated according to the same method of measurement. However several instances of [[IfcElementQuantity]] are assignable to an element, thus allowing for an element having quantities generated according to several methods of measurement. EXAMPLE To exchange the net floor area of spaces in the German region as [[IfcSpace]] , the name might be Netto Grundfläche net floor area , and the method of measurement might be accordingly DIN277 2 German industry norm no. 277 edition 2 . EXAMPLE The same instance of [[IfcSpace]] may have a different area measure assigned in the German region according to a housing regulation, the name would be Wohnfläche and the method of measurement would be 2.BV . It would be attached to the [[IfcSpace]] by a separate [[IfcRelDefinesByProperties]] relationship. The [[IfcElementQuantity]] can have the following subtypes of [[IfcPhysicalQuantity]] within its SET of Quantities , which count for the basis measure types used count measure weight measure length measure area measure volume measure time measure Base quantities are quantity definitions that are independent of a particular method of measurement and therefore internationally applicable. Base quantities are defined as gross and net values and provided by measurement of the correct geometric shape representation of the element. This specification includes a set of base quantity definition. See each subtype of [[IfcElement]] for applicable base quantities. The following general agreements apply for each base quantity set [[IfcElementQuantity]].Name [[IfcElementQuantity]].MethodOfMeasurement BaseQuantities [[IfcElementQuantity]].Quantities SET of subtypes of [[IfcPhysicalSimpleQuantity]] with values for the Name attribute as published as part of this specifciation. HISTORY New entity in IFC2x. .change ifc2x4 IFC4 CHANGE Subtyped from new intermediate [[IfcQuantitySet]] supertype. bSI Documentation"
#:IFC.xml:27802
msgid "IfcElementQuantity_Quantities"
msgstr "Quantities"
msgid "IfcElementQuantity_Quantities_DEFINITION"
msgstr "Quantities"
#:IFC.xml:27795
msgid "IfcElementQuantity_MethodOfMeasurement"
msgstr "MethodOfMeasurement"
msgid "IfcElementQuantity_MethodOfMeasurement_DEFINITION"
msgstr "Name of the method of measurement used to calculate the element quantity. The method of measurement attribute has to be made recognizable by further agreements. X 0D X 0D .change ifc2x2 X 0D IFC2x2 Addendum 1 change The attribute has been changed to be optional"
#:IFC.xml:27814
msgid "IfcElementType"
msgstr "IfcElementType"
msgid "IfcElementType_DEFINITION"
msgstr "[[IfcElementType]] defines a list of commonly shared property set definitions of an element and an optional set of product representations. It is used to define an element specification i.e. the specific product information, that is common to all occurrences of that product type . NOTE The product representations are defined as representation maps at the level of the supertype [[IfcTypeProduct]] , which gets assigned by an element instance through the [[IfcShapeRepresentation]].Item 1 being an [[IfcMappedItem]] . An element type is used to define the common properties of a certain type or style of an element that may be applied to instances of that element type to assign a specific style. Element types the instantiable subtypes may be exchanged without being already assigned to occurrences. HISTORY New entity in IFC2x2 bSI Documentation"
#:IFC.xml:27815
msgid "IfcElementType_ElementType"
msgstr "ElementType"
msgid "IfcElementType_ElementType_DEFINITION"
msgstr "The type denotes a particular type that indicates the object further. The use has to be established at the level of instantiable subtypes. In particular it holds the user defined type, if the enumeration of the attribute PredefinedType is set to USERDEFINED."
#:IFC.xml:27822
msgid "IfcExternalSpatialElement"
msgstr "IfcExternalSpatialElement"
msgid "IfcExternalSpatialElement_DEFINITION"
msgstr "The external spatial element defines external regions at the building site. Those regions can be defined logically for example, an instance of [[IfcExternalSpatialElement]] could represent the air space around the building without having an own shape representation, or physically for example, an instance of [[IfcExternalSpatialElement]] could represent the sloping ground around the building to identify the part of the external building envelop that is below ground. HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:27825
msgid "IfcExternalSpatialElement_PredefinedType"
msgstr "PredefinedType"
msgid "IfcExternalSpatialElement_PredefinedType_DEFINITION"
msgstr "PredefinedType"
#:IFC.xml:27838
msgid "IfcExternalSpatialElement_BoundedBy"
msgstr "BoundedBy"
msgid "IfcExternalSpatialElement_BoundedBy_DEFINITION"
msgstr "BoundedBy"
#:IFC.xml:27850
msgid "IfcExternalSpatialElementTypeEnum"
msgstr "IfcExternalSpatialElementTypeEnum"
msgid "IfcExternalSpatialElementTypeEnum_DEFINITION"
msgstr "This enumeration defines the different types of external spatial elements. HISTORY New enumeration in IFC4. bSI Documentation"
#:IFC.xml:27856
msgid "IfcExternalSpatialElementTypeEnum_EXTERNAL_EARTH"
msgstr "EXTERNAL EARTH"
msgid "IfcExternalSpatialElementTypeEnum_EXTERNAL_EARTH_DEFINITION"
msgstr "EXTERNAL EARTH"
#:IFC.xml:27855
msgid "IfcExternalSpatialElementTypeEnum_EXTERNAL"
msgstr "EXTERNAL"
msgid "IfcExternalSpatialElementTypeEnum_EXTERNAL_DEFINITION"
msgstr "EXTERNAL"
#:IFC.xml:27858
msgid "IfcExternalSpatialElementTypeEnum_EXTERNAL_WATER"
msgstr "EXTERNAL WATER"
msgid "IfcExternalSpatialElementTypeEnum_EXTERNAL_WATER_DEFINITION"
msgstr "EXTERNAL WATER"
#:IFC.xml:27857
msgid "IfcExternalSpatialElementTypeEnum_EXTERNAL_FIRE"
msgstr "EXTERNAL FIRE"
msgid "IfcExternalSpatialElementTypeEnum_EXTERNAL_FIRE_DEFINITION"
msgstr "EXTERNAL FIRE"
#:IFC.xml:27859
msgid "IfcExternalSpatialStructureElement"
msgstr "IfcExternalSpatialStructureElement"
msgid "IfcExternalSpatialStructureElement_DEFINITION"
msgstr "The external spatial structure element is an abstract entity provided for different kind of external spaces, regions, and volumes. HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:27862
msgid "IfcFacility"
msgstr "IfcFacility"
msgid "IfcFacility_DEFINITION"
msgstr "A Facility derived from SpatialStructureElement may be an [[IfcBuilding]], an [[IfcBridge]], an [[IfcRailway]], an [[IfcRoad]], an [[IfcMarineFacility]] or any other type of built facility defined in the future, such as REMOVE [[IfcRoad]], [[IfcRailway]] and IfcTunnel . bSI Documentation"
#:IFC.xml:27867
msgid "IfcFacilityPart"
msgstr "IfcFacilityPart"
msgid "IfcFacilityPart_DEFINITION"
msgstr "[[IfcFacilityPart]] provides for spatial breakdown of built facilities. It may be further specialised according to the type of facility being broken down. bSI Documentation"
#:IFC.xml:27868
msgid "IfcFacilityPart_PredefinedType"
msgstr "PredefinedType"
msgid "IfcFacilityPart_PredefinedType_DEFINITION"
msgstr "PredefinedType"
#:IFC.xml:27873
msgid "IfcFacilityPart_UsageType"
msgstr "UsageType"
msgid "IfcFacilityPart_UsageType_DEFINITION"
msgstr "UsageType"
#:IFC.xml:27904
msgid "IfcFeatureElement"
msgstr "IfcFeatureElement"
msgid "IfcFeatureElement_DEFINITION"
msgstr "A feature element is a generalization of all existence dependent elements which modify the shape and appearance of the associated master element. The [[IfcFeatureElement]] offers the ability to handle shape modifiers as semantic objects within the IFC object model. NOTE The term feature has a predefined meaning in a context of feature based modeling and within steel construction work. It is introduced here in a broader sense to cover all existence dependent, but semantically described, modifiers of an element s shape and appearance. It is envisioned that future releases enhance the feature based capabilities of the IFC model. In contrary to the aggregation, as used in [[IfcElementAssembly]] , that defines the aggregate as a container element, that has equally treated parts, the feature concept introduced by [[IfcFeatureElement]] defines the master element with subordinate parts as additions, or with voids or cut outs as subtractions. HISTORY New entity in IFC2x2. .change ifc2x2 IFC2x2 CHANGE The entity is introduced as an upward compatible extension of the IFC2x platform. It is an intermediate abstract supertype without defining its own explicit attributes. bSI Documentation"
#:IFC.xml:27907
msgid "IfcFeatureElementAddition"
msgstr "IfcFeatureElementAddition"
msgid "IfcFeatureElementAddition_DEFINITION"
msgstr "A feature element addition is a specialization of the general feature element, that represents an existence dependent element which modifies the shape and appearance of the associated master element. The [[IfcFeatureElementAddition]] offers the ability to handle shape modifiers as semantic objects within the IFC object model that add to the shape of the master element. The [[IfcFeatureElementAddition]] is associated to its master element by virtue of the objectified relationship [[IfcRelProjectsElement]] . This relationship implies a Boolean union operation between the shape of the master element and the shape of the addition feature. The local placement for [[IfcFeatureElementAddition]] is defined in its supertype [[IfcProduct]] . It is defined by the [[IfcLocalPlacement]] , which defines the local coordinate system that is referenced by all geometric representations. The local placement is always defined in relation to the local placement of the element to which the feature element is added The PlacementRelTo relationship of [[IfcLocalPlacement]] shall point to the local placement of the same [[IfcElement]] , which is used in the HasAdditionFeature.RelatingElement inverse attribute. HISTORY New entity in IFC2x2. .change ifc2x2 IFC2x2 CHANGE The entity is introduced as an upward compatible extension of the IFC2x platform. It is an intermediate abstract supertype without defining its own explicit attributes. bSI Documentation"
#:IFC.xml:27910
msgid "IfcFeatureElementAddition_ProjectsElements"
msgstr "ProjectsElements"
msgid "IfcFeatureElementAddition_ProjectsElements_DEFINITION"
msgstr "ProjectsElements"
#:IFC.xml:27924
msgid "IfcFeatureElementSubtraction"
msgstr "IfcFeatureElementSubtraction"
msgid "IfcFeatureElementSubtraction_DEFINITION"
msgstr "The [[IfcFeatureElementSubtraction]] is specialization of the general feature element, that represents an existence dependent elements which modifies the shape and appearance of the associated master element. The [[IfcFeatureElementSubtraction]] offers the ability to handle shape modifiers as semantic objects within the IFC object model that subtract from the shape of the master element. NOTE A single subtraction feature such as the subtype [[IfcOpeningElement]] is assigned by a single subtraction relationship [[IfcRelVoidsElement]] to one occurrences of [[IfcElement]] . It establishes a 1 1 relationship between the opening and the element. An element may have several [[IfcRelVoidsElement]] relationships, enabling several voids. The voiding relationship between a master element and a subtraction feature is geometrically resolved by a Boolean difference operation. The local placement for [[IfcFeatureElementSubtraction]] is defined in its supertype [[IfcProduct]] . It is defined by the [[IfcLocalPlacement]] , which defines the local coordinate system that is referenced by all geometric representations. The local placement is always defined in relation to the local placement of the building element from which the feature element substration is substracted The PlacementRelTo relationship of [[IfcLocalPlacement]] shall point if given to the local placement of the same [[IfcElement]] , which is used in the VoidsElements.RelatingElement inverse attribute. HISTORY New entity in IFC2x2. .change ifc2x2 IFC2x2 CHANGE The entity is introduced as an upward compatible extension of the IFC2x platform. It is an intermediate abstract supertype without defining its own explicit attributes. bSI Documentation"
#:IFC.xml:27935
msgid "IfcFeatureElementSubtraction_VoidsElements"
msgstr "VoidsElements"
msgid "IfcFeatureElementSubtraction_VoidsElements_DEFINITION"
msgstr "VoidsElements"
#:IFC.xml:27949
msgid "IfcFurnishingElement"
msgstr "IfcFurnishingElement"
msgid "IfcFurnishingElement_DEFINITION"
msgstr "A furnishing element is a generalization of all furniture related objects. Furnishing objects are characterized as being pre manufactured and assembled on site, or manufactured on site built in Thus furnishing elements can either be movable, or not as the built ins . HISTORY New entity in IFC2x. .change ifc2x4 IFC4 CHANGE The entity is marked as deprecated for instantiation will be made ABSTRACT after IFC4. bSI Documentation"
#:IFC.xml:27952
msgid "IfcFurnishingElementType"
msgstr "IfcFurnishingElementType"
msgid "IfcFurnishingElementType_DEFINITION"
msgstr "[[IfcFurnishingElementType]] defines a list of commonly shared property set definitions of an element and an optional set of product representations. It is used to define an element specification the specific product information, that is common to all occurrences of that product type . NOTE The product representations are defined as representation maps at the level of the supertype [[IfcTypeProduct]] , which gets assigned by an element occurrence instance through the [[IfcShapeRepresentation]].Item 1 being an [[IfcMappedItem]] . A furnishing element type is used to define the common properties of a certain type of a furnishing element that may be applied to many instances of that feature type to assign a specific style. Furnishing element types or the instantiable subtypes may be exchanged without being already assigned to occurrences. The occurrences of the [[IfcFurnishingElementType]] are represented by instances of [[IfcFurnishingElement]] or its subtypes . HISTORY S New entity in IFC2x2. .change ifc2x3 IFC2x3 CHANGE The entity has been made non abstract .change ifc2x4 IFC4 CHANGE The entity is marked as deprecated for instantiation will be made ABSTRACT after IFC4. bSI Documentation"
#:IFC.xml:27955
msgid "IfcGeographicElement"
msgstr "IfcGeographicElement"
msgid "IfcGeographicElement_DEFINITION"
msgstr "An [[IfcGeographicElement]] is a generalization of all elements within a geographical landscape. It includes occurrences of typical geographical elements, often referred to as features, such as trees or terrain. Common type information behind several occurrences of [[IfcGeographicElement]] is provided by the [[IfcGeographicElementType]] . REMOVE NOTE Roads are now represented by [[IfcCivilElement]] . HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:27964
msgid "IfcGeographicElement_PredefinedType"
msgstr "PredefinedType"
msgid "IfcGeographicElement_PredefinedType_DEFINITION"
msgstr "PredefinedType"
#:IFC.xml:27983
msgid "IfcGeographicElementType"
msgstr "IfcGeographicElementType"
msgid "IfcGeographicElementType_DEFINITION"
msgstr "An [[IfcGeographicElementType]] is used to define an element specification of a geographic element i.e. the specific product information, that is common to all occurrences of that product type . Geographic element types include for different types of element that may be used to represent information within a geographical landscape external to a building. Within the world of geographic information they are referred to generally as features . [[IfcGeographicElementType]] s include point features such as seating, bus shelters, signage, trees linear features such as layby s area features such as ponds, lakes, woods and forests drainage such as catchment, reserver or outfall. The specification of the specific types are given by the inherited attribute [[IfcElementType]].ElementType given as an [[IfcLabel]] . Geographic element types are frequently identified in feature catalogs that are produced for particular purposes. The [[IfcGeographicElementType]] entity enables the continued use of existing feature catalogs through capture of their identity and attributes. Information from feature catalogs might be captured in various ways via property sets, some of which will be specifically defined within the IFC property set catalog whilst others will be created for local use this is the form of capture that is expected to be most widely used through use of the IFC classification model whereby features might be identified through an [[IfcClassificationReference]] with additional description in which case, any further attributes required would still need to be captured in property sets. NOTE This is due to the range of choices of element type thyat are available and their expression in different languages. It is not considered possible to create a reasonably full list of types within an enumeration. It is suggested that selection of the relevant type be drawn from an available feature catalog . HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:27988
msgid "IfcGeographicElementType_PredefinedType"
msgstr "PredefinedType"
msgid "IfcGeographicElementType_PredefinedType_DEFINITION"
msgstr "PredefinedType"
#:IFC.xml:28007
msgid "IfcGeographicElementTypeEnum"
msgstr "IfcGeographicElementTypeEnum"
msgid "IfcGeographicElementTypeEnum_DEFINITION"
msgstr "This enumeration defines the different predefined types of geographic elements that can further specify an [[IfcGeographicElement]] or an [[IfcGeographicElementType]] . NOTE Cuurently no other predefined types beside terrain are defined. HISTORY New enumeration in IFC2x2. bSI Documentation"
#:IFC.xml:28010
msgid "IfcGeographicElementTypeEnum_SOIL_BORING_POINT"
msgstr "SOIL BORING POINT"
msgid "IfcGeographicElementTypeEnum_SOIL_BORING_POINT_DEFINITION"
msgstr ""
#:IFC.xml:28011
msgid "IfcGeographicElementTypeEnum_TERRAIN"
msgstr "TERRAIN"
msgid "IfcGeographicElementTypeEnum_TERRAIN_DEFINITION"
msgstr ""
#:IFC.xml:28012
msgid "IfcGrid"
msgstr "IfcGrid"
msgid "IfcGrid_DEFINITION"
msgstr "[[IfcGrid]] ia a planar design grid defined in 3D space used as an aid in locating structural and design elements. The position of the grid ObjectPlacement is defined by a 3D coordinate system and thereby the design grid can be used in plan, section or in any position relative to the world coordinate system . The position can be relative to the object placement of other products or grids. The XY plane of the 3D coordinate system is used to place the grid axes, which are 2D curves for example, line, circle, arc, polyline . The inherited attributes Name and Description can be used to define a descriptive name of the grid and to indicate the grid s purpose. A grid is defined by normally two, or in case of a triangular grid three lists of grid axes. The following figures shows some examples. A grid may support a rectangular layout as shown in Figure 1, a radial layout as shown in Figure 2, or a triangular layout as shown in Figure 3. NOTE The PredefinedType denotes the type of grid that is represented by [[IfcGrid]] . The instantiation of [[IfcGridAxis]] s has to agree to the PredefinedType , if provided. NOTE The grid axes, defined within the design grid, are those elements to which project objects will be placed relatively using the [[IfcGridPlacement]] . Figure 1 Grid rectangular layout Figure 2 Grid radial layout Figure 3 Grid triangular layout HISTORY New entity in IFC1.0. .change ifc2x4 IFC4 CHANGE The attribute PredefinedType has been added at the end of the attribute list. .spec head Informal Propositions Grid axes, which are referenced in different lists of axes UAxes, VAxes, WAxes shall not be parallel. Grid axes should be defined such as there are no two grid axes which intersect twice see Figure 189 . NOTE Left side ambiguous intersections A1 and A2, a grid containing such grid axes is not a valid design grid Right side the conflict can be resolved by splitting one grid axis in a way, such as no ambiguous intersections exist. Figure 4 Grid intersections bSI Documentation"
#:IFC.xml:9643
msgid "IfcGrid_UAxes"
msgstr "UAxes"
msgid "IfcGrid_UAxes_DEFINITION"
msgstr "UAxes"
#:IFC.xml:9657
msgid "IfcGrid_WAxes"
msgstr "WAxes"
msgid "IfcGrid_WAxes_DEFINITION"
msgstr "WAxes"
#:IFC.xml:9671
msgid "IfcGrid_VAxes"
msgstr "VAxes"
msgid "IfcGrid_VAxes_DEFINITION"
msgstr "VAxes"
#:IFC.xml:28015
msgid "IfcGrid_PredefinedType"
msgstr "PredefinedType"
msgid "IfcGrid_PredefinedType_DEFINITION"
msgstr "PredefinedType"
#:IFC.xml:28027
msgid "IfcGridTypeEnum"
msgstr "IfcGridTypeEnum"
msgid "IfcGridTypeEnum_DEFINITION"
msgstr "This enumeration defines the different layout types of grids. Restriction on the correct use of [[IfcGrid]] instantiations may be imposed depending on the value of the PredefinedType being [[IfcGridTypeEnum]] . HISTORY New enumeration in IFC4. NOTE View definitions or implementer agreements may impose further restrictions on how to populate the grid axes. The first grid axis being part of u axes may have to be parallel to the x axis of the grid object placement. bSI Documentation"
#:IFC.xml:28032
msgid "IfcGridTypeEnum_IRREGULAR"
msgstr "IRREGULAR"
msgid "IfcGridTypeEnum_IRREGULAR_DEFINITION"
msgstr "An [[IfcGrid]] with u axes, v axes, and optionally w axes that cannot be described by the patterns."
#:IFC.xml:28035
msgid "IfcGridTypeEnum_TRIANGULAR"
msgstr "TRIANGULAR"
msgid "IfcGridTypeEnum_TRIANGULAR_DEFINITION"
msgstr "An [[IfcGrid]] with u axes, v axes, and w axes all being co linear axis lines with a 2D offset. The v axes are at 60 degree rotated counter clockwise from the u axes, and the w axes are at 120 degree rotated counter clockwise from the u axes."
#:IFC.xml:28033
msgid "IfcGridTypeEnum_RADIAL"
msgstr "RADIAL"
msgid "IfcGridTypeEnum_RADIAL_DEFINITION"
msgstr "An [[IfcGrid]] with straight u axes and curved v axes. All grid axes being part of V axes have the same center point and are concentric circular arcs. All grid axes being part of u axes intersect at the same center point and rotate counter clockwise."
#:IFC.xml:28034
msgid "IfcGridTypeEnum_RECTANGULAR"
msgstr "RECTANGULAR"
msgid "IfcGridTypeEnum_RECTANGULAR_DEFINITION"
msgstr "RECTANGULAR"
#:IFC.xml:28036
msgid "IfcInternalOrExternalEnum"
msgstr "IfcInternalOrExternalEnum"
msgid "IfcInternalOrExternalEnum_DEFINITION"
msgstr "This enumeration defines the different types of space boundaries in terms of either being inside the building or outside the building. HISTORY New enumeration in IFC2.0 .change ifc2x4 IFC4 CHANGE Enumeration no longer applicable to [[IfcSpace]] . The following enumerators are added EXTERNAL EARTH, EXTERNAL WATER, EXTERNAL FIRE. bSI Documentation"
#:IFC.xml:28044
msgid "IfcLinearPositioningElement"
msgstr "IfcLinearPositioningElement"
msgid "IfcLinearPositioningElement_DEFINITION"
msgstr "An [[IfcLinearPositioningElement]] is an abstract entity describing positioning according to a curve. bSI Documentation"
#:IFC.xml:11299
msgid "IfcLinearPositioningElement_Axis"
msgstr "Axis"
msgid "IfcLinearPositioningElement_Axis_DEFINITION"
msgstr "Axis"
#:IFC.xml:28047
msgid "IfcOpeningElement"
msgstr "IfcOpeningElement"
msgid "IfcOpeningElement_DEFINITION"
msgstr "The opening element stands for opening, recess or chase, all reflecting voids. It represents a void within any element that has physical manifestation. Openings can be inserted into walls, slabs, beams, columns, or other elements. The IFC specification provides two entities for opening elements [[IfcOpeningStandardCase]] is used for all openings that have a constant profile along a linear extrusion. They are placed relative to the voided elements and the extrusion direction is perpendicular to the plane of the element horizontally for walls, vertically for slabs . Only a single extrusion body is allowed. It cuts through the whole thickness of the voided element, i.e. it reflects a true opening. [[IfcOpeningElement]] is used for all other occurrences of openings and in particular also for niches or recesses. NOTE View definitions or implementer agreements may restrict the types of elements which can be voided by an [[IfcOpeningElement]] or [[IfcOpeningStandardCase]] There are two different types of opening elements an opening, where the thickness of the opening is greater or equal to the thickness of the element a recess or niche, where the thickness of the recess is smaller than the thickness of the element. The attribute PredefinedType should be used to capture the differences, the attribute is set to OPENING for an opening or the attribute is set to RECESS for a recess or niche. If the value for PredefinedType is omitted, or the value is set to NOTDEFINED, no specific information of whether it is an opening or recess shall be assumed. An [[IfcOpeningElement]] has to be inserted into an [[IfcElement]] by using the [[IfcRelVoidsElement]] relationship. It may be filled by an [[IfcDoor]] , [[IfcWindow]] , or another filling element by using the relationship IfcRelFillsElements . Depending on the type of the [[IfcShapeRepresentation]] of the [[IfcOpeningElement]] the voiding relationship implies if the [[IfcShapeRepresentation]] . emRepresentationIdentifier Body , then the Body shape represntation of the opening has to be subtracted from the body shape representation of the voided element implicit Boolean difference operation. if the [[IfcShapeRepresentation]] . emRepresentationIdentifier Reference , then the Reference shape representation of the opening is not subtracted, it is provided in addition to the hole in the Body shape representation of the voided element. The [[IfcOpeningElement]] shall not participate in the containment relationship, i.e. it is not linked directly to the spatial structure of the project. It has a mandatory VoidsElements inverse relationship pointing to the [[IfcElement]] that is contained in the spatial structure. The inverse relationship ContainedInStructure shall be NIL. NOTE See [[IfcRelVoidsElement]] for a diagram on how to apply spatial containment and the voiding relationship. HISTORY New entity in IFC1.0 .change ifc2x IFC2x CHANGE The intermediate ABSTRACT supertypes [[IfcFeatureElement]] and IfcFeatureSubtraction have been added. .change ifc2x4 IFC4 CHANGE The attribute PredefinedType has been added at the end of attribute list. It should be used instead of the inherited attribute ObjectType from now on. bSI Documentation"
#:IFC.xml:28052
msgid "IfcOpeningElement_PredefinedType"
msgstr "PredefinedType"
msgid "IfcOpeningElement_PredefinedType_DEFINITION"
msgstr "PredefinedType"
#:IFC.xml:28064
msgid "IfcOpeningElement_HasFillings"
msgstr "HasFillings"
msgid "IfcOpeningElement_HasFillings_DEFINITION"
msgstr "HasFillings"
#:IFC.xml:28078
msgid "IfcOpeningElementTypeEnum"
msgstr "IfcOpeningElementTypeEnum"
msgid "IfcOpeningElementTypeEnum_DEFINITION"
msgstr "This enumeration defines the basic types for opening elements. HISTORY New enumeration type in IFC4. bSI Documentation"
#:IFC.xml:28081