Interoperable Infrastructure for Universities, Enterprises and the Public Sector
summary
Manual Erasmus paperwork spawns thousands of emails; a concrete alternative uses Matrix federation for Slack-like messaging, Open Cloud Mesh (Nextcloud et al.) for cross‑server file shares, and JSON‑LD with schema.org for machine-readable course data so crawlers stop breaking. The claim: combining these reduces brittle scraping and signer chains, scales to 65 alliances (~8–9 members each) without centralizing on a US vendor, supports end‑to‑end encryption, and lets framing/expand operations yield unambiguous English name/ECTS fields.
AI-written summary · about
chapters (14)
- 0:00Interoperable infrastructure intro
- 1:57Email fails for student mobility
- 3:46EU Interoperable Europe Act
- 6:15Risks of proprietary solutions
- 8:41Three interoperability use cases
- 9:24Decentralized messaging with Matrix
- 11:31Federated file sharing with OpenCloudMesh
- 13:37Challenges in data sharing
- 16:52Problems with ad-hoc APIs
- 17:34Semantics with JSON-LD
- 25:25Benefits of lightweight standards
- 26:06Summary of technical solutions
- 26:50Interoperability first in development
- 27:33Q&A on funding
related talks
29mDMLS, MIMI, etc
31mUsing European Open Source to build a Sovereign Multi-Cloud
15mJourneying through Data Spaces - New Path to Interoperability?
40mSovereignty Spotlight: EU Regulations and the...
53m36C3 PART 4: Alexis Roussel, Gregor Žavcer & Sergey Simanovsky EPI #115
25mData collaboration with Federated Learning
39mMobility of the Future and Open Collaboration – A good Idea?
30mThe Challenge of Decentralised Communication