buildingSMART / buildingSMART/NextGen-IFC
Have more meaningful prefix than Pset or Qset for standardized property sets
Open
Decision made
enhancement
- Dominant language
- TeX
- Stars
- 64
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Description of the proposal:
Having "Pset" and "Qset" as prefix for "official" property sets is quite funny. Could the prefix be something else, like IFC, or nothing. Why do we need them?
What do we win:
More meaningful property set names
What do we loose
?
Schema impact:
None
Instance model impact:
Small
Backwards compatible:
None
Automatic migration possible:
?
Additional implications:
-
Note that not all points need to be satisfied!
Backwards compatibility and file size are not concerns.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.