mirror of
https://github.com/IfcOpenShell/IfcOpenShell.git
synced 2026-08-09 17:31:45 +00:00
Line ending git fix?
This commit is contained in:
Dion Moult
@@ -3172,11 +3172,11 @@ It may be human readable (such as a key) or not (such as a handle or uuid) depen
|
||||
</EPM-HTML>"
|
||||
3776;Name;<EPM-HTML>Optional name to further specify the reference. It can provide a human readable identifier (which does not necessarily need to have a counterpart in the internal structure of the document).<EPM-HTML>
|
||||
3777;ExternalReferenceForResources;"<EPM-HTML>
|
||||
Reference to all associations between this external reference and objects within the <i>IfcResourceObjectSelect</i> that are tagged by the external reference.
|
||||
Reference to all associations between this external reference and objects within the <i>IfcResourceObjectSelect</i> that are tagged by the external reference.
|
||||
<blockquote>
|
||||
<small>
|
||||
<font color=""FF0000"">
|
||||
IFC2x4 CHANGE New inverse attribute added with upward compatibility.
|
||||
<font color=""FF0000"">
|
||||
IFC2x4 CHANGE New inverse attribute added with upward compatibility.
|
||||
</font>
|
||||
</small>
|
||||
</blockquote>
|
||||
@@ -3308,11 +3308,11 @@ The document information with which objects are associated.
|
||||
3847;Name;<EPM-HTML><P>A name used to identify or qualify the relationship.</P></EPM-HTML>
|
||||
3848;Description;<EPM-HTML><P>A description that may apply additional information about the relationship.</P></EPM-HTML>
|
||||
3850;RelatingReference;"<EPM-HTML>
|
||||
An external reference that can be used to tag an object within the range of <i>IfcResourceObjectSelect</i>.
|
||||
An external reference that can be used to tag an object within the range of <i>IfcResourceObjectSelect</i>.
|
||||
<blockquote>
|
||||
<p>
|
||||
<small>
|
||||
NOTE External references can be a library reference (for example a dictionary or a catalogue reference), a classification reference, or a documentation reference.
|
||||
<small>
|
||||
NOTE External references can be a library reference (for example a dictionary or a catalogue reference), a classification reference, or a documentation reference.
|
||||
</small>
|
||||
</p>
|
||||
</blockquote>
|
||||
@@ -4613,15 +4613,15 @@ The line of the axis of revolution.
|
||||
The curve used to define the sweeping operation. The solid is generated by sweeping the <i>SELF\IfcSweptAreaSolid.SweptArea</i> along the <i>Directrix</i>.
|
||||
</EPM-HTML>"
|
||||
5372;StartParam;"<EPM-HTML>
|
||||
The parameter value on the <i>Directrix</i> at which the sweeping operation commences. <font color=""#0000ff"">If no value is provided the start of the sweeping operation is at the start of the <i>Directrix</i>.</font>.
|
||||
<blockquote>
|
||||
<small><font color=""#ff0000"">IFC2x4 CHANGE The attribute has been changed to OPTIONAL with upward compatibility for file-based exchange.</font></small>
|
||||
The parameter value on the <i>Directrix</i> at which the sweeping operation commences. <font color=""#0000ff"">If no value is provided the start of the sweeping operation is at the start of the <i>Directrix</i>.</font>.
|
||||
<blockquote>
|
||||
<small><font color=""#ff0000"">IFC2x4 CHANGE The attribute has been changed to OPTIONAL with upward compatibility for file-based exchange.</font></small>
|
||||
</blockquote>
|
||||
</EPM-HTML>"
|
||||
5373;EndParam;"<EPM-HTML>
|
||||
The parameter value on the <i>Directrix</i> at which the sweeping operation ends. <font color=""#0000ff"">If no value is provided the end of the sweeping operation is at the end of the <i>Directrix</i>.</font>.
|
||||
<blockquote>
|
||||
<small><font color=""#ff0000"">IFC2x4 CHANGE The attribute has been changed to OPTIONAL with upward compatibility for file-based exchange.</font></small>
|
||||
The parameter value on the <i>Directrix</i> at which the sweeping operation ends. <font color=""#0000ff"">If no value is provided the end of the sweeping operation is at the end of the <i>Directrix</i>.</font>.
|
||||
<blockquote>
|
||||
<small><font color=""#ff0000"">IFC2x4 CHANGE The attribute has been changed to OPTIONAL with upward compatibility for file-based exchange.</font></small>
|
||||
</blockquote>
|
||||
</EPM-HTML>"
|
||||
5374;ReferenceSurface;"<EPM-HTML>
|
||||
@@ -4631,7 +4631,7 @@ The surface containing the <i>Directrix</i>.
|
||||
The curve used to define the sweeping operation. The solid is generated by sweeping the <i>SELF\IfcSweptAreaSolid.SweptArea</i> along the <i>Directrix</i>.
|
||||
</EPM-HTML>"
|
||||
5377;StartParam;"<EPM-HTML>
|
||||
The parameter value on the <i>Directrix</i> at which the sweeping operation commences. <span style=""color:blue"">If no value is provided the start of the sweeping operation is at the start of the <i>Directrix</i>.</span>
|
||||
The parameter value on the <i>Directrix</i> at which the sweeping operation commences. <span style=""color:blue"">If no value is provided the start of the sweeping operation is at the start of the <i>Directrix</i>.</span>
|
||||
</EPM-HTML>"
|
||||
5378;EndParam;"<EPM-HTML>
|
||||
The parameter value on the <i>Directrix</i> at which the sweeping operation ends. < style=""color:blue"">If no value is provided the end of the sweeping operation is at the end of the <i>Directrix</i>.</span>
|
||||
@@ -4691,15 +4691,15 @@ The <i>Radius</i> of the circular disk to be swept along the <i>directrix</i>. D
|
||||
This attribute is optional, if present it defines the radius of a circular hole in the centre of the disk.
|
||||
</EPM-HTML>"
|
||||
5414;StartParam;"<EPM-HTML>
|
||||
The parameter value on the <i>Directrix</i> at which the sweeping operation commences. <font color=""#0000ff"">If no value is provided the start of the sweeping operation is at the start of the <i>Directrix</i>.</font>.
|
||||
<blockquote>
|
||||
<small><font color=""#ff0000"">IFC2x4 CHANGE The attribute has been changed to OPTIONAL with upward compatibility for file-based exchange.</font></small>
|
||||
The parameter value on the <i>Directrix</i> at which the sweeping operation commences. <font color=""#0000ff"">If no value is provided the start of the sweeping operation is at the start of the <i>Directrix</i>.</font>.
|
||||
<blockquote>
|
||||
<small><font color=""#ff0000"">IFC2x4 CHANGE The attribute has been changed to OPTIONAL with upward compatibility for file-based exchange.</font></small>
|
||||
</blockquote>
|
||||
</EPM-HTML>"
|
||||
5415;EndParam;"<EPM-HTML>
|
||||
The parameter value on the <i>Directrix</i> at which the sweeping operation ends. <font color=""#0000ff"">If no value is provided the end of the sweeping operation is at the end of the <i>Directrix</i>.</font>.
|
||||
<blockquote>
|
||||
<small><font color=""#ff0000"">IFC2x4 CHANGE The attribute has been changed to OPTIONAL with upward compatibility for file-based exchange.</font></small>
|
||||
The parameter value on the <i>Directrix</i> at which the sweeping operation ends. <font color=""#0000ff"">If no value is provided the end of the sweeping operation is at the end of the <i>Directrix</i>.</font>.
|
||||
<blockquote>
|
||||
<small><font color=""#ff0000"">IFC2x4 CHANGE The attribute has been changed to OPTIONAL with upward compatibility for file-based exchange.</font></small>
|
||||
</blockquote>
|
||||
</EPM-HTML>"
|
||||
5420;FilletRadius;"<EPM-HTML>
|
||||
|
||||
|
@@ -1826,22 +1826,22 @@ IFC2x3 CHANGE The <i>IfcBoxAlignment</i> has been added.
|
||||
<li>bottom-right</li>
|
||||
</ul>
|
||||
|
||||
<blockquote class=""note"">
|
||||
NOTE The top-left is the default value.
|
||||
</blockquote>
|
||||
|
||||
<p>Figure 298 illustrates alignment values.</p>
|
||||
|
||||
<table>
|
||||
<blockquote class=""note"">
|
||||
NOTE The top-left is the default value.
|
||||
</blockquote>
|
||||
|
||||
<p>Figure 298 illustrates alignment values.</p>
|
||||
|
||||
<table>
|
||||
<tr><td><img alt=""9 alignment values"" src=""figures/IfcBoxAlignment_Fig1.gif"" height=""250"" width=""400""></td></tr>
|
||||
<tr><td><p class=""figure"">Figure 298 — Box alignment values</p></td></tr>
|
||||
</table>
|
||||
|
||||
<p>Figure 299 illustrates use of alignment values together with the placement and planar extent.</p>
|
||||
<table>
|
||||
<tr><td><img alt=""use with planar extent"" src=""figures/IfcBoxAlignment_Fig2.gif"" height=""300"" width=""500""></td></tr>
|
||||
<tr><td><p class=""figure"">Figure 299 — Box alignment examples</p></td></tr>
|
||||
</table>
|
||||
<table>
|
||||
<tr><td><img alt=""use with planar extent"" src=""figures/IfcBoxAlignment_Fig2.gif"" height=""300"" width=""500""></td></tr>
|
||||
<tr><td><p class=""figure"">Figure 299 — Box alignment examples</p></td></tr>
|
||||
</table>
|
||||
|
||||
<blockquote class=""history"">
|
||||
HISTORY New type in IFC2x2 Addendum2.
|
||||
|
||||
|
@@ -8904,8 +8904,8 @@ NOTE: The product representations are defined as representation maps (at the lev
|
||||
|
||||
<p>A energy conversion type is used to define the common properties of a
|
||||
energy conversion device that may be applied to many occurrences of that type.
|
||||
An energy conversion device is a building systems device that converts energy from one form into another such
|
||||
as a boiler (i.e., combusting gas to heat water), chiller (i.e., using a refrigeration cycle to cool a
|
||||
An energy conversion device is a building systems device that converts energy from one form into another such
|
||||
as a boiler (i.e., combusting gas to heat water), chiller (i.e., using a refrigeration cycle to cool a
|
||||
liquid), or a cooling coil (i.e., using the phase-change characteristics of a refrigerant to cool air).
|
||||
Energy conversion types (or the instantiable subtypes) may be exchanged
|
||||
without being already assigned to occurrences.</p>
|
||||
@@ -8938,7 +8938,7 @@ liquid), or a cooling coil (i.e., using the phase-change characteristics of a re
|
||||
|
||||
<p>A flow moving type is used to define the common properties of a
|
||||
flow moving device that may be applied to many occurrences of that type.
|
||||
A flow moving device is a device that is used to produce a pressure differential in a distribution system,
|
||||
A flow moving device is a device that is used to produce a pressure differential in a distribution system,
|
||||
such as a pump, fan, compressor, etc.
|
||||
Flow moving types (or the instantiable subtypes) may be exchanged
|
||||
without being already assigned to occurrences.</p>
|
||||
@@ -8971,8 +8971,8 @@ such as a pump, fan, compressor, etc.
|
||||
|
||||
<p>A flow controller type is used to define the common properties of a
|
||||
flow controller that may be applied to many occurrences of that type.
|
||||
A flow controller is a device that regulates flow within a distribution system, such as a valve in a piping
|
||||
system, modulating damper in an air distribution system, or electrical switch in an electrical distribution
|
||||
A flow controller is a device that regulates flow within a distribution system, such as a valve in a piping
|
||||
system, modulating damper in an air distribution system, or electrical switch in an electrical distribution
|
||||
system. Flow controller types (or the instantiable subtypes) may be exchanged
|
||||
without being already assigned to occurrences.</p>
|
||||
|
||||
@@ -9004,7 +9004,7 @@ system. Flow controller types (or the instantiable subtypes) may be exchanged
|
||||
|
||||
<p>A flow segment type is used to define the common properties of a
|
||||
flow segment that may be applied to many occurrences of that type.
|
||||
A flow segment is a section of a distribution system, such as a duct, pipe, conduit, etc. that typically has
|
||||
A flow segment is a section of a distribution system, such as a duct, pipe, conduit, etc. that typically has
|
||||
only two ports.
|
||||
Flow segment types (or the instantiable subtypes) may be exchanged
|
||||
without being already assigned to occurrences.</p>
|
||||
@@ -9051,8 +9051,8 @@ only two ports.
|
||||
|
||||
<p>A flow fitting type is used to define the common properties of a
|
||||
flow fitting that may be applied to many occurrences of that type.
|
||||
A flow fitting is a device that is used to interconnect flow segments or other fittings within a distribution
|
||||
system, such as a tee in a ducted system that branches flow into two directions, a junction box in an
|
||||
A flow fitting is a device that is used to interconnect flow segments or other fittings within a distribution
|
||||
system, such as a tee in a ducted system that branches flow into two directions, a junction box in an
|
||||
electrical distribution system, etc.
|
||||
Flow fitting types (or the instantiable subtypes) may be exchanged
|
||||
without being already assigned to occurrences.</p>
|
||||
@@ -9084,7 +9084,7 @@ HISTORY: New entity in IFC Release 2x2.<br>
|
||||
1123;IfcFlowTreatmentDeviceType;"<EPM-HTML>
|
||||
<p>The element type <i>IfcFlowTreatmentDeviceType</i> defines a list of commonly shared property set definitions of a flow treatment device and an optional set of product representations. It is used to define a flow treatment device specification (the specific product information that is common to all occurrences of that product type).</p>
|
||||
|
||||
<p>A flow treatment device is a device used to change the physical properties of the medium, such as an air, oil
|
||||
<p>A flow treatment device is a device used to change the physical properties of the medium, such as an air, oil
|
||||
or water filter (used to remove particulates from the fluid), or a duct silencer (used to attenuate noise). Flow treatment types (or the instantiable subtypes) may be exchanged without being already assigned to occurrences.</p>
|
||||
|
||||
<p>The occurrences of the <i>IfcFlowTreatmentDeviceType</i> are represented by instances of <i>IfcFlowTreatmentDevice</i> or its subtypes.</p>
|
||||
@@ -9418,7 +9418,7 @@ HISTORY: New entity in IFC R2x.<br>
|
||||
<p>The distribution flow element <i>IfcFlowStorageDevice</i> defines
|
||||
the occurrence of a device that participates in a distribution
|
||||
system and is used for temporary storage of a fluid
|
||||
such as a liquid or a gas (e.g., tank). Its type is defined by
|
||||
such as a liquid or a gas (e.g., tank). Its type is defined by
|
||||
<i>IfcFlowStorageDeviceType</i> or its subtypes.</p>
|
||||
|
||||
<blockquote>
|
||||
@@ -17685,8 +17685,8 @@ set for building system occurrences</li>
|
||||
|
||||
<p>An inventory is a list of items within an enterprise.</p>
|
||||
|
||||
<p>Various types of inventory can be included. These are identified by the range of values within the inventory type enumeration which includes space, asset, and furniture. User defined inventories can also be defined for lists of particular types of element such as may be required in operating and maintenance instructions. Such inventories should be constrained to contain a list of elements of a restricted type.<br/><br/>There are a number of actors that can be associated with an inventory, each actor having a role. Actors within the scope of the project are indicated using the <a href=""../../ifckernel/lexical/ifcrelassignstoactor.htm"">IfcRelAssignsToActor</a> relationship in which case roles should be defined through the <a href=""../../ifcactorresource/lexical/ifcactorrole.htm"">IfcActorRole</a> class; otherwise principal actors are identified as attributes of the class. In the existence of both, direct attributes take precedence.<br/><br/>There are a number of costs that can be associated with an inventory, each cost having a role. These are specified through the <i>CurrentValue</i> and <i>OriginalValue</i> attributes.</p
|
||||
|
||||
<p>Various types of inventory can be included. These are identified by the range of values within the inventory type enumeration which includes space, asset, and furniture. User defined inventories can also be defined for lists of particular types of element such as may be required in operating and maintenance instructions. Such inventories should be constrained to contain a list of elements of a restricted type.<br/><br/>There are a number of actors that can be associated with an inventory, each actor having a role. Actors within the scope of the project are indicated using the <a href=""../../ifckernel/lexical/ifcrelassignstoactor.htm"">IfcRelAssignsToActor</a> relationship in which case roles should be defined through the <a href=""../../ifcactorresource/lexical/ifcactorrole.htm"">IfcActorRole</a> class; otherwise principal actors are identified as attributes of the class. In the existence of both, direct attributes take precedence.<br/><br/>There are a number of costs that can be associated with an inventory, each cost having a role. These are specified through the <i>CurrentValue</i> and <i>OriginalValue</i> attributes.</p
|
||||
|
||||
><blockquote><font color=""#0000ff"" size=""-1"">HISTORY: New entity in IFC2.0. Modified in IFC2x4 to make all attributes optional and remove Where Rule.<br></font></blockquote>
|
||||
|
||||
<p><b><u>Assignment Use Definition</u></b></p>
|
||||
@@ -17704,8 +17704,8 @@ set for building system occurrences</li>
|
||||
|
||||
<p>An occupant is a type of actor that defines the form of occupancy of a property.</p>
|
||||
|
||||
<p>The principal purpose of <b>IfcOccupant</b> is to determine the nature of occupancy of a property for a particular actor. All characteristics relating to the actor (name and organization details) are inherited from the <a href=""../../ifckernel/lexical/ifcactor.htm"">IfcActor</a> class.</p
|
||||
|
||||
<p>The principal purpose of <b>IfcOccupant</b> is to determine the nature of occupancy of a property for a particular actor. All characteristics relating to the actor (name and organization details) are inherited from the <a href=""../../ifckernel/lexical/ifcactor.htm"">IfcActor</a> class.</p
|
||||
|
||||
><blockquote><font color=""#0000ff"" size=""-1"">HISTORY: New entity in IFC2x<br></font></blockquote>
|
||||
|
||||
<p><b><u>Assignment Use Definition</u></b></p>
|
||||
@@ -17749,8 +17749,8 @@ set for building system occurrences</li>
|
||||
|
||||
<p>Furniture defines complete furnishings such as a table, desk, chair, or cabinet, which may or may not be permanently attached to a building structure.</p>
|
||||
|
||||
<p>Occurrences of furniture that are built in (where the property <i>Pset_FurnitureTypeCommon.IsBuiltIn</i> is asserted to be TRUE) should have their connection relationship with a building element occurrence defined through the <a href=""../../ifcproductextension/lexical/ifcrelconnectselements.htm"">IfcRelConnectsElements</a> relationship.</p
|
||||
|
||||
<p>Occurrences of furniture that are built in (where the property <i>Pset_FurnitureTypeCommon.IsBuiltIn</i> is asserted to be TRUE) should have their connection relationship with a building element occurrence defined through the <a href=""../../ifcproductextension/lexical/ifcrelconnectselements.htm"">IfcRelConnectsElements</a> relationship.</p
|
||||
|
||||
><blockquote><font color=""#0000ff"" size=""-1"">HISTORY: New entity in IFC2x2<br></font></blockquote>
|
||||
|
||||
<p><b><u>Type Use Definition</u></b></p>
|
||||
|
||||
|
Can't render this file because it is too large.
|
@@ -4116,9 +4116,9 @@ HISTORY: New Enumeration in IFC Release 2.0.
|
||||
The <i>IfcCoolingTowerTypeEnum</i> contains the following:</p>
|
||||
<ul>
|
||||
<li><b>NATURALDRAFT</b>: Air flow is produced naturally.</li>
|
||||
<li><b>MECHANICALINDUCEDDRAFT</b>: Air flow is produced by a mechanical device, typically one or more fans, located on
|
||||
<li><b>MECHANICALINDUCEDDRAFT</b>: Air flow is produced by a mechanical device, typically one or more fans, located on
|
||||
the air outlet side of the cooling tower.</li>
|
||||
<li><b>MECHANICALFORCEDDRAFT</b>: Air flow is produced by a mechanical device, typically one or more fans, located on
|
||||
<li><b>MECHANICALFORCEDDRAFT</b>: Air flow is produced by a mechanical device, typically one or more fans, located on
|
||||
the inlet air side of the cooling tower.</li>
|
||||
<li><b>USERDEFINED</b>: User-defined cooling tower type.</li>
|
||||
<li><b>NOTDEFINED</b>: Undefined cooling tower type.</li>
|
||||
@@ -5033,12 +5033,12 @@ IFC2x4 CHANGE: Extended to include LOGICALXOR, LOGICALNOTAND and LOGICALNOTOR.
|
||||
</tr>
|
||||
<tr>
|
||||
<td>LOGICALAND</td>
|
||||
<td>Defines a relationship between operands whereby the result is true if all operands are true, i.e. false if at least
|
||||
<td>Defines a relationship between operands whereby the result is true if all operands are true, i.e. false if at least
|
||||
one operand is false.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>LOGICALOR</td>
|
||||
<td>Defines a relationship between operands whereby the result is true if at least one operand is true, i.e false if
|
||||
<td>Defines a relationship between operands whereby the result is true if at least one operand is true, i.e false if
|
||||
all operands are false.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -5047,19 +5047,19 @@ all operands are false.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>LOGICALNOTAND</td>
|
||||
<td>Defines a relationship between operands whereby the result is true if at least one operand is false, i.e false if
|
||||
<td>Defines a relationship between operands whereby the result is true if at least one operand is false, i.e false if
|
||||
all operands are true.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>LOGICALNOTOR</td>
|
||||
<td>Defines a relationship between operands whereby the result is true if all operands are false, i.e false if at least
|
||||
<td>Defines a relationship between operands whereby the result is true if all operands are false, i.e false if at least
|
||||
one operand is true.</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<h3>Use Definition</h3>
|
||||
|
||||
<p>The <I>IfcLogicalOperatorEnum</I>, when applied in a case of three operands, A, B and C, evaluates for each operator as
|
||||
<p>The <I>IfcLogicalOperatorEnum</I>, when applied in a case of three operands, A, B and C, evaluates for each operator as
|
||||
follows:
|
||||
</p>
|
||||
|
||||
@@ -5843,22 +5843,22 @@ IFC2x3 CHANGE This concept was initially introduced in IFC 2.0 as <i>IfcMo
|
||||
</epm-html>
"
|
||||
5269;IfcChangeActionEnum;"<epm-html>
|
||||
|
||||
<p><i>IfcChangeActionEnum</i> identifies the type of change that might have occurred to the object during the last session (for example, added, modified, deleted). This information is required in a partial model exchange scenario so that an application or model server will know how an object might have been affected by the previous application. Valid enumerations are:</p>
|
||||
<p><i>IfcChangeActionEnum</i> identifies the type of change that might have occurred to the object during the last session (for example, added, modified, deleted). This information is required in a partial model exchange scenario so that an application or model server will know how an object might have been affected by the previous application. Valid enumerations are:</p>
|
||||
|
||||
<ul>
|
||||
<li>NOCHANGE: Object has not been modified.</li>
|
||||
<li>MODIFIED: A modification to the object has been made by the user and application defined by the LastModifyingUser and LastModifyingApplication respectively.</li>
|
||||
<li>ADDED: The object has been created by the user and application defined by the OwningUser and OwningApplication respectively.</li>
|
||||
<li>DELETED: The object has been deleted by the user and application defined by the LastModifyingUser and LastModifyingApplication respectively.</li>
|
||||
<ul>
|
||||
<li>NOCHANGE: Object has not been modified.</li>
|
||||
<li>MODIFIED: A modification to the object has been made by the user and application defined by the LastModifyingUser and LastModifyingApplication respectively.</li>
|
||||
<li>ADDED: The object has been created by the user and application defined by the OwningUser and OwningApplication respectively.</li>
|
||||
<li>DELETED: The object has been deleted by the user and application defined by the LastModifyingUser and LastModifyingApplication respectively.</li>
|
||||
<li>NOTDEFINED: The change action is not known or has not been defined.</li>
|
||||
</ul>
|
||||
|
||||
<p>Consider Application A will create an IFC dataset that it wants to publish to others for modification and have the ability to subsequently merge these changes back into the original model. Before publication, it may want to set the <i>IfcChangeActionEnum</i> to NOCHANGE to establish a baseline so that other application changes can be easily identified. Application B then receives this IFC dataset and adds a new object and sets <i>IfcChangeActionEnum</i> to ADDED with Application B defined as the OwningApplication. Application B then modifies an existing object and (re)defines the LastModifiedDate to the time of the modification, LastModifyingUser to the <i>IfcPersonAndOrganization</i> making the change, and sets the LastModifyingApplication to Application B. When Application A receives this modified dataset, it can determine which objects have been added and modified by Application B and either merge or reject these changes as necessary. Consequently, the intent is that an application only modifies the value of <i>IfcChangeActionEnum</i> when it does something to the object, with the further intent that a model server is responsible for clearing the <i>IfcChangeActionEnum</i> back to NOCHANGE when it is ready to be republished.</p>
|
||||
|
||||
<blockquote class=""history"">
|
||||
</ul>
|
||||
|
||||
<p>Consider Application A will create an IFC dataset that it wants to publish to others for modification and have the ability to subsequently merge these changes back into the original model. Before publication, it may want to set the <i>IfcChangeActionEnum</i> to NOCHANGE to establish a baseline so that other application changes can be easily identified. Application B then receives this IFC dataset and adds a new object and sets <i>IfcChangeActionEnum</i> to ADDED with Application B defined as the OwningApplication. Application B then modifies an existing object and (re)defines the LastModifiedDate to the time of the modification, LastModifyingUser to the <i>IfcPersonAndOrganization</i> making the change, and sets the LastModifyingApplication to Application B. When Application A receives this modified dataset, it can determine which objects have been added and modified by Application B and either merge or reject these changes as necessary. Consequently, the intent is that an application only modifies the value of <i>IfcChangeActionEnum</i> when it does something to the object, with the further intent that a model server is responsible for clearing the <i>IfcChangeActionEnum</i> back to NOCHANGE when it is ready to be republished.</p>
|
||||
|
||||
<blockquote class=""history"">
|
||||
HISTORY: New enumeration in IFC R2.0. Modified in IFC2x4.
|
||||
</blockquote>
|
||||
|
||||
</blockquote>
|
||||
|
||||
</epm-html>
"
|
||||
5452;IfcBooleanOperator;"<EPM-HTML>
|
||||
<p><u>Definition from ISO/CD 10303-42:1992</u>: This type defines the three Boolean operators used in the definition of CSG solids.</p>
|
||||
|
||||
|
Reference in New Issue
Block a user