-
Notifications
You must be signed in to change notification settings - Fork 25
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #797 from larswik/GeoScience-usages
Geo science usages
- Loading branch information
Showing
12 changed files
with
202 additions
and
30 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 changes: 1 addition & 1 deletion
2
...ections/Core data schemas/Schemas/IfcProductExtension/Entities/IfcVoxelData/DocEntity.xml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 changes: 1 addition & 1 deletion
2
...t data schemas/Schemas/IfcSharedInfrastructureElements/Entities/IfcBorehole/DocEntity.xml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 changes: 1 addition & 1 deletion
2
...hemas/Schemas/IfcSharedInfrastructureElements/Entities/IfcGeoScienceElement/DocEntity.xml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,3 @@ | ||
| <?xml version="1.0" encoding="utf-8"?> | ||
| <DocEntity xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" Name="IfcGeoScienceElement" UniqueId="c765fabf-302f-4b26-b2bc-939f814c6eae" BaseDefinition="IfcElement" /> | ||
| <DocEntity xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="IfcGeoScienceElement" Name="IfcGeoScienceElement" UniqueId="c765fabf-302f-4b26-b2bc-939f814c6eae" BaseDefinition="IfcElement" /> | ||
|
|
2 changes: 1 addition & 1 deletion
2
...hemas/Schemas/IfcSharedInfrastructureElements/Entities/IfcGeoScienceFeature/DocEntity.xml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 changes: 1 addition & 1 deletion
2
...s/Schemas/IfcSharedInfrastructureElements/Entities/IfcGeoScienceObservation/DocEntity.xml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
27 changes: 27 additions & 0 deletions
27
...s/Object Composition/Aggregation/Complementary Data Composition/DocTemplateDefinition.xml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,27 @@ | ||
| <?xml version="1.0" encoding="utf-8"?> | ||
| <DocTemplateDefinition xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="Complementary_Data_Composition_0MQ9I7W893Nea$npjChteY" Name="Complementary Data Composition" UniqueId="16689487-8082-435e-893f-c73b4caf7a22" Type="IfcComplementaryData"> | ||
| <Rules> | ||
| <DocModelRuleAttribute Name="Decomposes" Identification="Decomposes"> | ||
| <Rules> | ||
| <DocModelRuleEntity Name="IfcRelAggregates"> | ||
| <Rules> | ||
| <DocModelRuleAttribute Name="RelatingObject" Identification="RelatingObject"> | ||
| <Rules> | ||
| <DocModelRuleEntity Name="IfcComplementaryData"> | ||
| <Rules> | ||
| <DocModelRuleAttribute Name="Name" Identification="ElementName"> | ||
| <Rules> | ||
| <DocModelRuleEntity Name="IfcLabel" /> | ||
| </Rules> | ||
| </DocModelRuleAttribute> | ||
| </Rules> | ||
| </DocModelRuleEntity> | ||
| </Rules> | ||
| </DocModelRuleAttribute> | ||
| </Rules> | ||
| </DocModelRuleEntity> | ||
| </Rules> | ||
| </DocModelRuleAttribute> | ||
| </Rules> | ||
| </DocTemplateDefinition> | ||
|
|
15 changes: 15 additions & 0 deletions
15
.../Object Composition/Aggregation/Complementary Data Composition/Documentation.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,15 @@ | ||
| Provision of an aggregation structure where the complementary data is part of another complementary data representing the composite. The part then provides, if such concepts are in scope of the Model View Definition, exclusively the following: | ||
|
|
||
| * _Body Geometry_ — The partial body shape representation and its placement; | ||
| * _Material_ — The material information for the part. | ||
|
|
||
| The part may also provide, in addition to the aggregate, more specifically the following: | ||
|
|
||
| * _Property Sets_ — The parts may have individual property sets assigned, solely or in addition to the composite; | ||
| * _Quantity Sets_ — The parts may have individual quantity sets assigned, solely or in addition to the composite. | ||
|
|
||
| The part should not be contained in the spatial hierarchy, i.e. the concept _Spatial Containment_ shall not be used at the level of parts. The part is contained in the spatial structure by the spatial containment of its composite. | ||
|
|
||
| The part should not be assigned to an _IfcProduct_, i.e. the concept _Product Assignment_ shall not be used at the level of parts. | ||
|
|
||
| > EXAMPLE An _IfcComplementaryData_ may be aggregated into a composite _IfcComplementaryData_ using the objectified relationship _IfcRelAggregates_, refering to it by its inverse attribute SELF\IfcObjectDefinition.Decomposes. Any subtype of _IfcComplementaryData_ can be an element assembly. In this case it should not be additionally contained in the spatial hierarchy, i.e. _SELF\IfcElement.ContainedInStructure_ should be NIL. |
27 changes: 27 additions & 0 deletions
27
...Object Composition/Aggregation/Complementary Data Decomposition/DocTemplateDefinition.xml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,27 @@ | ||
| <?xml version="1.0" encoding="utf-8"?> | ||
| <DocTemplateDefinition xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="Complementary_Data_Decomposition_2dPaQJZv96NvJhXffrZ$uJ" Name="Complementary Data Decomposition" UniqueId="a7664693-8f92-465f-94eb-869a758ffe13" Type="IfcComplementaryData"> | ||
| <Rules> | ||
| <DocModelRuleAttribute Name="IsDecomposedBy" Identification="IsDecomposedBy"> | ||
| <Rules> | ||
| <DocModelRuleEntity Name="IfcRelAggregates"> | ||
| <Rules> | ||
| <DocModelRuleAttribute Name="RelatedObjects" Identification="RelatedObjects"> | ||
| <Rules> | ||
| <DocModelRuleEntity Name="IfcComplementaryData"> | ||
| <Rules> | ||
| <DocModelRuleAttribute Name="Name" Identification="PartName"> | ||
| <Rules> | ||
| <DocModelRuleEntity Name="IfcLabel" /> | ||
| </Rules> | ||
| </DocModelRuleAttribute> | ||
| </Rules> | ||
| </DocModelRuleEntity> | ||
| </Rules> | ||
| </DocModelRuleAttribute> | ||
| </Rules> | ||
| </DocModelRuleEntity> | ||
| </Rules> | ||
| </DocModelRuleAttribute> | ||
| </Rules> | ||
| </DocTemplateDefinition> | ||
|
|
11 changes: 11 additions & 0 deletions
11
...bject Composition/Aggregation/Complementary Data Decomposition/Documentation.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| Provision of an aggregation structure where the complementary data, representing the composite, is decomposed into parts represented by other complementary data instances. | ||
|
|
||
| The composite then provides, if such concepts are in scope of the Model View Definition, exclusively the following: | ||
|
|
||
| * _Product Placement_ — the common object coordinate system to which the parts are placed relative | ||
|
|
||
| By default the following constraints apply to an element being decomposed by _Element Decomposition_: | ||
|
|
||
| * _Body Geometry_ — composite is constructed from the sum of the _Body Geometry_ of the parts; | ||
| * the composite shall not have an own _Body Geometry_, body geometry is provided at the parts; | ||
| * the composite shall not have an own _Material_ assignment, material is assigned to the parts. |
7 changes: 0 additions & 7 deletions
7
...uct Geometric Representation/Body Geometry/Body Voxel Geometry/Documentation.md
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.