buildingSMART / buildingSMART/NextGen-IFC
Transactional Exchanges
- Dominant language
- TeX
- Stars
- 64
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
One discussion I would like to open regarding this topic is a request protocol for querying data. An efficient way would be to standardize the pulling of data through a protocol. Probably mvdxml could serve as a basis. In essence, send your request e.g. as an mvdxml and get the data back (whether SPF, XML, JSON or any other format). It is probably a complementary method to APIs as it would also support complete file exchange.
Currently, everyone has to setup their IFC export in their tool whether it be Archicad, Revit, Allplan etc. instead of the receiver defining what they want and send a standardized request to the tool generating the data.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue does not identify repository files, tests, or entry points. Start by reviewing the proposed mvdxml-based request protocol and how existing APIs and complete file exchange are handled; done would require an agreed standard for requesting data and returning it in formats such as SPF, XML, or JSON.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- xml
- Domain
- api, backend-api-design, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100