buildingSMART / buildingSMART/IFC4.x-development
Proposal for Location to fall back to the referenced IfcExternalInformation if null
Open
allocated
allocated-core
ifc-update-out
- Dominant language
- Python
- Stars
- 234
- Forks
- 123
- Avg merge
- 15h 4m
- Merged PRs (30d)
- 5
Description
IfcExternalInformation like IfcDocumentInformation, IfcLibraryInformation, IfcClassification has an inherited Location.
The references to the document / library / classification, (i.e. subclasses of IfcExternalReference) all also have an inherited Location.
The external reference may be associated back to the external information.
I think it makes sense to state that if the external reference Location is set to null, the next place to check for a location would be the external information's Location as a fallback.
Does this make sense? Should a sentence be written about it in the docs?
Contributor guide
Assessment
This issue has not been assessed yet.