We must be able to support data interoperability across applications while enabling secure collaboration and query using intuitive data boundaries.
Diversity in how the same data will be accessed and manipulated by different entities and applications increases the need for reliable mechanisms that protect against data corruption, data leakage, or broken workflows
Standard methods and mechanisms for interoperability, collaboration, and security of data in a Solid Pod must realize these needs, and it must be done without changing the fundamentals of Solid.
Read our stated Problems and Goals for an in-depth understanding of the panel's focus.
- Specification — Source — Rendered
- Application Primer — Source — Rendered
- Authorization Agent Primer — Source — Rendered
- Resources
- Publish 1.0 Draft of Application Interoperability Specification
- Publish 1.0 Draft of Application Primer
- Publish 1.0 Draft of Authorization Agent Primer
- Complete Typescript library implementation
- Complete Java library implementation
- Complete Typescript Authorization Agent Service implementation
- Publish 1.0 Draft of Shape Trees Specification
- Publish 1.0 Draft of Shape Trees Primer
- Complete Typescript Shape Tree Implementation
- Complete Java Shape Trees Implementation
- Submit Server-side Shape Tree validation to solid/specification
- Integrate server-side Shape Tree validation into CSS
Resource Metadata — Resource Metadata was submitted as a candidate proposal to the solid/specification. It was renamed to Auxiliary Resources during Editorial Review.
The work items of the Solid Data Interoperability Panel are discussed during the following Solid Community Group meetings.
- General meetings: every Wednesday from 14:00 to 15:00 UTC
- Special topic meetings: tentative on Tuesdays from 14:00 to 16:00 UTC
Both meetings take place in the solid-cg Jitsi room.
Please refer to the Solid Community Group calendar and the Special Topic Meetings schedule for more information. Every meeting is also announced on Matrix, with a link to its agenda.
Initiative proposals must be submitted as issues, and receive support from members of the panel. At least three panelists (not including the panelist proposing the project) must support creation of the project, with no panel members actively rejecting it. Initiative proposals with support will be prioritized and undertaken by the panel.
Substantive changes submitted to active panel initiatives should be submitted as pull requests, and should receive at least two review approvals from panelists, with no one actively rejecting.
Panel members should work together to settle deadlocks. It may be helpful to request the perspective of a Solid Editor who would ultimately be responsible for accepting submitted candidate proposals to settle deadlocks.