NickNisbet

a. I don't believe sup-port nesting has ever been used. b. However, consider a UK small-power plug and a socket. These can be represented as a port-to-port connection. If necessary...

Yes, we need Exceptions (not IfcSpace and not IfcOpeningElement) alongside Applicability and Requirement. Also Selections (any IfcWindow and any IfcDoor) or (any IfcWindow and anything with ThermalTransmittance>0.2) Regards, Nick. From:...

I quote form the enquiry below, seeking the implementation of Exceptions. > Can I check if this is wrong? I expected that each entry in an Applicability list would progressively...

To meet your expectation, the applicability should have entity is a ifcfurnishingelement only but the requirement should hold the pset name and property value. This then would verbalise as passing...

I am currently battling with writing the buildingSMART Sustainability IDS standard without it becoming tediously long and unmanageable: I believe that there is a need for 1. a Selection section...

It seems extraordinary that requirements are appearing in the application section (for example) there should be a lift, instead of expressing that (for example) a building should have a lift...

Leaving the requirement empty is not natural. It is not understandable. Requirements (even if cardinality or valency) should not be in applicability . ‘There should be a lift’ is not...

Yes, my example was a bit too functional, but the point that requirements are appearing in the application section stands. This lack of clarity is happening because of the lack...

This is Applicability: Valve Relevant Requirement Field identifier Logically this is not(valve) or not(relevant) or field_identifier Sent whilst away from my desk. Regards, Nick. Nicholas Nisbet FRSA MA(Cantab) DipArch(UNL) Fellow:...

Lets not make 'has it been used by brand X or brand Y?' the criteria. Does a complex property have meaning? Yes, because some properties have meta-properties surrounding it (like...