forked from buildingSMART/IFC4.3.x-output
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathIfcDateTimeResource.pot
691 lines (496 loc) · 34.9 KB
/
IfcDateTimeResource.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
# 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:3565
msgid "IfcDataOriginEnum"
msgstr "IfcDataOriginEnum"
msgid "IfcDataOriginEnum_DEFINITION"
msgstr "[[IfcDataOriginEnum]] identifies the origin of time data. HISTORY New enumeration in IFC2x2. bSI Documentation"
#:IFC.xml:3572
msgid "IfcEventTime"
msgstr "IfcEventTime"
msgid "IfcEventTime_DEFINITION"
msgstr "[[IfcEventTime]] captures the time related information about an event including the different types of event dates i.e. actual, scheduled, early, and late . All given values should be provided by the application, that is, the IFC schema does not deal with dependencies between process time values. At this stage there is also no consistency check through where rules that guarantee a meaningful population of date values. Thus, an application is responsible to provide reasonable values and, if an application receives event dates, has to make consistency checks by their own. [[IfcEventTime]] furthermore provides a generic mechanism to differentiate between user given time values and time values derived from user given time values and other constraints such as work calendars and assigned resources derived from the process graph . The data origin flag is provided as a single attribute applying to all date time related attributes of [[IfcEventTime]] . HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:3573
msgid "IfcEventTime_ActualDate"
msgstr "ActualDate"
msgid "IfcEventTime_ActualDate_DEFINITION"
msgstr "The date on which an event actually occurs. It is a measured value."
#:IFC.xml:3578
msgid "IfcEventTime_EarlyDate"
msgstr "EarlyDate"
msgid "IfcEventTime_EarlyDate_DEFINITION"
msgstr "The earliest date on which an event can occur. It is a calculated value."
#:IFC.xml:3583
msgid "IfcEventTime_LateDate"
msgstr "LateDate"
msgid "IfcEventTime_LateDate_DEFINITION"
msgstr "The latest date on which an event can occur. It is a calculated value."
#:IFC.xml:3588
msgid "IfcEventTime_ScheduleDate"
msgstr "ScheduleDate"
msgid "IfcEventTime_ScheduleDate_DEFINITION"
msgstr "The date on which an event is scheduled to occur. X 0D The value might be measured or somehow calculated, which is defined by X 0D ScheduleDataOrigin ."
#:IFC.xml:3607
msgid "IfcIrregularTimeSeries"
msgstr "IfcIrregularTimeSeries"
msgid "IfcIrregularTimeSeries_DEFINITION"
msgstr "In an irregular time series, unpredictable bursts of data arrive at unspecified points in time, or most time stamps cannot be characterized by a repeating pattern. EXAMPLE A circulating pump cycles on and off at unpredictable times as dictated by the demands on the piping system the amount of light in a classroom varies depending on when the lights are manually switched on and off and how many lamps are controlled by each switch. HISTORY New entity in IFC2x2. bSI Documentation"
#:IFC.xml:3610
msgid "IfcIrregularTimeSeries_Values"
msgstr "Values"
msgid "IfcIrregularTimeSeries_Values_DEFINITION"
msgstr "Values"
#:IFC.xml:3622
msgid "IfcIrregularTimeSeriesValue"
msgstr "IfcIrregularTimeSeriesValue"
msgid "IfcIrregularTimeSeriesValue_DEFINITION"
msgstr "The [[IfcIrregularTimeSeriesValue]] describes a value or set of values at a particular time point. HISTORY New entity in IFC2x2. bSI Documentation"
#:IFC.xml:3623
msgid "IfcIrregularTimeSeriesValue_TimeStamp"
msgstr "TimeStamp"
msgid "IfcIrregularTimeSeriesValue_TimeStamp_DEFINITION"
msgstr "The specification of the time point."
#:IFC.xml:3628
msgid "IfcIrregularTimeSeriesValue_ListValues"
msgstr "ListValues"
msgid "IfcIrregularTimeSeriesValue_ListValues_DEFINITION"
msgstr "A list of time series values. At least one value is required."
#:IFC.xml:3634
msgid "IfcLagTime"
msgstr "IfcLagTime"
msgid "IfcLagTime_DEFINITION"
msgstr "[[IfcLagTime]] describes the time parameters that may exist within a sequence relationship between two processes. An [[IfcLagTime]] provides information about the time lag that exists between the predecessor and successor process in a sequence. The assertion of the time lag is optional for a sequence but for work schedules that specifically deal with processes occurring at particular times, it should be asserted. A lag time has a duration type. This allows the identification of whether elapsed time or work time is being measured where work time is the estimate of the time required to complete the process and elapsed time being the amount of time actually allocated to the process The form of measurement of the duration can be captured. Allowed values for this are MEASURED, PREDICTED or SIMULATED. The selection of this value depends on the use of the schedule. A NOTDEFINED value is also allowed. The value of the time lag may be selected as being either a percentage ratio or an actual time measure. If selected as a ratio, the percentage should apply to the duration of the predecessor process relating process such that e.g. a value of 0.5 50 would indicate that the successor task should start when the predecessor task is 50 complete if a START START sequence type is used or should wait for 50 of the duration of the predecessor process to have elapsed after the finish of the predecessor process in case of a FINISH START sequence type. The time unit for the task duration may also be set and this may be set to any allowed unit of time measure. HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:3635
msgid "IfcLagTime_LagValue"
msgstr "LagValue"
msgid "IfcLagTime_LagValue_DEFINITION"
msgstr "Value of the time lag selected as being either a ratio or a X 0D time measure."
#:IFC.xml:3640
msgid "IfcLagTime_DurationType"
msgstr "DurationType"
msgid "IfcLagTime_DurationType_DEFINITION"
msgstr "The allowed types of task duration that specify the lag time X 0D measurement work time or elapsed time ."
#:IFC.xml:3659
msgid "IfcRecurrencePattern"
msgstr "IfcRecurrencePattern"
msgid "IfcRecurrencePattern_DEFINITION"
msgstr "[[IfcRecurrencePattern]] defines repetitive time periods on the basis of regular recurrences such as each Monday in a week, or every third Tuesday in a month. The population of the remaining attributes such as DayComponent , Position , and Interval depend on the specified recurrence type. [[IfcRecurrencePattern]] supports various recurrence patterns that are differentiated by a type definition [[IfcRecurrencePattern]].RecurrenceType , which is required to provide the meaning of the given values. It can be further constrained by applicable times through specified [[IfcTimePeriod]] instances, thus enabling time periods such as between 7 00 and 12 00 and between 13 00 and 17 00 for each of the applicable days, weeks or months. HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:3696
msgid "IfcRecurrencePattern_TimePeriods"
msgstr "TimePeriods"
msgid "IfcRecurrencePattern_TimePeriods_DEFINITION"
msgstr "TimePeriods"
#:IFC.xml:3660
msgid "IfcRecurrencePattern_RecurrenceType"
msgstr "RecurrenceType"
msgid "IfcRecurrencePattern_RecurrenceType_DEFINITION"
msgstr "Defines the recurrence type that gives meaning to the used X 0D attributes and decides about possible attribute X 0D combinations, i.e. what attributes are needed to fully X 0D describe the pattern type."
#:IFC.xml:3665
msgid "IfcRecurrencePattern_DayComponent"
msgstr "DayComponent"
msgid "IfcRecurrencePattern_DayComponent_DEFINITION"
msgstr "The position of the specified day in a month."
#:IFC.xml:3670
msgid "IfcRecurrencePattern_WeekdayComponent"
msgstr "WeekdayComponent"
msgid "IfcRecurrencePattern_WeekdayComponent_DEFINITION"
msgstr "The weekday name of the specified day in a week."
#:IFC.xml:3675
msgid "IfcRecurrencePattern_MonthComponent"
msgstr "MonthComponent"
msgid "IfcRecurrencePattern_MonthComponent_DEFINITION"
msgstr "The position of the specified month in a year."
#:IFC.xml:3680
msgid "IfcRecurrencePattern_Position"
msgstr "Position"
msgid "IfcRecurrencePattern_Position_DEFINITION"
msgstr "The position of the specified component, e.g. the 3rd X 0D position 3 Tuesday weekday component in a month. A X 0D negative position value is used to define the last position X 0D of the component 1 , the next to last position 2 etc."
#:IFC.xml:3685
msgid "IfcRecurrencePattern_Interval"
msgstr "Interval"
msgid "IfcRecurrencePattern_Interval_DEFINITION"
msgstr "An interval can be given according to the pattern type. An X 0D interval value of 2 can for instance every two days, weeks, X 0D months, years. An empty interval value is regarded as 1. The X 0D used interval values should be in a reasonable range, e.g. X 0D not 0 or 0."
#:IFC.xml:3690
msgid "IfcRecurrencePattern_Occurrences"
msgstr "Occurrences"
msgid "IfcRecurrencePattern_Occurrences_DEFINITION"
msgstr "Defines the number of occurrences of this pattern, e.g. a weekly X 0D event might be defined to occur 5 times before it stops."
#:IFC.xml:3732
msgid "IfcRecurrenceTypeEnum"
msgstr "IfcRecurrenceTypeEnum"
msgid "IfcRecurrenceTypeEnum_DEFINITION"
msgstr "[[IfcRecurrenceTypeEnum]] enumerates the recurring pattern type, with valid combinations as indicated. HISTORY New enumeration in IFC4. bSI Documentation"
#:IFC.xml:3742
msgid "IfcRegularTimeSeries"
msgstr "IfcRegularTimeSeries"
msgid "IfcRegularTimeSeries_DEFINITION"
msgstr "In a regular time series, the data arrives predictably at predefined intervals. In a regular time series there is no need to store multiple time stamps and the algorithms for analyzing the time series are therefore significantly simpler. Using the start time provided in the supertype, the time step is used to identify the frequency of the occurrences of the list of values. EXAMPLE A smoke detector samples the concentration of particulates in a space at a fixed rate for example, every six seconds a control system measures the outside air temperature every hour. HISTORY New entity in IFC2x2. bSI Documentation"
#:IFC.xml:3750
msgid "IfcRegularTimeSeries_Values"
msgstr "Values"
msgid "IfcRegularTimeSeries_Values_DEFINITION"
msgstr "Values"
#:IFC.xml:3743
msgid "IfcRegularTimeSeries_TimeStep"
msgstr "TimeStep"
msgid "IfcRegularTimeSeries_TimeStep_DEFINITION"
msgstr "A duration of time intervals between values."
#:IFC.xml:3762
msgid "IfcResourceTime"
msgstr "IfcResourceTime"
msgid "IfcResourceTime_DEFINITION"
msgstr "[[IfcResourceTime]] captures the time related information about a construction resource. HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:3763
msgid "IfcResourceTime_ScheduleWork"
msgstr "ScheduleWork"
msgid "IfcResourceTime_ScheduleWork_DEFINITION"
msgstr "Indicates the total work e.g. person hours allocated to the task on behalf of the resource. X 0D Note this is not necessarily the same as the task duration [[IfcTaskTime]].ScheduleDuration it may vary according to the resource usage ratio and other resources assigned to the task."
#:IFC.xml:3768
msgid "IfcResourceTime_ScheduleUsage"
msgstr "ScheduleUsage"
msgid "IfcResourceTime_ScheduleUsage_DEFINITION"
msgstr "Indicates the amount of the resource used concurrently. For example, 100 means 1 worker, 300 means 3 workers, 50 means half of 1 worker s time for scenarios where multitasking is feasible. If not provided, then the usage ratio is considered to be 100 ."
#:IFC.xml:3773
msgid "IfcResourceTime_ScheduleStart"
msgstr "ScheduleStart"
msgid "IfcResourceTime_ScheduleStart_DEFINITION"
msgstr "Indicates the time when the resource is scheduled to start working."
#:IFC.xml:3778
msgid "IfcResourceTime_ScheduleFinish"
msgstr "ScheduleFinish"
msgid "IfcResourceTime_ScheduleFinish_DEFINITION"
msgstr "Indicates the time when the resource is scheduled to finish working."
#:IFC.xml:3783
msgid "IfcResourceTime_ScheduleContour"
msgstr "ScheduleContour"
msgid "IfcResourceTime_ScheduleContour_DEFINITION"
msgstr "Indicates how a resource should be leveled over time by adjusting the resource usage according to a specified curve. Standard values include Flat , BackLoaded , FrontLoaded , DoublePeak , EarlyPeak , LatePeak , Bell , and Turtle . Custom values may specify a custom name or formula."
#:IFC.xml:3788
msgid "IfcResourceTime_LevelingDelay"
msgstr "LevelingDelay"
msgid "IfcResourceTime_LevelingDelay_DEFINITION"
msgstr "Indicates a delay in the ScheduleStart caused by leveling."
#:IFC.xml:3793
msgid "IfcResourceTime_IsOverAllocated"
msgstr "IsOverAllocated"
msgid "IfcResourceTime_IsOverAllocated_DEFINITION"
msgstr "Indicates that the resource is scheduled in excess of its capacity."
#:IFC.xml:3798
msgid "IfcResourceTime_StatusTime"
msgstr "StatusTime"
msgid "IfcResourceTime_StatusTime_DEFINITION"
msgstr "Indicates the date and time for which status values are applicable particularly completion, actual, and remaining values. If values are time phased the referencing [[IfcConstructionResource]] has associated time series values for attributes , then the status values may be determined from such time phased data as of the StatusTime."
#:IFC.xml:3803
msgid "IfcResourceTime_ActualWork"
msgstr "ActualWork"
msgid "IfcResourceTime_ActualWork_DEFINITION"
msgstr "Indicates the actual work performed by the resource as of the StatusTime."
#:IFC.xml:3808
msgid "IfcResourceTime_ActualUsage"
msgstr "ActualUsage"
msgid "IfcResourceTime_ActualUsage_DEFINITION"
msgstr "Indicates the actual amount of the resource used concurrently."
#:IFC.xml:3813
msgid "IfcResourceTime_ActualStart"
msgstr "ActualStart"
msgid "IfcResourceTime_ActualStart_DEFINITION"
msgstr "Indicates the time when the resource actually started working."
#:IFC.xml:3818
msgid "IfcResourceTime_ActualFinish"
msgstr "ActualFinish"
msgid "IfcResourceTime_ActualFinish_DEFINITION"
msgstr "Indicates the time when the resource actually finished working."
#:IFC.xml:3823
msgid "IfcResourceTime_RemainingWork"
msgstr "RemainingWork"
msgid "IfcResourceTime_RemainingWork_DEFINITION"
msgstr "Indicates the work remaining to be completed by the resource."
#:IFC.xml:3828
msgid "IfcResourceTime_RemainingUsage"
msgstr "RemainingUsage"
msgid "IfcResourceTime_RemainingUsage_DEFINITION"
msgstr ""
#:IFC.xml:3833
msgid "IfcResourceTime_Completion"
msgstr "Completion"
msgid "IfcResourceTime_Completion_DEFINITION"
msgstr "Indicates the percent completion of this resource. If the resource is assigned to a task, then indicates completion of the task on behalf of the resource if the resource is partitioned into sub allocations, then indicates overall completion of sub allocations."
#:IFC.xml:3840
msgid "IfcSchedulingTime"
msgstr "IfcSchedulingTime"
msgid "IfcSchedulingTime_DEFINITION"
msgstr "[[IfcSchedulingTime]] is the abstract supertype of entities that capture time related information of processes. HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:3841
msgid "IfcSchedulingTime_Name"
msgstr "Name"
msgid "IfcSchedulingTime_Name_DEFINITION"
msgstr "Optional name for the time definition."
#:IFC.xml:3846
msgid "IfcSchedulingTime_DataOrigin"
msgstr "DataOrigin"
msgid "IfcSchedulingTime_DataOrigin_DEFINITION"
msgstr "Specifies the origin of the scheduling time entity. It currently X 0D differentiates between predicted, simulated, measured, and user defined values."
#:IFC.xml:3851
msgid "IfcSchedulingTime_UserDefinedDataOrigin"
msgstr "UserDefinedDataOrigin"
msgid "IfcSchedulingTime_UserDefinedDataOrigin_DEFINITION"
msgstr "Value of the data origin if DataOrigin attribute is USERDEFINED."
#:IFC.xml:3857
msgid "IfcTaskDurationEnum"
msgstr "IfcTaskDurationEnum"
msgid "IfcTaskDurationEnum_DEFINITION"
msgstr "[[IfcTaskDurationEnum]] identifies how a time duration is measured. HISTORY New enumeration in IFC4. bSI Documentation"
#:IFC.xml:3862
msgid "IfcTaskTime"
msgstr "IfcTaskTime"
msgid "IfcTaskTime_DEFINITION"
msgstr "[[IfcTaskTime]] captures the time related information about a task including the different types actual or scheduled of starting and ending times. All given values should be provided by the application the IFC schema does not deal with dependencies between task time values. There is also no consistency check through where rules that guarantee a meaningful population of time values. Thus, an application is responsible to provide reasonable values and, if an application receives task times, has to make consistency checks by their own. [[IfcTaskTime]] furthermore provides a generic mechanism to differentiate between user given time values and time values derived from user given time values and other constraints such as work calendars and assigned resources. HISTORY New entity in IFC4, adapted from IfcScheduleTimeControl . Differently to IfcScheduleTimeControl it is also possible to differentiate duration time measures between the two possible types 1 work time and 2 elapsed time. bSI Documentation"
#:IFC.xml:3863
msgid "IfcTaskTime_DurationType"
msgstr "DurationType"
msgid "IfcTaskTime_DurationType_DEFINITION"
msgstr "Enables to specify the type of duration values for ScheduleDuration , ActualDuration and RemainingTime . The duration type is either work time or elapsed time."
#:IFC.xml:3868
msgid "IfcTaskTime_ScheduleDuration"
msgstr "ScheduleDuration"
msgid "IfcTaskTime_ScheduleDuration_DEFINITION"
msgstr "The amount of time which is scheduled for completion of a task. The value might be measured or somehow calculated, which is defined by X 0D ScheduleDataOrigin . The value is either given as elapsed time or work time, which is defined by DurationType . X 0D X 0D NOTE Scheduled Duration may be calculated as the time from scheduled start date to scheduled finish date."
#:IFC.xml:3873
msgid "IfcTaskTime_ScheduleStart"
msgstr "ScheduleStart"
msgid "IfcTaskTime_ScheduleStart_DEFINITION"
msgstr "The date on which a task is scheduled to be started. The value might be measured or somehow calculated, which is defined by X 0D ScheduleDataOrigin . X 0D NOTE The scheduled start date must be greater than or equal to the earliest start date."
#:IFC.xml:3878
msgid "IfcTaskTime_ScheduleFinish"
msgstr "ScheduleFinish"
msgid "IfcTaskTime_ScheduleFinish_DEFINITION"
msgstr "The date on which a task is scheduled to be finished. The value might be measured or somehow calculated, which is defined by ScheduleDataOrigin . X 0D NOTE The scheduled finish date must be greater than or equal to the earliest finish date."
#:IFC.xml:3883
msgid "IfcTaskTime_EarlyStart"
msgstr "EarlyStart"
msgid "IfcTaskTime_EarlyStart_DEFINITION"
msgstr "The earliest date on which a task can be started. It is a calculated value."
#:IFC.xml:3888
msgid "IfcTaskTime_EarlyFinish"
msgstr "EarlyFinish"
msgid "IfcTaskTime_EarlyFinish_DEFINITION"
msgstr "The earliest date on which a task can be finished. It is a calculated value."
#:IFC.xml:3893
msgid "IfcTaskTime_LateStart"
msgstr "LateStart"
msgid "IfcTaskTime_LateStart_DEFINITION"
msgstr "The latest date on which a task can be started. It is a calculated value."
#:IFC.xml:3898
msgid "IfcTaskTime_LateFinish"
msgstr "LateFinish"
msgid "IfcTaskTime_LateFinish_DEFINITION"
msgstr "The latest date on which a task can be finished. It is a calculated value."
#:IFC.xml:3903
msgid "IfcTaskTime_FreeFloat"
msgstr "FreeFloat"
msgid "IfcTaskTime_FreeFloat_DEFINITION"
msgstr "The amount of time during which the start or finish of a task may be varied without any effect on the overall programme of work. It is a calculated elapsed time value."
#:IFC.xml:3908
msgid "IfcTaskTime_TotalFloat"
msgstr "TotalFloat"
msgid "IfcTaskTime_TotalFloat_DEFINITION"
msgstr "The difference between the duration available to carry out a task and the scheduled duration of the task. It is a calculated elapsed time value. X 0D NOTE Total Float time may be calculated as being the difference between the scheduled duration of a task and the available duration from earliest start to latest finish. Float time may be either positive, zero or negative. Where it is zero or negative, the task becomes critical."
#:IFC.xml:3913
msgid "IfcTaskTime_IsCritical"
msgstr "IsCritical"
msgid "IfcTaskTime_IsCritical_DEFINITION"
msgstr "A flag which identifies whether a scheduled task is a critical item within the programme. X 0D NOTE A task becomes critical when the float time becomes zero or negative."
#:IFC.xml:3918
msgid "IfcTaskTime_StatusTime"
msgstr "StatusTime"
msgid "IfcTaskTime_StatusTime_DEFINITION"
msgstr "The date or time at which the status of the tasks within the schedule is analyzed."
#:IFC.xml:3923
msgid "IfcTaskTime_ActualDuration"
msgstr "ActualDuration"
msgid "IfcTaskTime_ActualDuration_DEFINITION"
msgstr "The actual duration of the task. It is a measured value. The value is either given as elapsed time or work time, which is defined by DurationType ."
#:IFC.xml:3928
msgid "IfcTaskTime_ActualStart"
msgstr "ActualStart"
msgid "IfcTaskTime_ActualStart_DEFINITION"
msgstr "The date on which a task is actually started. It is a measured value. X 0D NOTE The scheduled start date must be greater than or equal to the earliest start date. No constraint is applied to the actual start date with respect to the scheduled start date since a task may be started earlier than had originally been scheduled if circumstances allow."
#:IFC.xml:3933
msgid "IfcTaskTime_ActualFinish"
msgstr "ActualFinish"
msgid "IfcTaskTime_ActualFinish_DEFINITION"
msgstr "The date on which a task is actually finished."
#:IFC.xml:3938
msgid "IfcTaskTime_RemainingTime"
msgstr "RemainingTime"
msgid "IfcTaskTime_RemainingTime_DEFINITION"
msgstr "The amount of time remaining to complete a task. It is a predicted value. The value is either given as elapsed time or work time, which is defined by DurationType . X 0D NOTE The time remaining in which to complete a task may be determined both for tasks which have not yet started and those which have. Remaining time for a task not yet started has the same value as the scheduled duration. For a task already started, remaining time is calculated as the difference between the scheduled finish and the point of analysis."
#:IFC.xml:3943
msgid "IfcTaskTime_Completion"
msgstr "Completion"
msgid "IfcTaskTime_Completion_DEFINITION"
msgstr "The extent of completion expressed as a ratio or percentage. It is a measured value."
#:IFC.xml:3962
msgid "IfcTaskTimeRecurring"
msgstr "IfcTaskTimeRecurring"
msgid "IfcTaskTimeRecurring_DEFINITION"
msgstr "[[IfcTaskTimeRecurring]] is a recurring instance of [[IfcTaskTime]] for handling regularly scheduled or repetitive tasks. HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:3708
msgid "IfcTaskTimeRecurring_Recurrence"
msgstr "Recurrence"
msgid "IfcTaskTimeRecurring_Recurrence_DEFINITION"
msgstr "Recurrence"
#:IFC.xml:3965
msgid "IfcTimePeriod"
msgstr "IfcTimePeriod"
msgid "IfcTimePeriod_DEFINITION"
msgstr "[[IfcTimePeriod]] defines a time period given by a start and end time. Both time definitions consider the time zone and allow for the daylight savings offset. A time period is defined by a start and an end time, which is defined by [[IfcTime]] . The given time period should be within reasonable values for example, the start time must be before the end time . It is furthermore expected that both time definitions use the same time zone and, if given, the same daylight saving offset. HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:3966
msgid "IfcTimePeriod_StartTime"
msgstr "StartTime"
msgid "IfcTimePeriod_StartTime_DEFINITION"
msgstr "Start time of the time period."
#:IFC.xml:3971
msgid "IfcTimePeriod_EndTime"
msgstr "EndTime"
msgid "IfcTimePeriod_EndTime_DEFINITION"
msgstr "End time of the time period."
#:IFC.xml:3977
msgid "IfcTimeSeries"
msgstr "IfcTimeSeries"
msgid "IfcTimeSeries_DEFINITION"
msgstr "A time series is a set of a time stamped data entries. It allows a natural association of data collected over intervals of time. Time series can be regular or irregular. In regular time series data arrive predictably at predefined intervals. In irregular time series some or all time stamps do not follow a repetitive pattern and unpredictable bursts of data may arrive at unspecified points in time. The modeling of buildings and their performance involves data that are generated and recorded over a period of time. Such data cover a large spectrum, from weather data to schedules of all kinds to status measurements to reporting to everything else that has a time related aspect. Their correct placement in time is essential for their proper understanding and use, and the [[IfcTimeSeries]] subtypes provide the appropriate data structures to accommodate these types of data. HISTORY New entity in IFC2x2. bSI Documentation"
#:IFC.xml:4022
msgid "IfcTimeSeries_HasExternalReference"
msgstr "HasExternalReference"
msgid "IfcTimeSeries_HasExternalReference_DEFINITION"
msgstr "HasExternalReference"
#:IFC.xml:3978
msgid "IfcTimeSeries_Name"
msgstr "Name"
msgid "IfcTimeSeries_Name_DEFINITION"
msgstr "An unique name for the time series."
#:IFC.xml:3983
msgid "IfcTimeSeries_Description"
msgstr "Description"
msgid "IfcTimeSeries_Description_DEFINITION"
msgstr "A text description of the data that the series represents."
#:IFC.xml:3988
msgid "IfcTimeSeries_StartTime"
msgstr "StartTime"
msgid "IfcTimeSeries_StartTime_DEFINITION"
msgstr "The start time of a time series."
#:IFC.xml:3993
msgid "IfcTimeSeries_EndTime"
msgstr "EndTime"
msgid "IfcTimeSeries_EndTime_DEFINITION"
msgstr "The end time of a time series."
#:IFC.xml:3998
msgid "IfcTimeSeries_TimeSeriesDataType"
msgstr "TimeSeriesDataType"
msgid "IfcTimeSeries_TimeSeriesDataType_DEFINITION"
msgstr "The time series data type."
#:IFC.xml:4003
msgid "IfcTimeSeries_DataOrigin"
msgstr "DataOrigin"
msgid "IfcTimeSeries_DataOrigin_DEFINITION"
msgstr "The origin of a time series data."
#:IFC.xml:4008
msgid "IfcTimeSeries_UserDefinedDataOrigin"
msgstr "UserDefinedDataOrigin"
msgid "IfcTimeSeries_UserDefinedDataOrigin_DEFINITION"
msgstr "Value of the data origin if DataOrigin attribute is USERDEFINED."
#:IFC.xml:4013
msgid "IfcTimeSeries_Unit"
msgstr "Unit"
msgid "IfcTimeSeries_Unit_DEFINITION"
msgstr "The unit to be assigned to all values within the time series. Note that mixing units is not allowed. If the value is not given, the global unit for the type of [[IfcValue]] , as defined at [[IfcProject]].UnitsInContext is used."
#:IFC.xml:4034
msgid "IfcTimeSeriesDataTypeEnum"
msgstr "IfcTimeSeriesDataTypeEnum"
msgid "IfcTimeSeriesDataTypeEnum_DEFINITION"
msgstr "[[IfcTimeSeriesDataTypeEnum]] describes a type of time series data and is used to determine a value during the time series which is not explicitly specified. HISTORY New enumeration in IFC2x2. bSI Documentation"
#:IFC.xml:4043
msgid "IfcTimeSeriesValue"
msgstr "IfcTimeSeriesValue"
msgid "IfcTimeSeriesValue_DEFINITION"
msgstr "A time series value is a list of values that comprise the time series. At least one value must be supplied. Applications are expected to normalize values by applying the following three rules All time universal, local, daylight savings, and solar is normalized against the ISO 8601 standard GMT UTC Universal Coordinated Time . Any rollover is handled by the application providing the data. Rollover occurs, for example, when the measurement device resets itself while measuring and the recording data do not include the data measured before the reset. The normalized data refer to the preceding time unit. The time series example shown in Figure 1 below contains four time points Time a indicates the beginning of the time series and the associated datum has no relevance. Data at time points b, c and d are associated with values 1, 2 and 3, respectively. time series values .. .. .. .. .. .. figures ifctimeseries timeseriesvalue.gif Figure 1 Time series value HISTORY New entity in IFC2x2. bSI Documentation"
#:IFC.xml:4044
msgid "IfcTimeSeriesValue_ListValues"
msgstr "ListValues"
msgid "IfcTimeSeriesValue_ListValues_DEFINITION"
msgstr "A list of time series values. At least one value is required."
#:IFC.xml:4050
msgid "IfcWorkTime"
msgstr "IfcWorkTime"
msgid "IfcWorkTime_DEFINITION"
msgstr "[[IfcWorkTime]] defines time periods that are used by [[IfcWorkCalendar]] for either describing working times or non working exception times. Besides start and finish dates, a set of time periods can be given by various types of recurrence patterns. A work time should have a meaningful name that describes the time periods for example, working week, holiday name . Non recurring time periods should have a start date [[IfcWorkTime]].Start and a finish date [[IfcWorkTime]].Finish . In that case it is assumed that the time period begins at 0 00 on the start date and ends at 24 00 on the finish date. The start and finish date is optional if a recurrence pattern is given [[IfcWorkTime]].RecurrencePattern . They then restrict never ending recurrence patterns. HISTORY New entity in IFC4. bSI Documentation"
#:IFC.xml:3720
msgid "IfcWorkTime_RecurrencePattern"
msgstr "RecurrencePattern"
msgid "IfcWorkTime_RecurrencePattern_DEFINITION"
msgstr "RecurrencePattern"
#:IFC.xml:4051
msgid "IfcWorkTime_Start"
msgstr "Start"
msgid "IfcWorkTime_Start_DEFINITION"
msgstr "Start date of the work time 0 00 , that might be further X 0D restricted by a recurrence pattern."
#:IFC.xml:4056
msgid "IfcWorkTime_Finish"
msgstr "Finish"
msgid "IfcWorkTime_Finish_DEFINITION"
msgstr "End date of the work time 24 00 , that might be further X 0D restricted by a recurrence pattern."
#:IFC.xml:4087
msgid "IfcTimeOrRatioSelect"
msgstr "IfcTimeOrRatioSelect"
msgid "IfcTimeOrRatioSelect_DEFINITION"
msgstr "[[IfcTimeOrRatioSelect]] allows a value to be selected as being either a ratio or a time measure. HISTORY New select type in IFC4"
#:IFC.xml:4088
msgid "IfcDate"
msgstr "IfcDate"
msgid "IfcDate_DEFINITION"
msgstr "The IfcData identifies a particular calender day, expressed by year, calender month and day in month. It is expressed by a string value following a particular lexical representation. The lexical representation for [[IfcDate]] is the YYYY MM DD, where YYYY represents the calendar year, MM the ordinal number of the calendar month, and DD the ordinal number of the day within the calendar month. No left truncation is allowed. An optional following time zone qualifier is allowed. To accommodate year values outside the range from 0001 to 9999, additional digits can be added to the left of this representation and a preceding sign is allowed. NOTE See extended format representation of date as defined in ISO 8601. The restrictions defined in XML Schema Part 2 apply. HISTORY New type in IFC4. bSI Documentation"
#:IFC.xml:4092
msgid "IfcDateTime"
msgstr "IfcDateTime"
msgid "IfcDateTime_DEFINITION"
msgstr "The IfcDataTime identifies a particular point in time, expressed by hours, minutes and optional seconds elapsed within a calender day, expressed by year, calender month and day in month. It is expressed by a string value following a particular lexical representation. This lexical representation for IfcDataTime is YYYY MM DDThh mm ss where YYYY represent the year, MM the month and DD the day, preceded by an optional leading sign to indicate a negative year number. If the sign is omitted, is assumed. The letter T is the date time separator and hh , mm , ss represent hour, minute and second respectively. Additional digits can be used to increase the precision of fractional seconds if desired i.e the format ss.ss... with any number of digits after the decimal point is supported. The fractional seconds part is optional other parts of the lexical form are not optional. To accommodate year values greater than 9999 additional digits can be added to the left of this representation. Leading zeros are required if the year value would otherwise have fewer than four digits otherwise they are forbidden. The year 0000 is prohibited. NOTE See extended format representation of dateTime as defined in ISO 8601. The restrictions defined in XML Schema Part 2 apply. HISTORY New type in IFC4. bSI Documentation"
#:IFC.xml:4096
msgid "IfcDayInMonthNumber"
msgstr "IfcDayInMonthNumber"
msgid "IfcDayInMonthNumber_DEFINITION"
msgstr "[[IfcDayInMonthNumber]] is an integer that defines the position of the specified day in a month. Type INTEGER HISTORY New type in IFC1.5.1. .change ifc2x4 IFC4 CHANGE Where rule ValidRange added. bSI Documentation"
#:IFC.xml:4103
msgid "IfcDayInWeekNumber"
msgstr "IfcDayInWeekNumber"
msgid "IfcDayInWeekNumber_DEFINITION"
msgstr "The [[IfcDayInWeekNumber]] is an integer that defines the position of the specified day in a week. The positions have the following meaning that assigns the ordinal day number in the week to the Calendar day name. Ordinal day numbers map to calendar days as follows 1 Monday 2 Tuesday 3 Wednesday 4 Thursday 5 Friday 6 Saturday 7 Sunday bSI Documentation"
#:IFC.xml:4110
msgid "IfcDuration"
msgstr "IfcDuration"
msgid "IfcDuration_DEFINITION"
msgstr "The [[IfcDuration]] identifies a quantity of time or a lenght of an event occurring in time . This lexical representation for IfcDataTime is PnYnMnDTnHnMnS, where nY represents the number of years, nM the number of months, nD the number of days, T is the date time separator, nH the number of hours, nM the number of minutes and nS the number of seconds. The number of seconds can include decimal digits to arbitrary precision. EXAMPLE P2Y10M15DT10H30M20S duration of two years, 10 months, 15 days, 10 hours, 30 minutes and 20 seconds . NOTE See extended format representation of duration as defined in ISO 8601. The restrictions defined in XML Schema Part 2 apply. HISTORY New type in IFC4 bSI Documentation"
#:IFC.xml:4115
msgid "IfcMonthInYearNumber"
msgstr "IfcMonthInYearNumber"
msgid "IfcMonthInYearNumber_DEFINITION"
msgstr "[[IfcMonthInYearNumber]] is an integer that defines the position of the specified month in a year. Calendar month numbers map to calendar month names as follows 1 January 2 February 3 March 4 April 5 May 6 June 7 July 8 August 9 September 10 October 11 November 12 December Type INTEGER NOTE See definition of calendar month as defined in ISO 8601. .note HISTORY New type in IFC1.5.1. bSI Documentation"
#:IFC.xml:4122
msgid "IfcTime"
msgstr "IfcTime"
msgid "IfcTime_DEFINITION"
msgstr "The [[IfcTime]] identifies a time within a day, expressed by hours, minutes and second. It is expressed by a string value following a particular lexical representation. The lexical representation for [[IfcTime]] is hh mm ss where where hh represents hours, mm minutes and ss seconds. Additional digits can be used to increase the precision of fractional seconds if desired i.e the format ss.ss... A time zone indicator may be provided by a representation of the different to the Coordinated Universal Time. It is appended with a sign followed by hh and optionally mm. EXAMPLE 13 20 00 05 00 represents 1 20 pm for a time zone which is 5 hours behind Coordinated Universal Time such as Eastern Standard Time NOTE See extended format representation of time as defined in ISO 8601. The restrictions defined in XML Schema Part 2 apply. HISTORY New type in IFC4. bSI Documentation"
#:IFC.xml:4126
msgid "IfcTimeStamp"
msgstr "IfcTimeStamp"
msgid "IfcTimeStamp_DEFINITION"
msgstr "[[IfcTimeStamp]] is an indication of date and time by measuring the number of seconds which have elapsed since 1 January 1970, 00 00 00 UTC. Type INTEGER NOTE Defined in IEEE Std 1003.1. HISTORY New type in IFC1.5.1. bSI Documentation"