rvba/ifc-data-horse
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Actualiser README.md

Browse source
This commit is contained in:
Milovann Yanatchkov 2025-11-23 10:59:23 +01:00
parent 80fa76fcd9
commit 37f6ad670e
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -25,14 +25,14 @@
* Although **OpenBIM** aims to support **interoperability**, it still lacks robust mechanisms for * Although **OpenBIM** aims to support **interoperability**, it still lacks robust mechanisms for
> **bi-directional data exchange** > **bi-directional data exchange** ✅
* —particularly when it comes to **re-integrating data into CAD and CDE environments**. * —particularly when it comes to **re-integrating data into CAD and CDE environments**.
* **Existing initiatives often do not prioritize full OpenBIM compliance**, leaving a clear opportunity for alternative, standards-aligned solutions. * **Existing initiatives often do not prioritize full OpenBIM compliance**, leaving a clear opportunity for alternative, standards-aligned solutions.
### 'Flat Modules' vs 'Monolithic Blob' ### 'Flat Modules' vs 'Monolithic Blob'
> At the same time, the emerging **modularized and layerized IFC5** standard > At the same time, the emerging **modularized and layerized IFC5** standard ✅
* introduces new capabilities for more flexible, **fine-grained**, and machine-friendly data handling. * introduces new capabilities for more flexible, **fine-grained**, and machine-friendly data handling.
* These advances open the door to **new workflows** built around decentralized, **event-driven data exchange** rather than **monolithic file transfers**. * These advances open the door to **new workflows** built around decentralized, **event-driven data exchange** rather than **monolithic file transfers**.