``PSE001`` Standard properties and property sets validation - v3
========================================================================================================================================================================================================

.. parsed-literal::

   001 | \@implementer-agreement
   002 | \@PSE
   003 | \@version3
   004 | Feature: PSE001 - Standard properties and property sets validation
   005 | The rule verifies that each IfcPropertySet starting with 'Pset\_' is defined correctly.
   006 | 
   007 |   Background:
   008 |    :doc:`Given An .IfcPropertySet. </steps/stepsentity_selectionpy_Anentity_opt_stmt>`
   009 |    :doc:`Given its .Name. attribute ^starts^ with 'Pset\_' </steps/givensattributespy_Itsattributeattributeprefix_conditionprefix_conditionwithprefix>`
   010 | 
   011 | 
   012 |   Scenario: IfcPropertySet Name
   013 | 
   014 |     :doc:`Then The .IfcPropertySet. attribute .Name. must use standard values [according to the table] 'pset\_definitions' </steps/stepspropertysets_qtys_unitspy_Theinst_typeproperty_set_or_element_quantityattributeNamemustusestandardvaluesaccordingtothetabletable>`
   015 | 
   016 | 
   017 |   Scenario: Property Name
   018 | 
   019 |       :doc:`Then Each associated .IfcProperty. must be named [according to the table] 'pset\_definitions' </steps/stepspropertysets_qtys_unitspy_Eachassociatedinst_typeproperty_or_physical_quantitymustbenamedaccordingtothetabletable>`
   020 | 
   021 | 
   022 |   Scenario: PropertySet definitions
   023 | 
   024 |       :doc:`Then The .IfcPropertySet. must be related to a valid entity type [according to the table] 'pset\_definitions' </steps/stepspropertysets_qtys_unitspy_Theinst_typeproperty_set_or_element_quantitymustberelatedtoavalidentitytypeaccordingtothetabletable>`
   025 | 
   026 | 
   027 |   Scenario: Property Type
   028 | 
   029 |       :doc:`Then Each associated .IfcProperty. must be of valid entity type [according to the table] 'pset\_definitions' </steps/stepspropertysets_qtys_unitspy_Eachassociatedinst_typeproperty_or_physical_quantitymustbeofvalidentitytypeaccordingtothetabletable>`
   030 | 
   031 | 
   032 |   Scenario: Property Data Type
   033 | 
   034 |         :doc:`Then Each associated .IfcProperty. value must be of valid data type [according to the table] 'pset\_definitions' </steps/stepspropertysets_qtys_unitspy_Eachassociatedinst_typeproperty_or_physical_quantityvaluemustbeofvaliddatatypeaccordingtothetabletable>`
   035 | 

.. rubric:: Version history

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

   * - Version
     - Tag
     - Date
     - Commit
     - Rule link
   * - v1
     - :tag:`v0.6.6`
     - 2024-01-16
     - :commit:`8c4e0eda347e37c444f61eee4391f78b29f6880c`
     - `view <https://github.com/buildingSMART/ifc-gherkin-rules/blob/release/0.6.6/features/PSE001_Standard-properties-and-property-sets-validation.feature>`_
   * - v2
     - :tag:`v0.6.6`
     - 2024-05-13
     - :commit:`8bca3ddaeb5defcc307d9e2aca6a9449363d76c4`
     - `view <https://github.com/buildingSMART/ifc-gherkin-rules/blob/release/0.6.6/features/PSE001_Standard-properties-and-property-sets-validation.feature>`_
   * - v3
     - :tag:`v0.7.1`
     - 2025-02-27
     - :commit:`8f4976cba3bc740263ce20838b089f5f896fc813`
     - `view <https://github.com/buildingSMART/ifc-gherkin-rules/blob/release/0.7.1/features/rules/PSE/PSE001_Standard-properties-and-property-sets-validation.feature>`_