Skip to content

Latest commit

 

History

History
136 lines (103 loc) · 9.54 KB

panels.md

File metadata and controls

136 lines (103 loc) · 9.54 KB
Raw

Solid Panels

Below is a listing of Solid Panels. Solid Panels are groups of individuals focused on a specific problem or domain relevant to Solid, with an aim to propose changes to the Solid Specification, Solid Roadmap, and/or Supporting Documentation. Anyone may join a panel or suggest a new panel.

Anyone can create a Solid Panel by submitting a request to the Solid W3C community group mailing list, or by making a pull request directly to this document.

This listing helps people find panels in which they may want to participate, and helps editors find panels to consult as part of the editorial process.

Example Panel

This is an example that people can use as a template for submitting their own panels. A description of the panel, including its focus and goal, should go here.

Communication channels

  • Link to join mailing list goes here
  • Link to public chat goes here
  • Any other public communication link goes here

Panelists

Editorial Assignment

Candidate Proposals to the Solid Specification produced by this panel are likely to be associated with the Editorial Assignment Name, and will be principally reviewed by any editors assigned to it.

Index of Panels

All Panels can be reached on [email protected]

There is a weekly W3C Solid Community Group call to review all panels on Thursdays alternating between 1000CEST and 1600CEST on https://zoom.us/j/121552099. See here to read the minutes of previous calls, find out the agenda and exact time of the next call, or to add an item to the next agenda.

You can also read weekly updates of all panels on This Week in Solid.

Authorization

How various agents and authorized to access resources.

Communication channels

Panelists

Editorial Assignment

Candidate Proposals to the Solid Specification produced by this panel are likely to be associated with the Authorization editorial topic, and will be principally reviewed by any editors assigned to it.

Authentication

Discussion and specs relating to Authentication and Auth Delegation protocols, including:

  • Solid-OIDC auth delegation protocol
  • WebID-TLS auth delegation protocol
  • Username + password recommendations for local authentication
  • WebAuthentication (proposed future integration)
  • DID Authentication (proposed future integration)
  • HTTP Signatures (proposed future integration)

Communication channels

Panelists

Editorial Assignment

Candidate Proposals to the Solid Specification produced by this panel are likely to be associated with the Authentication editorial topic, and will be principally reviewed by any editors assigned to it.

Interoperability

Ensuring the interoperability of data as it is read and written by different users and/or applications. Topics of discussion will include vocabularies, shapes, shape trees, and the mechanisms through which these work together to provide consistent and safe access and manipulation of data in a pod by different agents and/or users.

Communication channels

Panelists

Editorial Assignment

Candidate Proposals to the Solid Specification produced by this panel are likely to be associated with the Data Interoperability and Portability editorial topic, and will be principally reviewed by any editors assigned to it.

Test Suite

The panel will develop open source conformance testing software, author and review tests, release implementation reports, and provide feedback to technical report development. See [Charter]((https://github.com/solid/process/blob/main/test-suite-panel-charter.md)

Communication channels

Notifications

Development of mechanisms to shape and exchange notifications. See Charter.

Communication channels

Editorial Assignment

The test suite should never contradict the Solid specification. When implementations and specification disagree, the test suite can help bring them closer together, but should not itself act as a voice in the discussion. It should help pod server implementations comply with the specification. It should help pod server implementations be compatible with one another. It doesn't necessarily have to test every possible combination of situations as long as it is useful to pod server implementers, and the reports its produces are a reliable source of information.