Léon van Berlo comments

Results 92 comments of


                                            Léon van Berlo

Use common base16 encoded GlobalIds instead of bespoke base64

Great suggestion!

Lack of randomness in pset template GlobalIds

policy for IFC 4.3.x is that property names and Pset names are unique. Names can be used as identifier.

Badly defined psets for infrastructure

Seems the allocation of these Psets has changed, so assuming they are fixed now. Could someone confirm?

Badly defined psets for infrastructure

@larswik

Badly defined psets for infrastructure

looks fixed

Properties and quantities not differentiated

In IFC 4.3 the properties are normalized. In your example the property 'length' is the same in every Pset. Properties have unique names throughout the full spec of IFC.

Properties and quantities not differentiated

Ah; I see your point now. Indeed this needs to be clarified.

Multiple regex patterns in the same requirement

A combination of (multiple) patterns and other restrictions like enumerations, min/max restrictions, etc. is also possible.

Restriction of values: Enumeration limited to string-based datatype or do we allow for real, integer and measurements

I would say Strings for IfcLengthMeasurement is not supported in IDS, or anywhere else in a situation where we want interoperability.

Add textual definitions to each IDS element

You can find those in IDS under 'instructions' and 'description'.