``OJT001`` Object predefined type - v3
========================================================================================================================================================================================================

.. parsed-literal::

   001 | \@implementer-agreement
   002 | \@OJT
   003 | \@version3
   004 | Feature: OJT001 - Object Predefined Type
   005 | 
   006 |   The rule verifies that the attribute 'PredefinedType' for object occurrences
   007 |   is used in accordance with Concept Template 4.1.3.2 - Object Predefined Type.
   008 |   Ref: https://standards.buildingsmart.org/IFC/RELEASE/IFC4\_3/HTML/concepts/Object\_Attributes/Object\_Predefined\_Type/content.html
   009 | 
   010 | Background:
   011 |   :doc:`Given a model with Schema 'IFC4' or 'IFC4.3' </steps/givensattributespy_Afile_or_modelwithfieldvalues>`
   012 | 
   013 | Scenario: Validating the proper use of USERDEFINED PredefinedType for an object typed at the occurrence
   014 |   :doc:`Given An .IfcObject. ^with subtypes^ </steps/stepsentity_selectionpy_Anentity_opt_stmtsubtype_handling>`
   015 |   :doc:`Given .IsTypedBy. ^is^ empty </steps/stepsattribute_valuepy_attributecomparison_operatorequal_or_not_equalvalue>`
   016 |   :doc:`Given .PredefinedType. ^is^ 'USERDEFINED' </steps/stepsattribute_valuepy_attributecomparison_operatorequal_or_not_equalvalue>`
   017 |   :doc:`Then The value of attribute .ObjectType. must be ^not empty^ </steps/thensattributespy_Thevalueofattributeattributemustbevalue_or_comparison_op>`
   018 | 
   019 | Scenario: Validating the proper use of USERDEFINED PredefinedType for an object typed by IfcTypeObject
   020 |   :doc:`Given An .IfcTypeObject. ^with subtypes^ </steps/stepsentity_selectionpy_Anentity_opt_stmtsubtype_handling>`
   021 |   :doc:`Given .PredefinedType. ^is^ 'USERDEFINED' </steps/stepsattribute_valuepy_attributecomparison_operatorequal_or_not_equalvalue>`
   022 |   :doc:`Then The value of attribute .ElementType. must be ^not empty^ </steps/thensattributespy_Thevalueofattributeattributemustbevalue_or_comparison_op>`
   023 | 
   024 | Scenario: Validating the proper use of PredefinedType for an Object typed by IfcTypeObject
   025 |   :doc:`Given A model with Schema 'IFC4' or 'IFC4.3' </steps/givensattributespy_Afile_or_modelwithfieldvalues>`
   026 |   :doc:`Given An .IfcTypeObject. ^with subtypes^ </steps/stepsentity_selectionpy_Anentity_opt_stmtsubtype_handling>`
   027 |   :doc:`Given Its .PredefinedType. attribute ^does not start^ with 'NOTDEFINED' </steps/givensattributespy_Itsattributeattributeprefix_conditionprefix_conditionwithprefix>`
   028 |   :doc:`Given A relationship .IfcRelDefinesByType. from .IfcTypeObject. to .IfcObject. and following that </steps/givensrelationshipspy_Arelationshiprelationshipdir1from_toentitydir2from_toother_entitytailmaybe_and_following_that>`
   029 |   :doc:`Then The value of attribute .PredefinedType. must be ^empty^ [and display entity instance] </steps/thensattributespy_Thevalueofattributeattributemustbevalue_or_comparison_opdisplay_entitydisplay_entity>`

.. rubric:: Version history

.. list-table::
   :header-rows: 1

   * - Version
     - Tag
     - Date
     - Commit
     - Rule link
   * - v1
     - :tag:`v0.6.6`
     - 2024-06-06
     - :commit:`816455630f0fdbed987c7f6cb0ed208f25a07015`
     - `view <https://github.com/buildingSMART/ifc-gherkin-rules/blob/release/0.6.6/features/OJT001_Object-predefined-type.feature>`_
   * - v2
     - :tag:`v0.6.6`
     - 2024-07-10
     - :commit:`b84422143af4e077d8be670d1710c95563d7ea7d`
     - `view <https://github.com/buildingSMART/ifc-gherkin-rules/blob/release/0.6.6/features/OJT001_Object-predefined-type.feature>`_
   * - v3
     - :tag:`v0.8.3`
     - 2025-11-13
     - :commit:`45a7c1151eb79c95356ea8f208430703df9b6707`
     - `view <https://github.com/buildingSMART/ifc-gherkin-rules/blob/release/0.8.3/features/rules/OJT/OJT001_Object-predefined-type.feature>`_