buildingSMART / buildingSMART/IFC5-development
[ How to find the actual path of a node ]
- Dominant language
- HTML
- Stars
- 220
- Forks
- 80
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 2
Description
Not sure what title to give, not sure if you already tought about that and if it is a problem:
- suppose to have the hello-wall example, then add the 2nd storey from the course by declaring a new node that inherits from the existing storey
- since the original storey contained a Space Boundary, the new storey will have aswell
- now, when refering to the "relatingSpace", both will have as path: **"e3035b71-bd9f-4cdc-86fd-b56e2f4605b6"**
but in actual implementation, how do you know if it is refering to the space on the original floor, to the one on the new floor, or both?
I mean, if I ask, which is the space referred from the space boundary on the first floor, it is not possible to answer, because this is ambiguous
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the hello-wall example and the second-storey course example, focusing on the inherited Space Boundary and its relatingSpace path. Determine how the implementation should distinguish the original-floor space from the new-floor space, and document a resolution for the ambiguity.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100