diff --git a/IFC4x3/ModelViews/General Usage/DocModelView.xml b/IFC4x3/ModelViews/General Usage/DocModelView.xml
index 3f88bba3a..d63eae002 100644
--- a/IFC4x3/ModelViews/General Usage/DocModelView.xml
+++ b/IFC4x3/ModelViews/General Usage/DocModelView.xml
@@ -530,6 +530,60 @@ The **IfcActionRequest** may have assignments of its own using the [IfcRelAssign
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
@@ -557,6 +611,15 @@ The **IfcActionRequest** may have assignments of its own using the [IfcRelAssign
+
+
+
+
+
+
+
+
+
@@ -603,6 +666,51 @@ The **IfcActionRequest** may have assignments of its own using the [IfcRelAssign
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
@@ -2061,6 +2169,12 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they
Some _IfcBuildingElement_ may be represented by an surface as an abstract geometric representation. See each subtype for specific guidance.
+
+
+
+
+
+
@@ -4853,6 +4967,12 @@ The assignment of types to distribution element occurrences is vital for providi
+
+
+
+
+
+
@@ -10508,6 +10628,24 @@ Figure 1 illustrates project relationships with spatial structures, elements, an
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Sections/Core data schemas/Schemas/IfcProductExtension/Entities/IfcAlignmentSegment/DocEntity.xml b/IFC4x3/Sections/Core data schemas/Schemas/IfcProductExtension/Entities/IfcAlignmentSegment/DocEntity.xml
index 1d0c497af..e604903ef 100644
--- a/IFC4x3/Sections/Core data schemas/Schemas/IfcProductExtension/Entities/IfcAlignmentSegment/DocEntity.xml
+++ b/IFC4x3/Sections/Core data schemas/Schemas/IfcProductExtension/Entities/IfcAlignmentSegment/DocEntity.xml
@@ -1,5 +1,5 @@
-
+
diff --git a/IFC4x3/Templates/Object Assignment/Assignment to Group/Alignment Grouping/DocTemplateDefinition.xml b/IFC4x3/Templates/Object Assignment/Assignment to Group/Alignment Grouping/DocTemplateDefinition.xml
new file mode 100644
index 000000000..fce951b07
--- /dev/null
+++ b/IFC4x3/Templates/Object Assignment/Assignment to Group/Alignment Grouping/DocTemplateDefinition.xml
@@ -0,0 +1,27 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Object Assignment/Assignment to Group/Survey Elements Grouping/DocTemplateDefinition.xml b/IFC4x3/Templates/Object Assignment/Assignment to Group/Survey Elements Grouping/DocTemplateDefinition.xml
new file mode 100644
index 000000000..c39299175
--- /dev/null
+++ b/IFC4x3/Templates/Object Assignment/Assignment to Group/Survey Elements Grouping/DocTemplateDefinition.xml
@@ -0,0 +1,58 @@
+
+
+
+
+ <p>The assignment of survey annotations, such as point and lines, to a group. The template can be used when the order of the elements is irrelevant, for example for point clouds or collections of survey string lines.</p>
+<p>For ordered list of survey elements, use the Survey Elements Nesting template.</p>
+<blockquote>
+<p>NOTE Having an <em>IfcGroup</em> grouping a list of <em>IfcAnnotation</em>'s, properties can be associated to each annotation (i.e., to each point and line) as well as to the group collecting all survey elements.</p>
+</blockquote>
+<p></p>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Object Association/Material Association/Material Set/DocTemplateDefinition.xml b/IFC4x3/Templates/Object Association/Material Association/Material Set/DocTemplateDefinition.xml
new file mode 100644
index 000000000..8dc9b2d82
--- /dev/null
+++ b/IFC4x3/Templates/Object Association/Material Association/Material Set/DocTemplateDefinition.xml
@@ -0,0 +1,107 @@
+
+
+
+
+ <p>Composite or multiple materials may be described using a material set. There are three types of material sets to choose from:</p>
+<ul>
+<li>Layer sets - layered materials with a thickness that fills a boundary</li>
+<li>Profile sets - when materials are extruded along a profiled shape</li>
+<li>Constituent sets - when materials are either homogenously mixed, or arbitrarily placed</li>
+</ul>
+<blockquote>
+<p>EXAMPLE A wall or slab may use a layer set. A beam, column, pipe, or duct may use a profile set, even if it only has one profile. Composite beams may be made out of multiple profiles. Concrete may use a constituent set for portions of sand and cement. A window frame may also use a constituent set for one material for its frame and another material for its glazing portion.</p>
+</blockquote>
+<p>The material is defined by either <em>IfcMaterialLayerSet</em>, <em>IfcMaterialProfileSet</em>, or <em>IfcMaterialConstituentSet</em> and related using <em>IfcRelAssociatesMaterial</em>.RelatingMaterial. Independent of the material used, each layer, profile, or constituent within the set may be identified using a name and category.</p>
+<p>```
+concept {
+ IfcObjectDefinition:HasAssociations -> IfcRelAssociatesMaterial:RelatedObjects
+ IfcRelAssociatesMaterial:RelatingMaterial -> IfcMaterialLayerSet
+ IfcRelAssociatesMaterial:RelatingMaterial -> IfcMaterialProfileSet
+ IfcRelAssociatesMaterial:RelatingMaterial -> IfcMaterialConstituentSet</p>
+<pre></pre>
+<p>}
+```</p>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Object Composition/Aggregation/Alignment Aggregation To Project/DocTemplateDefinition.xml b/IFC4x3/Templates/Object Composition/Aggregation/Alignment Aggregation To Project/DocTemplateDefinition.xml
new file mode 100644
index 000000000..b8ac81542
--- /dev/null
+++ b/IFC4x3/Templates/Object Composition/Aggregation/Alignment Aggregation To Project/DocTemplateDefinition.xml
@@ -0,0 +1,37 @@
+
+
+
+
+ <p>Every <em>IfcAlignment</em> must be related to <em>IfcProject</em> using the <em>IfcRelAggregates</em> relationship - either directly or indirectly. The indirect case is when a child alignment is aggregated to a parent alignment. In this case, only the parent alignment must be related to <em>IfcProject</em>.</p>
+<p>```
+concept {
+ IfcAlignment:Decomposes -> IfcRelAggregates:RelatedObjects
+ IfcAlignment:Name -> IfcLabel
+ IfcRelAggregates:RelatingObject -> IfcProject:IsDecomposedBy</p>
+<pre></pre>
+<p>}
+```</p>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Object Composition/Nesting/Alignment Layouts/Alignment Layout - Horizontal, Vertical and Cant/DocTemplateDefinition.xml b/IFC4x3/Templates/Object Composition/Nesting/Alignment Layouts/Alignment Layout - Horizontal, Vertical and Cant/DocTemplateDefinition.xml
new file mode 100644
index 000000000..d58959f77
--- /dev/null
+++ b/IFC4x3/Templates/Object Composition/Nesting/Alignment Layouts/Alignment Layout - Horizontal, Vertical and Cant/DocTemplateDefinition.xml
@@ -0,0 +1,104 @@
+
+
+
+
+ <p>Nesting relationships between <em>IfcAlignment</em> and the three layouts, with respective segments, that may define it (i.e., <em>IfcAlignmentHorizontal</em>, <em>IfcAlignmentVerticalSegment</em>, <em>IfcAlignmentCant</em>).</p>
+<p>When defining the list of segments for the business logic (i.e., <em>IfcAlignmentHorizontalSegment</em>, <em>IfcAlignmentVerticalSegment</em>, <em>IfcAlignmentCantSegment</em>):</p>
+<ol>
+<li>A <strong>zero-length segment</strong> shall be added, at the end of the list of segments for <em>IfcAlignmentSegment.DesignParameters</em>.</li>
+<li>If the geometry definition is also present, then each of the zero-length segments shall have a <em>IfcCurveSegment</em> counterpart - of length zero.</li>
+</ol>
+<p></p>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Object Composition/Nesting/Alignment Layouts/Alignment Layout - Reusing Horizontal Layout/DocTemplateDefinition.xml b/IFC4x3/Templates/Object Composition/Nesting/Alignment Layouts/Alignment Layout - Reusing Horizontal Layout/DocTemplateDefinition.xml
new file mode 100644
index 000000000..99ff5d5af
--- /dev/null
+++ b/IFC4x3/Templates/Object Composition/Nesting/Alignment Layouts/Alignment Layout - Reusing Horizontal Layout/DocTemplateDefinition.xml
@@ -0,0 +1,174 @@
+
+
+
+
+ <p>Nesting and aggregation relationships between <em>IfcAlignment</em>'s and their layouts, in the case where multiple alignments re-use the same horizontal layout definition.</p>
+<p>In the diagram below is an example of a <em>parent</em> alignment, with the horizontal layout, and two <em>child</em> alignments, one with a vertical layout, and the other with a vertical and a cant layout; both re-using the definition of the horizontal layout from the <em>parent</em> alignment.</p>
+<p>When defining the list of segments for the business logic (i.e., <em>IfcAlignmentHorizontalSegment</em>, <em>IfcAlignmentVerticalSegment</em>, <em>IfcAlignmentCantSegment</em>):</p>
+<ol>
+<li>A <strong>zero-length segment</strong> shall be added, at the end of the list of segments for <em>IfcAlignmentSegment.DesignParameters</em>.</li>
+<li>If the geometry definition is also present, then each of the zero-length segments shall have a <em>IfcCurveSegment</em> counterpart - of length zero.</li>
+</ol>
+<p></p>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Object Composition/Nesting/Alignment Layouts/DocTemplateDefinition.xml b/IFC4x3/Templates/Object Composition/Nesting/Alignment Layouts/DocTemplateDefinition.xml
new file mode 100644
index 000000000..1439ca85f
--- /dev/null
+++ b/IFC4x3/Templates/Object Composition/Nesting/Alignment Layouts/DocTemplateDefinition.xml
@@ -0,0 +1,33 @@
+
+
+
+
+ <p>A single alignment may be described by one ore more of the following layouts:</p>
+<ul>
+<li>a horizontal layout (<em>IfcAlignmentHorizontal</em>), defined in the x/y plane of the engineering coordinate system.</li>
+<li>an accompanying vertical layout (<em>IfcAlignmentVertical</em>), defined along the horizontal layout in the distance along / z coordinate space.</li>
+<li>an accompanying cant layout (<em>IfcAlignmentCant</em>), defined as lateral inclination along the horizontal layout.</li>
+</ul>
+<p>These 3 layouts may be used in different configurations. See <strong>Alignment Layout - Horizontal, Vertical and Cant</strong> and <strong>Alignment Layout - Reusing Horizontal Layout</strong> for details.</p>
+<p></p>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Object Composition/Nesting/Survey Elements Nesting/DocTemplateDefinition.xml b/IFC4x3/Templates/Object Composition/Nesting/Survey Elements Nesting/DocTemplateDefinition.xml
new file mode 100644
index 000000000..4f8416e90
--- /dev/null
+++ b/IFC4x3/Templates/Object Composition/Nesting/Survey Elements Nesting/DocTemplateDefinition.xml
@@ -0,0 +1,64 @@
+
+
+
+
+ <p>The ordered arrangement of survey annotations, such as point, lines, curves.</p>
+<p>For set of survey elements where the order of items is not relevant (e.g., point clouds or collections of survey string lines), the Survey Elements Grouping template can be used.</p>
+<blockquote>
+<p>NOTE Having an <em>IfcAnnotation</em> nesting a list of <em>IfcAnnotation</em>'s, properties can be associated to the each annotation of the list (i.e., to each point and line) as well as to the annotation collecting all survey elements.</p>
+</blockquote>
+<p></p>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Object Connectivity/Alignment Spatial Reference/DocTemplateDefinition.xml b/IFC4x3/Templates/Object Connectivity/Alignment Spatial Reference/DocTemplateDefinition.xml
new file mode 100644
index 000000000..f5d3fff98
--- /dev/null
+++ b/IFC4x3/Templates/Object Connectivity/Alignment Spatial Reference/DocTemplateDefinition.xml
@@ -0,0 +1,36 @@
+
+
+
+
+ <p>```
+concept {
+ IfcAlignment:ReferencedInStructures -> IfcRelReferencedInSpatialStructure:RelatedElements
+ IfcAlignment:Name -> IfcLabel_0
+ IfcRelReferencedInSpatialStructure:RelatingStructure -> IfcSpatialElement:ReferencesElements</p>
+<pre></pre>
+<p>}
+```</p>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Object Definition/Property Sets/Property Sets for Contexts/DocTemplateDefinition.xml b/IFC4x3/Templates/Object Definition/Property Sets/Property Sets for Contexts/DocTemplateDefinition.xml
new file mode 100644
index 000000000..17930d1dd
--- /dev/null
+++ b/IFC4x3/Templates/Object Definition/Property Sets/Property Sets for Contexts/DocTemplateDefinition.xml
@@ -0,0 +1,57 @@
+
+
+
+
+ <p>The concept template <em>Property Sets for Contexts</em> describes how an context can be related to a single or multiple property sets. A property set contains a single or multiple properties. The data types of an individual property are single value, enumerated value, bounded value, table value, reference value, list value, and combination of property occurrences.</p>
+<p></p>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Object Definition/Property Sets/Property Sets for Materials/DocTemplateDefinition.xml b/IFC4x3/Templates/Object Definition/Property Sets/Property Sets for Materials/DocTemplateDefinition.xml
new file mode 100644
index 000000000..7f2c19f74
--- /dev/null
+++ b/IFC4x3/Templates/Object Definition/Property Sets/Property Sets for Materials/DocTemplateDefinition.xml
@@ -0,0 +1,68 @@
+
+
+
+
+ <p>The concept template <em>Property Sets for Materials</em> describes how a material can be related to a single or multiple property sets. A property set contains a single or multiple properties. The data type of an individual property can be one of single, enumerated, value, table, reference or list value, and combination of property occurrences.</p>
+<p>NOTE: An IfcMaterial is not an IfcObject. For legacy reasons, this concept is listed under <em>Object Definition</em>. In future versions of the standard the various property set association mechanisms will likely be unified. In the current version of this template, there is no mechanism to further guide the applicability in a way similar to how applicability can be tailored to individual predefined types of leaf entities of IfcObject that feature the PredefinedType attribute. In future versions of the standard there will likely be the possibility to make property sets applicable to specific categories of IfcMaterial.</p>
+<p>Property Sets applicable to this template will carry the IfcPropertySetTemplateTypeEnum "PSET_MATERIALDRIVEN".</p>
+<p>```
+concept {
+ IfcMaterialDefinition:HasProperties -> IfcMaterialProperties:Material</p>
+<pre></pre>
+<p>}
+```</p>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Object Definition/Property Sets/Property Sets for Profiles/DocTemplateDefinition.xml b/IFC4x3/Templates/Object Definition/Property Sets/Property Sets for Profiles/DocTemplateDefinition.xml
new file mode 100644
index 000000000..5e18ed5c1
--- /dev/null
+++ b/IFC4x3/Templates/Object Definition/Property Sets/Property Sets for Profiles/DocTemplateDefinition.xml
@@ -0,0 +1,66 @@
+
+
+
+
+ <p>The concept template <em>Property Sets for Profiles</em> describes how a profile can be related to a single or multiple property sets. A property set contains a single or multiple properties. The data type of an individual property can be one of single, enumerated, value, table, reference or list value, and combination of property occurrences.</p>
+<p>NOTE: An <em>IfcProfileDef</em> is not an <em>IfcObject</em>. For legacy reasons, this concept is listed under <em>Object Definition</em>. In future versions of the standard the various property set association mechanisms will likely be unified.</p>
+<p>Property Sets applicable to this template will carry the <em>IfcPropertySetTemplateTypeEnum</em> "PSET_PROFILEDRIVEN".</p>
+<p>```
+concept {
+ IfcProfileDef:HasProperties -> IfcProfileProperties:ProfileDefinition</p>
+<pre></pre>
+<p>}
+```</p>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Partial Templates/Profile Definition/Derived Profile Definition/Composite Profile Definition/DocTemplateDefinition.xml b/IFC4x3/Templates/Partial Templates/Profile Definition/Derived Profile Definition/Composite Profile Definition/DocTemplateDefinition.xml
new file mode 100644
index 000000000..3e7b14e01
--- /dev/null
+++ b/IFC4x3/Templates/Partial Templates/Profile Definition/Derived Profile Definition/Composite Profile Definition/DocTemplateDefinition.xml
@@ -0,0 +1,29 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Partial Templates/Profile Definition/Derived Profile Definition/DocTemplateDefinition.xml b/IFC4x3/Templates/Partial Templates/Profile Definition/Derived Profile Definition/DocTemplateDefinition.xml
new file mode 100644
index 000000000..d31defe17
--- /dev/null
+++ b/IFC4x3/Templates/Partial Templates/Profile Definition/Derived Profile Definition/DocTemplateDefinition.xml
@@ -0,0 +1,19 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Partial Templates/Profile Definition/Derived Profile Definition/Transformed Profile Definition/DocTemplateDefinition.xml b/IFC4x3/Templates/Partial Templates/Profile Definition/Derived Profile Definition/Transformed Profile Definition/DocTemplateDefinition.xml
new file mode 100644
index 000000000..93e08792a
--- /dev/null
+++ b/IFC4x3/Templates/Partial Templates/Profile Definition/Derived Profile Definition/Transformed Profile Definition/DocTemplateDefinition.xml
@@ -0,0 +1,35 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Product Shape/Product Geometric Representation/Alignment Geometry/Alignment Geometry - Horizontal and Vertical/DocTemplateDefinition.xml b/IFC4x3/Templates/Product Shape/Product Geometric Representation/Alignment Geometry/Alignment Geometry - Horizontal and Vertical/DocTemplateDefinition.xml
new file mode 100644
index 000000000..3db810994
--- /dev/null
+++ b/IFC4x3/Templates/Product Shape/Product Geometric Representation/Alignment Geometry/Alignment Geometry - Horizontal and Vertical/DocTemplateDefinition.xml
@@ -0,0 +1,146 @@
+
+
+
+
+ <p>This concept template applies to alignments defined by an horizontal and a vertical layouts.</p>
+<p>For the <em>IfcCompositeCurve</em>:
+* <em>RepresentationIdentifier</em> = 'FootPrint'
+* <em>RepresentationType</em> = 'Curve2D'</p>
+<p>For the <em>IfcGradientCurve</em>:
+* <em>RepresentationIdentifier</em> = 'Axis'
+* <em>RepresentationType</em> = 'Curve3D'</p>
+<p>When defining the list of segments for the business logic (i.e., <em>IfcAlignmentHorizontalSegment</em>, <em>IfcAlignmentVerticalSegment</em>, <em>IfcAlignmentCantSegment</em>):</p>
+<ol>
+<li>A <strong>zero-length segment</strong> shall be added, at the end of the list of segments for <em>IfcAlignmentSegment.DesignParameters</em>.</li>
+<li>If the geometry definition is also present, then each of the zero-length segments shall have a <em>IfcCurveSegment</em> counterpart - of length zero.</li>
+</ol>
+<p></p>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Product Shape/Product Geometric Representation/Alignment Geometry/Alignment Geometry - Horizontal, Vertical and Cant/DocTemplateDefinition.xml b/IFC4x3/Templates/Product Shape/Product Geometric Representation/Alignment Geometry/Alignment Geometry - Horizontal, Vertical and Cant/DocTemplateDefinition.xml
new file mode 100644
index 000000000..7b1801be5
--- /dev/null
+++ b/IFC4x3/Templates/Product Shape/Product Geometric Representation/Alignment Geometry/Alignment Geometry - Horizontal, Vertical and Cant/DocTemplateDefinition.xml
@@ -0,0 +1,159 @@
+
+
+
+
+ <p>This concept template applies to alignments defined by an horizontal, a vertical and a cant layouts.</p>
+<p>For the <em>IfcCompositeCurve</em>:
+* <em>RepresentationIdentifier</em> = 'FootPrint'
+* <em>RepresentationType</em> = 'Curve2D'</p>
+<p>For the <em>IfcSegmentedReferenceCurve</em>:
+* <em>RepresentationIdentifier</em> = 'Axis'
+* <em>RepresentationType</em> = 'Curve3D'</p>
+<p>When defining the list of segments for the business logic (i.e., <em>IfcAlignmentHorizontalSegment</em>, <em>IfcAlignmentVerticalSegment</em>, <em>IfcAlignmentCantSegment</em>):</p>
+<ol>
+<li>A <strong>zero-length segment</strong> shall be added, at the end of the list of segments for <em>IfcAlignmentSegment.DesignParameters</em>.</li>
+<li>If the geometry definition is also present, then each of the zero-length segments shall have a <em>IfcCurveSegment</em> counterpart - of length zero.</li>
+</ol>
+<p></p>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Product Shape/Product Geometric Representation/Alignment Geometry/Alignment Geometry - Horizontal/DocTemplateDefinition.xml b/IFC4x3/Templates/Product Shape/Product Geometric Representation/Alignment Geometry/Alignment Geometry - Horizontal/DocTemplateDefinition.xml
new file mode 100644
index 000000000..aabd103a2
--- /dev/null
+++ b/IFC4x3/Templates/Product Shape/Product Geometric Representation/Alignment Geometry/Alignment Geometry - Horizontal/DocTemplateDefinition.xml
@@ -0,0 +1,95 @@
+
+
+
+
+ <p>This concept template applies to alignments defined only by an horizontal layout.</p>
+<ul>
+<li><em>RepresentationIdentifier</em> = 'Axis'</li>
+<li><em>RepresentationType</em> = 'Curve2D'</li>
+</ul>
+<p>When defining the list of segments for the business logic (i.e., <em>IfcAlignmentHorizontalSegment</em>, <em>IfcAlignmentVerticalSegment</em>, <em>IfcAlignmentCantSegment</em>):</p>
+<ol>
+<li>A <strong>zero-length segment</strong> shall be added, at the end of the list of segments for <em>IfcAlignmentSegment.DesignParameters</em>.</li>
+<li>If the geometry definition is also present, then each of the zero-length segments shall have a <em>IfcCurveSegment</em> counterpart - of length zero.</li>
+</ol>
+<p>```
+concept {
+ IfcAlignment:Representation -> IfcProductDefinitionShape
+ IfcProductDefinitionShape:Representations -> IfcShapeRepresentation_0
+ IfcShapeRepresentation_0:RepresentationIdentifier -> IfcLabel_2
+ IfcShapeRepresentation_0:RepresentationType -> IfcLabel_3
+ IfcShapeRepresentation_0:Items -> IfcCompositeCurve
+ IfcLabel_2 -> constraint_2
+ constraint_2[label="='Axis'"]
+ IfcLabel_3 -> constraint_3
+ constraint_3[label="='Curve2D'"]
+ IfcCompositeCurve:Segments -> IfcCurveSegment_0</p>
+<p>}
+```</p>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Product Shape/Product Geometric Representation/Alignment Geometry/Alignment Geometry - Segments/DocTemplateDefinition.xml b/IFC4x3/Templates/Product Shape/Product Geometric Representation/Alignment Geometry/Alignment Geometry - Segments/DocTemplateDefinition.xml
new file mode 100644
index 000000000..893600eab
--- /dev/null
+++ b/IFC4x3/Templates/Product Shape/Product Geometric Representation/Alignment Geometry/Alignment Geometry - Segments/DocTemplateDefinition.xml
@@ -0,0 +1,90 @@
+
+
+
+
+ <p>This concept template applies to segments of all type of alignment layout: <em>IfcAlignmentHorizontalSegment</em>, <em>IfcAlignmentVerticalSegment</em> and <em>IfcAlignmentCantSegment</em>.</p>
+<ul>
+<li><em>RepresentationIdentifier</em> = 'Axis'</li>
+<li><em>RepresentationType</em> = 'Segment'</li>
+</ul>
+<p>When defining the list of segments for the business logic (i.e., <em>IfcAlignmentHorizontalSegment</em>, <em>IfcAlignmentVerticalSegment</em>, <em>IfcAlignmentCantSegment</em>):</p>
+<ol>
+<li>A <strong>zero-length segment</strong> shall be added, at the end of the list of segments for <em>IfcAlignmentSegment.DesignParameters</em>.</li>
+<li>If the geometry definition is also present, then each of the zero-length segments shall have a <em>IfcCurveSegment</em> counterpart - of length zero.</li>
+</ol>
+<p>```
+concept {
+ IfcAlignmentSegment:Representation -> IfcProductDefinitionShape
+ IfcAlignmentSegment:DesignParameters -> IfcAlignmentHorizontalSegment
+ IfcAlignmentSegment:DesignParameters -> IfcAlignmentVerticalSegment
+ IfcAlignmentSegment:DesignParameters -> IfcAlignmentCantSegment
+ IfcProductDefinitionShape:Representations -> IfcShapeRepresentation_0</p>
+<pre></pre>
+<p>}
+```</p>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Product Shape/Product Geometric Representation/Annotation Geometry/Set Of Survey Points/DocTemplateDefinition.xml b/IFC4x3/Templates/Product Shape/Product Geometric Representation/Annotation Geometry/Set Of Survey Points/DocTemplateDefinition.xml
new file mode 100644
index 000000000..b1f7f3c41
--- /dev/null
+++ b/IFC4x3/Templates/Product Shape/Product Geometric Representation/Annotation Geometry/Set Of Survey Points/DocTemplateDefinition.xml
@@ -0,0 +1,90 @@
+
+
+
+
+ <p>Geometry representation of a set of survey points. They can be 2D points or 3D points. The set of points may not form a closed surface or a survey line.</p>
+<blockquote>
+<p>NOTE When a single <em>IfcAnnotation</em> is represented by multiple survey points, it is not possible to associate properties to the single geometrical points of the set, but only to the whole annotation. </p>
+</blockquote>
+<p></p>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Product Shape/Product Geometric Representation/Annotation Geometry/Single Survey Line/DocTemplateDefinition.xml b/IFC4x3/Templates/Product Shape/Product Geometric Representation/Annotation Geometry/Single Survey Line/DocTemplateDefinition.xml
new file mode 100644
index 000000000..175a63b2f
--- /dev/null
+++ b/IFC4x3/Templates/Product Shape/Product Geometric Representation/Annotation Geometry/Single Survey Line/DocTemplateDefinition.xml
@@ -0,0 +1,89 @@
+
+
+
+
+ <p>Geometry representation of a single survey line. It can be a 2D or a 3D line, therefore using <em>IfcPolyline</em>, or <em>IfcIndexedPolyCurve</em>, or <em>IfcGradientCurve</em>, or <em>IfcCompositeCurve</em></p>
+<p></p>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Product Shape/Product Geometric Representation/Annotation Geometry/Single Survey Point Linearly Placed/DocTemplateDefinition.xml b/IFC4x3/Templates/Product Shape/Product Geometric Representation/Annotation Geometry/Single Survey Point Linearly Placed/DocTemplateDefinition.xml
new file mode 100644
index 000000000..4d043f3a6
--- /dev/null
+++ b/IFC4x3/Templates/Product Shape/Product Geometric Representation/Annotation Geometry/Single Survey Point Linearly Placed/DocTemplateDefinition.xml
@@ -0,0 +1,86 @@
+
+
+
+
+ <p>Geometry representation of a single survey point linearly placed along a curve.</p>
+<p></p>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Product Shape/Product Geometric Representation/Annotation Geometry/Single Survey Point/DocTemplateDefinition.xml b/IFC4x3/Templates/Product Shape/Product Geometric Representation/Annotation Geometry/Single Survey Point/DocTemplateDefinition.xml
new file mode 100644
index 000000000..251454588
--- /dev/null
+++ b/IFC4x3/Templates/Product Shape/Product Geometric Representation/Annotation Geometry/Single Survey Point/DocTemplateDefinition.xml
@@ -0,0 +1,86 @@
+
+
+
+
+ <p>Geometry representation of a single survey point.</p>
+<p></p>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Project Context/Project Global Positioning Geographic/DocTemplateDefinition.xml b/IFC4x3/Templates/Project Context/Project Global Positioning Geographic/DocTemplateDefinition.xml
new file mode 100644
index 000000000..66c754c10
--- /dev/null
+++ b/IFC4x3/Templates/Project Context/Project Global Positioning Geographic/DocTemplateDefinition.xml
@@ -0,0 +1,63 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IFC4x3/Templates/Project Context/Project Global Positioning Mapped/DocTemplateDefinition.xml b/IFC4x3/Templates/Project Context/Project Global Positioning Mapped/DocTemplateDefinition.xml
new file mode 100644
index 000000000..f0a23a5bd
--- /dev/null
+++ b/IFC4x3/Templates/Project Context/Project Global Positioning Mapped/DocTemplateDefinition.xml
@@ -0,0 +1,63 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+