ArturTomczak

Thanks all, I mainly wanted to be sure if I'm not mistaken. And yes, this example is already removed from latest Dev branch. > My hope is to enforce it...

yes, we are now in the process of adding all missing IFC types of properties to bSDD, also Lists and Tables. While it might take a few weeks, the solution...

Hi @lfontanella, Interesting use case. The ClassProperty is an assignment of Property to a Class. The IFC schema only allows property sets to have unique properties (https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/IfcUniquePropertyName.htm) so there can't...

Good! I still don't understand why you define Thermal Transmittance property if it already exists and is standardised in IFC. https://identifier.buildingsmart.org/uri/buildingsmart/ifc/4.3/prop/ThermalTransmittance (yours: https://identifier.buildingsmart.org/uri/Iuav/UValue-CAM/0.32/prop/TT.01). Isn't it the same property? Also, why...

Closing and moving the discussion to the idea about exceptions: "Complete IDS by adding two more sections and recursion" #323

Resolved with #304

(1.) IfcRelServicesBuildings is deprecated, so shouldn't be used. Let's discuss in the IDS group if _IfcRelReferencedInSpatialStructure_ should be added to _PartOf_ facet. If not, we should update the IDS docs...

The first, seems to trigger an error because `.*` might as well be 'Pset_'. I tried changing the pattern to `Ps.*` and it still triggers an error, but `Psx.*` already...

Resolution: the IDS Purpose and Milestone now closely align with Purpose and Milestone description from the LOIN standard (EN17412). A user can use that IDS metadata to reference/implement their LOINs....

The group has reached a conclusion, and @giuseppeverduciALMA summarised it in #294. Closing this issue. If needed, please continue in #78.