buildingSMART / buildingSMART/NextGen-IFC
Case sensitivity of IFC classes/entities
- Dominant language
- TeX
- Stars
- 64
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Refer to discussion:
https://forums.buildingsmart.org/t/ifc-entities-are-case-sensitive-or-not/1143
Description of the proposal:
Do we need to enforce case in the schema/documentation?
Describe how it contributes to the objectives set in https://github.com/buildingSMART/NextGen-IFC/wiki/Towards-a-technology-independent-IFC:
What do we win:
What do we loose
Schema impact:
Instance model impact:
Backwards compatible:
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
Research direction
Start with the linked buildingSMART forum discussion and the “Towards a technology-independent IFC” wiki page. Clarify whether the proposal changes schema naming, documentation, instance data, or all three, then define the compatibility and migration outcomes before identifying implementation work.
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