forked from buildingSMART/IFC4.3.x-output
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathIfcKernel.pot
1446 lines (1035 loc) · 115 KB
/
IfcKernel.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:20050
msgid "IfcActor"
msgstr "IfcActor"
msgid "IfcActor_DEFINITION"
msgstr "The [[IfcActor]] defines all actors or human agents involved in a project during its full life cycle. It facilitates the use of person and organization definitions in the resource part of the IFC object model. This includes name, address, telecommunication addresses, and roles. HISTORY New entity in IFC2.0 bSI Documentation"
#:IFC.xml:20059
msgid "IfcActor_IsActingUpon"
msgstr "IsActingUpon"
msgid "IfcActor_IsActingUpon_DEFINITION"
msgstr "IsActingUpon"
#:IFC.xml:20051
msgid "IfcActor_TheActor"
msgstr "TheActor"
msgid "IfcActor_TheActor_DEFINITION"
msgstr "Information about the actor."
#:IFC.xml:20073
msgid "IfcComplexPropertyTemplate"
msgstr "IfcComplexPropertyTemplate"
msgid "IfcComplexPropertyTemplate_DEFINITION"
msgstr "The [[IfcComplexPropertyTemplate]] defines the template for all complex properties, either the [[IfcComplexProperty]] s, or the [[IfcPhysicalComplexQuantity]] s. The individual complex property templates are interpreted according to their Name attribute and and optional UsageName attribute. HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:20089
msgid "IfcComplexPropertyTemplate_HasPropertyTemplates"
msgstr "HasPropertyTemplates"
msgid "IfcComplexPropertyTemplate_HasPropertyTemplates_DEFINITION"
msgstr "HasPropertyTemplates"
#:IFC.xml:20103
msgid "IfcComplexPropertyTemplate_TemplateType"
msgstr "TemplateType"
msgid "IfcComplexPropertyTemplate_TemplateType_DEFINITION"
msgstr "TemplateType"
#:IFC.xml:20082
msgid "IfcComplexPropertyTemplate_UsageName"
msgstr "UsageName"
msgid "IfcComplexPropertyTemplate_UsageName_DEFINITION"
msgstr ""
#:IFC.xml:20115
msgid "IfcComplexPropertyTemplateTypeEnum"
msgstr "IfcComplexPropertyTemplateTypeEnum"
msgid "IfcComplexPropertyTemplateTypeEnum_DEFINITION"
msgstr "This enumeration defines the applicable subtype of instances of [[IfcComplexProperty]] or [[IfcPhysicalComplexQuantity]] that may be created and defined by an [[IfcComplexPropertyTemplate]] . HISTORY New enumeration in IFC4. bSI Documentation"
#:IFC.xml:21286
msgid "IfcComplexPropertyTemplateTypeEnum_Q_COMPLEX"
msgstr "Q COMPLEX"
msgid "IfcComplexPropertyTemplateTypeEnum_Q_COMPLEX_DEFINITION"
msgstr ""
#:IFC.xml:21258
msgid "IfcComplexPropertyTemplateTypeEnum_P_COMPLEX"
msgstr "P COMPLEX"
msgid "IfcComplexPropertyTemplateTypeEnum_P_COMPLEX_DEFINITION"
msgstr "the properties defined by this [[IfcComplexPropertyTemplate]] are of type [[IfcComplexProperty]] ."
#:IFC.xml:20118
msgid "IfcContext"
msgstr "IfcContext"
msgid "IfcContext_DEFINITION"
msgstr "[[IfcContext]] is the generalization of a project context in which objects, type objects, property sets, and properties are defined. The [[IfcProject]] as subtype of [[IfcContext]] provides the context for all information on a construction project, it may include one or several [[IfcProjectLibrary]] s as subtype of [[IfcContext]] to register the included libraries for the project. A library of products that is referenced is declared within the [[IfcProjectLibrary]] as the context of that library. Context definitions can be named, using the inherited Name attribute, which should be a user recognizable key or number for the context. The LongName can add a full name. Further explanations to the context can be given using the inherited Description attribute. A Context is declared by the relationship object [[IfcRelDeclares]] that refers to the corresponding objects within the context. More specific relationships are introduced at the level of subtypes. HISTORY New abstract entity in IFC4. bSI Documentation"
#:IFC.xml:20142
msgid "IfcContext_RepresentationContexts"
msgstr "RepresentationContexts"
msgid "IfcContext_RepresentationContexts_DEFINITION"
msgstr "RepresentationContexts"
#:IFC.xml:20161
msgid "IfcContext_UnitsInContext"
msgstr "UnitsInContext"
msgid "IfcContext_UnitsInContext_DEFINITION"
msgstr "UnitsInContext"
#:IFC.xml:20180
msgid "IfcContext_Declares"
msgstr "Declares"
msgid "IfcContext_Declares_DEFINITION"
msgstr "Declares"
#:IFC.xml:20194
msgid "IfcContext_IsDefinedBy"
msgstr "IsDefinedBy"
msgid "IfcContext_IsDefinedBy_DEFINITION"
msgstr "IsDefinedBy"
#:IFC.xml:20119
msgid "IfcContext_ObjectType"
msgstr "ObjectType"
msgid "IfcContext_ObjectType_DEFINITION"
msgstr "The object type denotes a particular type that indicates the object further. The use has to be established at the level of instantiable subtypes. X 0D NOTE Subtypes of [[IfcContext]] do not introduce a PredefinedType attribute, therefore the usage of ObjectType is not bound to the selection of USERDEFINED within the PredefinedType enumaration."
#:IFC.xml:20124
msgid "IfcContext_LongName"
msgstr "LongName"
msgid "IfcContext_LongName_DEFINITION"
msgstr "Long name for the context as used for reference purposes."
#:IFC.xml:20129
msgid "IfcContext_Phase"
msgstr "Phase"
msgid "IfcContext_Phase_DEFINITION"
msgstr "Current project phase, or life cycle phase of this project. Applicable values have to be agreed upon by view definitions or implementer agreements."
#:IFC.xml:20206
msgid "IfcControl"
msgstr "IfcControl"
msgid "IfcControl_DEFINITION"
msgstr "[[IfcControl]] is the abstract generalization of all concepts that control or constrain the utilization of products, processes, or resources in general. It can be seen as a regulation, cost schedule, request or order, or other requirements applied to a product, process or resource whose requirements and provisions must be fulfilled. EXAMPLE Controls include action requests, cost schedules, project orders, work plans, and work calendars. HISTORY New entity in IFC1.0. .change ifc2x4 IFC4 CHANGE Attribute Identification added. bSI Documentation"
#:IFC.xml:20214
msgid "IfcControl_Controls"
msgstr "Controls"
msgid "IfcControl_Controls_DEFINITION"
msgstr "Controls"
#:IFC.xml:20207
msgid "IfcControl_Identification"
msgstr "Identification"
msgid "IfcControl_Identification_DEFINITION"
msgstr "An identifying designation given to a control X 0D It is the identifier at the occurrence level. X 0D X 0D .change ifc2x4 X 0D IFC4 CHANGE Attribute unified by promoting from various subtypes of [[IfcControl]] ."
#:IFC.xml:20228
msgid "IfcCorrectObjectAssignment"
msgstr "IfcCorrectObjectAssignment"
msgid "IfcCorrectObjectAssignment_DEFINITION"
msgstr "This function checks, whether the correct object types are used within the [[IfcRelAssigns]] relationship or one of its subtypes . HISTORY New function in IFC2x"
#:IFC.xml:20236
msgid "IfcGroup"
msgstr "IfcGroup"
msgid "IfcGroup_DEFINITION"
msgstr "[[IfcGroup]] is an generalization of any arbitrary group. A group is a logical collection of objects. It does not have its own position, nor can it hold its own shape representation. Therefore a group is an aggregation under some non geometrical topological grouping aspects. EXAMPLE An example for a group is a system, since it groups elements under the aspect of their role, regardless of their position in a building. One of the most important usage of a group representing a system is the [[IfcDistributionSystem]] , that groups distribution components, such as space heaters and valves into a heating system. A group can hold any collection of objects, the relationship [[IfcRelAssignsToGroup]] is used to establish the group collection. Objects within a group are S products, processes, controls, resources, actors or other groups, thus groups can be nested. An object can be part of zero, one, or many groups. Grouping relationships are not required to be hierarchical nor do they imply a dependency. Groups are assigned to other objects such as a process or a resource by the relationship object that refers to the corresponding object Process assigned using [[IfcRelAssignsToProcess]] Resource assigned using [[IfcRelAssignsToResource]] Controls affecting the group using [[IfcRelAssignsToControl]] A group can be exchanged without having already objects within the group collection. [[IfcGroup]] does not define an own object coordinate system, nor does it have an independent shape representation. NOTE Use [[IfcRelAggregates]] together with the appropriate subtypes of [[IfcProduct]] to define an aggregation of products that may have its own position and shape representation. This relationship shall be used to create a product breakdown structure. HISTORY New entity in IFC1.0. .change ifc2x4 IFC4 CHANGE The inverse IsGroupedBy relationship is set to 0..n bSI Documentation"
#:IFC.xml:20241
msgid "IfcGroup_IsGroupedBy"
msgstr "IsGroupedBy"
msgid "IfcGroup_IsGroupedBy_DEFINITION"
msgstr "IsGroupedBy"
#:IFC.xml:20255
msgid "IfcObject"
msgstr "IfcObject"
msgid "IfcObject_DEFINITION"
msgstr "An [[IfcObject]] is the generalization of any semantically treated thing or process. Objects are things as they appear i.e. occurrences. NOTE Examples of [[IfcObject]] include physically tangible items such as wall, beam or covering, physically existing items such as spaces, or conceptual items such as grids or virtual boundaries. It also stands for processes such as work tasks, for controls such as cost items, or for actors such as persons involved in the design process. Objects can be named, using the inherited Name attribute, which should be a user recognizable label for the object occurrance. Further explanations to the object can be given using the inherited Description attribute. The ObjectType attribute is used to store the user defined value for all subtypes of [[IfcObject]] , where a PredefinedType attribute is given, and its value is set to USERDEFINED. to provide a type information could be seen as a very lightweight classifier of the subtype of [[IfcObject]] , if no PredefinedType attribute is given. This is often the case, if no comprehensive list of predefined types is available. Objects are independent pieces of information that might contain or reference other pieces of information. There are several relationships in which objects can be involved Association to external internal resource information an association relationship that refers to external internal sources of information. See supertype [[IfcObjectDefinition]] for more information. Assignment of other objects an assignment relationship that refers to other types of objects. See supertype [[IfcObjectDefinition]] for more information. Aggregation of other objects an aggregation relationship that establishes a whole part relation. Objects can either be a whole, or a part, or both. See supertype [[IfcObjectDefinition]] for more information. Assignment of a type IsTypedBy a definition relationship [[IfcRelDefinesByType]] that uses a type definition to define the common characteristics of this occurrences, potentially including the common shape representation and common properties of all object occurrences assigned to this type. It is a specific occurrence relationship with implied dependencies as the occurrence properties depend on the properties of the type, but may override them . Assignment of a partial type IsDeclaredBy , Declares a definition relationship [[IfcRelDefinesByObject]] that uses a component of a type definition a part of a type, called the declaring part to define a component of an occurence part of occurrence, called the reflected part . This is also refered to as a deep copy . The common characteristics of all parts in the occurrence are defined by parts in the type. It is a specific occurrence relationship with implied dependencies as the occurrence properties depend on the properties of the type, but may override them . Assignment of property sets IsDefinedBy a definition relationship [[IfcRelDefinesByProperties]] that assignes property set definitions to the object occurrence. NOTE See [[IfcRelDefinesByType]] for an explanatory figure. Also see there for how to override type properties by occurrence properties. See [[IfcRelDefinesByObject]] for an explanatory figure for the assignment of a partial type. HISTORY New entity in IFC1.0 .change ifc2x4 IFC4 CHANGE The inverse relationships Declares , IsDeclaredBy , and IsTypedBy have been added, types are not longer included in the IsDefinesBy relationship. [[IfcProject]] has been promoted to be a subtype of [[IfcObjectDefinition]] [[IfcContext]] . .spec head Informal Propositions 1. A partial type assignment, i.e. the inverse attribute IsDeclaredBy , or Declares shall only be used, if the object is part of a decomposition, i.e. if either IsDecomposedBy , or Decomposes is exerted. bSI Documentation"
#:IFC.xml:20277
msgid "IfcObject_Declares"
msgstr "Declares"
msgid "IfcObject_Declares_DEFINITION"
msgstr "Declares"
#:IFC.xml:20291
msgid "IfcObject_IsDeclaredBy"
msgstr "IsDeclaredBy"
msgid "IfcObject_IsDeclaredBy_DEFINITION"
msgstr "IsDeclaredBy"
#:IFC.xml:20305
msgid "IfcObject_IsDefinedBy"
msgstr "IsDefinedBy"
msgid "IfcObject_IsDefinedBy_DEFINITION"
msgstr "IsDefinedBy"
#:IFC.xml:20317
msgid "IfcObject_IsTypedBy"
msgstr "IsTypedBy"
msgid "IfcObject_IsTypedBy_DEFINITION"
msgstr "IsTypedBy"
#:IFC.xml:20260
msgid "IfcObject_ObjectType"
msgstr "ObjectType"
msgid "IfcObject_ObjectType_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:20331
msgid "IfcObjectDefinition"
msgstr "IfcObjectDefinition"
msgid "IfcObjectDefinition_DEFINITION"
msgstr "An [[IfcObjectDefinition]] is the generalization of any semantically treated thing or process, either being a type or an occurrences. Object defintions can be named, using the inherited Name attribute, which should be a user recognizable label for the object occurrance. Further explanations to the object can be given using the inherited Description attribute. A context is a specific kind of object definition as it provides the project or library context in which object types and object occurrences are defined. Objects are independent pieces of information that might contain or reference other pieces of information. There are four essential kinds of relationships in which object definitons by their instantiable subtypes can be involved Assignment of other objects an assignment relationship [[IfcRelAssigns]] that refers to other types of objects and creates a bi directional association. The semantic of the assignment is established at the level of the subtypes of the general [[IfcRelAssigns]] relationship. There is no dependency implied a priori by the assignment. Association to external resources an association relationship [[IfcRelAssociates]] that refers to external sources of information most notably a classification or document and creates a uni directional association. There is no dependency implied by the association. Aggregation of other objects an aggregation relationship [[IfcRelAggregates]] that establishes an unordered, spatial whole part relation and creates a bi directional relation. There is an implied dependency established. Nesting of other objects a nesting relationship [[IfcRelNests]] that establishes an ordered, non spatial whole part relation and creates a bi directional relation. There is an implied dependency established. Declaration within a context a relationship [[IfcRelDeclares]] of the uppermost object definition within the object definition tree e.g. the summary object within an object nesting tree to the context a project or project library . It applies the units, representation context and other context information to this object definition and all dependent ones. NOTE The link between the uppermost object in the spatial structure tree, that is [[IfcSite]] or ifcBuilding , and the context provided by [[IfcProject]] is created using the [[IfcRelAggregates]] relationship. See [[IfcProject]] for more information. HISTORY New abstract entity in IFC2x3. .change ifc2x4 IFC4 CHANGE The new subtype [[IfcContext]] and the relationship to context HasContext has been added . The decomposition relationship is split into ordered nesting Nests , IsNestedBy and un ordered aggregating Decomposes , IsDecomposedBy . bSI Documentation"
#:IFC.xml:20335
msgid "IfcObjectDefinition_HasAssociations"
msgstr "HasAssociations"
msgid "IfcObjectDefinition_HasAssociations_DEFINITION"
msgstr "HasAssociations"
#:IFC.xml:20347
msgid "IfcObjectDefinition_HasAssignments"
msgstr "HasAssignments"
msgid "IfcObjectDefinition_HasAssignments_DEFINITION"
msgstr "HasAssignments"
#:IFC.xml:20361
msgid "IfcObjectDefinition_IsNestedBy"
msgstr "IsNestedBy"
msgid "IfcObjectDefinition_IsNestedBy_DEFINITION"
msgstr "IsNestedBy"
#:IFC.xml:20375
msgid "IfcObjectDefinition_Nests"
msgstr "Nests"
msgid "IfcObjectDefinition_Nests_DEFINITION"
msgstr "Nests"
#:IFC.xml:20401
msgid "IfcObjectDefinition_HasContext"
msgstr "HasContext"
msgid "IfcObjectDefinition_HasContext_DEFINITION"
msgstr "HasContext"
#:IFC.xml:20413
msgid "IfcObjectDefinition_IsDecomposedBy"
msgstr "IsDecomposedBy"
msgid "IfcObjectDefinition_IsDecomposedBy_DEFINITION"
msgstr "IsDecomposedBy"
#:IFC.xml:20427
msgid "IfcObjectDefinition_Decomposes"
msgstr "Decomposes"
msgid "IfcObjectDefinition_Decomposes_DEFINITION"
msgstr "Decomposes"
#:IFC.xml:20441
msgid "IfcObjectTypeEnum"
msgstr "IfcObjectTypeEnum"
msgid "IfcObjectTypeEnum_DEFINITION"
msgstr "This enumeration defines the applicable object categories. Attached to an object, it indicates to which subtype of [[IfcObject]] the entity referencing it would otherwise comply with. HISTORY New entity in IFC1.0. .deprecated DEPRECATION The use of this enumeration is deprecated since IFC2x3. bSI Documentation"
#:IFC.xml:20451
msgid "IfcPreDefinedPropertySet"
msgstr "IfcPreDefinedPropertySet"
msgid "IfcPreDefinedPropertySet_DEFINITION"
msgstr "[[IfcPreDefinedPropertySet]] is a generalization of all statically defined property sets that are assigned to an object or type object. The statically or pre defined property sets are entities with a fixed list of attributes having particular defined data types. Property sets are related to other objects by using the relationship object that refers to the corresponding object Occurrence Object [[IfcRelDefinesByProperties]] using the inverse attribute DefinesOccurrence . Type Object using a direct link by inverse attribute DefinesType . [[IfcPreDefinedPropertySet]] s can be assigned to objects and object types but do not have a defining property set template. HISTORY New entity in IFC4 bSI Documentation"
#:IFC.xml:20454
msgid "IfcProcess"
msgstr "IfcProcess"
msgid "IfcProcess_DEFINITION"
msgstr "[[IfcProcess]] is defined as one individual activity or event, that is ordered in time, that has sequence relationships with other processes, which transforms input in output, and may connect to other other processes through input output relationships. An [[IfcProcess]] can be an activity or task , or an event. It takes usually place in building construction with the intent of designing, costing, acquiring, constructing, or maintaining products or other and similar tasks or procedures. Figure 1 illustrates process relationships. .extDef NOTE Definition according to ISO9000 A process is a set of activities that are interrelated or that interact with one another. Processes use resources to transform inputs into outputs. Processes are interconnected because the output from one process becomes the input for another process. In effect, processes are glued together by means of such input output relationships. icon diagram .. .. .. .. .. .. figures ifcprocess icon fig.png Figure 1 Process relationships and the ICON process diagram. Process information relates to other objects by establishing the following relationships Nesting of processes [[IfcRelNests]] A process can contain sub processes and thereby be nested. Sequencing of processes [[IfcRelSequence]] Processes can be placed in sequence including overlapping for parallel tasks , and have predecessors and successors. Assigning process to schedules [[IfcRelAssignsToControl]] Activities such as tasks, and predominately summary tasks, are assigned to a work schedule. Having a product assigned to the process as input [[IfcRelAssignsToProcess]] Products can be assigned as input to a process, such as for construction process planning. Having a product assigned to the process as output [[IfcRelAssignsToProduct]] Products can be assigned as output to a process, such as for construction process planning. Having a control assigned to the process as process control [[IfcRelAssignsToProcess]] Items that act as a control onto the process can be assigned to a process, such as for cost management a cost item assigned to a work task . Having a resource assigned to the process as consumed by the process [[IfcRelAssignsToProcess]] Items that act as a mechanism to a process, such as labor, material and equipment in cost calculations. HISTORY New entity in IFC1.0. .change ifc2x IFC2x CHANGE The attribute Productivity has been removed. .change ifc2x4 IFC4 CHANGE The attribute Identification has been promoted from subtypes [[IfcTask]] and others. bSI Documentation"
#:IFC.xml:20469
msgid "IfcProcess_IsSuccessorFrom"
msgstr "IsSuccessorFrom"
msgid "IfcProcess_IsSuccessorFrom_DEFINITION"
msgstr "IsSuccessorFrom"
#:IFC.xml:20483
msgid "IfcProcess_OperatesOn"
msgstr "OperatesOn"
msgid "IfcProcess_OperatesOn_DEFINITION"
msgstr "OperatesOn"
#:IFC.xml:20495
msgid "IfcProcess_IsPredecessorTo"
msgstr "IsPredecessorTo"
msgid "IfcProcess_IsPredecessorTo_DEFINITION"
msgstr "IsPredecessorTo"
#:IFC.xml:20455
msgid "IfcProcess_Identification"
msgstr "Identification"
msgid "IfcProcess_Identification_DEFINITION"
msgstr "An identifying designation given to a process or activity. X 0D It is the identifier at the occurrence level. X 0D X 0D .change ifc2x4 X 0D IFC4 CHANGE Attribute promoted from subtypes."
#:IFC.xml:20460
msgid "IfcProcess_LongDescription"
msgstr "LongDescription"
msgid "IfcProcess_LongDescription_DEFINITION"
msgstr "An extended description or narrative that may be provided. X 0D .change ifc2x4 X 0D IFC4 CHANGE New attribute."
#:IFC.xml:20509
msgid "IfcProduct"
msgstr "IfcProduct"
msgid "IfcProduct_DEFINITION"
msgstr "The [[IfcProduct]] is an abstract representation of any object that relates to a geometric or spatial context. An [[IfcProduct]] occurs at a specific location in space if it has a geometric representation assigned. It can be placed relatively to other products, but ultimately relative to the project coordinate system. The ObjectPlacement attribute establishes the coordinate system in which all points and directions used by the geometric representation items under Representation are founded. The Representation is provided by an [[IfcProductDefinitionShape]] being either a geometric shape representation, or a topology representation with or without underlying geometry of the topological items . Products include manufactured, supplied or created objects referred to as elements for incorporation into an AEC FM project. This also includes objects that are created indirectly by other products, as spaces are defined by bounding elements. Products can be designated for permanent use or temporary use, an example for the latter is formwork. Products are defined by their properties and representations. In addition to physical products covered by the subtype [[IfcElement]] and spatial items covered by the subtype [[IfcSpatialElement]] the [[IfcProduct]] also includes non physical items, that relate to a geometric or spatial contexts, such as grid, port, annotation, structural actions, etc. Any instance of [[IfcProduct]] defines a particular occurrence of a product, the common type information, that relates to many similar or identical occurrences of [[IfcProduct]] , is handled by the [[IfcTypeProduct]] and its subtypes , assigned to one or many occurrences of [[IfcProduct]] by using the objectified relationship [[IfcRelDefinesByType]] . The [[IfcTypeProduct]] may provide, in addition to common properties, also a common geometric representation for all occurrences. NOTE See [[IfcTypeProduct]] for how to use a common geometric representation and [[IfcRelDefinesByType]] for using and overriding common properties. On a generic level products can be assigned to processes, controls, resources, project by using the relationship objects that refer to the corresponding object Having a control applied assigned using [[IfcRelAssignsToControl]] linking the [[IfcProduct]] to an [[IfcControl]] Being assigned to a process assigned using [[IfcRelAssignsToProcess]] linking the [[IfcProduct]] to an [[IfcProcess]] Being assigned to a resource assigned using [[IfcRelAssignsToResource]] linking the [[IfcProduct]] to an [[IfcResource]] EXAMPLE An example of the control relationship is the assignment of a performance history to a distribution element. An example of process assignment relationship is the assignment of products like wall, slab, column to a contruction task for construction planning. And an example of resource assignment relationship is the assignment of products to a construction resource that consumes the product. HISTORY New entity in IFC1.0 bSI Documentation"
#:IFC.xml:9807
msgid "IfcProduct_ObjectPlacement"
msgstr "ObjectPlacement"
msgid "IfcProduct_ObjectPlacement_DEFINITION"
msgstr "ObjectPlacement"
#:IFC.xml:20519
msgid "IfcProduct_Representation"
msgstr "Representation"
msgid "IfcProduct_Representation_DEFINITION"
msgstr "Representation"
#:IFC.xml:20543
msgid "IfcProduct_ReferencedBy"
msgstr "ReferencedBy"
msgid "IfcProduct_ReferencedBy_DEFINITION"
msgstr "ReferencedBy"
#:IFC.xml:20555
msgid "IfcProduct_ReferencedInStructures"
msgstr "ReferencedInStructures"
msgid "IfcProduct_ReferencedInStructures_DEFINITION"
msgstr "ReferencedInStructures"
#:IFC.xml:20567
msgid "IfcProduct_PositionedRelativeTo"
msgstr "PositionedRelativeTo"
msgid "IfcProduct_PositionedRelativeTo_DEFINITION"
msgstr "PositionedRelativeTo"
#:IFC.xml:20593
msgid "IfcProject"
msgstr "IfcProject"
msgid "IfcProject_DEFINITION"
msgstr "[[IfcProject]] indicates the undertaking of some design, engineering, construction, or maintenance activities leading towards a product. The project establishes the context for information to be exchanged or shared, and it may represent a construction project but does not have to. The [[IfcProject]] s main purpose in an exchange structure is to provide the root instance and the context for all other information items included. The context provided by the [[IfcProject]] includes the default units the geometric representation context for exchange structures including shape representations the project coordinate system the coordinate space dimension the precision used within the geometric representations optionally the indication of the true north optionally the map conversion between the project coordinate system and the geospatial coordinate reference system. HISTORY New entity in IFC1.0 .change ifc2x4 IFC4 CHANGE The attributes RepresentationContexts and UnitsInContext are made optional and are promoted to supertype [[IfcContext]] . .spec head Informal Propositions 1. There shall only be one project within the exchange context. This is enforced by the global rule [[IfcSingleProjectInstance]] . bSI Documentation"
#:IFC.xml:20608
msgid "IfcProjectLibrary"
msgstr "IfcProjectLibrary"
msgid "IfcProjectLibrary_DEFINITION"
msgstr "An [[IfcProjectLibrary]] collects all library elements that are included within a referenced project data set. Examples for project libraries include type libraries also called style or family libraries a collection of subtypes of [[IfcTypeObject]] property definition libraries a collections of [[IfcPropertySetTemplate]] or IfcPropertyTemplates The inherited attributes RepresentationContext and UnitsInContext have the following meaning Context of the representations used within the project library. When the project library includes shape representations for its library type objects, one or several geometric representation contexts need to be included that define the coordinate system, the coordinate space dimensions, and or the precision factor, Units locally assigned to measure types used within the context of this project library. NOTE It is generally discouraged to use a different length measure and plane angle measure in an included project library compared with the project itself. It may lead to unexpected results for the shape representation of items included in the project library. Instances of [[IfcProjectLibrary]] are assigned to the project context using the [[IfcRelDeclares]] relationship and accessible through the inverse attribute HasContext . Individual object types and property set templates are assigned to the [[IfcProjectLibrary]] using the [[IfcRelDeclares]] relationship and are accessible through the inverse attribute Declares . An [[IfcProjectLibrary]] may be decomposed into sub libraries using the relationship [[IfcRelNests]] . Sub libraries are accessed by the [[IfcProjectLibrary]] through the inverse attribute IsNestedBy . HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:20611
msgid "IfcPropertyDefinition"
msgstr "IfcPropertyDefinition"
msgid "IfcPropertyDefinition_DEFINITION"
msgstr "[[IfcPropertyDefinition]] defines the generalization of all characteristics i.e. a grouping of individual properties , that may be assigned to objects. Currently, subtypes of [[IfcPropertyDefinition]] include property set occurrences, property set templates, and property templates. Property set template [[IfcPropertySetTemplate]] , a collection of property templates that determine the definition of properties used within a project context. Property template [[IfcPropertyTemplate]] , a single template that determines the definition of a particular property used in the same project context. The template may determine the name, description, data type, the unit, or a standard expression for each property that is based on that template. Property set occurrence [[IfcPropertySet]] , a set of individual properties that may or may not be determined by a property template holding individual values, measure types and units, and are associated to an object occurrence or object type. NOTE The subtype hierarchy of [[IfcPropertyDefinition]] also includes statically defined property sets as [[IfcPreDefinedPropertySet]] . Those are rarely used collections of fixed attributes combined in an entity definition. The [[IfcPreDefinedPropertySet]] can not be determined by an [[IfcPropertySetTemplate]] . NOTE Individual properties, subtypes of [[IfcProperty]] , are currently not included in the subtype hierarchy of [[IfcPropertyDefinition]] . This anomaly is due to upward compatibility reasons with earlier releases of this standard. Property definitions define information that is shared among multiple instances of objects, either object occurrences or object types. [[IfcPropertyDefinition]] s by their instantiable subtypes can participate within the following relationships Assignment to a project context an HasContext relationship to [[IfcRelDeclares]] that establishes the project context in which this property definition is declared. This relationship is predominately applicable to subtypes of [[IfcPropertyTemplateDefinition]] . Association to external resources an HasAssociation relationship to [[IfcRelAssociates]] that refers to external sources of information most notably a classification or document and creates a uni directional association. There is no dependency implied by the association. Subtypes are included in more specific relationships, see [[IfcPropertySetDefinition]] and [[IfcPropertyTemplateDefinition]] for details. HISTORY New entity in IFC2.0 bSI Documentation"
#:IFC.xml:20615
msgid "IfcPropertyDefinition_HasContext"
msgstr "HasContext"
msgid "IfcPropertyDefinition_HasContext_DEFINITION"
msgstr "HasContext"
#:IFC.xml:20627
msgid "IfcPropertyDefinition_HasAssociations"
msgstr "HasAssociations"
msgid "IfcPropertyDefinition_HasAssociations_DEFINITION"
msgstr "HasAssociations"
#:IFC.xml:20639
msgid "IfcPropertySet"
msgstr "IfcPropertySet"
msgid "IfcPropertySet_DEFINITION"
msgstr "The [[IfcPropertySet]] is a container that holds properties within a property tree. These properties are interpreted according to their name attribute. Each individual property has a significant name string. Some property sets are included in the specification of this standard and have a predefined set of properties indicated by assigning a significant name. These property sets are listed under property sets within this specification. Property sets applicable to certain objects are listed in the object specification. The naming convention Pset Xxx applies to all those property sets that are defined as part of this specification and it shall be used as the value of the Name attribute. In addition any user defined property set can be captured. Property sets that are not declared as part of the IFC specification shall have a Name value not including the Pset prefix. [[IfcPropertySet]] can be assigned to object occurrences and object types. An [[IfcPropertySet]] assigned to an object type is shared among all occurrences of the same object type. NOTE See [[IfcRelDefinesByType]] for how to override property sets assigned to an object type within the object occurrence. An [[IfcPropertySetTemplate]] may define the underlying structure, i.e. the required name, the applicable object or object types to which the property set can be attached, and the individual properties that can be included. Property sets are related to other objects by using the relationship object that refers to the corresponding object Occurrence Object [[IfcRelDefinesByProperties]] using the inverse attribute DefinesOccurrence . Type Object using a direct link by inverse attribute DefinesType . Underlying template [[IfcRelDefinesByTemplate]] using the inverse attribute IsDefinedBy . External reference subtypes of [[IfcRelAssociates]] are used to provide a link to a classification system, or external library providing further reference to the property set. Accessible by inverse attribute HasAssociations . HISTORY New entity in IFC1.0 .change ifc2x4 IFC4 CHANGE All statically defined property set entities are no longer subtypes of [[IfcPropertySet]] . bSI Documentation"
#:IFC.xml:20650
msgid "IfcPropertySet_HasProperties"
msgstr "HasProperties"
msgid "IfcPropertySet_HasProperties_DEFINITION"
msgstr "HasProperties"
#:IFC.xml:20664
msgid "IfcPropertySetDefinition"
msgstr "IfcPropertySetDefinition"
msgid "IfcPropertySetDefinition_DEFINITION"
msgstr "[[IfcPropertySetDefinition]] is a generalization of all individual property sets that can be assigned to an object or type object. The property set definition can be either Dynamically extendable property sets [[IfcPropertySet]] , a set of properties for which the IFC specification only provides a kind of meta model , to be further declared by agreement. This means no entity definition of the properties exists within the IFC specification. The declaration is done by assigning a significant string value to the Name attribute of the entity as defined in the entity [[IfcPropertySet]] and at each subtype of [[IfcProperty]] , referenced by the property set. Dynamically defined property sets may have an underlying template provided by [[IfcPropertySetTemplate]] . Statically defined property sets [[IfcPreDefinedPropertySet]] , a property set entity that exists within the IFC specification. The semantic meaning of each statically defined property set is declared by its entity type and the meaning of the properties is defined by the name and data type of the explicit attribute representing it. Property set definitions define information that is shared among multiple instances of objects, either object occurrences or object types. [[IfcPropertySetDefinition]] s by their instantiable subtypes can participate within the following relationships Assignment to object types an DefinesType direct relationship to [[IfcTypeObject]] that applies the property set, with all included properties, to the object type. Those properties apply to all object occurrences having the same object type. Assignment to object occurrences an DefinesOccurrence relationship to [[IfcRelDefinesByProperties]] that applies the property set, with all included properties, to the object occurrence. NOTE Properties assigned to object occurrences may override properties assigned to the object type. See [[IfcRelDefinesByType]] for further information. HISTORY New entity in IFC2x .change ifc2x4 IFC4 CHANGE The subtype [[IfcPreDefinedPropertySet]] has been added. bSI Documentation"
#:IFC.xml:20668
msgid "IfcPropertySetDefinition_DefinesType"
msgstr "DefinesType"
msgid "IfcPropertySetDefinition_DefinesType_DEFINITION"
msgstr "DefinesType"
#:IFC.xml:20682
msgid "IfcPropertySetDefinition_IsDefinedBy"
msgstr "IsDefinedBy"
msgid "IfcPropertySetDefinition_IsDefinedBy_DEFINITION"
msgstr "IsDefinedBy"
#:IFC.xml:20696
msgid "IfcPropertySetDefinition_DefinesOccurrence"
msgstr "DefinesOccurrence"
msgid "IfcPropertySetDefinition_DefinesOccurrence_DEFINITION"
msgstr "DefinesOccurrence"
#:IFC.xml:20708
msgid "IfcPropertySetTemplate"
msgstr "IfcPropertySetTemplate"
msgid "IfcPropertySetTemplate_DEFINITION"
msgstr "[[IfcPropertySetTemplate]] defines the template for all dynamically extensible property sets represented by [[IfcPropertySet]] . The property set template is a container of property templates within a property tree. The individual property templates are interpreted according to their Name attribute and shall have no values assigned. NOTE By convention an [[IfcPropertySetTemplate]] can also be used as a template for an [[IfcElementQuantity]] , being a particular type of a property set definition. Property set templates can form part of a property library used and declared within a project. Depending on the TemplateType the [[IfcPropertySetTemplate]] defines a template for Pset occurrences of [[IfcPropertySet]] QTO occurrences of [[IfcElementQuantity]] The inherited HasContext inverse relation to [[IfcRelDeclares]] is used to declare the [[IfcPropertySetTemplate]] within a project library. If included in an exchange data set it can then be traversed through the [[IfcProjectLibrary]] . The Defines inverse relation to [[IfcRelDefinesByTemplate]] is provided to keep the definition relationship between the [[IfcPropertySetTemplate]] and the one to many [[IfcPropertySet]] s, for which it provides the template. Figure 1 illustrates relationships used for property set templates. property set template .. .. .. .. .. .. figures ifcpropertysettemplate fig 1.png Figure 1 Property set template relationships Between [[IfcProperty]] s within the HasProperties set of [[IfcPropertySet]] having the same Name attribute value as the [[IfcPropertyTemplate]] s within the HasPropertyTemplates set of [[IfcPropertySetTemplate]] an implicit definition relationship is established that assigns the template to the individual properties. HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:20724
msgid "IfcPropertySetTemplate_HasPropertyTemplates"
msgstr "HasPropertyTemplates"
msgid "IfcPropertySetTemplate_HasPropertyTemplates_DEFINITION"
msgstr "HasPropertyTemplates"
#:IFC.xml:20738
msgid "IfcPropertySetTemplate_TemplateType"
msgstr "TemplateType"
msgid "IfcPropertySetTemplate_TemplateType_DEFINITION"
msgstr "TemplateType"
#:IFC.xml:20750
msgid "IfcPropertySetTemplate_Defines"
msgstr "Defines"
msgid "IfcPropertySetTemplate_Defines_DEFINITION"
msgstr "Defines"
#:IFC.xml:20717
msgid "IfcPropertySetTemplate_ApplicableEntity"
msgstr "ApplicableEntity"
msgid "IfcPropertySetTemplate_ApplicableEntity_DEFINITION"
msgstr "The attribute optionally defines the data type of the applicable type or occurrence object, to which the assigned property set template can relate. If not present, no instruction is given to which type or occurrence object the property set template is applicable. The following conventions are used X 0D The IFC entity name of the applicable entity using the IFC naming convention, CamelCase with IFC prefix X 0D It can be optionally followed by the predefined type after the separator forward slash , using upper case X 0D If a performance history object of a particular distribution object is attributes by the property set template, then the entity name and potentially amended by the predefined type is expanded by adding PerformanceHistory X 0D If one property set template is applicable to many type and or occurrence objects, then those object names should be separate by comma , forming a comma separated string. X 0D X 0D EXAMPLE Refering to a boiler type as applicable entity would be expressed as [[IfcBoilerType]] , refering to a steam boiler type as applicable entity would be expressed as [[IfcBoilerType]] STEAM , refering to a wall and wall standard case and a wall type would be expressed as [[IfcWall]], [[IfcWallStandardCase]], [[IfcWallType]] . An applicable [[IfcPerformanceHistory]] assigned to an occurrence or type object would be indicated by [[IfcBoilerType]] PerformanceHistory , or respectively [[IfcBoilerType]] STEAM PerformanceHistory ."
#:IFC.xml:20764
msgid "IfcPropertySetTemplateTypeEnum"
msgstr "IfcPropertySetTemplateTypeEnum"
msgid "IfcPropertySetTemplateTypeEnum_DEFINITION"
msgstr "This enumeration defines the general applicability of instances of [[IfcPropertySet]] , or [[IfcElementQuantity]] defined by this [[IfcPropertySetTemplate]] , to subtypes of [[IfcObjectDefinition]] . HISTORY New enumeration in IFC4. bSI Documentation"
msgid "IfcPropertySetTemplateTypeEnum_NOTDEFINED"
msgstr "NOTDEFINED"
msgid "IfcPropertySetTemplateTypeEnum_NOTDEFINED_DEFINITION"
msgstr "NOTDEFINED"
#:IFC.xml:21292
msgid "IfcPropertySetTemplateTypeEnum_QTO_OCCURRENCEDRIVEN"
msgstr "QTO OCCURRENCEDRIVEN"
msgid "IfcPropertySetTemplateTypeEnum_QTO_OCCURRENCEDRIVEN_DEFINITION"
msgstr "The element quantity defined by this [[IfcPropertySetTemplate]] can only be X 0D assigned to subtypes of [[IfcObject]] ."
#:IFC.xml:21293
msgid "IfcPropertySetTemplateTypeEnum_QTO_TYPEDRIVENONLY"
msgstr "QTO TYPEDRIVENONLY"
msgid "IfcPropertySetTemplateTypeEnum_QTO_TYPEDRIVENONLY_DEFINITION"
msgstr "The element quantity defined by this [[IfcPropertySetTemplate]] can only be assigned to subtypes of [[IfcTypeObject]] ."
#:IFC.xml:21283
msgid "IfcPropertySetTemplateTypeEnum_PSET_TYPEDRIVENONLY"
msgstr "PSET TYPEDRIVENONLY"
msgid "IfcPropertySetTemplateTypeEnum_PSET_TYPEDRIVENONLY_DEFINITION"
msgstr "The property sets defined by this [[IfcPropertySetTemplate]] can only be assigned to subtypes of [[IfcTypeObject]] ."
#:IFC.xml:21282
msgid "IfcPropertySetTemplateTypeEnum_PSET_PERFORMANCEDRIVEN"
msgstr "PSET PERFORMANCEDRIVEN"
msgid "IfcPropertySetTemplateTypeEnum_PSET_PERFORMANCEDRIVEN_DEFINITION"
msgstr "The property sets defined by this [[IfcPropertySetTemplate]] can only be assigned to [[IfcPerformanceHistory]] ."
#:IFC.xml:21281
msgid "IfcPropertySetTemplateTypeEnum_PSET_OCCURRENCEDRIVEN"
msgstr "PSET OCCURRENCEDRIVEN"
msgid "IfcPropertySetTemplateTypeEnum_PSET_OCCURRENCEDRIVEN_DEFINITION"
msgstr "The property sets defined by this [[IfcPropertySetTemplate]] can only be assigned to subtypes of [[IfcObject]] ."
#:IFC.xml:21294
msgid "IfcPropertySetTemplateTypeEnum_QTO_TYPEDRIVENOVERRIDE"
msgstr "QTO TYPEDRIVENOVERRIDE"
msgid "IfcPropertySetTemplateTypeEnum_QTO_TYPEDRIVENOVERRIDE_DEFINITION"
msgstr "The element quantity defined by this [[IfcPropertySetTemplate]] can be X 0D assigned to subtypes of [[IfcTypeObject]] and can be overridden X 0D by an element quantity with same name at subtypes of [[IfcObject]] ."
#:IFC.xml:21284
msgid "IfcPropertySetTemplateTypeEnum_PSET_TYPEDRIVENOVERRIDE"
msgstr "PSET TYPEDRIVENOVERRIDE"
msgid "IfcPropertySetTemplateTypeEnum_PSET_TYPEDRIVENOVERRIDE_DEFINITION"
msgstr "The property sets defined by this [[IfcPropertySetTemplate]] can be assigned X 0D to subtypes of [[IfcTypeObject]] and can be overridden by a X 0D property set with same name at subtypes of [[IfcObject]] ."
#:IFC.xml:20772
msgid "IfcPropertyTemplate"
msgstr "IfcPropertyTemplate"
msgid "IfcPropertyTemplate_DEFINITION"
msgstr "The [[IfcPropertyTemplate]] is an abstract supertype comprising the templates for all dynamically extensible properties, either as an [[IfcComplexPropertyTemplate]] , or an [[IfcSimplePropertyTemplate]] . These templates determine the structure of in case of [[IfcComplexPropertyTemplate]] an [[IfcComplexProperty]] an [[IfcPhysicalComplexQuantity]] in case of [[IfcSimplePropertyTemplate]] a subtype of [[IfcSimpleProperty]] a subtype of [[IfcPhysicalSimpleQuantity]] The individual property templates are interpreted according to their Name attribute and may have a predefined property type, property unit, and property data type. A template however shall not have measure values, or quantity values assigned. NOTE Property templates can form part of a property library used and attached as part of a project library. In general the [[IfcPropertySetTemplate]] , containing the subtypes of [[IfcPropertyTemplate]] would be directly linked to the [[IfcProjectLibrary]] . HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:20089
msgid "IfcPropertyTemplate_PartOfComplexTemplate"
msgstr "PartOfComplexTemplate"
msgid "IfcPropertyTemplate_PartOfComplexTemplate_DEFINITION"
msgstr "PartOfComplexTemplate"
#:IFC.xml:20724
msgid "IfcPropertyTemplate_PartOfPsetTemplate"
msgstr "PartOfPsetTemplate"
msgid "IfcPropertyTemplate_PartOfPsetTemplate_DEFINITION"
msgstr "PartOfPsetTemplate"
#:IFC.xml:20775
msgid "IfcPropertyTemplateDefinition"
msgstr "IfcPropertyTemplateDefinition"
msgid "IfcPropertyTemplateDefinition_DEFINITION"
msgstr "[[IfcPropertyTemplateDefinition]] is a generalization of all property and property set templates. Templates define the collection, types, names, applicable measure types and units of individual properties used in a project. The property template definition can be either Property set template [[IfcPropertySetTemplate]] , a collection of property templates that determine the definition of properties used within a project context. Property template [[IfcPropertyTemplate]] , a single template that determines the definition of a particular property used in the same project context. The template may determine the name, description, data type, the unit, or a standard expression for each property that is based on that template. The subtypes of [[IfcPropertyTemplateDefinition]] are declared within a project context. The uppermost template definition e.g. the [[IfcPropertySetTemplate]] including several [[IfcPropertyTemplate]] s should be related to the context, either [[IfcProject]] , or [[IfcProjectLibrary]] , using the inherited HasContext inverse attribute. HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:20778
msgid "IfcProxy"
msgstr "IfcProxy"
msgid "IfcProxy_DEFINITION"
msgstr "[[IfcProxy]] is intended to be a kind of a container for wrapping objects which are defined by associated properties, which may or may not have a geometric representation and placement in space. A proxy may have a semantic meaning, defined by the Name attribute, and property definitions, attached through the property assignment relationship, which definition may be outside of the definitions given by the current release of IFC. The ProxyType may give an indication to which high level semantic breakdown of object the semantic definition of the proxy relates to. the Tag attribute may be used to assign a human or system interpretable identifier such as a serial number or bar code . NOTE Given that only a limited number of semantic constructs can be formally defined within IFC and it will never be possible to define all , there has to be a mechanism for capturing those constructs that are not yet defined by IFC. NOTE Product proxies are a mechanism that allows to exchange data that is part of the project but not necessarily part of the IFC model. Those proxies may have geometric representations assigned. HISTORY New entity in IFC1.5. .deprecated DEPRECATION The entity is deprecated and shall not be used. bSI Documentation"
#:IFC.xml:20783
msgid "IfcProxy_ProxyType"
msgstr "ProxyType"
msgid "IfcProxy_ProxyType_DEFINITION"
msgstr "High level and only semantic meaning attached to the [[IfcProxy]], defining the basic construct type behind the Proxy, e.g. Product or Process."
#:IFC.xml:20788
msgid "IfcProxy_Tag"
msgstr "Tag"
msgid "IfcProxy_Tag_DEFINITION"
msgstr "The tag or label identifier at the particular instance of a product, e.g. the serial number, or the position number. It is the identifier at the occurrence level."
#:IFC.xml:20795
msgid "IfcQuantitySet"
msgstr "IfcQuantitySet"
msgid "IfcQuantitySet_DEFINITION"
msgstr "[[IfcQuantitySet]] is the the abstract supertype for all quantity sets attached to objects. The quantity set is a container class that holds the individual quantities within a quantity tree. These quantities are interpreted according to their name attribute and classified according to their measure type. Some quantity sets are included in the IFC specification and have a predefined set of quantities indicated by assigning a significant name. These quantity sets are listed as quantity sets within this specification. Quantity sets applicable to certain objects are listed in the object specification. An [[IfcPropertySetTemplate]] may define the underlying structure, i.e. the required name, the applicable object or object types to which the quantity set can be attached, and the individual quantities that maybe included. Quantity sets are related to other objects by using the relationship object that refers to the corresponding object Occurrence Object [[IfcRelDefinesByProperties]] using the inverse attribute DefinesOccurrence . Type Object using a direct link by inverse attribute DefinesType . Underlying template [[IfcRelDefinesByTemplate]] using the inverse attribute IsDefinedBy . External reference subtypes of [[IfcRelAssociates]] are used to provide a link to a classification system, or external library providing further reference to the quantity set. Accessible by inverse attribute HasAssociations . HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:20798
msgid "IfcRelAggregates"
msgstr "IfcRelAggregates"
msgid "IfcRelAggregates_DEFINITION"
msgstr "The aggregation relationship [[IfcRelAggregates]] is a special type of the general composition decomposition or whole part relationship [[IfcRelDecomposes]] . The aggregation relationship can be applied to all subtypes of [[IfcObjectDefinition]] . In cases of aggregation of physical elements into a physical aggregate the shape representation of the whole within the same representation identifier can be taken from the sum of the shape representations of the parts. EXAMPLE A roof is the aggregation of the roof elements, such as roof slabs, rafters, purlins, etc. Within the same representation identifier such as the body geometric representation , the shape representation of the roof is given by the shape representation of its parts. Decompositions imply a dependency, implying that the whole depends on the definition of the parts and the parts depend on the existence of the whole. The behaviour that is implied from the dependency relationship has to be established inside the applications. HISTORY New entity in IFC2x. .change ifc2x4 IFC4 CHANGE The attributes RelatingObject and RelatedObjects are demoted from the supertype [[IfcRelDecomposes]] . bSI Documentation"
#:IFC.xml:20413
msgid "IfcRelAggregates_RelatingObject"
msgstr "RelatingObject"
msgid "IfcRelAggregates_RelatingObject_DEFINITION"
msgstr "RelatingObject"
#:IFC.xml:20427
msgid "IfcRelAggregates_RelatedObjects"
msgstr "RelatedObjects"
msgid "IfcRelAggregates_RelatedObjects_DEFINITION"
msgstr "RelatedObjects"
#:IFC.xml:20805
msgid "IfcRelAssigns"
msgstr "IfcRelAssigns"
msgid "IfcRelAssigns_DEFINITION"
msgstr "The assignment relationship, [[IfcRelAssigns]] , is a generalization of link relationships among instances of [[IfcObject]] and its various 1 st level subtypes. A link denotes the specific association through which one object the client applies the services of other objects the suppliers , or through which one object may navigate to other objects. The client is denoted as the relating object and is established at the level of the specific, instantiable subtypes of [[IfcRelAssigns]] . The suppliers are denoted as the related objects and they are established by the RelatedObjects attribute. NOTE The terms client and supplier are used in a general concept and do not imply any meaning for implementations of systems like client server . EXAMPLE A resource may receive information about its nature of representing real building products by establishing a link between [[IfcResource]] and IfcBuildingElement subtype of [[IfcProduct]] through the assignment relationship [[IfcRelAssignsToResource]] . The resource is then the client that applies the services of other objects here building elements to express the particular view of elements to be consumed as a resource in a process. The assignment relationship establishs a bi directional relationship among the participating objects and does not imply any dependency. The subtypes of [[IfcRelAssigns]] establishes the particular semantic meaning of the assignment relationship. HISTORY New entity in IFC2x. bSI Documentation"
#:IFC.xml:20347
msgid "IfcRelAssigns_RelatedObjects"
msgstr "RelatedObjects"
msgid "IfcRelAssigns_RelatedObjects_DEFINITION"
msgstr "RelatedObjects"
#:IFC.xml:20810
msgid "IfcRelAssigns_RelatedObjectsType"
msgstr "RelatedObjectsType"
msgid "IfcRelAssigns_RelatedObjectsType_DEFINITION"
msgstr "Particular type of the assignment relationship. It can constrain the applicable object types, used within the role of RelatedObjects . X 0D .change ifc2x4 X 0D IFC4 CHANGE The attribute is deprecated and shall no longer be used. A NIL value should always be assigned."
#:IFC.xml:20817
msgid "IfcRelAssignsToActor"
msgstr "IfcRelAssignsToActor"
msgid "IfcRelAssignsToActor_DEFINITION"
msgstr "The objectified relationship [[IfcRelAssignsToActor]] handles the assignment of objects subtypes of [[IfcObject]] to an actor subtypes of [[IfcActor]] . The [[IfcRelAssignsToActor]] objectified relationship defines a relationship between an [[IfcActor]] and one or many objects. A particular role of the actor played in that relationship can be associated. If specified, it takes priority over the role that may be directly assigned to the person or organization. EXAMPLE An occupant as an actor may rent a flat as a collection of spaces or a zone . This would be an application of this generic relationship. Reference to the objects or single object on which the actor acts upon in a certain role if given is specified in the inherited RelatedObjects attribute. HISTORY New entity in IFC2.0. Has been renamed from IfcRelActsUpon in IFC2x. bSI Documentation"
#:IFC.xml:62
msgid "IfcRelAssignsToActor_ActingRole"
msgstr "ActingRole"
msgid "IfcRelAssignsToActor_ActingRole_DEFINITION"
msgstr "ActingRole"
#:IFC.xml:20059
msgid "IfcRelAssignsToActor_RelatingActor"
msgstr "RelatingActor"
msgid "IfcRelAssignsToActor_RelatingActor_DEFINITION"
msgstr "RelatingActor"
#:IFC.xml:20824
msgid "IfcRelAssignsToControl"
msgstr "IfcRelAssignsToControl"
msgid "IfcRelAssignsToControl_DEFINITION"
msgstr "The objectified relationship [[IfcRelAssignsToControl]] handles the assignment of a control represented by subtypes of [[IfcControl]] to other objects represented by subtypes of [[IfcObject]] , with the exception of controls . EXAMPLE The assignment of a performance history as subtype of [[IfcControl]] for a building service element as subtype of [[IfcObject]] is an application of this generic relationship. HISTORY New entity in IFC2.0. .change ifc2x IFC2x CHANGE Entity has been renamed from IfcRelControls . bSI Documentation"
#:IFC.xml:20214
msgid "IfcRelAssignsToControl_RelatingControl"
msgstr "RelatingControl"
msgid "IfcRelAssignsToControl_RelatingControl_DEFINITION"
msgstr "RelatingControl"
#:IFC.xml:20831
msgid "IfcRelAssignsToGroup"
msgstr "IfcRelAssignsToGroup"
msgid "IfcRelAssignsToGroup_DEFINITION"
msgstr "The objectified relationship [[IfcRelAssignsToGroup]] handles the assignment of object definitions individual object occurrences as subtypes of [[IfcObject]] , and object types as subtypes of [[IfcTypeObject]] to a group subtypes of [[IfcGroup]] . The relationship handles the assignment of group members to the group object. It allows for grouping arbitrary objects within a group, including other groups. The grouping relationship can be applied in a recursive manner. The resulting group is of type [[IfcGroup]] . NOTE Examples of groups include zones as a grouping of spaces, distribution systems as a grouping of building service components, or structural analysis models as a grouping of structural items. The inherited attribute RelatedObjects gives the references to the objects, which are the elements within the group. The RelatingGroup is the group that comprises all elements. The same object or object type can be included in zero, one or many groups. Grouping relationships are not hierarchical. .spec head Informal Propositions 1. The group assignment relationship shall be acyclic, that is, a group shall not participate in its own grouping relationship. HISTORY New entity in IFC1.0. It has been renamed from IfcRelGroups in IFC2x. bSI Documentation"
#:IFC.xml:20241
msgid "IfcRelAssignsToGroup_RelatingGroup"
msgstr "RelatingGroup"
msgid "IfcRelAssignsToGroup_RelatingGroup_DEFINITION"
msgstr "RelatingGroup"
#:IFC.xml:20838
msgid "IfcRelAssignsToGroupByFactor"
msgstr "IfcRelAssignsToGroupByFactor"
msgid "IfcRelAssignsToGroupByFactor_DEFINITION"
msgstr "The objectified relationship [[IfcRelAssignsToGroupByFactor]] is a specialization of the general grouping mechanism. It allows to add a factor to define the ratio that applies to the assignment of object definitions individual object occurrences as subtypes of [[IfcObject]] and object types as subtypes of [[IfcTypeObject]] to a group subtypes of [[IfcGroup]] . The ratio can be used to define a percentage assignment. For example, a Factor of 0.8 would indicate that the object is assigned by 80 to the group, or a Factor of 2.5 would indicate the object is assigned with a weight factor of 2.5 to the group. NOTE Examples of factored groups include the assignment of load cases in a load combination in structural analysis, or the assignment of spaces by percentage to different rental zones. The same object or object type may be included with the same or different Factor values to many groups. Grouping relationships are not hierarchical. HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:20839
msgid "IfcRelAssignsToGroupByFactor_Factor"
msgstr "Factor"
msgid "IfcRelAssignsToGroupByFactor_Factor_DEFINITION"
msgstr "Factor provided as a ratio measure that identifies the fraction or weighted factor that applies to the group assignment."
#:IFC.xml:20846
msgid "IfcRelAssignsToProcess"
msgstr "IfcRelAssignsToProcess"
msgid "IfcRelAssignsToProcess_DEFINITION"
msgstr "The objectified relationship [[IfcRelAssignsToProcess]] handles the assignment of one or many objects to a process or activity. An object can be a product that is the item the process operates on. Processes and activities can operate on things other than products, and can operate in ways other than input and output. EXAMPLE It may be common to define processes during estimating or scheduling that describe design tasks resulting in documents , procurement tasks resulting in construction materials , planning tasks resulting in processes , etc. Furthermore, the ways in which process can operate on something might include installs , finishes , transports , removes , etc. The ways are described as operation types. The inherited attribute RelatedObjects gives the references to the objects, or object type, which the process operates on. The RelatingProcess is the process or process type, that operates on the object. The operation types are captured in the inherited attribute Name . NOTE The agreement on valid and recognizable values for the Name attribute is part of view definitions and implementer agreements. HISTORY New entity in IFC1.5. Has been renamed from IfcRelProcessOperatesOn in IFC2x. .change ifc2x4 IFC4 CHANGE The data type RelatingProcess has been extended to cover also [[IfcTypeProcess]] bSI Documentation"
#:IFC.xml:20858
msgid "IfcRelAssignsToProcess_QuantityInProcess"
msgstr "QuantityInProcess"
msgid "IfcRelAssignsToProcess_QuantityInProcess_DEFINITION"
msgstr "QuantityInProcess"
#:IFC.xml:20851
msgid "IfcRelAssignsToProcess_RelatingProcess"
msgstr "RelatingProcess"
msgid "IfcRelAssignsToProcess_RelatingProcess_DEFINITION"
msgstr "Reference to the process to which the objects are assigned to. X 0D .change ifc2x4 X 0D IFC4 CHANGE Datatype expanded to include [[IfcProcess]] and [[IfcTypeProcess]] ."
#:IFC.xml:20882
msgid "IfcRelAssignsToProduct"
msgstr "IfcRelAssignsToProduct"
msgid "IfcRelAssignsToProduct_DEFINITION"
msgstr "The objectified relationship S [[IfcRelAssignsToProduct]] handles the assignment of objects subtypes of [[IfcObject]] to a product subtypes of [[IfcProduct]] . The Name attribute should be used to classify the usage of the [[IfcRelAssignsToProduct]] objectified relationship. The following Name values are proposed Context Assignment of a context specific representation, such as of structural members to a different context representation with potentially different decomposition breakdown such as of building elements S for a specific S context specific representation. S View Assignment of a product via RelatingProduct that is decomposed according to a discipline view, to another product via RelatedObjects that is decomposed according to a different discipline view. An example is the assignment of the architectural slab to a different decomposition of the pre manufactured sections of a slab under a precast concrete discipline view . HISTORY New entity in IFC2x .change ifc2x3 IFC2x3 CHANGE S The reference of a product within a spatial structure is now handled by a new relationship object [[IfcRelReferencedInSpatialStructure]] . The [[IfcRelAssignsToProduct]] shall not be used to represent this relation from IFC2x3 onwards. bSI Documentation"
#:IFC.xml:20887
msgid "IfcRelAssignsToProduct_RelatingProduct"
msgstr "RelatingProduct"
msgid "IfcRelAssignsToProduct_RelatingProduct_DEFINITION"
msgstr "Reference to the product or product type to which the objects are assigned to. X 0D .change ifc2x4 X 0D IFC4 CHANGE Datatype expanded to include [[IfcProduct]] and [[IfcTypeProduct]] ."
#:IFC.xml:20906
msgid "IfcRelAssignsToResource"
msgstr "IfcRelAssignsToResource"
msgid "IfcRelAssignsToResource_DEFINITION"
msgstr "The objectified relationship [[IfcRelAssignsToResource]] handles the assignment of objects as subtypes of [[IfcObject]] , acting as a resource usage or consumption, to a resource as subtypes of [[IfcResource]] . EXAMPLE The assignment of a resource usage to a construction resource is an application of this generic relationship. It could be an actor, as person or organization assigned to a labor resource, or a raw product assigned to a construction product or material resource . HISTORY New entity in IFC2x. bSI Documentation"
#:IFC.xml:20911
msgid "IfcRelAssignsToResource_RelatingResource"
msgstr "RelatingResource"
msgid "IfcRelAssignsToResource_RelatingResource_DEFINITION"
msgstr "Reference to the resource to which the objects are assigned to. X 0D .change ifc2x4 X 0D IFC4 CHANGE Datatype expanded to include [[IfcResource]] and [[IfcTypeResource]] ."
#:IFC.xml:20942
msgid "IfcRelAssociates"
msgstr "IfcRelAssociates"
msgid "IfcRelAssociates_DEFINITION"
msgstr "The association relationship [[IfcRelAssociates]] refers to sources of information most notably a classification, library, document, approval, contraint, or material . The information associated may reside internally or externally of the project data. There is no dependency implied by the association. EXAMPLE Further external information may be provided to the tank equipment as subtype of [[IfcProduct]] in terms of its classification and instruction documents, the source of the additional information is held external to the project data model. Association relationships can be established to objects occurrences as subtypes of [[IfcObject]] or to types as subtypes of [[IfcTypeObject]] . Some associations such as approval, or document may also be applied to property templates as subtypes of [[IfcPropertyDefinition]] . EXAMPLE The classification information for the storage tank equipment may be associated to the [[IfcTankType]] subtype of [[IfcTypeObject]] , defining the specific information for all occurencies of that tank in the project. Therefore the association of the Uniclass notation L6814 may be associated by a subtype of [[IfcRelAssociates]] to the type information. EXAMPLE The classification information for a particular space within a building may be associated to the [[IfcSpace]] object subtype of [[IfcObject]] , defining a particular occurrence of space. Therefore the association of the DIN notation NF 1.5 may be associated by a subtype of [[IfcRelAssociates]] to the object. The association relationship establishs an association between one to many objects or property templates and the associated information. The subtypes of [[IfcRelAssociates]] establish the particular semantic meaning of the association relationship. HISTORY New entity in IFC2x. .change ifc2x4 IFC4 CHANGE Entity has been changed into an ABSTRACT supertype bSI Documentation"
#:IFC.xml:20943
msgid "IfcRelAssociates_RelatedObjects"
msgstr "RelatedObjects"
msgid "IfcRelAssociates_RelatedObjects_DEFINITION"
msgstr "Set of object or property definitions to which the external references or information is associated. It includes object and type objects, property set templates, property templates and property sets and contexts. X 0D .change ifc2x4 X 0D IFC4 CHANGE The attribute datatype has been changed from [[IfcRoot]] to [[IfcDefinitionSelect]] ."
#:IFC.xml:20950
msgid "IfcRelAssociatesClassification"
msgstr "IfcRelAssociatesClassification"
msgid "IfcRelAssociatesClassification_DEFINITION"
msgstr "The objectified relationship [[IfcRelAssociatesClassification]] handles the assignment of a classification item items of the select [[IfcClassificationSelect]] to objects occurrences subtypes of [[IfcObject]] or object types subtypes of [[IfcTypeObject]] . The relationship is used to assign a classification item, or a classification system itself to objects. Depending on the type of the RelatingClassification it is either a reference to an classification item within an external classification system, or a reference to the classification system itself NOTE The reference to a classification item includes a link to the classification system within which the item is declared. It assigns the meaning of the classification item to the object ocurrence or type . The reference to the classification system provides the information that the object occurrence or type is governed by the classification system but no assignment of a particular items has been done yet. The inherited attribute RelatedObjects define the objects or object types to which the classification is applied. The attribute RelatingClassification is the reference to a classification, applied to the object s . A single RelatingClassification can thereby be applied to one or multiple objects. HISTORY New entity in IFC2x. bSI Documentation"
#:IFC.xml:20951
msgid "IfcRelAssociatesClassification_RelatingClassification"
msgstr "RelatingClassification"
msgid "IfcRelAssociatesClassification_RelatingClassification_DEFINITION"
msgstr "Classification applied to the objects."
#:IFC.xml:20958
msgid "IfcRelAssociatesDocument"
msgstr "IfcRelAssociatesDocument"
msgid "IfcRelAssociatesDocument_DEFINITION"
msgstr "The objectified relationship [[IfcRelAssociatesDocument]] handles the assignment of a document information items of the select [[IfcDocumentSelect]] to objects occurrences subtypes of [[IfcObject]] or object types subtypes of [[IfcTypeObject]] . The relationship is used to assign a document reference or a more detailed document information to objects. A single document reference can be applied to multiple objects. The inherited attribute RelatedObjects define the objects to which the document association is applied. The attribute RelatingDocument is the reference to a document reference, applied to the object s . HISTORY New entity in IFC2x. bSI Documentation"
#:IFC.xml:20959
msgid "IfcRelAssociatesDocument_RelatingDocument"
msgstr "RelatingDocument"
msgid "IfcRelAssociatesDocument_RelatingDocument_DEFINITION"
msgstr "Document information or reference which is applied to the objects."
#:IFC.xml:20966
msgid "IfcRelAssociatesLibrary"
msgstr "IfcRelAssociatesLibrary"
msgid "IfcRelAssociatesLibrary_DEFINITION"
msgstr "The objectified relationship [[IfcRelAssociatesLibrary]] handles the assignment of a library item items of the select [[IfcLibrarySelect]] to subtypes of [[IfcObjectDefinition]] or [[IfcPropertyDefinition]] . The relationship is used to assign a library reference or a more detailed link to a library information to objects, property sets or types. A single library reference can be applied to multiple items. The inherited attribute RelatedObjects define the items to which the library association is applied. The attribute RelatingLibrary is the reference to a library reference, applied to the item s . HISTORY New entity in IFC2x. bSI Documentation"
#:IFC.xml:20967
msgid "IfcRelAssociatesLibrary_RelatingLibrary"
msgstr "RelatingLibrary"
msgid "IfcRelAssociatesLibrary_RelatingLibrary_DEFINITION"
msgstr "Reference to a library, from which the definition of the property set is taken."
#:IFC.xml:20974
msgid "IfcRelationship"
msgstr "IfcRelationship"
msgid "IfcRelationship_DEFINITION"
msgstr "[[IfcRelationship]] is the abstract generalization of all objectified relationships in IFC. Objectified relationships are the preferred way to handle relationships among objects. This allows to keep relationship specific properties directly at the relationship and opens the possibility to later handle relationship specific behavior. There are two different types of relationships, 1 to 1 relationships and 1 to many relationship. used within the subtypes of [[IfcRelationship]] . The following convention applies to all subtypes The two sides of the objectified relationship are named Relating and Related In case of the 1 to many relationship, the related side of the relationship shall be an aggregate being a set 1 N HISTORY New entity in IFC1.0. bSI Documentation"
#:IFC.xml:20977
msgid "IfcRelConnects"
msgstr "IfcRelConnects"
msgid "IfcRelConnects_DEFINITION"
msgstr "[[IfcRelConnects]] is a connectivity relationship that connects objects under some criteria. As a general connectivity it does not imply constraints, however subtypes of the relationship define the applicable object types for the connectivity relationship and the semantics of the particular connectivity. HISTORY New entity in IFC2x. bSI Documentation"
#:IFC.xml:20980
msgid "IfcRelDeclares"
msgstr "IfcRelDeclares"
msgid "IfcRelDeclares_DEFINITION"
msgstr "The objectified relationship [[IfcRelDeclares]] handles the declaration of objects subtypes of [[IfcObject]] or properties subtypes of [[IfcPropertyDefinition]] to a project or project library represented by [[IfcProject]] , or [[IfcProjectLibrary]] . The relationship handles the assignment of other objects, like [[IfcActor]] , or [[IfcTypeObject]] to the project, or project libary. The attribute RelatedDefinitions provides the references to the first level objects, that are the elements within the context. All other objects that relate to the first level objects are also defined in the context. NOTE Every object as subtype of [[IfcObject]] has to be declared within the context of a single [[IfcProject]] , or of a [[IfcProjectLibrary]] assigned to a single [[IfcProject]] . This declaration is transitive. For example the [[IfcWorkPlan]] as first level object is declared within the context of [[IfcProject]] via [[IfcRelDeclares]] , all related [[IfcWorkSchedule]] s are related to the context in a transitive way through [[IfcWorkPlan]] . NOTE The assignment excludes subtypes of [[IfcProduct]] s, these are assigned to the [[IfcProject]] using the spatial structure approach through [[IfcSpatialStructureElement]] s , where the outer container element such as [[IfcSite]] or [[IfcBuilding]] has an [[IfcRelAggregates]] relationship with the [[IfcProject]] . The RelatingContext is the project, or project library that comprises all elements. The unit assignments and the presentation contexts defined at [[IfcProject]] or [[IfcProjectLibrary]] apply to all these elements. HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:20180
msgid "IfcRelDeclares_RelatingContext"
msgstr "RelatingContext"
msgid "IfcRelDeclares_RelatingContext_DEFINITION"
msgstr "RelatingContext"
#:IFC.xml:20985
msgid "IfcRelDeclares_RelatedDefinitions"
msgstr "RelatedDefinitions"
msgid "IfcRelDeclares_RelatedDefinitions_DEFINITION"
msgstr "Set of object or property definitions that are assigned to a context and to which the unit and representation context definitions of that context apply."
#:IFC.xml:20992
msgid "IfcRelDecomposes"
msgstr "IfcRelDecomposes"
msgid "IfcRelDecomposes_DEFINITION"
msgstr "The decomposition relationship, [[IfcRelDecomposes]] , defines the general concept of elements being composed or decomposed. The decomposition relationship denotes a whole part hierarchy with the ability to navigate from the whole the composition to the parts and vice versa. Decompositions may be constrained by requiring both, the whole and its parts, to be of the same type thus establishing a nesting relationship. Or they may require some form of physical containment, thus establishing special types of aggregation relationships. NOTE There are two special names for decomposition, which are linguistically distinguished, nesting and aggregation. The subtypes of [[IfcRelDecomposes]] will introduce either the nesting or aggregation convention see [[IfcRelNests]] and [[IfcRelAggregates]] . EXAMPLE A cost element is a nest of other cost elements. Or a structural frame is an aggregation of beams and columns. Both are applications of decomposition relationship. Decompositions imply a dependency, i.e. the definition of the whole depends on the definition of the parts and the parts depend on the existence of the whole. The decomposition relationship can be applied in a recursive manner, i.e. a decomposed element can be part in another decomposition. Cyclic references have to be prevented at application level. HISTORY New entity in IFC1.5, it is a generalisation of the IFC2.0 entity [[IfcRelNests]] . .change ifc2x4 IFC4 CHANGE The differentiation between the aggregation and nesting is determined to be a non ordered or an ordered collection of parts. The attributes RelatingObject and RelatedObjects have been demoted to the subtypes. bSI Documentation"
#:IFC.xml:20995
msgid "IfcRelDefines"
msgstr "IfcRelDefines"
msgid "IfcRelDefines_DEFINITION"
msgstr "A generic and abstract relationship which subtypes are used to assign a object type to an object occurrence assign a property set to an object instance assign a property set template to a property set EXAMPLE S Several instances of windows within the IFC project model may be of the same catalogue or manufacturer type. Thereby they share the same properties. This relationship is established by the subtype [[IfcRelDefinesByType]] of [[IfcRelDefines]] relationship assigning an [[IfcWindowStyle]] to multiple occurrences [[IfcWindow]] . EXAMPLE S The same property set, e.g. S Pset ProductManufacturerInfo, keeping the manufacturer name, label and production year of a product, can be assigned to one, or many instances of furnishing. This relationship is established by the subtype [[IfcRelDefinesByProperties]] of [[IfcRelDefines]] relationship assigning an [[IfcPropertySet]] to one or more instances of [[IfcFurnishingElement]] . HISTORY New entity in IFC2x. .change ifc2x4 IFC4 CHANGE The attribute RelatedObjects had been demoted to the subtypes [[IfcRelDefinesByProperties]] and [[IfcRelDefinesByType]] . bSI Documentation"
#:IFC.xml:20998
msgid "IfcRelDefinesByObject"
msgstr "IfcRelDefinesByObject"
msgid "IfcRelDefinesByObject_DEFINITION"
msgstr "The objectified relationship [[IfcRelDefinesByObject]] defines the relationship between an object taking part in an object type decomposition and an object occurrences taking part in an occurrence decomposition of that type. The [[IfcRelDefinesByObject]] is a 1 to N relationship, as it allows for the assignment of one declaring object information to a single or to many reflected objects. Those objects then share the same object property sets and, for subtypes of [[IfcProduct]] , the eventually assigned representation maps. Only objects that take part in a type decomposition and in an occurrence decomposition of the same type can be connected by the [[IfcRelDefinesByObject]] relationship. The [[IfcRelDefinesByObject]] links the decomposed object type part, also called the declaring part with the occurrence of that part inside the occurrence of the decomposed type, also called the reflected part , as shown in Figure 1. instance diagram .. .. .. .. .. .. figures ifcreldefinesbyobject fig 1.png Figure 1 Part definition relationships The [[IfcRelDefinesByObject]] can be used together with the shape representations of the product type as shown in Figure 2. The [[IfcShapeRepresentation]] of the declaring part is referenced by the reflected part . The [[IfcObjectPlacement]] of the model occurrence the whole determines the position within the project context. geometry diagram .. .. .. .. .. .. figures ifcreldefinesbyobject fig 2.png Figure 2 Part definition relationships with shape representation HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:20277
msgid "IfcRelDefinesByObject_RelatingObject"
msgstr "RelatingObject"
msgid "IfcRelDefinesByObject_RelatingObject_DEFINITION"
msgstr "RelatingObject"
#:IFC.xml:20291
msgid "IfcRelDefinesByObject_RelatedObjects"
msgstr "RelatedObjects"
msgid "IfcRelDefinesByObject_RelatedObjects_DEFINITION"
msgstr "RelatedObjects"
#:IFC.xml:21001
msgid "IfcRelDefinesByProperties"
msgstr "IfcRelDefinesByProperties"
msgid "IfcRelDefinesByProperties_DEFINITION"
msgstr "The objectified relationship [[IfcRelDefinesByProperties]] defines the relationships between property set definitions and objects. Properties are aggregated in property sets. Property sets can be either directly assigned to occurrence objects using this relationship, or assigned to an object type and assigned via that type to occurrence objects. The assignment of an [[IfcPropertySet]] to an [[IfcTypeObject]] is not handled via this objectified relationship, but through the direct relationship HasPropertySets at [[IfcTypeObject]] . The [[IfcRelDefinesByProperties]] is an N to N relationship, as it allows for the assignment of one or more property sets to one or more objects. Those objects then share the same property definition. HISTORY New entity in IFC2.0. Has been renamed from IfcRelAssignsProperties in IFC2x. .change ifc2x4 IFC4 CHANGE The attribute RelatedObjects had been demoted from the supertype [[IfcRelDefines]] to [[IfcRelDefinesByProperties]] . This relationship has been modified to support multiple property sets referenced by a single relationship. bSI Documentation"
#:IFC.xml:20194
msgid "IfcRelDefinesByProperties_RelatedObjects"
msgstr "RelatedObjects"
msgid "IfcRelDefinesByProperties_RelatedObjects_DEFINITION"
msgstr "RelatedObjects"
#:IFC.xml:21006
msgid "IfcRelDefinesByProperties_RelatingPropertyDefinition"
msgstr "RelatingPropertyDefinition"
msgid "IfcRelDefinesByProperties_RelatingPropertyDefinition_DEFINITION"
msgstr "Reference to the property set definition for that object or set of objects."
#:IFC.xml:21013
msgid "IfcRelDefinesByTemplate"
msgstr "IfcRelDefinesByTemplate"
msgid "IfcRelDefinesByTemplate_DEFINITION"
msgstr "The objectified relationship [[IfcRelDefinesByTemplate]] defines the relationships between property set template and property sets. Common information about property sets, e.g. the applicable name, description, contained properties, is defined by the property set template and assigned to all property sets. NOTE The assignment of an [[IfcPropertySetTemplate]] is supported for [[IfcPropertySet]] and [[IfcQuantitySet]] . The [[IfcRelDefinesByTemplate]] is a 1 to N relationship, as it allows for the assignment of one property set template to a single or to many property sets or quantity sets. Those property sets then share the same property set template definition. HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:20682
msgid "IfcRelDefinesByTemplate_RelatedPropertySets"
msgstr "RelatedPropertySets"
msgid "IfcRelDefinesByTemplate_RelatedPropertySets_DEFINITION"
msgstr "RelatedPropertySets"
#:IFC.xml:20750
msgid "IfcRelDefinesByTemplate_RelatingTemplate"
msgstr "RelatingTemplate"
msgid "IfcRelDefinesByTemplate_RelatingTemplate_DEFINITION"
msgstr "RelatingTemplate"
#:IFC.xml:21016
msgid "IfcRelDefinesByType"
msgstr "IfcRelDefinesByType"
msgid "IfcRelDefinesByType_DEFINITION"
msgstr "The objectified relationship [[IfcRelDefinesByType]] defines the relationship between an object type and object occurrences. The [[IfcRelDefinesByType]] is a 1 to N relationship, as it allows for the assignment of one type information to a single or to many objects. Those objects then share the same object type, and the property sets and properties assigned to the object type. The [[IfcRelDefinesByType]] links the object type definition with the object occurrence. Both may define properties by assigning an [[IfcPropertySet]] , including one or many subtypes of [[IfcProperty]] to either the object type or object occurrence, as shown in Figure 1. There are several scenarios to define the same property set on the object type definition and object occurrence side 1. All properties for all object occurrences of a common object type have the same value then only the object type definition has a property set assigned. 2. All properties for all object occurrences are different, that is there are no common property values for the object type definition then each of the object occurrence has a property set assigned. 3. Some properties within the same property set have common values and are assigned to the object type definition and some are occurrence specific and assigned with potentially different values to the object occurrences then The sum of all properties within a given property set applicable to an object occurrence is the union of properties assigned to the object type definition plus the properties assigned to the object occurrence. If the object occurrence has a property with the same [[IfcProperty]].Name in an [[IfcPropertySet]] , as the corresponding object type definition, then the occurrence property value overrides the type property value. Figure 1 Type definition relationships The following table provides an example of assigning properties assigned to [[IfcWall]] properties assigned to [[IfcWallType]] resulting property value for individual wall Pset WallCommon Pset WallCommon S S S ExtendToStructure TRUE S TRUE S S S ThermalTransmittance 0.375 0.375 S S ExtendToStructure FALSE S S ExtendToStructure TRUE FALSE HISTORY New entity in IFC2x. .change ifc2x4 IFC4 CHANGE The attribute RelatedObjects had been demoted from the supertype [[IfcRelDefines]] to [[IfcRelDefinesByType]] . bSI Documentation"
#:IFC.xml:20317
msgid "IfcRelDefinesByType_RelatedObjects"
msgstr "RelatedObjects"
msgid "IfcRelDefinesByType_RelatedObjects_DEFINITION"
msgstr "RelatedObjects"
#:IFC.xml:21019
msgid "IfcRelDefinesByType_RelatingType"
msgstr "RelatingType"
msgid "IfcRelDefinesByType_RelatingType_DEFINITION"
msgstr "RelatingType"
#:IFC.xml:21033
msgid "IfcRelNests"
msgstr "IfcRelNests"
msgid "IfcRelNests_DEFINITION"
msgstr "The nesting relationship [[IfcRelNests]] is a special type of the general composition decomposition or whole part relationship [[IfcRelDecomposes]] . The nesting relationship can be applied to all non physical subtypes of object and object types, namely processes, controls like cost items , and resources. It can also be applied to physical subtypes of object and object types, namely elements having ports. The nesting implies an order among the nested parts. EXAMPLE A nesting of costs items in an [[IfcCostSchedule]] is the composition of complex cost items from other cost items. The order of the nested cost items underneath the parent cost item is determined by the order of the list of RelatedObjects . EXAMPLE A nesting of [[IfcTask]] s within a work schedule is the composition of a parent work task from more specific sub work tasks. The order of the sub tasks underneath the parent task is determined by the order of the list of RelatedObjects . EXAMPLE A series of [[IfcDistributionPort]] s can be nested within an [[IfcDistributionElement]] . They decompose the distribution element and have an implied order. Decompositions imply a dependency, i.e. the definition of the whole depends on the definition of the parts and the parts depend on the existence of the whole. The behaviour that is implied from the dependency has to be established inside the applications. HISTORY New entity in IFC2.0 .change ifc2x4 IFC4 CHANGE The attributes RelatingObject and RelatedObjects are demoted from the supertype [[IfcRelDecomposes]] , and RelatedObjects is refined to be a list. The use of [[IfcRelNests]] is repurposed to be a nesting of an ordered collections of parts. bSI Documentation"
#:IFC.xml:20361
msgid "IfcRelNests_RelatingObject"
msgstr "RelatingObject"
msgid "IfcRelNests_RelatingObject_DEFINITION"
msgstr "RelatingObject"
#:IFC.xml:20375
msgid "IfcRelNests_RelatedObjects"
msgstr "RelatedObjects"
msgid "IfcRelNests_RelatedObjects_DEFINITION"
msgstr "RelatedObjects"
#:IFC.xml:21040
msgid "IfcResource"
msgstr "IfcResource"
msgid "IfcResource_DEFINITION"
msgstr "[[IfcResource]] contains the information needed to represent the costs, schedule, and other impacts from the use of a thing in a process. It is not intended to use [[IfcResource]] to model the general properties of the things themselves, while an optional linkage from [[IfcResource]] to the things to be used can be specified specifically, the relationship from subtypes of [[IfcResource]] to [[IfcProduct]] through the [[IfcRelAssignsToResource]] relationship . There are two basic intended uses of [[IfcResource]] . First, if the attributes of the thing are not needed for the purpose of the use of [[IfcResource]] , or the types of things are not explicitly modeled in IFC yet, then the linkage between the resource and the thing doesn t have to be instantiated in the system. That is, the attributes of [[IfcResource]] or its subtypes alone are sufficient to represent the use of the thing as a resource for the purpose of the project. EXAMPLE construction equipment such as earth moving vehicles or tools are not currently modeled within the IFC. For the purpose of estimating and scheduling, these can be represented using subtypes of [[IfcResource]] alone. Second, if the attributes of the thing are needed for the use of [[IfcResource]] objects, and they are modeled explicitly as objects, then the [[IfcResource]] instances can be linked to the instances of the type of the things being referenced. Things that might be used as resources and that are already modeled in the IFC include physical products, people and organizations, and materials. The relationship object [[IfcRelAssignsToResource]] is provided for this approach. The inherited attribute ObjectType is used as a textual code that identifies the resource type. HISTORY New entity in IFC1.0 .change ifc2x IFC2x CHANGE The attributes BaseUnit and ResourceConsumption have been removed from the abstract entity they are reintroduced at a lower level in the hierarchy. bSI Documentation"
#:IFC.xml:20930
msgid "IfcResource_ResourceOf"
msgstr "ResourceOf"
msgid "IfcResource_ResourceOf_DEFINITION"
msgstr "ResourceOf"
#:IFC.xml:21041
msgid "IfcResource_Identification"
msgstr "Identification"
msgid "IfcResource_Identification_DEFINITION"
msgstr "An identifying designation given to a resource. X 0D It is the identifier at the occurrence level. X 0D X 0D .change ifc2x4 X 0D IFC4 CHANGE Attribute promoted from subtype [[IfcConstructionResource]] ."
#:IFC.xml:21046
msgid "IfcResource_LongDescription"
msgstr "LongDescription"
msgid "IfcResource_LongDescription_DEFINITION"
msgstr "A detailed description of the resource e.g. the skillset for a labor resource . X 0D .change ifc2x4 X 0D IFC4 CHANGE The attribute LongDescription is added replacing the ResourceGroup attribute at subtype [[IfcConstructionResource]] ."
#:IFC.xml:21054
msgid "IfcRoot"