buildingSMART / buildingSMART/IFC4.x-development

Inconsistency in cardinality of property sets vs material properties

Open
#452 1 comment 0 reactions 0 assignees View on GitHub
allocated allocated-core ifc-update-out
Dominant language
Python
Stars
234
Forks
123
Avg merge
15h 4m
Merged PRs (30d)
5

Description

This situation is valid for IfcPropertySet:

IfcWallX, IfcSlabX <- IfcRelDefinesByProperties -> IfcPropertySetX

I.e. a single property set may be shared by multiple entities.

Material properties cannot be shared.

IfcMaterial -> IfcMaterialProperties

I suspect that this is more of an "IFC5" issue, but it would be really nice to make this cardinality consistent. Right now it adds an edge case whenever anybody wants to write code that manipulates properties.

Contributor guide

Open the contributing guide

Research direction

Start with the issue's comparison of IfcPropertySet and IfcMaterialProperties cardinalities in the IFC4.x specification. Determine whether the inconsistency should be resolved in IFC4.x or deferred to IFC5, then document the agreed cardinality behavior; done means the specification decision is recorded.

Written by the indexing model from the issue text.

Assessment

Domain
data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.