IntraDataspace - An architecture of a company-internal Dataspace
summary
Architecture claims: map each project to a connector to share documents, measurements and time series across ~1,000 projects/year using Eclipse Dataspace Components (EDC) Connector, integrate company IAM and a company issue tracking system to create auditable human decision tickets for policy exceptions, and use a central catalog to avoid scraping thousands of endpoints. Prototype works for discoverability but abandons access-policy enforcement and faces scaling pain; proposed fixes are multi‑tenant connectors or scale‑to‑zero deployment.
AI-written summary · about
chapters (12)
- 0:00Intro to IntraDataspace
- 1:07Traditional data spaces overview
- 3:14Large company data challenges
- 4:40Projects as participants
- 6:04Integrating existing IT
- 7:30Control center architecture
- 9:13Contract negotiation in EDC
- 11:01Trust and governance
- 12:07Scaling challenges
- 13:14Extending to external sharing
- 15:02Benefits over content management
- 16:04Knowledge sharing
related talks
37mData Swamp to Data Swimming Pool: Cleaning up the Mess
28mEnergy Models That Speak the Same Language: The Story of ESDL
14mBootstrapping InnerSource at Airbus
36mMission Digital Twin - Asset Administration Shell (AAS) realized by Open Source
31mOpen Source – Yes, Please! but How? Experiences From the Future Energy Lab
35mWhen Research Project teams learn Open Collaboration
34mHacking The Corporate
28mHow Open Source Enables Innovation A Case Study with dbt and Lightdash