From 8b5ced5317427f47c9a718f68a6434f184e04da5 Mon Sep 17 00:00:00 2001 From: Scott Lecher Date: Wed, 26 Nov 2025 16:06:04 -0500 Subject: [PATCH] remove unused rule codes (IVS-663) --- features/rules/ALB/ALB000_Alignment-layout.feature | 1 - .../rules/ALB/ALB002_Alignment-layout-relationships.feature | 1 - features/rules/ALB/ALB003_Alignment-nesting.feature | 2 +- ...B004_Alignment-in-spatial-structure-relationships.feature | 2 +- features/rules/ALB/ALB005_Positioning-of-referents.feature | 2 +- .../rules/ALB/ALB010_Alignment-nesting-referents.feature | 2 +- ...12_Alignment-vertical-segment-radius-of-curvature.feature | 2 +- ...lignment-business-logic-zero-length-final-segment.feature | 2 +- ...-overall-agreement-of-business-logic-and-geometry.feature | 2 +- .../ALB022_Alignment-agreement-on-number-of-segments.feature | 2 +- ...same-segment-types-in-business-logic-and-geometry.feature | 2 +- features/rules/ALB/ALB030_Alignment-local-placement.feature | 2 +- features/rules/ALS/ALS000_Alignment-geometry.feature | 1 - .../ALS004_Alignment-segment-shape-representation.feature | 3 --- .../rules/ALS/ALS005_Alignment-shape-representation.feature | 5 ----- .../ALS006_Alignment-horizontal-shape-representation.feature | 2 -- .../ALS007_Alignment-vertical-shape-representation.feature | 3 --- .../ALS/ALS008_Alignment-cant-shape-representation.feature | 3 --- ...pe-representation-has-the-correct-number-of-items.feature | 2 +- .../ALS011_Alignment-segment-entity-type-consistency.feature | 1 - ...lignment-segment-start-and-length-attribute-types.feature | 1 - ...lignment-representation-zero-length-final-segment.feature | 2 +- features/rules/ANN/ANN000_Annotations.feature | 1 - features/rules/ASM/ASM000_Composed-elements.feature | 1 - features/rules/AXG/AXG000_Axis-Geometry.feature | 1 - features/rules/BBX/BBX000_Bounding-box.feature | 1 - .../BBX/BBX001_Bounding-box-shape-representation.feature | 1 - features/rules/BLT/BLT000_Built-elements.feature | 1 - ...orrect-use-of-operation-type-attributes-for-doors.feature | 1 - ...t-use-of-partitioning-type-attributes-for-windows.feature | 1 - ...Polyhedral-IfcFace-boundary-no-self-intersections.feature | 2 +- .../BRP/BRP002_Single-component-in-connected-faceset.feature | 2 +- features/rules/BRP/BRP003_Planar-faces-are-planar.feature | 2 +- features/rules/CLS/CLS000_Classification-association.feature | 1 - .../CTX/CTX000_Presentation-colours-and-textures.feature | 1 - features/rules/GDP/GDP000_Grid-placement.feature | 2 +- features/rules/GEM/GEM001_Closed-shell-edge-usage.feature | 2 +- features/rules/GEM/GEM002_Space-representation.feature | 2 +- .../GEM/GEM003_Unique-representation-identifier.feature | 2 +- .../GEM004_Constraints-on-representation-identifiers.feature | 2 +- .../rules/GEM/GEM005_Building-shape-representation.feature | 2 +- features/rules/GEM/GEM011_Curve-segments-consistency.feature | 1 - .../rules/GEM/GEM051_Presence-of-geometric-context.feature | 2 +- .../rules/GEM/GEM052_Correct-geometric-subcontexts.feature | 2 +- ...o-duplicated-points-within-a-polyloop-or-polyline.feature | 4 ---- ...No-duplicated-points-within-an-indexed-poly-curve.feature | 1 - ...ve-arcs-must-not-be-defined-using-colinear-points.feature | 1 - features/rules/GRF/GRF000_Georeferencing.feature | 1 - .../rules/GRF/GRF001_Identical-coordinate-operations.feature | 1 - .../GRF002_EPSG-code-in-coordinate-reference-system.feature | 1 - .../GRF/GRF003_CRS-presence-with-spatial-entities.feature | 1 - ..._Valid-EPSG-prefix-in-coordinate-reference-system.feature | 1 - .../GRF/GRF006_WKT-specification-for-missing-EPSG.feature | 1 - .../rules/GRF/GRF007_valid-vertical-datum-crs-type.feature | 1 - features/rules/GRP/GRP000_Groups.feature | 1 - features/rules/GRP/GRP001_Acyclic-groups.feature | 1 - .../IFC/IFC101_Only-official-ifc-versions-allowed.feature | 1 - .../rules/IFC/IFC102_Absence-of-deprecated-entities.feature | 1 - ...e-entities-need-to-be-referenced-by-rooted-entity.feature | 1 - .../rules/LAY/LAY000_Presentation-layer-assignment.feature | 1 - features/rules/LIP/LIP000_Linear-Placement.feature | 1 - features/rules/LOP/LOP000_Local-placement.feature | 3 +-- features/rules/MAT/MAT000_Materials.feature | 1 - ...ntationIdentifier-in-the-context-of-IfcMappedItem.feature | 2 -- features/rules/OJP/OJP000_Object-placement.feature | 3 +-- ...cement-for-elements-aggregated-to-another-element.feature | 1 - features/rules/PJS/PJS000_Project.feature | 3 +-- .../PJS/PJS002_Correct-elements-related-to-project.feature | 1 - .../rules/PJS/PJS003_Globally-Unique-Identifiers.feature | 1 - features/rules/PJS/PJS101_Project-presence.feature | 1 - .../rules/POR/POR000_Port-connectivity-and-nesting.feature | 1 - ..._Standard-properties-and-property-sets-validation.feature | 1 - ...02_Custom-properties-and-property-sets-validation.feature | 1 - features/rules/QTY/QTY000_Quantities-for-objects.feature | 1 - ..._Standard-quantities-and-quantity-sets-validation.feature | 1 - features/rules/SPA/SPA000_Spaces-information.feature | 1 - .../SPS/SPS001_Basic-spatial-structure-for-buildings.feature | 1 - features/rules/SPS/SPS002_Correct-spatial-breakdown.feature | 1 - .../SPS/SPS003_Correct-containment-of-assemblies.feature | 1 - ...004_No-combination-of-containment-and-positioning.feature | 1 - .../SPS/SPS005_Simultaneous-spatial-relationships.feature | 1 - .../SPS006_Elements-referenced-in-Spatial-structures.feature | 1 - features/rules/SPS/SPS007_Spatial-containment.feature | 1 - ..._Arbitrary-profile-boundary-no-self-intersections.feature | 1 - ...ing-within-IfcDerivedProfileDef-shall-not-be-used.feature | 1 - features/rules/SYS/SYS001_Cable-signal-flow.feature | 2 -- ...001_Polygonal-face-boundary-no-self-intersections.feature | 1 - .../rules/VER/VER000_Versioning-and-revision-control.feature | 1 - features/rules/VRT/VRT000_Virtual-elements.feature | 1 - 89 files changed, 26 insertions(+), 108 deletions(-) diff --git a/features/rules/ALB/ALB000_Alignment-layout.feature b/features/rules/ALB/ALB000_Alignment-layout.feature index e46575396..1d60687bc 100644 --- a/features/rules/ALB/ALB000_Alignment-layout.feature +++ b/features/rules/ALB/ALB000_Alignment-layout.feature @@ -1,7 +1,6 @@ @implementer-agreement @ALB @version1 -@E00020 Feature: ALB000 - Alignment layout The rule verifies the presence of IFC entities used to define the business logic, or layout, of an alignment. diff --git a/features/rules/ALB/ALB002_Alignment-layout-relationships.feature b/features/rules/ALB/ALB002_Alignment-layout-relationships.feature index 211e699ba..ffeb6cd70 100644 --- a/features/rules/ALB/ALB002_Alignment-layout-relationships.feature +++ b/features/rules/ALB/ALB002_Alignment-layout-relationships.feature @@ -1,7 +1,6 @@ @implementer-agreement @ALB @version1 -@E00100 Feature: ALB002 - Alignment Layout Relationships The rule verifies that nesting and decomposition relationships are used correctly with alignment layouts. diff --git a/features/rules/ALB/ALB003_Alignment-nesting.feature b/features/rules/ALB/ALB003_Alignment-nesting.feature index 4c571577e..f4bb6d1c7 100644 --- a/features/rules/ALB/ALB003_Alignment-nesting.feature +++ b/features/rules/ALB/ALB003_Alignment-nesting.feature @@ -1,7 +1,7 @@ @implementer-agreement @ALB @version1 -@E00100 + Feature: ALB003 - Alignment Nesting The rule verifies that an Alignment has a nesting relationship with its components (i.e., Horizontal, Vertical, Cant layouts) or with Referents (e.g., mileage markers). And not with any other entity. diff --git a/features/rules/ALB/ALB004_Alignment-in-spatial-structure-relationships.feature b/features/rules/ALB/ALB004_Alignment-in-spatial-structure-relationships.feature index 3bdd18341..0ca61ddd4 100644 --- a/features/rules/ALB/ALB004_Alignment-in-spatial-structure-relationships.feature +++ b/features/rules/ALB/ALB004_Alignment-in-spatial-structure-relationships.feature @@ -1,7 +1,7 @@ @implementer-agreement @ALB @version1 -@E00100 + Feature: ALB004 - Alignment in spatial structure relationships The rule verifies that each IfcAlignment must be related to IfcProject using the IfcRelAggregates 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 shall be related to the project. diff --git a/features/rules/ALB/ALB005_Positioning-of-referents.feature b/features/rules/ALB/ALB005_Positioning-of-referents.feature index 073d3a41a..7eb4c3ece 100644 --- a/features/rules/ALB/ALB005_Positioning-of-referents.feature +++ b/features/rules/ALB/ALB005_Positioning-of-referents.feature @@ -2,7 +2,7 @@ @ALB @version1 @disabled -@E00100 + Feature: ALB005 - Positioning of referents The rule verifies that IfcReferents (typed POSITION or STATION) linked to IfcAlignments need a IfcRelPositions relationship diff --git a/features/rules/ALB/ALB010_Alignment-nesting-referents.feature b/features/rules/ALB/ALB010_Alignment-nesting-referents.feature index 763c21866..8daf4e62c 100644 --- a/features/rules/ALB/ALB010_Alignment-nesting-referents.feature +++ b/features/rules/ALB/ALB010_Alignment-nesting-referents.feature @@ -1,7 +1,7 @@ @industry-practice @ALB @version2 -@E00100 + Feature: ALB010 - Alignment Nesting Referents The rule verifies that each horizontal alignment nests at least one IfcReferent, such as stations or mileage points. These can be used as semantic entities holding information about locations along the alignment. diff --git a/features/rules/ALB/ALB012_Alignment-vertical-segment-radius-of-curvature.feature b/features/rules/ALB/ALB012_Alignment-vertical-segment-radius-of-curvature.feature index 744cef4e2..84443e146 100644 --- a/features/rules/ALB/ALB012_Alignment-vertical-segment-radius-of-curvature.feature +++ b/features/rules/ALB/ALB012_Alignment-vertical-segment-radius-of-curvature.feature @@ -1,7 +1,7 @@ @implementer-agreement @ALB @version2 -@E00020 + Feature: ALB012 - Alignment vertical segment radius of curvature The rule verifies the 'RadiusOfCurvature' design parameter for vertical alignment segments. Where specified, an absolute tolerance value in the length unit of the model is used for the comparison. diff --git a/features/rules/ALB/ALB015_Alignment-business-logic-zero-length-final-segment.feature b/features/rules/ALB/ALB015_Alignment-business-logic-zero-length-final-segment.feature index 28f5e9c5a..c0ab4f904 100644 --- a/features/rules/ALB/ALB015_Alignment-business-logic-zero-length-final-segment.feature +++ b/features/rules/ALB/ALB015_Alignment-business-logic-zero-length-final-segment.feature @@ -1,7 +1,7 @@ @implementer-agreement @ALB @version2 -@E00020 + Feature: ALB015 - Alignment business logic zero length final segment The rule verifies that each layout (horizontal, vertical, cant) of the alignment business logic ends with a segment of length = 0. diff --git a/features/rules/ALB/ALB021_Alignment-overall-agreement-of-business-logic-and-geometry.feature b/features/rules/ALB/ALB021_Alignment-overall-agreement-of-business-logic-and-geometry.feature index b32b7581c..a06345348 100644 --- a/features/rules/ALB/ALB021_Alignment-overall-agreement-of-business-logic-and-geometry.feature +++ b/features/rules/ALB/ALB021_Alignment-overall-agreement-of-business-logic-and-geometry.feature @@ -1,7 +1,7 @@ @implementer-agreement @ALB @version2 -@E00010 + Feature: ALB021 - Alignment overall agreement of business logic and geometry The rule verifies that when an Alignment has both business logic and geometry (representation), the representation entity type must correspond to the layouts present in the business logic. diff --git a/features/rules/ALB/ALB022_Alignment-agreement-on-number-of-segments.feature b/features/rules/ALB/ALB022_Alignment-agreement-on-number-of-segments.feature index 71ab4e798..4942d7c4f 100644 --- a/features/rules/ALB/ALB022_Alignment-agreement-on-number-of-segments.feature +++ b/features/rules/ALB/ALB022_Alignment-agreement-on-number-of-segments.feature @@ -1,7 +1,7 @@ @implementer-agreement @ALB @version1 -@E00040 + Feature: ALB022 - Alignment agreement on number of segments The rule verifies that when an Alignment has both business logic and geometry (representation), the number of segments in the representation must correspond to the number of segments indicated by the business logic. diff --git a/features/rules/ALB/ALB023_Alignment-same-segment-types-in-business-logic-and-geometry.feature b/features/rules/ALB/ALB023_Alignment-same-segment-types-in-business-logic-and-geometry.feature index d1e9b285c..692fb8d8f 100644 --- a/features/rules/ALB/ALB023_Alignment-same-segment-types-in-business-logic-and-geometry.feature +++ b/features/rules/ALB/ALB023_Alignment-same-segment-types-in-business-logic-and-geometry.feature @@ -1,7 +1,7 @@ @implementer-agreement @ALB @version2 -@E00040 + Feature: ALB023 - Alignment same segment types in business logic and geometry The rule verifies that when an Alignment has both business logic and geometry (representation), the geometry type of each segments in the business logic must be the same as its corresponding segment in the representation. diff --git a/features/rules/ALB/ALB030_Alignment-local-placement.feature b/features/rules/ALB/ALB030_Alignment-local-placement.feature index 5fd903dde..cab1b7f35 100644 --- a/features/rules/ALB/ALB030_Alignment-local-placement.feature +++ b/features/rules/ALB/ALB030_Alignment-local-placement.feature @@ -1,7 +1,7 @@ @implementer-agreement @ALB @version1 -@E00020 + Feature: ALB030 - Alignment local placement The rule verifies that the ObjectPlacement attribute of every instance of IfcAlignment is of type IfcLocalPlacement. While the schema allows other placement types (Grid or Linear), this rule ensures that IfcLocalPlacement is used for all alignments. diff --git a/features/rules/ALS/ALS000_Alignment-geometry.feature b/features/rules/ALS/ALS000_Alignment-geometry.feature index 2346ef0e4..cb1dbaa57 100644 --- a/features/rules/ALS/ALS000_Alignment-geometry.feature +++ b/features/rules/ALS/ALS000_Alignment-geometry.feature @@ -1,7 +1,6 @@ @implementer-agreement @ALS @version1 -@E00020 Feature: ALS000 - Alignment Geometry The rule verifies the presence of IFC entities used to represent the geometry of an alignment. diff --git a/features/rules/ALS/ALS004_Alignment-segment-shape-representation.feature b/features/rules/ALS/ALS004_Alignment-segment-shape-representation.feature index f5972a59d..ed5ef7f00 100644 --- a/features/rules/ALS/ALS004_Alignment-segment-shape-representation.feature +++ b/features/rules/ALS/ALS004_Alignment-segment-shape-representation.feature @@ -11,19 +11,16 @@ The rule verifies that each IfcAlignmentSegment uses correct representation. Given Its attribute .Representations. - @E00020 Scenario: Agreement on each IfcAlignmentSegment using correct value for RepresentationIdentifier Then .RepresentationIdentifier. ^is^ 'Axis' - @E00020 Scenario: Agreement on each IfcAlignmentSegment using correct value for RepresentationType Then .RepresentationType. ^is^ 'Segment' - @E00010 Scenario: Agreement on each IfcAlignmentSegment using correct entity type for Items Given Its attribute .Items. diff --git a/features/rules/ALS/ALS005_Alignment-shape-representation.feature b/features/rules/ALS/ALS005_Alignment-shape-representation.feature index 27c88df48..d14be3362 100644 --- a/features/rules/ALS/ALS005_Alignment-shape-representation.feature +++ b/features/rules/ALS/ALS005_Alignment-shape-representation.feature @@ -12,13 +12,11 @@ Checks for entity types are based upon the supported shape representations of If Given Its attribute .Representations. - @E00020 Scenario: Agreement on each IfcAlignment using correct representation - Value Then .RepresentationIdentifier. ^is^ 'FootPrint' or 'Axis' - @E00010 Scenario: Agreement on each IfcAlignment using correct representation - horizontal only Given .RepresentationIdentifier. ^is^ 'Axis' @@ -27,7 +25,6 @@ Checks for entity types are based upon the supported shape representations of If Then [Its entity type] ^is^ 'IfcCompositeCurve' or 'IfcIndexedPolycurve' or 'IfcPolyline' or 'IfcOffsetCurveByDistances' - @E00010 Scenario: Agreement on each IfcAlignment using correct representation - vertical or cant Given .RepresentationIdentifier. ^is^ 'Axis' @@ -36,14 +33,12 @@ Checks for entity types are based upon the supported shape representations of If Then [Its entity type] ^is^ 'IfcGradientCurve' or 'IfcSegmentedReferenceCurve' or 'IfcIndexedPolycurve' or 'IfcPolyline' or 'IfcOffsetCurveByDistances' - @E00010 Scenario: Agreement on each IfcAlignment using correct representation - identifier = 'FootPrint' Given .RepresentationIdentifier. ^is^ 'FootPrint' Then .RepresentationType. ^is^ 'Curve2D' - @E00010 Scenario: Agreement on each IfcAlignment using correct representation items - Type Given Its attribute .Items. diff --git a/features/rules/ALS/ALS006_Alignment-horizontal-shape-representation.feature b/features/rules/ALS/ALS006_Alignment-horizontal-shape-representation.feature index 8af7a7645..cdddb9796 100644 --- a/features/rules/ALS/ALS006_Alignment-horizontal-shape-representation.feature +++ b/features/rules/ALS/ALS006_Alignment-horizontal-shape-representation.feature @@ -10,14 +10,12 @@ The rule verifies that IfcAlignmentHorizontal is represented correctly with repr Given Its attribute .Representation. Given Its attribute .Representations. - @E00020 Scenario: Agreement on each IfcAlignmentHorizontal using correct representation - Value Then The value of attribute .RepresentationIdentifier. must be 'Axis' Then The value of attribute .RepresentationType. must be 'Curve2D' - @E00010 Scenario: Agreement on each IfcAlignmentHorizontal using correct representation - Type Then The type of attribute Items must be IfcCompositeCurve or IfcIndexedPolycurve or IfcPolyline diff --git a/features/rules/ALS/ALS007_Alignment-vertical-shape-representation.feature b/features/rules/ALS/ALS007_Alignment-vertical-shape-representation.feature index 637a4b071..ef39c11c6 100644 --- a/features/rules/ALS/ALS007_Alignment-vertical-shape-representation.feature +++ b/features/rules/ALS/ALS007_Alignment-vertical-shape-representation.feature @@ -11,20 +11,17 @@ The rule verifies that IfcAlignmentVertical is represented correctly with repres Given Its attribute .Representations. @version3 - @E00010 Scenario: Agreement on each IfcAlignmentVertical using correct representation - Type Given its attribute .Items. Then The type must be 'IfcGradientCurve' - @E00020 Scenario: Agreement on each IfcAlignmentVertical using correct representation - Value Given its attribute .RepresentationIdentifier. Then The value must be 'Axis' - @E00020 Scenario: Agreement on each IfcAlignmentVertical using correct representation - Type Given its attribute .RepresentationType. diff --git a/features/rules/ALS/ALS008_Alignment-cant-shape-representation.feature b/features/rules/ALS/ALS008_Alignment-cant-shape-representation.feature index 37007bc21..956cb6db6 100644 --- a/features/rules/ALS/ALS008_Alignment-cant-shape-representation.feature +++ b/features/rules/ALS/ALS008_Alignment-cant-shape-representation.feature @@ -10,21 +10,18 @@ Background: Given Its attribute .Representation. Given Its attribute .Representations. - @E00020 Scenario: Agreement on each IfcAlignmentCant using correct representation - Value Given its attribute .RepresentationIdentifier. Then The value must be 'Axis' - @E00020 Scenario: Agreement on each IfcAlignmentCant using correct representation - Type Given its attribute .RepresentationType. Then The value must be 'Curve3D' - @E00010 Scenario: Agreement on each IfcAlignmentCant using correct representation items - Type Given its attribute .Items. diff --git a/features/rules/ALS/ALS010_Alignment-segment-shape-representation-has-the-correct-number-of-items.feature b/features/rules/ALS/ALS010_Alignment-segment-shape-representation-has-the-correct-number-of-items.feature index b2d606c6e..32ac761af 100644 --- a/features/rules/ALS/ALS010_Alignment-segment-shape-representation-has-the-correct-number-of-items.feature +++ b/features/rules/ALS/ALS010_Alignment-segment-shape-representation-has-the-correct-number-of-items.feature @@ -1,7 +1,7 @@ @implementer-agreement @ALS @version1 -@E00040 + Feature: ALS010 - Alignment segment shape representation has the correct number of items The rule verifies that a shape representation of IfcAlignmentSegment has the correct number of items diff --git a/features/rules/ALS/ALS011_Alignment-segment-entity-type-consistency.feature b/features/rules/ALS/ALS011_Alignment-segment-entity-type-consistency.feature index 2b2ba3445..b0c60125d 100644 --- a/features/rules/ALS/ALS011_Alignment-segment-entity-type-consistency.feature +++ b/features/rules/ALS/ALS011_Alignment-segment-entity-type-consistency.feature @@ -1,7 +1,6 @@ @implementer-agreement @ALS @version2 -@E00010 Feature: ALS011 - Alignment segment entity type consistency diff --git a/features/rules/ALS/ALS012_Alignment-segment-start-and-length-attribute-types.feature b/features/rules/ALS/ALS012_Alignment-segment-start-and-length-attribute-types.feature index 86ff5edd2..dc1e755b5 100644 --- a/features/rules/ALS/ALS012_Alignment-segment-start-and-length-attribute-types.feature +++ b/features/rules/ALS/ALS012_Alignment-segment-start-and-length-attribute-types.feature @@ -1,7 +1,6 @@ @informal-proposition @ALS @version1 -@E00010 Feature: ALS012 - Alignment segment start and length attribute types diff --git a/features/rules/ALS/ALS015_Alignment-representation-zero-length-final-segment.feature b/features/rules/ALS/ALS015_Alignment-representation-zero-length-final-segment.feature index e64e2d857..726f8fe69 100644 --- a/features/rules/ALS/ALS015_Alignment-representation-zero-length-final-segment.feature +++ b/features/rules/ALS/ALS015_Alignment-representation-zero-length-final-segment.feature @@ -1,7 +1,7 @@ @implementer-agreement @ALS @version3 -@E00020 + Feature: ALS015 - Alignment representation zero length final segment The rule verifies that the alignment geometry (representation) curve diff --git a/features/rules/ANN/ANN000_Annotations.feature b/features/rules/ANN/ANN000_Annotations.feature index d27505e07..59c5ac8af 100644 --- a/features/rules/ANN/ANN000_Annotations.feature +++ b/features/rules/ANN/ANN000_Annotations.feature @@ -1,7 +1,6 @@ @implementer-agreement @ANN @version1 -@E00020 Feature: ANN000 - Annotations The rule verifies the presence of IFC entities used to add annotations to elements and spaces, such as labels, notes, and dimensions. In IFC, annotations are also used to represent survey elements (i.e., points, lines, areas) diff --git a/features/rules/ASM/ASM000_Composed-elements.feature b/features/rules/ASM/ASM000_Composed-elements.feature index 21aa8cce0..e5778a75a 100644 --- a/features/rules/ASM/ASM000_Composed-elements.feature +++ b/features/rules/ASM/ASM000_Composed-elements.feature @@ -1,7 +1,6 @@ @implementer-agreement @ASM @version1 -@E00020 Feature: ASM000 - Composed elements The rule verifies the presence of IFC entities used to model elements composed of / constructed by other elements. diff --git a/features/rules/AXG/AXG000_Axis-Geometry.feature b/features/rules/AXG/AXG000_Axis-Geometry.feature index dd201bf7a..4bd857077 100644 --- a/features/rules/AXG/AXG000_Axis-Geometry.feature +++ b/features/rules/AXG/AXG000_Axis-Geometry.feature @@ -1,7 +1,6 @@ @implementer-agreement @AXG @version1 -@E00020 Feature: AXG000 - Axis Geometry The rule verifies the presence of IFC entities used to representing the geometry using a set of axes, where each axis consists of a position in 3D space and a direction vector. diff --git a/features/rules/BBX/BBX000_Bounding-box.feature b/features/rules/BBX/BBX000_Bounding-box.feature index aac77db22..290e1146b 100644 --- a/features/rules/BBX/BBX000_Bounding-box.feature +++ b/features/rules/BBX/BBX000_Bounding-box.feature @@ -1,7 +1,6 @@ @implementer-agreement @BBX @version1 -@E00020 Feature: BBX000 - Bounding Box The rule verifies the presence of IFC entities used to define an orthogonal box, diff --git a/features/rules/BBX/BBX001_Bounding-box-shape-representation.feature b/features/rules/BBX/BBX001_Bounding-box-shape-representation.feature index 58ae8b2d4..c0ee888a2 100644 --- a/features/rules/BBX/BBX001_Bounding-box-shape-representation.feature +++ b/features/rules/BBX/BBX001_Bounding-box-shape-representation.feature @@ -1,7 +1,6 @@ @implementer-agreement @BBX @version1 -@E00020 Feature: BBX001 - Bounding Box Shape Representation The rule verifies the correct use of Bounding Box as shape representation. diff --git a/features/rules/BLT/BLT000_Built-elements.feature b/features/rules/BLT/BLT000_Built-elements.feature index 17a310a14..1d6bc461b 100644 --- a/features/rules/BLT/BLT000_Built-elements.feature +++ b/features/rules/BLT/BLT000_Built-elements.feature @@ -1,7 +1,6 @@ @implementer-agreement @BLT @version1 -@E00020 Feature: BLT000 - Built Elements The rule verifies the presence of IFC entities used to represent various building and infrastructure elements, diff --git a/features/rules/BLT/BLT001_Correct-use-of-operation-type-attributes-for-doors.feature b/features/rules/BLT/BLT001_Correct-use-of-operation-type-attributes-for-doors.feature index 380e513fa..8c4d25849 100644 --- a/features/rules/BLT/BLT001_Correct-use-of-operation-type-attributes-for-doors.feature +++ b/features/rules/BLT/BLT001_Correct-use-of-operation-type-attributes-for-doors.feature @@ -1,7 +1,6 @@ @implementer-agreement @BLT @version1 -@E00020 Feature: BLT001 - Correct use of operation type attributes for doors diff --git a/features/rules/BLT/BLT002_Correct-use-of-partitioning-type-attributes-for-windows.feature b/features/rules/BLT/BLT002_Correct-use-of-partitioning-type-attributes-for-windows.feature index 36b49cc25..bd460cbf0 100644 --- a/features/rules/BLT/BLT002_Correct-use-of-partitioning-type-attributes-for-windows.feature +++ b/features/rules/BLT/BLT002_Correct-use-of-partitioning-type-attributes-for-windows.feature @@ -1,7 +1,6 @@ @implementer-agreement @BLT @version1 -@E00020 Feature: BLT002 - Correct use of partitioning type attributes for windows diff --git a/features/rules/BRP/BRP001_Polyhedral-IfcFace-boundary-no-self-intersections.feature b/features/rules/BRP/BRP001_Polyhedral-IfcFace-boundary-no-self-intersections.feature index 5e4c91c8c..248a613fd 100644 --- a/features/rules/BRP/BRP001_Polyhedral-IfcFace-boundary-no-self-intersections.feature +++ b/features/rules/BRP/BRP001_Polyhedral-IfcFace-boundary-no-self-intersections.feature @@ -2,7 +2,7 @@ @informal-proposition @BRP @version2 -@E00050 + Feature: BRP001 - Polyhedral IfcFace boundary no self-intersections The rule verifies that IfcFace instances do not have any self-intersections in their boundaries. IfcFace with polygonal loops are used in IFC's Boundary Representation (BRep) mechanism. diff --git a/features/rules/BRP/BRP002_Single-component-in-connected-faceset.feature b/features/rules/BRP/BRP002_Single-component-in-connected-faceset.feature index 7e7dbfa66..a3ee6ac75 100644 --- a/features/rules/BRP/BRP002_Single-component-in-connected-faceset.feature +++ b/features/rules/BRP/BRP002_Single-component-in-connected-faceset.feature @@ -1,7 +1,7 @@ @informal-proposition @BRP @version2 -@E00050 + Feature: BRP002 - Single component in connected faceset The rule verifies that for connected facesets (open- and closed shells) their union of the domains of the faces and their bounding loops shall be arcwise connected. diff --git a/features/rules/BRP/BRP003_Planar-faces-are-planar.feature b/features/rules/BRP/BRP003_Planar-faces-are-planar.feature index e6c05f299..75fd21c93 100644 --- a/features/rules/BRP/BRP003_Planar-faces-are-planar.feature +++ b/features/rules/BRP/BRP003_Planar-faces-are-planar.feature @@ -1,7 +1,7 @@ @informal-proposition @BRP @version2 -@E00050 + Feature: BRP003 - Planar faces are planar The rule verifies that polygonal faces of open and closed shells, which do not have an explicit underlying surface geometry, are planar within the tolerance measure set in the geometric representation context. diff --git a/features/rules/CLS/CLS000_Classification-association.feature b/features/rules/CLS/CLS000_Classification-association.feature index 03b0047d1..5c236117c 100644 --- a/features/rules/CLS/CLS000_Classification-association.feature +++ b/features/rules/CLS/CLS000_Classification-association.feature @@ -1,7 +1,6 @@ @implementer-agreement @CLS @version1 -@E00020 Feature: CLS000 - Classification Association The rule verifies the presence of IFC entities used to classify elements, materials, and systems according to various classification systems, diff --git a/features/rules/CTX/CTX000_Presentation-colours-and-textures.feature b/features/rules/CTX/CTX000_Presentation-colours-and-textures.feature index eee0a8274..1431125b8 100644 --- a/features/rules/CTX/CTX000_Presentation-colours-and-textures.feature +++ b/features/rules/CTX/CTX000_Presentation-colours-and-textures.feature @@ -1,7 +1,6 @@ @implementer-agreement @CTX @version2 -@E00020 Feature: CTX000 - Presentation colours and textures The rule verifies the presence of IFC entities used to assign colour, texture and other presentation appearance information to objects. diff --git a/features/rules/GDP/GDP000_Grid-placement.feature b/features/rules/GDP/GDP000_Grid-placement.feature index b64aa9992..42a4828b1 100644 --- a/features/rules/GDP/GDP000_Grid-placement.feature +++ b/features/rules/GDP/GDP000_Grid-placement.feature @@ -1,7 +1,7 @@ @implementer-agreement @GDP @version1 -@E00020 + Feature: GDP000 - Grid Placement The rule verifies the presence of IFC entities used to define the placement of a product in relation to a design grid. diff --git a/features/rules/GEM/GEM001_Closed-shell-edge-usage.feature b/features/rules/GEM/GEM001_Closed-shell-edge-usage.feature index 32a17b952..776eddbf1 100644 --- a/features/rules/GEM/GEM001_Closed-shell-edge-usage.feature +++ b/features/rules/GEM/GEM001_Closed-shell-edge-usage.feature @@ -1,7 +1,7 @@ @informal-proposition @GEM @version3 -@E00050 + Feature: GEM001 - Closed shell edge usage The rule verifies that closed shells and closed facesets edges are referenced correctly. diff --git a/features/rules/GEM/GEM002_Space-representation.feature b/features/rules/GEM/GEM002_Space-representation.feature index 70a4fc173..0d43e51e7 100644 --- a/features/rules/GEM/GEM002_Space-representation.feature +++ b/features/rules/GEM/GEM002_Space-representation.feature @@ -1,7 +1,7 @@ @informal-proposition @GEM @version2 -@E00150 + Feature: GEM002 - Space representation The rule verifies that all IfcSpaces have a correct Body shape representation. diff --git a/features/rules/GEM/GEM003_Unique-representation-identifier.feature b/features/rules/GEM/GEM003_Unique-representation-identifier.feature index 2ceee82a3..14c4b980c 100644 --- a/features/rules/GEM/GEM003_Unique-representation-identifier.feature +++ b/features/rules/GEM/GEM003_Unique-representation-identifier.feature @@ -1,7 +1,7 @@ @informal-proposition @GEM @version1 -@E00050 + Feature: GEM003 - Unique Representation Identifier The rule verifies that Shape Representation identifier is unique within the product representation of an IfcProduct element. diff --git a/features/rules/GEM/GEM004_Constraints-on-representation-identifiers.feature b/features/rules/GEM/GEM004_Constraints-on-representation-identifiers.feature index 7c8bebc2e..93a653a17 100644 --- a/features/rules/GEM/GEM004_Constraints-on-representation-identifiers.feature +++ b/features/rules/GEM/GEM004_Constraints-on-representation-identifiers.feature @@ -1,7 +1,7 @@ @informal-proposition @GEM @version3 -@E00010 + Feature: GEM004 - Constraints on representation identifiers The rule verifies that shape representations adhere to the permissible values outlined in the CSV files found in the 'features/resources/{attribute}.csv' folder, as specified in the documentation. diff --git a/features/rules/GEM/GEM005_Building-shape-representation.feature b/features/rules/GEM/GEM005_Building-shape-representation.feature index 9af47cca0..68136359f 100644 --- a/features/rules/GEM/GEM005_Building-shape-representation.feature +++ b/features/rules/GEM/GEM005_Building-shape-representation.feature @@ -2,7 +2,7 @@ @GEM @version2 @disabled -@E00020 + Feature: GEM005 - Building shape representation The rule verifies that an IfcBuilding has a correct representation diff --git a/features/rules/GEM/GEM011_Curve-segments-consistency.feature b/features/rules/GEM/GEM011_Curve-segments-consistency.feature index 3bc05645b..d79d416f6 100644 --- a/features/rules/GEM/GEM011_Curve-segments-consistency.feature +++ b/features/rules/GEM/GEM011_Curve-segments-consistency.feature @@ -1,7 +1,6 @@ @implementer-agreement @GEM @version1 -@E00010 Feature: GEM011 - Curve segments consistency diff --git a/features/rules/GEM/GEM051_Presence-of-geometric-context.feature b/features/rules/GEM/GEM051_Presence-of-geometric-context.feature index fa418d895..f8df539f2 100644 --- a/features/rules/GEM/GEM051_Presence-of-geometric-context.feature +++ b/features/rules/GEM/GEM051_Presence-of-geometric-context.feature @@ -1,7 +1,7 @@ @industry-practice @GEM @version2 -@E00020 + Feature: GEM051 - Presence of Geometric Context The rule verifies that a geometric context is present in the model, that its attribute ContextType is provided (not empty) and its value is valid. diff --git a/features/rules/GEM/GEM052_Correct-geometric-subcontexts.feature b/features/rules/GEM/GEM052_Correct-geometric-subcontexts.feature index 277a5eb40..5d1457c38 100644 --- a/features/rules/GEM/GEM052_Correct-geometric-subcontexts.feature +++ b/features/rules/GEM/GEM052_Correct-geometric-subcontexts.feature @@ -1,7 +1,7 @@ @industry-practice @GEM @version2 -@E00050 + Feature: GEM052 - Correct geometric subcontexts The rule verifies that there is a minimum of at least one subcontext per context, that its attribute ContextIdentifier is provided (not empty) and its value is one of the allowed values in the list of shape representation identifiers. Reference: https://github.com/buildingSMART/Sample-Test-Files/issues/137. diff --git a/features/rules/GEM/GEM111_No-duplicated-points-within-a-polyloop-or-polyline.feature b/features/rules/GEM/GEM111_No-duplicated-points-within-a-polyloop-or-polyline.feature index 7d4a132e5..33c703239 100644 --- a/features/rules/GEM/GEM111_No-duplicated-points-within-a-polyloop-or-polyline.feature +++ b/features/rules/GEM/GEM111_No-duplicated-points-within-a-polyloop-or-polyline.feature @@ -7,13 +7,11 @@ In that case, it must be identical by reference (referencing the same instance), Two points are considered to be duplicates if the distance between them is less than the Precision factor of the applicable geometric context. - @E00050 Scenario: Agreement on no duplicated points within a polyloop Given An .IfcPolyLoop. Then It must have no duplicate points including first and last point - @E00050 Scenario: Agreement on no duplicated points within a polyline Given An .IfcPolyLine. @@ -21,7 +19,6 @@ the Precision factor of the applicable geometric context. Then It must have no duplicate points including first and last point - @E00050 Scenario: Agreement on no duplicated points within a polyline Given An .IfcPolyLine. @@ -29,7 +26,6 @@ the Precision factor of the applicable geometric context. Then It must have no duplicate points excluding first and last point - @E00120 Scenario: Agreement on first and last point of IfcPolyline being identical by reference (referencing the same instance of IfcCartesianPoint) Given An .IfcPolyline. diff --git a/features/rules/GEM/GEM112_No-duplicated-points-within-an-indexed-poly-curve.feature b/features/rules/GEM/GEM112_No-duplicated-points-within-an-indexed-poly-curve.feature index fa1a3aa3e..ab6b17386 100644 --- a/features/rules/GEM/GEM112_No-duplicated-points-within-an-indexed-poly-curve.feature +++ b/features/rules/GEM/GEM112_No-duplicated-points-within-an-indexed-poly-curve.feature @@ -6,7 +6,6 @@ The rule verifies that all indexed poly curves will have no duplicate points. Two points are considered to be duplicates if the distance between them is less than the Precision factor of the applicable geometric context. - @E00050 Scenario: Agreement on no duplicated points within an indexed poly curve Given An .IfcIndexedPolyCurve. diff --git a/features/rules/GEM/GEM113_Indexed-poly-curve-arcs-must-not-be-defined-using-colinear-points.feature b/features/rules/GEM/GEM113_Indexed-poly-curve-arcs-must-not-be-defined-using-colinear-points.feature index 0f36490df..02038584e 100644 --- a/features/rules/GEM/GEM113_Indexed-poly-curve-arcs-must-not-be-defined-using-colinear-points.feature +++ b/features/rules/GEM/GEM113_Indexed-poly-curve-arcs-must-not-be-defined-using-colinear-points.feature @@ -4,7 +4,6 @@ Feature: GEM113 - Indexed poly curve arcs must not be defined using colinear points The rule verifies that all the three points of any IfcArcIndex segment of an IfcIndexedPolyCurve are not colinear after taking the Precision factor into account - @E00050 Scenario: No poly curve arcs using colinear points Given An .IfcIndexedPolyCurve. diff --git a/features/rules/GRF/GRF000_Georeferencing.feature b/features/rules/GRF/GRF000_Georeferencing.feature index 04e8415f8..74c05665c 100644 --- a/features/rules/GRF/GRF000_Georeferencing.feature +++ b/features/rules/GRF/GRF000_Georeferencing.feature @@ -1,7 +1,6 @@ @implementer-agreement @GRF @version1 -@E00050 Feature: GRF000 - Georeferencing The rule verifies the presence of IFC entities used to define the geographic location and orientation of the model relative to a coordinate reference system. The simple attributes on IfcSite: RefLatitude, RefLongitude and RefElevation are not considered proper georeferencing in the context of this rule. diff --git a/features/rules/GRF/GRF001_Identical-coordinate-operations.feature b/features/rules/GRF/GRF001_Identical-coordinate-operations.feature index d72258971..c4f4eeb55 100644 --- a/features/rules/GRF/GRF001_Identical-coordinate-operations.feature +++ b/features/rules/GRF/GRF001_Identical-coordinate-operations.feature @@ -1,7 +1,6 @@ @implementer-agreement @GRF @version2 -@E00050 Feature: GRF001 - Identical coordinate operations The rule verifies that if multiple instances of IfcGeometricRepresentationContext are provided to the IfcProject, all contexts must share an identical instance of IfcCoordinateOperation, each referring to the same instance of IfcCoordinateReferenceSystem. diff --git a/features/rules/GRF/GRF002_EPSG-code-in-coordinate-reference-system.feature b/features/rules/GRF/GRF002_EPSG-code-in-coordinate-reference-system.feature index 73c7d488c..5b0fb3216 100644 --- a/features/rules/GRF/GRF002_EPSG-code-in-coordinate-reference-system.feature +++ b/features/rules/GRF/GRF002_EPSG-code-in-coordinate-reference-system.feature @@ -1,7 +1,6 @@ @industry-practice @GRF @version1 -@E00100 Feature: GRF002 - EPSG code in coordinate reference system The rule verifies that the name of the coordinate reference system refers to a valid EPSG code from the official EPSG geodetic parameter dataset. EPSG code validation is performed using the pyproj library, which includes a local copy of the official EPSG dataset (https://epsg.org) maintained by IOGP. diff --git a/features/rules/GRF/GRF003_CRS-presence-with-spatial-entities.feature b/features/rules/GRF/GRF003_CRS-presence-with-spatial-entities.feature index 4958ce20b..9e471b4fe 100644 --- a/features/rules/GRF/GRF003_CRS-presence-with-spatial-entities.feature +++ b/features/rules/GRF/GRF003_CRS-presence-with-spatial-entities.feature @@ -2,7 +2,6 @@ @no-activation @GRF @version1 -@E00010 Feature: GRF003 - CRS presence with spatial entities The rule verifies that proper georeferencing using a coordinate reference system is established when facilities such as buildings or bridges are present in a model. Models containing IfcFacility must contain a IfcProjectedCRS or IfcGeographicCRS. diff --git a/features/rules/GRF/GRF004_Valid-EPSG-prefix-in-coordinate-reference-system.feature b/features/rules/GRF/GRF004_Valid-EPSG-prefix-in-coordinate-reference-system.feature index ca2473eb3..f56753a6e 100644 --- a/features/rules/GRF/GRF004_Valid-EPSG-prefix-in-coordinate-reference-system.feature +++ b/features/rules/GRF/GRF004_Valid-EPSG-prefix-in-coordinate-reference-system.feature @@ -1,7 +1,6 @@ @implementer-agreement @GRF @version1 -@E00500 Feature: GRF004 - Valid EPSG prefix in coordinate reference system The rule verifies that if the name of a CRS starts with "EPSG:", it must refer to a valid code from the official EPSG geodetic parameter dataset. EPSG code validation is performed using the pyproj library, which includes a local copy of the official EPSG dataset (https://epsg.org) maintained by IOGP. diff --git a/features/rules/GRF/GRF006_WKT-specification-for-missing-EPSG.feature b/features/rules/GRF/GRF006_WKT-specification-for-missing-EPSG.feature index a3be65d79..29737b277 100644 --- a/features/rules/GRF/GRF006_WKT-specification-for-missing-EPSG.feature +++ b/features/rules/GRF/GRF006_WKT-specification-for-missing-EPSG.feature @@ -1,7 +1,6 @@ @implementer-agreement @GRF @version2 -@E00500 Feature: GRF006 - WKT specification for missing EPSG The rule verifies that if an ESPG code does not exist for the coordinate reference system, this CRS shall be further speciied using the IfcWellKnownText entity https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/IfcCoordinateReferenceSystem.htm#8.18.3.2.3-Attributes diff --git a/features/rules/GRF/GRF007_valid-vertical-datum-crs-type.feature b/features/rules/GRF/GRF007_valid-vertical-datum-crs-type.feature index 75746afaf..2479e6df2 100644 --- a/features/rules/GRF/GRF007_valid-vertical-datum-crs-type.feature +++ b/features/rules/GRF/GRF007_valid-vertical-datum-crs-type.feature @@ -1,7 +1,6 @@ @implementer-agreement @GRF @version1 -@E00500 Feature: GRF007 - Valid vertical datum CRS type The rule verifies that any coordinate reference system (CRS) assigned as a vertical datum is either a vertical CRS or a compound CRS containing a vertical component, to ensure valid height referencing. https://pyproj4.github.io/pyproj/stable/api/crs/crs.html diff --git a/features/rules/GRP/GRP000_Groups.feature b/features/rules/GRP/GRP000_Groups.feature index d48291042..e22fd7568 100644 --- a/features/rules/GRP/GRP000_Groups.feature +++ b/features/rules/GRP/GRP000_Groups.feature @@ -1,7 +1,6 @@ @implementer-agreement @GRP @version1 -@E00050 Feature: GRP000 - Groups The rule verifies the presence of IFC entities used to define a group as a logical collection of objects. diff --git a/features/rules/GRP/GRP001_Acyclic-groups.feature b/features/rules/GRP/GRP001_Acyclic-groups.feature index 1a0167180..0444caffe 100644 --- a/features/rules/GRP/GRP001_Acyclic-groups.feature +++ b/features/rules/GRP/GRP001_Acyclic-groups.feature @@ -1,7 +1,6 @@ @implementer-agreement @GRP @version1 -@E00120 Feature: GRP001 - Acyclic groups The rule verifies that an IfcGroup does not reference itself, not even through intermediary entities. diff --git a/features/rules/IFC/IFC101_Only-official-ifc-versions-allowed.feature b/features/rules/IFC/IFC101_Only-official-ifc-versions-allowed.feature index c77791151..344fa3a38 100644 --- a/features/rules/IFC/IFC101_Only-official-ifc-versions-allowed.feature +++ b/features/rules/IFC/IFC101_Only-official-ifc-versions-allowed.feature @@ -1,6 +1,5 @@ @critical @version1 -@W00030 Feature: IFC101 - Only official IFC versions allowed The rule verifies that the IFC model has a schema identifier corresponding to any of the official versions released by buildingSMART. diff --git a/features/rules/IFC/IFC102_Absence-of-deprecated-entities.feature b/features/rules/IFC/IFC102_Absence-of-deprecated-entities.feature index a2e44a7e0..24c1f1f0c 100644 --- a/features/rules/IFC/IFC102_Absence-of-deprecated-entities.feature +++ b/features/rules/IFC/IFC102_Absence-of-deprecated-entities.feature @@ -1,6 +1,5 @@ @IFC @version5 -@E00030 @implementer-agreement Feature: IFC102 - Absence of deprecated entities diff --git a/features/rules/IFC/IFC105_Resource-entities-need-to-be-referenced-by-rooted-entity.feature b/features/rules/IFC/IFC105_Resource-entities-need-to-be-referenced-by-rooted-entity.feature index fe0044df8..32fc5daeb 100644 --- a/features/rules/IFC/IFC105_Resource-entities-need-to-be-referenced-by-rooted-entity.feature +++ b/features/rules/IFC/IFC105_Resource-entities-need-to-be-referenced-by-rooted-entity.feature @@ -1,6 +1,5 @@ @IFC @version3 -@E00030 @implementer-agreement Feature: IFC105 - Resource entities need to be referenced by rooted entity diff --git a/features/rules/LAY/LAY000_Presentation-layer-assignment.feature b/features/rules/LAY/LAY000_Presentation-layer-assignment.feature index 7ead29412..25f6c87df 100644 --- a/features/rules/LAY/LAY000_Presentation-layer-assignment.feature +++ b/features/rules/LAY/LAY000_Presentation-layer-assignment.feature @@ -1,7 +1,6 @@ @implementer-agreement @LAY @version1 -@E00020 Feature: LAY000 - Presentation Layer Assignment The rule verifies the presence of IFC entities used to assign layers (also known as, CAD layer) to collection of elements. diff --git a/features/rules/LIP/LIP000_Linear-Placement.feature b/features/rules/LIP/LIP000_Linear-Placement.feature index ad7252d33..003044445 100644 --- a/features/rules/LIP/LIP000_Linear-Placement.feature +++ b/features/rules/LIP/LIP000_Linear-Placement.feature @@ -1,7 +1,6 @@ @implementer-agreement @LIP @version1 -@E00020 Feature: LIP000 - Linear Placement The rule verifies the presence of IFC entities used to position elements relative to an IfcLinearPositioningElement diff --git a/features/rules/LOP/LOP000_Local-placement.feature b/features/rules/LOP/LOP000_Local-placement.feature index c1e551879..b38239620 100644 --- a/features/rules/LOP/LOP000_Local-placement.feature +++ b/features/rules/LOP/LOP000_Local-placement.feature @@ -5,8 +5,7 @@ Feature: LOP000 - Local placement The rule verifies the presence of IFC entities used to position a product in relation to the placement of another product; or its absolute placement within the geometric representation context of the project. - @E00010 - Scenario: Check for activation . + Scenario: Check for activation . Given An .IfcObject. Given Its attribute .ObjectPlacement. diff --git a/features/rules/MAT/MAT000_Materials.feature b/features/rules/MAT/MAT000_Materials.feature index c02571325..9191c8f01 100644 --- a/features/rules/MAT/MAT000_Materials.feature +++ b/features/rules/MAT/MAT000_Materials.feature @@ -1,7 +1,6 @@ @implementer-agreement @MAT @version1 -@E00020 Feature: MAT000 - Materials The rule verifies the presence of IFC entities used to define materials assigned to elements. diff --git a/features/rules/MPD/MPD001_Correct-use-of-RepresentationType-and-RepresentationIdentifier-in-the-context-of-IfcMappedItem.feature b/features/rules/MPD/MPD001_Correct-use-of-RepresentationType-and-RepresentationIdentifier-in-the-context-of-IfcMappedItem.feature index 9098522d9..59f5160be 100644 --- a/features/rules/MPD/MPD001_Correct-use-of-RepresentationType-and-RepresentationIdentifier-in-the-context-of-IfcMappedItem.feature +++ b/features/rules/MPD/MPD001_Correct-use-of-RepresentationType-and-RepresentationIdentifier-in-the-context-of-IfcMappedItem.feature @@ -5,7 +5,6 @@ Feature: MPD001 - Correct use of RepresentationType and RepresentationIdentifier The rule verifies that the shape representations being mapped as part of an IfcMappedItem all have the same RepresentationType and that the RepresentationIdentifier correspond to that of the representation that owns the mapped item. - @E00010 Scenario: Agreement on the equality of RepresentationIdentifier Given an .IfcShapeRepresentation. @@ -19,7 +18,6 @@ RepresentationType and that the RepresentationIdentifier correspond to that of t Then the value 'ChildIdentifier' must be ^equal to^ the value 'ParentIdentifier' - @E00060 Scenario: Agreement on the equality of RepresentationType Given an .IfcShapeRepresentation. diff --git a/features/rules/OJP/OJP000_Object-placement.feature b/features/rules/OJP/OJP000_Object-placement.feature index c2b5ff229..9d519ff81 100644 --- a/features/rules/OJP/OJP000_Object-placement.feature +++ b/features/rules/OJP/OJP000_Object-placement.feature @@ -4,8 +4,7 @@ Feature: OJP000 - Object placement The rule verifies the presence of IFC entities used to define an object placement, which in turns establishes the local coordinate system and spatial position of the product. - @E00010 - Scenario: Check for activation . + Scenario: Check for activation . Given An .IfcObject. Given Its attribute .ObjectPlacement. diff --git a/features/rules/OJP/OJP001_Relative-placement-for-elements-aggregated-to-another-element.feature b/features/rules/OJP/OJP001_Relative-placement-for-elements-aggregated-to-another-element.feature index 63c4082c0..17c8dfb1c 100644 --- a/features/rules/OJP/OJP001_Relative-placement-for-elements-aggregated-to-another-element.feature +++ b/features/rules/OJP/OJP001_Relative-placement-for-elements-aggregated-to-another-element.feature @@ -6,7 +6,6 @@ The rule verifies that if an IfcElement is a part of another IfcElement (the con IfcRelAggregates, then the relative placement of that IfcElement shall be provided by an IfcLocalPlacement with an PlacementRelTo attribute pointing to the IfcLocalPlacement of the container element. - @E00010 Scenario: Agreement on the relative placement of IfcElements being a part of another IfcElement through the relationship IfcRelAggregates Given A model with Schema 'IFC2X3' or 'IFC4' diff --git a/features/rules/PJS/PJS000_Project.feature b/features/rules/PJS/PJS000_Project.feature index 35162b4e8..7885d6f92 100644 --- a/features/rules/PJS/PJS000_Project.feature +++ b/features/rules/PJS/PJS000_Project.feature @@ -5,8 +5,7 @@ Feature: PJS000 - Project The rule verifies the presence of IFC entities used to define the overall context and a directory of objects contained within. https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/concepts/Project_Context/content.html - @E00010 - Scenario: Check for activation. + Scenario: Check for activation. Given An .IfcProject. diff --git a/features/rules/PJS/PJS002_Correct-elements-related-to-project.feature b/features/rules/PJS/PJS002_Correct-elements-related-to-project.feature index a16c6d69b..1381510be 100644 --- a/features/rules/PJS/PJS002_Correct-elements-related-to-project.feature +++ b/features/rules/PJS/PJS002_Correct-elements-related-to-project.feature @@ -1,7 +1,6 @@ @implementer-agreement @PJS @version2 -@E00010 Feature: PJS002 - Correct elements related to project The rule verifies that object occurrences (e.g. beams, walls) used within the context of a project diff --git a/features/rules/PJS/PJS003_Globally-Unique-Identifiers.feature b/features/rules/PJS/PJS003_Globally-Unique-Identifiers.feature index 7cac1cffa..42a0ea49a 100644 --- a/features/rules/PJS/PJS003_Globally-Unique-Identifiers.feature +++ b/features/rules/PJS/PJS003_Globally-Unique-Identifiers.feature @@ -1,7 +1,6 @@ @implementer-agreement @PJS @version1 -@E00010 Feature: PJS003 - Globally Unique Identifiers The rule verifies that the GUID of each element adheres to the Global Unique Identifier format and ensures compliance with constraints that are not yet validated by other methods. diff --git a/features/rules/PJS/PJS101_Project-presence.feature b/features/rules/PJS/PJS101_Project-presence.feature index 7816d3957..5662a1537 100644 --- a/features/rules/PJS/PJS101_Project-presence.feature +++ b/features/rules/PJS/PJS101_Project-presence.feature @@ -1,7 +1,6 @@ @PJS @industry-practice @version1 -@E00020 Feature: PJS101 - Project presence The rule verifies that there is exactly one instance of IfcProject. While this is a common industry practice, it does not make the IFC model invalid. diff --git a/features/rules/POR/POR000_Port-connectivity-and-nesting.feature b/features/rules/POR/POR000_Port-connectivity-and-nesting.feature index 1086619a8..3cf43872e 100644 --- a/features/rules/POR/POR000_Port-connectivity-and-nesting.feature +++ b/features/rules/POR/POR000_Port-connectivity-and-nesting.feature @@ -1,7 +1,6 @@ @implementer-agreement @POR @version1 -@E00020 Feature: POR000 - Port Connectivity and Nesting The rule verifies the presence of IFC entities used to define ports (as means for an element to connect to other elements) and the relationship that is made between two ports. diff --git a/features/rules/PSE/PSE001_Standard-properties-and-property-sets-validation.feature b/features/rules/PSE/PSE001_Standard-properties-and-property-sets-validation.feature index 543bc1db5..b6d555b10 100644 --- a/features/rules/PSE/PSE001_Standard-properties-and-property-sets-validation.feature +++ b/features/rules/PSE/PSE001_Standard-properties-and-property-sets-validation.feature @@ -1,7 +1,6 @@ @implementer-agreement @PSE @version3 -@E00020 Feature: PSE001 - Standard properties and property sets validation The rule verifies that each IfcPropertySet starting with 'Pset_' is defined correctly. diff --git a/features/rules/PSE/PSE002_Custom-properties-and-property-sets-validation.feature b/features/rules/PSE/PSE002_Custom-properties-and-property-sets-validation.feature index 312a75350..300d76b22 100644 --- a/features/rules/PSE/PSE002_Custom-properties-and-property-sets-validation.feature +++ b/features/rules/PSE/PSE002_Custom-properties-and-property-sets-validation.feature @@ -1,7 +1,6 @@ @industry-practice @PSE @version1 -@E00020 Feature: PSE002 - Custom properties and property sets validation The rule verifies that property set names do not start with any upper- and lowercase variation of 'pset' in order to prevent confusion with standardized property sets in the IFC specification. The property sets defined in the IFC specification all start with 'Pset_' diff --git a/features/rules/QTY/QTY000_Quantities-for-objects.feature b/features/rules/QTY/QTY000_Quantities-for-objects.feature index 15101adcf..01ae370f1 100644 --- a/features/rules/QTY/QTY000_Quantities-for-objects.feature +++ b/features/rules/QTY/QTY000_Quantities-for-objects.feature @@ -1,7 +1,6 @@ @implementer-agreement @QTY @version1 -@E00020 Feature: QTY000 - Quantities for Objects The rule verifies the presence of IFC entities used to define quantities of elements, such as their dimensions, volume, area, weight. diff --git a/features/rules/QTY/QTY001_Standard-quantities-and-quantity-sets-validation.feature b/features/rules/QTY/QTY001_Standard-quantities-and-quantity-sets-validation.feature index fa7f441c7..664c3bc18 100644 --- a/features/rules/QTY/QTY001_Standard-quantities-and-quantity-sets-validation.feature +++ b/features/rules/QTY/QTY001_Standard-quantities-and-quantity-sets-validation.feature @@ -1,7 +1,6 @@ @implementer-agreement @QTY @version1 -@E00020 Feature: QTY001 - Standard quantities and quantity sets validation The rule verifies that each IfcElementQuantity starting with 'Qto_' is defined correctly. diff --git a/features/rules/SPA/SPA000_Spaces-information.feature b/features/rules/SPA/SPA000_Spaces-information.feature index 02cf18ea3..8bf718155 100644 --- a/features/rules/SPA/SPA000_Spaces-information.feature +++ b/features/rules/SPA/SPA000_Spaces-information.feature @@ -1,7 +1,6 @@ @implementer-agreement @SPA @version1 -@E00020 Feature: SPA000 - Spaces Information The rule verifies the presence of IFC entities used to model spaces, such as rooms, hallways, clearance zones, and circulation areas. diff --git a/features/rules/SPS/SPS001_Basic-spatial-structure-for-buildings.feature b/features/rules/SPS/SPS001_Basic-spatial-structure-for-buildings.feature index 15403d456..0d0e3bfa7 100644 --- a/features/rules/SPS/SPS001_Basic-spatial-structure-for-buildings.feature +++ b/features/rules/SPS/SPS001_Basic-spatial-structure-for-buildings.feature @@ -1,7 +1,6 @@ @implementer-agreement @SPS @version2 -@E00160 Feature: SPS001 - Basic spatial structure for buildings The rule verifies that there's maximum one instance of IfcSite and at least one instance of IfcBuilding as part of the spatial structure. diff --git a/features/rules/SPS/SPS002_Correct-spatial-breakdown.feature b/features/rules/SPS/SPS002_Correct-spatial-breakdown.feature index ecd423e25..2e84f1773 100644 --- a/features/rules/SPS/SPS002_Correct-spatial-breakdown.feature +++ b/features/rules/SPS/SPS002_Correct-spatial-breakdown.feature @@ -1,7 +1,6 @@ @implementer-agreement @SPS @version3 -@E00100 Feature: SPS002 - Correct spatial breakdown The rule verifies that spatial elements are aggregated as per the Spatial Composition Table. The possible allowed breakdown can be found in the csv file in the folder 'features/resources/spatial_CompositionTable.csv' diff --git a/features/rules/SPS/SPS003_Correct-containment-of-assemblies.feature b/features/rules/SPS/SPS003_Correct-containment-of-assemblies.feature index d3394a8d2..d29558333 100644 --- a/features/rules/SPS/SPS003_Correct-containment-of-assemblies.feature +++ b/features/rules/SPS/SPS003_Correct-containment-of-assemblies.feature @@ -1,7 +1,6 @@ @implementer-agreement @SPS @version1 -@E00040 Feature: SPS003 - Correct containment of assemblies The rule verifies that IfcElement that are aggregated in another IfcElement must not be contained using IfcRelContainedInSpatialStructure. diff --git a/features/rules/SPS/SPS004_No-combination-of-containment-and-positioning.feature b/features/rules/SPS/SPS004_No-combination-of-containment-and-positioning.feature index 77e0dd532..408d388e4 100644 --- a/features/rules/SPS/SPS004_No-combination-of-containment-and-positioning.feature +++ b/features/rules/SPS/SPS004_No-combination-of-containment-and-positioning.feature @@ -2,7 +2,6 @@ @SPS @version2 @disabled -@E00040 Feature: SPS004 - No combination of containment and positioning The rule verifies that each IfcProduct can either be contained in one and only one IfcSpatialStructureElement, or contained in one and only one IfcLinearPositioningElement, but not both. diff --git a/features/rules/SPS/SPS005_Simultaneous-spatial-relationships.feature b/features/rules/SPS/SPS005_Simultaneous-spatial-relationships.feature index 12824dedd..6d849c3ad 100644 --- a/features/rules/SPS/SPS005_Simultaneous-spatial-relationships.feature +++ b/features/rules/SPS/SPS005_Simultaneous-spatial-relationships.feature @@ -1,7 +1,6 @@ @implementer-agreement @SPS @version2 -@E00040 Feature: SPS005 - Simultaneous spatial relationships The rule verifies that an IfcElement does not simultaneously act as a child in two or more spatial relationships. For example, an element cannot participate in both nesting and aggregating children roles. diff --git a/features/rules/SPS/SPS006_Elements-referenced-in-Spatial-structures.feature b/features/rules/SPS/SPS006_Elements-referenced-in-Spatial-structures.feature index fa90520d4..dba7ae9d6 100644 --- a/features/rules/SPS/SPS006_Elements-referenced-in-Spatial-structures.feature +++ b/features/rules/SPS/SPS006_Elements-referenced-in-Spatial-structures.feature @@ -2,7 +2,6 @@ @SPS @disabled @version2 -@E00040 Feature: SPS006 - Elements referenced in Spatial structures The rule verifies that if an IfcElement is positioned in relation to an IfcPositioningElement, then it must be also referenced (instead of contained) into a IfcSpatialStructureElement diff --git a/features/rules/SPS/SPS007_Spatial-containment.feature b/features/rules/SPS/SPS007_Spatial-containment.feature index 4a905c447..dc43a1c4e 100644 --- a/features/rules/SPS/SPS007_Spatial-containment.feature +++ b/features/rules/SPS/SPS007_Spatial-containment.feature @@ -1,7 +1,6 @@ @implementer-agreement @SPS @version6 -@E00040 Feature: SPS007 - Spatial Containment The rule verifies that spatial containment via IfcRelContainedInSpatialStructure is utilised in accordance with Concept Template for Spatial Containment diff --git a/features/rules/SWE/SWE001_Arbitrary-profile-boundary-no-self-intersections.feature b/features/rules/SWE/SWE001_Arbitrary-profile-boundary-no-self-intersections.feature index 055315a71..ff982f109 100644 --- a/features/rules/SWE/SWE001_Arbitrary-profile-boundary-no-self-intersections.feature +++ b/features/rules/SWE/SWE001_Arbitrary-profile-boundary-no-self-intersections.feature @@ -1,7 +1,6 @@ @informal-proposition @SWE @version4 -@E00050 Feature: SWE001 - Arbitrary profile boundary no self-intersections The rule verifies that IfcArbitraryClosedProfileDefs and IfcArbitraryProfileDefWithVoids do not have any self-intersections in their boundaries. Profile definitions are the basis of diff --git a/features/rules/SWE/SWE002_Mirroring-within-IfcDerivedProfileDef-shall-not-be-used.feature b/features/rules/SWE/SWE002_Mirroring-within-IfcDerivedProfileDef-shall-not-be-used.feature index 51f7e29e5..8139602e3 100644 --- a/features/rules/SWE/SWE002_Mirroring-within-IfcDerivedProfileDef-shall-not-be-used.feature +++ b/features/rules/SWE/SWE002_Mirroring-within-IfcDerivedProfileDef-shall-not-be-used.feature @@ -1,7 +1,6 @@ @informal-proposition @SWE @version2 -@E00050 Feature: SWE002 - Mirroring within IfcDerivedProfileDef shall not be used The rule verifies that the transformation defined in IfcDerivedProfileDef.Operator does not introduce mirroring. diff --git a/features/rules/SYS/SYS001_Cable-signal-flow.feature b/features/rules/SYS/SYS001_Cable-signal-flow.feature index 847d93555..6afa6c36c 100644 --- a/features/rules/SYS/SYS001_Cable-signal-flow.feature +++ b/features/rules/SYS/SYS001_Cable-signal-flow.feature @@ -10,12 +10,10 @@ The rule verifies that IfcCableSegment must define 2 distribution ports, 1 as a Given A model with Schema 'IFC4.3' Given an .IfcCableSegment. - @E00100 Scenario: Agreement on IfcCableSegment having ports Then It [must be nested by] ^exactly^ [2] instance(s) of .IfcDistributionPort. - @E00100 Scenario: Agreement on port directions Given a relationship .IfcRelNests. from .IfcAlignment. to .IfcDistributionPort. and following that diff --git a/features/rules/TAS/TAS001_Polygonal-face-boundary-no-self-intersections.feature b/features/rules/TAS/TAS001_Polygonal-face-boundary-no-self-intersections.feature index 81fbb75ed..704c443e9 100644 --- a/features/rules/TAS/TAS001_Polygonal-face-boundary-no-self-intersections.feature +++ b/features/rules/TAS/TAS001_Polygonal-face-boundary-no-self-intersections.feature @@ -2,7 +2,6 @@ @informal-proposition @TAS @version2 -@E00050 Feature: TAS001 - Polygonal face boundary no self-intersections The rule verifies that IfcFace instances do not have any self-intersections in their boundaries. IfcFace with polygonal loops are used in IFC's Boundary Representation (BRep) mechanism. diff --git a/features/rules/VER/VER000_Versioning-and-revision-control.feature b/features/rules/VER/VER000_Versioning-and-revision-control.feature index 10cbfa9bb..1026bc0dd 100644 --- a/features/rules/VER/VER000_Versioning-and-revision-control.feature +++ b/features/rules/VER/VER000_Versioning-and-revision-control.feature @@ -1,7 +1,6 @@ @implementer-agreement @VER @version1 -@E00020 Feature: VER000 - Versioning and revision control The rule verifies the presence of IFC entities used to track changes to building data over time and maintain a comprehensive history of those changes. diff --git a/features/rules/VRT/VRT000_Virtual-elements.feature b/features/rules/VRT/VRT000_Virtual-elements.feature index 10e14f29f..37e11e7f7 100644 --- a/features/rules/VRT/VRT000_Virtual-elements.feature +++ b/features/rules/VRT/VRT000_Virtual-elements.feature @@ -1,7 +1,6 @@ @implementer-agreement @VRT @version1 -@E00020 Feature: VRT000 - Virtual Elements The rule verifies the presence of IFC entities used to model special elements providing imaginary, placeholder, or provisional areas (e.g. clearance), volumes, and boundaries.