Skip to content

Latest commit

 

History

History
367 lines (279 loc) · 24 KB

panels.md

File metadata and controls

367 lines (279 loc) · 24 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.

Accessibility

How to ensure that the technical decisions are taking accessibility considerations into account.

Communication channels

Panelists

Editorial Assignment

currently none

Auditing Panel

Pertaining to the mechanisms through which access and manipulation events of resources in a data pod are recorded and accessible.

Communication channels

Panelists

Editorial Assignment

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

Authorization and Access Control

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.

Artificial Intelligence

To discuss Artificial Intelligence for Solid

Communication channels

Panelists

Editorial Assignment

currently none

Authentication

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

  • WebID-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.

Caching

Ensure that caching mechanisms, both currently standardized and future standards are employed within Solid.

Communication channels

Panelists

Editorial Assignment

currently none

Cryptography, Security, and Privacy

Discussion and specs related to performing decentralized Key Management, Cryptographic Signatures (including integration with Verifiable Credentials), and at-rest data Encryption on Solid servers. Pertaining to mechanisms used and considerations taken when securing a data pod, a conformant server implementation, and/or the immediate ecosystem around them. Pertaining to the mechanisms through which cryptographic techniques are employed to provide data privacy, data integrity, and verifiable information. The focus of this panel is to ensure Privacy is always kept in mind in the various proposals of the project across all panels, and that individuals' rights are inherently protected in the Solid ecosystem. It will do so by:

  • Leading Privacy discussions and initiatives.
  • Reviewing the proposals of other panels for anything Privacy related, and provide guidance to them if requested.
  • Researching how the technical side of the project (specification, implementations):
    • Can affect the Privacy of individuals; Per example by unexpectedly leaking information in the protocol itself.
    • Affect their rights; Per example by making it difficult for them to find privacy policies or delete remote content.
    • Lead to any kind of harm to the individual; Per example, by allowing a malicious individual to publish private content unchecked.
  • Ensuring practical guides are produced for individuals and Data Privacy Officers alike, allowing them to know how to deal with their legal rights and obligations respectively.
  • Making sure laws like GDPR are directly taken into account when designing new feature / product / software.

Communication channels

Panelists

Editorial Assignment

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

Data Interoperability and Portability

Ensuring the interoperability of data as it is read and written by different users and/or applications. Topics of discussion will include vocabularies, shapes, footprints, 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. Pertaining to mechanisms that ensure disparate applications or agents can safely and seamlessly read and write the data they need. Pertaining to mechanisms that ensure the portability of data stored in a data pod such that it can be safely migrated between conformant Solid server implementations, as well as exported to other mediums.

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.

Events and Notifications

Pertaining to mechanisms that process and/or emit events between pods and agents, or other pods. Development of mechanisms to shape and exchange notifications.Development of mechanisms to shape and exchange notifications.

Communication channels

Panelists

Editorial Assignment

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

Explaining the Vision

Taking the suggestions on the channels listed below to produce proposals explaining what is Solid and the Solid vision, mission, and values. Related conversations to take into consideration:

Communication channels

Panelists

Editorial Assignment

currently none

External Interop and Outreach

How to technically link to other initiatives to build positive win-win collaborations.

Communication channels

Panelists

Editorial Assignment

currently none

Identity

Discussions and specs for expanding the capabilities of Solid's WebID identity system, including user profiles, Decentralized Identifiers (DIDs), and related standards.

Communication channels

Panelists

Editorial Assignment

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

Internationalisation

To ensure internationalisation is taken into consideration during the Solid design.

Communication channels

Panelists

Editorial Assignment

currently none

Resource Access

Pertaining to the access of resources in a data pod over a network via HTTP and LDP

Communication channels

Panelists

Editorial Assignment

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

Query

Discussion, specs and recommendations for implementing querying mechanisms beyond LDP, such as SPARQL, Triple Pattern Fragments (TPF), GraphQL, and others.

Communication channels

Panelists

Editorial Assignment

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

Self Hosting Panel

Develop clarity on how to self-host and remain interoperable with other Pod providers.

Communication channels

Panelists

  • Danny Haider

Editorial Assignment

currently none

Specification Entry Document Panel

To create a structure for the document at https://github.com/solid/specification/, and the division in documents it links to and well as translating the community consensus regarding the application of the specifications mentioned in this document into a clear, unambiguous and implementable text.

Communication channels

Panelists

Editorial Assignment

currently none

Editorial Assignment

Candidate Proposals to the Solid Specification produced by this panel are likely to be associated with the general editors, and will be principally reviewed by any editors.

User Lifecycle

To build Solid-based APIs for registering, commissioning, recovery, deleting and managing users and their Pods.

Communication channels

Panelists

Editorial Assignment

currently none