buildingSMART / buildingSMART/IFC4.x-development

Proposal to remove IfcPropertySetDefinitionSelect / IfcPropertySetDefinitionSet

Open
#1,157 2 comments 0 reactions 0 assignees View on GitHub
after-NWI iso-compatibility
Dominant language
Python
Stars
234
Forks
123
Avg merge
15h 4m
Merged PRs (30d)
5

Description

I am the only person, after how many years of IFC radiation exposure, of being surprised by this? :) https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/IfcPropertySetDefinitionSelect.htm

Would love to hear if there's something I'm missing, but from what I can tell this is merely an anomaly that changes the usual 1:N relationship classes into a N:N relationship ... and it's sometimes 1:N, sometimes N:N. Surely this would trip up lots of people.

Is the semantics of "this group of properties is related to that group of elements" so important?

Contributor guide

Open the contributing guide

Research direction

Start with the linked IFC4x3 lexical page for IfcPropertySetDefinitionSelect and IfcPropertySetDefinitionSet, then compare the documented 1:N and N:N relationship semantics. The issue does not name implementation files or tests; done would require a maintainer decision on whether these constructs should be removed and corresponding specification updates.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.