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.
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.
- Link to join mailing list goes here
- Link to public chat goes here
- Any other public communication link goes here
- [Panellist Name](link to github profile) <email@example.org> (@github handle)
- [Panellist Name](link to github profile) <email@example.org> (@github handle)
- Accessibility Panel
- App Authorization Panel
- Artificial Intelligence Panel
- Authentication Panel
- Caching Panel
- Client Side Libraries Panel
- Cryptography (Signing and Encryption) Panel
- Data Interoperability Panel
- Explaining the Vision Panel
- External Interop and Outreach Panel
- Identity Panel
- Internationalisation Panel
- Natural Language Processing Panel
- Privacy and Individuals Rights Protection Panel
- Query Panel
- Specification Entry Document Panel
- Teaching Materials Panel
- Test Suite Panel
All Panels can be reached on public-solid@w3.org
How to ensure that the technical decisions are taking accessibility considerations into account.
- Sina Bahram <sina@sinabahram.com> (@spudthebud)
- elf Pavlik <elf-pavlik@hackers4peace.net> (@elf-pavlik)
How do apps request access to specific containers, shapes, and/or realms of a user's data.
Wednesdays at 10AM Eastern at https://meet.google.com/dci-nqnf-exg
- Michiel de Jong <michieldj@inrupt.com> (@michielbdejong)
- Dmitri Zagidulin <dzagidulin@gmail.com> (@dmitrizagidulin)
- Michael Thornburgh <mthornbu@adobe.com> (@zenomt)
- Justin Bingham <justin.bingham@janeirodigital.com> (@justinwb)
- Jackson Morgan <jacksonm@inrupt.com> (@jaxoncreed)
To discuss Artificial Intelligence for Solid
- Tom <sideshowtom@yahoo.com> (@sideshowtom)
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)
Mondays at 10AM Eastern at https://hangouts.google.com/call/3k5z3gBVKm-58m8Xgm2YAEEE
- Dmitri Zagidulin <dzagidulin@gmail.com> (@dmitrizagidulin)
- Paul Worrall <paulw@inrupt.com> (@pjworrall)
- Michael Thornburgh <mthornbu@adobe.com> (@zenomt)
- Justin Bingham <justin.bingham@janeirodigital.com> (@justinwb)
- Jackson Morgan <jacksonm@inrupt.com> (@jaxoncreed)
- Aaron Coburn <aaronc@inrupt.com> (@acoburn)
- Matthias Evering <me@evering.eu> (@ewingson)
Ensure that caching mechanisms, both currently standardized and future standards are employed within Solid.
- Kjetil Kjernsmo <kjetil@inrupt.com> (@kjetilk)
(aim to be inserted here)
- Ruben Verborgh <Ruben.Verborgh@UGent.be>(@RubenVerborgh)
- Jeff Zucker <dubzed@gmail.com> (@jeff-zucker)
Discussion and specs related to performing decentralized Key Management, Cryptographic Signatures (including integration with Verifiable Credentials), and at-rest data Encryption on Solid servers.
- Dmitri Zagidulin <dzagidulin@gmail.com> (@dmitrizagidulin)
- Paul Worrall <paulw@inrupt.com> (@pjworrall)
- Justin Bingham <justin.bingham@janeirodigital.com> (@justinwb)
- Kjetil Kjernsmo <kjetil@inrupt.com> (@kjetilk)
- Rob McColl <rob@nix.software> (@robmccoll)
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.
- Dmitri Zagidulin <dzagidulin@gmail.com> (@dmitrizagidulin)
- Justin Bingham <justin.bingham@janeirodigital.com> (@justinwb)
- Eric Prud'hommeaux <eric@w3.org> (@ericprud)
- Max Dor <max@dorius.io> (@maxidorius)
- James Schoening <james.r.schoening.civ@mail.mil> (@jimschoening)
- Jose Emilio Labra Gayo <jelabra@gmail.com> (@labra)
- Ruben Verborgh <Ruben.Verborgh@UGent.be>(@RubenVerborgh)
- Kjetil Kjernsmo <kjetil@inrupt.com> (@kjetilk)
- Jason Reynolds <jason.reynolds@polarisalpha.com> (@JKReynolds)
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:
- solid-contrib/information#202
- solid-contrib/information#180
- https://github.com/solid/roadmap/pull/1
- https://github.com/solid/roadmap/pull/3
- https://github.com/solid/roadmap/pull/4
- https://github.com/solid/roadmap/pull/5
- https://github.com/solid/roadmap/pull/6
- https://github.com/solid/roadmap/pull/7
- https://github.com/solid/roadmap/pull/8
- https://github.com/solid/roadmap/pull/9
- dedicated forum thread
- GitHub team discussion board
- Explaining the Visions Solid Github Repository
- most converstation about "What is Solid" is here solid-contrib/Explaining-the-Vision-Panel#1 (comment)
- Dan Wilkinson <dan@get-even.co.uk> (@danwilkinsoncreative)
- Paul Worrall <paulw@inrupt.com> (@pjworrall)
- Ruben Verborgh <Ruben.Verborgh@UGent.be>(@RubenVerborgh)
- Justin Bingham <justin.bingham@janeirodigital.com> (@justinwb)
- Kjetil Kjernsmo <kjetil@inrupt.com> (@kjetilk)
How to technically link to other initiatives to build positive win-win collaborations.
- Dmitri Zagidulin <dzagidulin@gmail.com> (@dmitrizagidulin)
- David H. Mason <vid_github_solid_outreach@zooid.org> (@vid)
Discussions and specs for expanding the capabilities of Solid's WebID identity system, including user profiles, Decentralized Identifiers (DIDs), and related standards.
- Dmitri Zagidulin <dzagidulin@gmail.com> (@dmitrizagidulin)
- Paul Worrall <paulw@inrupt.com> (@pjworrall)
- Justin Bingham <justin.bingham@janeirodigital.com> (@justinwb)
To ensure internationalisation is taken into consideration during the Solid design.
- King Wang <kingwang@hsfranchise.com> (@kingwang88)
- Philip Laszkowicz <phil@fillip.pro> (@HelloFillip)
- elf Pavlik <elf-pavlik@hackers4peace.net> (@elf-pavlik)
To discuss Natural Language Processing for Solid
- Tom <sideshowtom@yahoo.com> (@sideshowtom)
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.
- Max Dor <max@dorius.io> (@maxidorius)
Discussion, specs and recommendations for implementing querying mechanisms beyond LDP, such as SPARQL, Triple Pattern Fragments (TPF), GraphQL, and others.
- Dmitri Zagidulin <dzagidulin@gmail.com> (@dmitrizagidulin)
- Aaron Coburn <aaronc@inrupt.com> (@acoburn)
- Ruben Verborgh <Ruben.Verborgh@UGent.be>(@RubenVerborgh)
- Kjetil Kjernsmo <kjetil@inrupt.com> (@kjetilk)
- Jeff Zucker <dubzed@gmail.com> (@jeff-zucker)
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.
- Ruben Verborgh <Ruben.Verborgh@UGent.be>(@RubenVerborgh)
- Kjetil Kjernsmo <kjetil@inrupt.com> (@kjetilk)
- Sarven Capadisli <csarven@inrupt.com> (@csarven)
- Justin Bingham <justin.bingham@janeirodigital.com> (@justinwb)
- King Wang <kingwang@hsfranchise.com> (@kingwang88)
The Solid Teaching Material Panel has the aim to produce content to be able to effectively teach people to build Solid identity providers, Pods, and apps. The Solid teaching material can be found in this file. Documentation.md is a place that gives an overview of all the content in this file and links to it.
- Vincent Tunru <vincentt@inrupt.com> (@Vinnl)
- Jose Emilio Labra Gayo <jelabra@gmail.com> (@labra)
- King Wang <kingwang@hsfranchise.com> (@kingwang88)
- Raul R Pearson (@raulrpearson)
- Arne Hassel <arneh@inrupt.com> (@megoth)
- Jackson Morgan <jacksonm@inrupt.com> (@jaxoncreed)
- Dan Wilkinson <dan@get-even.co.uk> (@danwilkinsoncreative)
- Kartika Tulusan @artificialgods_gitlab
Include the test suite in the Solid specification.
- Aaron Coburn <aaronc@inrupt.com> (@acoburn)
- elf Pavlik <elf-pavlik@hackers4peace.net> (@elf-pavlik)
- Jackson Morgan <jacksonm@inrupt.com> (@jaxoncreed)
- Kjetil Kjernsmo <kjetil@inrupt.com> (@kjetilk)
- Scott McWhirter <scott@konobi.co.uk> (@konobi)
- Michiel de Jong <michieldj@inrupt.com> (@michielbdejong)