Dion Moult
Dion Moult
> As there is a need for heigh/width for almost any predefined type why not just move it in a pset that apply to all predefined type ? Less cases...
I did think about that, but I couldn't identify what that element would be. When the electrical engineer described it to me, the example of "DALI" did not seem like...
Note that in the new system, you lose the ability to have multiple addresses.
> ... some sort of 'null' material I'll really be stretching my imagination here. Cheers, that makes three of us happy to make it non optional.
Yes, this is a problem. However, some properties should exist on the object, not the material, because the object is tested as a system, and the material is simply a...
@TLiebich to move this into proposal can you help list exactly what changes need to be made? Or a PR?
+1 that makes complete sense to me. Ping @aothms ?
I would like to extend the proposal to include: - IfcReinforcingBar - IfcTendon
Ping @Jesusbill @krande @jmirtsch is there a commonality between the attributes on IfcReinforcingMesh(Type) IfcReinforcingBar(Type) and IfcTendon(Type) that can be shared if these attributes were migrated to a property set?
Good point, I am working with Brickschema who has a lot of experience in referencing timeseries (they require an external reference) so once I have a prototype testing this out...