-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathDocProject.xml
359 lines (343 loc) · 25.7 KB
/
DocProject.xml
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
<?xml version="1.0" encoding="utf-8"?>
<DocProject xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Annexes>
<DocAnnex Name="Computer interpretable listings" UniqueId="fd206c24-846c-4c23-bf1b-826c38309b2c" Code="IFC4">
<Documentation>This annex contains a listing of the complete EXPRESS schema combining all definitions of clauses 5, 6, 7, and 8 without comments or other explanatory text. These listings are available in computer-interpretable form that may be parsed by computer.
Official schema publications for this release are at the following URLs:
* **IFC EXPRESS**: [http://www.buildingsmart-tech.org/ifc/review/IFC4x1/RC3/IFC4x1_RC3.exp](http://www.buildingsmart-tech.org/ifc/review/IFC4x1/RC3/IFC4x1_RC3.exp){ target="_blank"}
* **ifcXML XSD**: [http://www.buildingsmart-tech.org/ifc/review/IFC4x1/RC3/IFC4x1_RC3.xsd](http://www.buildingsmart-tech.org/ifc/review/IFC4x1/RC3/IFC4x1_RC3.xsd){ target="_blank"}
* **ifcXML Config**: [http://www.buildingsmart-tech.org/ifc/review/IFC4x1/RC3/IFC4x1_RC3_config.xml](http://www.buildingsmart-tech.org/ifc/review/IFC4x1/RC3/IFC4x1_RC3_config.xml){ target="_blank"}</Documentation>
</DocAnnex>
<DocAnnex Name="Alphabetical listings" UniqueId="65e0182b-6622-4757-a3d9-77225e2cb119" Code="IFC4" Status="Candidate">
<Documentation>This annex contains listings of definitions an alphabetical order according to identifier and language-specific name.</Documentation>
</DocAnnex>
<DocAnnex Name="Inheritance listings" UniqueId="89866beb-9946-4e73-875e-18545783f5c6">
<Documentation>This annex contains listings of entity definitions organized by inheritance.</Documentation>
</DocAnnex>
<DocAnnex Name="Diagrams" UniqueId="0532ee2f-2277-40d1-bfce-4ba0f53cc5c9">
<Documentation>This annex contains schema and instance diagrams.</Documentation>
</DocAnnex>
<DocAnnex Name="Examples" UniqueId="e2793a27-4484-4f4a-95eb-a7fa517b24be">
<Documentation>This annex contains examples that implement this specification.</Documentation>
</DocAnnex>
<DocAnnex Name="Change logs" UniqueId="6e2c10a0-0f1b-4502-9182-9f376a374ff8">
<Documentation>This annex contains change logs comparing this release with prior releases.
#### Update Log
Updates to this publication are described below.
{ .gridtable}
Date | Description
---- | -----------
2016-08-23 | Initial draft with proposed data types.
2016-08-30 | Added referents and types to support variable cross sections.
2016-10-10 | Added spatial entities for infrastructure.
2016-11-16 | Added example for bridge geometry using alignment curves and string lines based on offset curves.
2016-12-05 | Added IfcSectionedSolidHorizontal; removed IfcFixedDirectionSweptAreaSolid, IfcRelPositions, and spatial entities for infrastructure; updated examples to use new data types.
2017-01-20 | Added and corrected new Where rules, removed Schramm transition curve type (identical to biquadratic parabola), documented transition curve types and triangulated irregular networks.
2017-01-24 | Updated examples, corrected reported errors, added guidance for alignment curve types, added links for reporting issues.
2017-01-26 | Added example for IfcLinearPlacement, marked as Release Candidate 3
2017-03-02 | Deprecated IfcClothoidalArcSegment2D, corrected errors in examples, clarified descriptions for vertical curves.
2017-03-10 | Replaced IfcCartesianPointList2DLabelled with TagList attributes at IfcCartesianPointList2D and IfcCartesianPointList3D, subtyped orphaned alignment definitions from IfcGeometricRepresentationItem, fixed formatting errors in rules and examples.
2019-03-24 | Added bridge specific types and entities for the IFC Bridge extension. Added model views for bridges. See Change log for details</Documentation>
</DocAnnex>
</Annexes>
<NormativeReferences>
<DocReference Name="ISO 10303-11" UniqueId="1848a793-461c-47d3-b7ed-149824d71bbe">
<Documentation>Industrial automation systems and integration &mdash; Product data representation and exchange &mdash; Part 11: description methods: The EXPRESS Language Reference Manual</Documentation>
</DocReference>
<DocReference Name="ISO 10303-21" UniqueId="51d21cc3-e453-4d0c-94cc-077420cecac1">
<Documentation>Industrial automation systems and integration &mdash; Product data representation and exchange &mdash; Part 21: Implementation methods: Clear text encoding of the exchange structure</Documentation>
</DocReference>
<DocReference Name="ISO 10303-28" UniqueId="962a62ba-5fee-479c-a69d-b60e2b811a53">
<Documentation>Industrial automation systems and integration &mdash; Product data representation and exchange &mdash; Part 28: Implementation methods: XML representations of EXPRESS schemas and data, using XML schemas</Documentation>
</DocReference>
</NormativeReferences>
<InformativeReferences>
<DocReference Name="CSS-1" UniqueId="2f60ac08-1312-4d8d-a0e3-2b777a6eb9cb">
<Documentation>Cascading Style Sheets, level 1 &mdash; W3C Recommendation</Documentation>
</DocReference>
<DocReference Name="ISO 10303-1" UniqueId="09dd93d9-670a-4d59-aa0f-e230e535267f">
<Documentation>Industrial automation systems and integration &mdash; Product data representation and exchange &mdash; Part 1: Overview and fundamental principles</Documentation>
</DocReference>
<DocReference Name="ISO 10303-41" UniqueId="066d4470-575e-4ea0-bdff-a9e87c719b29">
<Documentation>Product data representation and exchange &mdash; Integrated generic resource &mdash; Fundamentals of product description and support</Documentation>
</DocReference>
<DocReference Name="ISO 10303-42" UniqueId="1a76cac6-f269-4cde-82af-751a632fb6a8">
<Documentation>Product data representation and exchange &mdash; Integrated generic resource &mdash; Geometric and topological representation</Documentation>
</DocReference>
<DocReference Name="ISO 10303-43" UniqueId="f00c8723-afea-4ca5-a8de-f96dbfe00fdc">
<Documentation>Product data representation and exchange &mdash; Integrated generic resource &mdash; Representation structures</Documentation>
</DocReference>
<DocReference Name="ISO 10303-46" UniqueId="0d68024b-47a7-4bc7-a470-911cadc6b050">
<Documentation>Product data representation and exchange &mdash; Integrated generic resource &mdash; Visual presentation</Documentation>
</DocReference>
<DocReference Name="ISO 10303-514" UniqueId="f771d154-91ec-483a-9e0f-64bedc7f4b42">
<Documentation>Product data representation and exchange &mdash; Application interpreted construct &mdash; Advanced boundary representation</Documentation>
</DocReference>
<DocReference Name="ISO 12006-3" UniqueId="f55b1b1e-2028-47d8-8ee5-5c327aa1a2f3">
<Documentation>Building construction &mdash; Organization of information about construction works &mdash; Part 3: Framework for object-oriented information</Documentation>
</DocReference>
<DocReference Name="ISO 639-1" UniqueId="db00bbff-02e7-4dfa-8e7b-2d1d648338b2">
<Documentation>Codes for the representation of names of languages &mdash; Part 1: Alpha-2 code</Documentation>
</DocReference>
<DocReference Name="ISO 639-2" UniqueId="9d2ee731-d68a-4679-a5e7-e0a78b11965c">
<Documentation>Codes for the representation of names of languages &mdash; Part 2: Alpha-3 code</Documentation>
</DocReference>
<DocReference Name="ISO 639-3" UniqueId="a09ccb62-e326-42b4-9a05-7dd7d6d2877f">
<Documentation>Codes for the representation of names of languages &mdash; Part 3: Alpha-3 code for comprehensive coverage of languages</Documentation>
</DocReference>
<DocReference Name="ISO 6707-1" UniqueId="14d1aa90-e804-42ec-993e-dfcbc7023045">
<Documentation>Building and civil engineering &mdash; Vocabulary &mdash; Part 1: General terms</Documentation>
</DocReference>
<DocReference Name="ISO 8601" UniqueId="17cf43a5-1caf-4dff-9d21-0618eb3ebc2a">
<Documentation>Data elements and interchange formats &mdash; Information Exchange &mdash; Representation of dates and times</Documentation>
</DocReference>
<DocReference Name="ISO/IEC 14772-1" UniqueId="badddda3-0d08-46f6-8fca-621b64295034">
<Documentation>Information technology &mdash; Computer graphics and image processing &mdash; The Virtual Reality Modeling Language &mdash; Part 1: Functional specification and UTF-8 encoding</Documentation>
</DocReference>
<DocReference Name="ISO/IEC 19775-1" UniqueId="c4c6a19e-d6e1-4b19-a696-b04f4ced36df">
<Documentation>Information technology &mdash; Computer graphics and image processing &mdash; Extensible 3D (X3D) &mdash; Part 1: Architecture and base components</Documentation>
</DocReference>
<DocReference Name="ISO/IEC 81346-12" UniqueId="52439504-5e35-46e1-b64e-1f6da70df041">
<Documentation>Industrial systems, installations and equipment and industrial products &mdash; Structuring principles and reference designations &mdash; Part 12: Buildings and building services</Documentation>
</DocReference>
<DocReference Name="ISO/IEC 8824-1" UniqueId="68060012-1926-4502-b5d2-0e1eb4054efe">
<Documentation>Information technology &mdash; Abstract Syntax Notation One (ASN.1) &mdash; Part 1: Specification of basic notation</Documentation>
</DocReference>
<DocReference Name="LandXML" UniqueId="e3dcb8fa-6730-43d5-b78f-e79d766d4033">
<Documentation>LandXML.org &mdash; Transition Curves in Road Design</Documentation>
</DocReference>
<DocReference Name="RFC 3986" UniqueId="e03625a9-98bf-4d4d-a4bc-84f212ec2e5f">
<Documentation>Uniform Resource Identifier (URI): Generic Syntax &mdash; Network Working Group NWG Standard</Documentation>
</DocReference>
<DocReference Name="RFC 5646" UniqueId="dbb10b69-00a3-43a4-a9e0-b73da88a285f">
<Documentation>Tags for Identifying Languages &mdash; Internet Engineering Task Force IETF Best Current Practice 47</Documentation>
</DocReference>
<DocReference Name="XML Schema Part 2" UniqueId="ffa91bdb-30bc-4dfb-abbb-cb7517724337">
<Documentation>XML Schema Part 2: Datatypes &mdash; W3C Recommendation</Documentation>
</DocReference>
</InformativeReferences>
<Terms>
<DocTerm Name="actor" UniqueId="4475e3f8-d524-4059-a93a-ad142ceb17e1">
<Documentation>person, an organization, or person acting on behalf of an organization
> NOTE A specialization of the general term object.</Documentation>
</DocTerm>
<DocTerm Name="attribute" UniqueId="c41363a6-d9e0-4752-b280-49d136a3b916">
<Documentation>unit of information within an entity, defined by a particular type or reference to a particular entity
> NOTE There are three kinds of attributes: direct attributes, inverse attributes and derived attributes.</Documentation>
<Terms>
<DocTerm Name="direct attribute" UniqueId="80a3bba7-3775-4651-9abf-323d3bf650de">
<Documentation>scalar values or collections including Set (unordered, unique), List (ordered), or Array (ordered, sparse) as defined in [ISO 10303-11]
> NOTE Similar to the term "field" in common programming languages.</Documentation>
</DocTerm>
<DocTerm Name="inverse attribute" UniqueId="e388a2b8-24fa-4937-96b1-9829419e4ef4">
<Documentation>unit of information defining queries for obtaining related data and enforcing referential integrity
> NOTE Similar to the term "navigation property" in entity-relational programming frameworks.</Documentation>
</DocTerm>
<DocTerm Name="derived attribute" UniqueId="19a5f4e8-f227-4220-9073-e74870af2a0c">
<Documentation>unit of information computed from other attributes using an expression defined in the schema</Documentation>
</DocTerm>
<DocTerm Name="constraints on attributes" UniqueId="686d037e-f9a8-4a61-831b-ef11e94a38e6">
<Documentation>data type restricting the values of attributes
> NOTE The most general constraint is about the existence of attribute values. There are basically two types: mandatory and optional attributes. Values of mandatory attributes must be provided whereas values of optional attributes may be omitted.
> NOTE For aggregation data types such as Set, List, or Array, the existence constraint is often refined by a minimal and maximal number of elements, which is also known as cardinality.</Documentation>
</DocTerm>
</Terms>
</DocTerm>
<DocTerm Name="classification" UniqueId="be7ae9de-9a6e-4d5b-9d72-392f636c08b9">
<Documentation>categorization, the act of distributing things into classes or categories of the same type</Documentation>
</DocTerm>
<DocTerm Name="constraint" UniqueId="aede2368-b9da-47af-b1e5-d2b766753a39">
<Documentation>restriction for a specified reason
> NOTE A specialization of the general term control.</Documentation>
</DocTerm>
<DocTerm Name="control" UniqueId="6cdc3322-2264-4e38-a555-71277a30dddd">
<Documentation>directive to meet specified requirements such as for scope, time, or cost
> NOTE A specialization of the general term object.</Documentation>
</DocTerm>
<DocTerm Name="dictionary" UniqueId="2b13c0dc-2e6f-45b3-b4e5-8fed105ee7a4">
<Documentation>collection of words, terms or concepts, with their definition</Documentation>
</DocTerm>
<DocTerm Name="element" UniqueId="f34155e6-4862-4a91-8000-deeecf4b1cbb">
<Documentation>tangible physical product that can be described by its shape representation, material representations, and other properties
> NOTE A specialization of the general term product.</Documentation>
<Terms>
<DocTerm Name="element occurrence" UniqueId="62b2365f-717f-4084-8334-3d64eac71306">
<Documentation>element's position within the project coordinate system and its containment within the spatial structure</Documentation>
</DocTerm>
</Terms>
</DocTerm>
<DocTerm Name="entity" UniqueId="5ba445f4-1bf1-45f7-84f7-5956d9181c5a">
<Documentation>class of information defined by common attributes and constraints as defined in [ISO 10303-11]
> NOTE Similar to the term "class" in common programming languages but describing data structure only (not behavior such as methods).</Documentation>
</DocTerm>
<DocTerm Name="external reference" UniqueId="001e056f-d0eb-4de0-ba7d-d032dfc1641b">
<Documentation>link to information outside the data set, with direct relevance to the specific information the link originates from inside the data set</Documentation>
</DocTerm>
<DocTerm Name="feature" UniqueId="5cb5ee7c-cfa0-47de-bf1d-bca254244bd1">
<Documentation>parametric information and additional property information modifiying the shape representation of an element to which it applies</Documentation>
</DocTerm>
<DocTerm Name="group" UniqueId="158e49d9-6fe6-4e9f-8c20-659684d47d5a">
<Documentation>collection of information that fulfills a specified purpose
> NOTE A specialization of the general term object.</Documentation>
</DocTerm>
<DocTerm Name="identification" UniqueId="3f4bf606-3d77-49ed-b363-2a15cfdace98">
<Documentation>capability to find, retrieve, report, change, or delete specific instances without ambiguity</Documentation>
</DocTerm>
<DocTerm Name="instance" UniqueId="2a8a64cc-87bc-42a2-bc82-2503e4f522bf">
<Documentation>occurrence of an entity
> NOTE Similar to the term "instance of a class" in object oriented programming.</Documentation>
</DocTerm>
<DocTerm Name="library" UniqueId="e23e1ee2-2574-4d4b-8516-40c454f3e511">
<Documentation>catalogue, database or holder of data, that is relevant to information in the data set
> NOTE It is information referenced from an external source that is not copied into the data set.</Documentation>
</DocTerm>
<DocTerm Name="model" UniqueId="83121c1b-c2f4-42fd-9a4f-a0f0ad5416a6">
<Documentation>a data set, governed by the structure of an underlying schema, to meet certain data requirements
> NOTE&nbsp; Information models and building information models are examples for a model.
> NOTE&nbsp; In scope of this standard IFC models are populations of the IFC schema.</Documentation>
</DocTerm>
<DocTerm Name="model view" UniqueId="7d1ca355-d45d-4af1-b982-535968fb4f6f">
<Documentation>subset of a schema, representing the data structure required to fullfil the data requirements within one or several exchange scenarios
> NOTE&nbsp; Beside being a subset of a schema, a model view (or model view definition) may also impose additional constraints to the population of the subset schema</Documentation>
<Terms>
<DocTerm Name="concept" UniqueId="8650d894-ddd1-4e56-b060-d6dfb9b4195a">
<Documentation>rules on using a subset of the schema structure identified as a concept template to enable a certain functionality within the context of a concept root contained in a model view
> NOTE&nbsp; The utilization of material definitions for a paticular concept root representing a wall is an example of a concept.</Documentation>
</DocTerm>
<DocTerm Name="concept template" UniqueId="b052bbe1-5b2a-402d-9442-4305403fc3a6">
<Documentation>the specification of a subset of the schema structure to enable a certain unit of functionality
> NOTE&nbsp; The identification of the entities, attributes and constraints needed to express a material definition independently on how it is utilized later in the context of a wall is an example of a concept template.</Documentation>
</DocTerm>
<DocTerm Name="concept root" UniqueId="d1065277-a0eb-4517-903e-acabc2e30de2">
<Documentation>an entity of a schema used to assign concepts to describe the required functionality
> NOTE&nbsp; A root concept often describes a model element, such as wall, air outlet, construction task, or similar, that is the root of a graph of connected entities and attributes defining the specific information items required, such as geometry, material, breakdown structure, etc.</Documentation>
</DocTerm>
</Terms>
</DocTerm>
<DocTerm Name="object" UniqueId="138eb22c-325c-4136-a3a9-9301a2cb1d17">
<Documentation>anything perceivable or conceivable that has a distinct existence, albeit not material</Documentation>
<Terms>
<DocTerm Name="object occurrence" UniqueId="c0836241-4778-40a1-911a-bb40a9b77966">
<Documentation>characteristics of an object as an individual
> NOTE Similar to "object", "instance", "individual" in other publications.</Documentation>
</DocTerm>
<DocTerm Name="object type" UniqueId="ea2e1c47-993e-4a78-8a67-69cca3d2ba12">
<Documentation>common characteristics shared by multiple object-occurrences
> NOTE Similar to "class", "template", "type" in other publications.</Documentation>
</DocTerm>
</Terms>
</DocTerm>
<DocTerm Name="process" UniqueId="c497955f-0eb5-4191-accd-8f44213e823e">
<Documentation>object-occurrence located in time, indicating "when"</Documentation>
</DocTerm>
<DocTerm Name="product" UniqueId="34bbbb1b-f741-4754-bc5f-023637d4bf3b">
<Documentation>physical or conceptual object that occurs in space
> NOTE It is specialization of the general term object.</Documentation>
</DocTerm>
<DocTerm Name="project" UniqueId="ccb1e357-de00-4d8f-97a5-d3c4ac8dfb54">
<Documentation>encapsulation of related information for a particular purpose providing context for information contained within
> NOTE Context information may include default measurement units or representation context and precision.</Documentation>
</DocTerm>
<DocTerm Name="property" UniqueId="810b5f89-761d-4f66-9c61-ea689a317835">
<Documentation>unit of information that is dynamically defined as a particular entity instance
> NOTE Similar to "late-bound" or "run-time" in programming terminology.</Documentation>
<Terms>
<DocTerm Name="property occurrence" UniqueId="6fddaecd-a666-4be4-9d7e-66b38bb1cd58">
<Documentation>unit of information providing a value for a property identified by name</Documentation>
</DocTerm>
<DocTerm Name="property template" UniqueId="99ba7b63-c330-484d-a1fe-8afd140310c1">
<Documentation>metadata for a property including name, description, and data type
> NOTE Similar in concept to "extension property" in common programming languages.</Documentation>
</DocTerm>
<DocTerm Name="property set occurrence" UniqueId="42c41b5c-b048-4f87-9ca3-906cf07424c8">
<Documentation>unit of information containing a set of property occurrences, each having a unique name within the property set</Documentation>
</DocTerm>
<DocTerm Name="property set template" UniqueId="d5efe4f1-7c65-4382-aaa7-6051d599e5e8">
<Documentation>set of property templates serving a common purpose and having applicability to objects of a particular entity
> NOTE Similar in concept to "extension class" in common programming languages.</Documentation>
</DocTerm>
</Terms>
</DocTerm>
<DocTerm Name="proxy" UniqueId="b1b74ac8-c633-4e63-b55b-b52b6d50d779">
<Documentation>object that does not hold a specific object type information
> NOTE a specialization of object occurrence.</Documentation>
</DocTerm>
<DocTerm Name="quantity" UniqueId="0921ed5b-4acc-4508-852d-6626da31ffd4">
<Documentation>measurement of a scope-based metric, specifically length, area, volume, weight, count, or time</Documentation>
</DocTerm>
<DocTerm Name="relationship" UniqueId="556a1caa-78c9-4f8d-9632-883c4e504cce">
<Documentation>unit of information describing an interaction between items</Documentation>
</DocTerm>
<DocTerm Name="representation" UniqueId="e39bac1f-7153-4b5c-9ef1-d771718483e2">
<Documentation>unit of information describing how an object is displayed, such as physical shape or topology</Documentation>
</DocTerm>
<DocTerm Name="resource" UniqueId="668bf36b-2c77-4d4d-97da-ab9d13ad7f12">
<Documentation>entity with limited availability such as materials, labor, or equipment
> NOTE a specialization of the general term object.
> NOTE the "resource definition data schemas" section is unrelated to this concept.</Documentation>
</DocTerm>
<DocTerm Name="schema" UniqueId="36e68fd4-23a3-464e-afc2-db2f42493f0d">
<Documentation>the definition of the structure to organize data for storage, exchange and sharing, using a formal language
> NOTE&nbsp; The formal languages EXPRESS [ISO 10303-11] and XML Schema [W3C Recommendation] are currently used to define the schemata of this standard</Documentation>
</DocTerm>
<DocTerm Name="space" UniqueId="a266f8d5-bd1d-4339-9d35-2e44ff0c49ff">
<Documentation>area or volume bounded actually or theoretically
> NOTE a specialization of the general term product.</Documentation>
</DocTerm>
<DocTerm Name="type" UniqueId="56ecd9a3-37c4-4d93-bc86-43b5fad62d52">
<Documentation>basic information construct derived from a primitive, an enumeration, or a select of entities
> NOTE Similar to the "Type" construct as defined in [ISO 10303-11].
> NOTE Similar in concept to "typedef" or "value type" in common programming languages.</Documentation>
<Terms>
<DocTerm Name="select" UniqueId="8239ba54-e5e5-49ea-aa8a-e714ed5c11bc">
<Documentation>construct that allows an attribute value to be one of multiple types or entities
> NOTE Similar to the "Select" construct as defined in [ISO 10303-11].
> NOTE Similar to a "marker interface" in common programming languages.</Documentation>
</DocTerm>
<DocTerm Name="enumeration" UniqueId="7f75d324-feac-4442-b68d-1e089f02af11">
<Documentation>construct that allows an attribute value to be one of multiple predefined values identified by name
> NOTE Similar to the "Enumeration" construct as defined in [ISO 10303-11].
> NOTE Similar in concept to "enum" in common programming languages.</Documentation>
</DocTerm>
</Terms>
</DocTerm>
</Terms>
<Abbreviations>
<DocAbbreviation Name="AEC" UniqueId="ad8a8f28-b2d7-47b8-b0b4-3b2054431287">
<Documentation>Architecture, Engineering, and Construction</Documentation>
</DocAbbreviation>
<DocAbbreviation Name="AEC-FM" UniqueId="d4c9338f-00a9-4927-99ba-e0c395b10453">
<Documentation>Architecture, Engineering, Construction, and Facilities Management</Documentation>
</DocAbbreviation>
<DocAbbreviation Name="BIM" UniqueId="0ccd0e83-d8e7-4926-a02d-1a0bad0a1002">
<Documentation>Building Information Modeling</Documentation>
</DocAbbreviation>
<DocAbbreviation Name="GUID" UniqueId="ede29532-1c66-4aa1-ac46-b43e1ad0e49d">
<Documentation>Globally Unique Identifier</Documentation>
</DocAbbreviation>
<DocAbbreviation Name="IFC" UniqueId="cd41aeea-aa58-4f73-a38f-b45e3210e1b6">
<Documentation>Industry Foundation Classes</Documentation>
</DocAbbreviation>
<DocAbbreviation Name="IFD" UniqueId="818d0474-78e7-4490-b1c1-3e04f759f14b">
<Documentation>International Framework for Dictionaries</Documentation>
</DocAbbreviation>
<DocAbbreviation Name="MVD" UniqueId="134733e0-5471-4477-a094-9d5e961e8fa5">
<Documentation>Model View Definition</Documentation>
</DocAbbreviation>
<DocAbbreviation Name="SPF" UniqueId="269e86ce-0537-4196-b9dc-892e03338e0e">
<Documentation>STEP Physical File</Documentation>
</DocAbbreviation>
<DocAbbreviation Name="STEP" UniqueId="eed23239-de91-48e2-bf28-ddae2770a4a5">
<Documentation>STandard for the Exchange of Product data</Documentation>
</DocAbbreviation>
<DocAbbreviation Name="URI" UniqueId="89732118-d64e-4cb3-9fd3-840865a4ccb3">
<Documentation>Uniform Resource Identifier</Documentation>
</DocAbbreviation>
<DocAbbreviation Name="UUID" UniqueId="a1dbfb0b-6e4d-4700-8f65-fe39bb03086b">
<Documentation>Universally Unique Identifier</Documentation>
</DocAbbreviation>
<DocAbbreviation Name="XML" UniqueId="0a0685e9-204e-4563-93eb-25063c9b16db">
<Documentation>Extensible Markup Language</Documentation>
</DocAbbreviation>
</Abbreviations>
</DocProject>