diff --git a/draft-working-group-charter/charter-style.css b/draft-working-group-charter/charter-style.css deleted file mode 100644 index 551b783..0000000 --- a/draft-working-group-charter/charter-style.css +++ /dev/null @@ -1,89 +0,0 @@ -#template h1 { clear: none } - -form { width: 90%; - background: #eee5de; - color: black; - border: thin black solid; - padding: .5em; - margin-bottom: 1em; - margin-left: auto; - margin-right: auto - } - -body { counter-reset: h2; } - -h2.nocount:before { content: "" } - -h2:before { - content: counter(h2) ". "; - display: inline; - } - -h2.nocount { - counter-increment: none; - counter-reset: none - } - -h2 { - counter-increment: h2; - counter-reset: h3; - } - -h3:before { - content: counter(h2) "." counter(h3) " "; - display: inline; - } - -h3 { counter-increment: h3; } - -h4 { margin-left: 0 } - -tfoot -{ - font-size: 0.9em; - font-style: italic; - background-color: #ddd; -} - -td.meeting { background: #FFE } -td.WD1 { background: #FED } -td.LC { background: #FCB } -td.CR { background: #FA9 } -td.PR { background: #F87 } -td.REC { background: #F60 } -td.note { background: #F60 } - -.toadd { background-color: #FF0; font-style: italic} - -strong.must { color: #F30; } - -strong.should { color: #C63; padding: 0; border: none } -.should { - padding: .25em; - border: thin #C63 solid; - } - -li.may, strong.may { color: #99C; } -div.may { - padding: 3px; - background-color: #e2edfe; - border: 1px #005A9C solid; } - -.example -{ - background-color: #CC9; -} - -div.example, ul.example, p.example, ol.example -{ - width: 80%; - border: thin black solid; -} - -@media print { - .noprint { display: none } -} - -.todo { - background-color:#FFC; -} \ No newline at end of file diff --git a/draft-working-group-charter/index.html b/draft-working-group-charter/index.html deleted file mode 100644 index 42da5da..0000000 --- a/draft-working-group-charter/index.html +++ /dev/null @@ -1,608 +0,0 @@ - - - - - - W3C Solid Working Group Charter DRAFT-BR-2023-01-23 - - - - - - - - - - - -
-

Solid Working Group Charter

- -

- Cloud services in use on the Web today (2023) often require users to store their data and place control over that data at a third-party cloud provider. Solid adds to existing Web standards to enable user control: to realise a space where individuals can maintain their autonomy, control their data and privacy, and choose applications and services to fulfil their needs. Solid defines the notion of Pods, in which users place their own data and control access to that data, and a suite of interoperable protocols for managing Pods, applications that use pods, and interactions with existing protocols for authentication. - - Solid presents several advantages over more traditional architectures for data use by Web services today, including: -

- - - -

- W3C Members that would like to learn more about the motivations that led to this work may find the About Solid page useful. The Solid project consists of a draft specification and a suite of implementations, tools, and libraries for developers. -

- -

- The mission of the Solid Working Group (LINK TBD) is to standardize the Solid Protocol and its use of associated data interoperability and authentication schemes. This effort will culminate in open standards that can be used by developers of servers and applications to continue to build a rich ecosystem that returns control of data back to users. -

- -
-

- Join the Solid Working Group (LINK TBD). -

-
- -
- - - - - - - - - - - - - - - - - - - - - - -
- Start date - - DD Month YYYY -
- End date - - DD Month YYYY -
- Chairs - - Ruben Verborgh (imec)
- Justin Bingham (Janeiro Digital)
- Aaron Coburn (Inrupt) -
- Team Contact - - Pierre-Antoine Champin (0.1 FTE) -
- Meeting Schedule - - Teleconferences: 1-hour calls will be held bi-weekly -
- Face-to-face: we will meet -during the W3C's annual Technical Plenary week; additional face-to-face -meetings may be scheduled by consent of the participants, usually no -more than 3 per year. -
-
- -
-

Scope

- -

- The design approach for the Solid specification will continue substantial efforts undertaken previously in the Solid community to specify a set of interoperable protocol standards for enabling the use and development of Solid Pods and applications across a wide range of use cases. -

- -

- The Working Group will: -

-
    -
  1. - Define a core protocol specification for the secure and efficient operation of Solid servers and the behavior of clients interacting with those servers. -
    2. -
  2. - Recommend a data and protocol model for interoperability between multiple applications built upon Solid. -
    3. -
  3. - Recommend a set of practices needed for data security for Solid Pods, and for both server and client software, including use of appropriate authentication, authorization, verification, identity, and other standards, integrating existing outside efforts. -
    4. -
  4. - Recommend a set of protocol behaviors and best practices for the use in Solid of the OpenID Connect (OIDC) / Federation identity layer on top of the OAuth 2.0 protocol. -
    5. -
  5. - Recommend a set of protocol behaviors and best practices to request and grant access to data stored in Solid Pods. -
    6. -
  6. - Define a protocol for state synchronization regarding changes to resources in Solid pods. -
    7. -
- -
-

Out of Scope

-

- The following features and topics are out of scope and will not be addressed by this Working Group. -

- -
    -
  • - Definition of identity mechanisms such as WebID and DID -
    • -
  • - Definition of linked data formats -
    • -
-
- -
-

Success Criteria

-

- In order to advance to the status of - Proposed Recommendation, each specification will fulfill the - implementation experience required by the W3C Process as follows: -

- -
    -
  • - The Working Group will seek evidence of independent interoperable uses of the Solid protocol from at least two independent implementations of each feature defined in the specification. -
    • -
  • - The group will add a section detailing any known security or privacy implications for implementers, Web authors, and end users. -
    • -
  • - The group will maintain and advance a test suite (LINK TBD), which, among other goals, will enable interoperability testing. -
    • -
-
-
- -
-

- Deliverables -

-

- More detailed milestones and updated publication schedules are available on the - group publication status page (LINK TBD). -

- -
-

- Normative Specifications -

-

- The Solid Working Group will deliver the following W3C normative specifications: -

-
-
Solid Protocol v1.0
-
-

- The Solid Protocol specification aims to provide applications with secure and permissioned access to externally stored data in an interoperable way. An overarching design goal of the Solid ecosystem is to be evolvable and to provide fundamental affordances for decentralised Web applications for information exchange in a way that is secure and privacy respecting. In this environment, actors allocate identifiers for their content, shape and store data where they have access to, set access control policies, and use preferred applications and services to achieve them. -

-

- When possible, the Solid Protocol will evolve while maintaining a high degree of compatibility with existing implementations, of both servers and clients, and with features from prior versions. If incompatible changes have to be made, then they will be done by introducing a stage where both old and new protocols are supported, to allow the implementors to upgrade their systems in a managed way. -

-

- The Solid specification may include protocol details for integration with the following: -

    -
  1. - OpenID Connect -
    2. -
  2. - Access grants using W3C Verifiable Credentials -
    3. -
  3. - Identity mechanisms such as WebID and DID -
    4. -
  4. - Notifications about resource changes -
    5. -
  5. - Authorization mechanisms such as Web Access Control and Access Control Policy -
    6. -

    -
-
- -

- Note that the WG may decide, based on editorial and readability considerations, to spin off sections into separate Recommendations track specifications. -

-

- All specifications, regardless of their progress along the W3C process line from Working Draft to Recommendation, will be given a version number, such as 0.9, which will be incremented like from 0.9 to 0.10 for minor changes. A major version increment like 2.2 to 3.0 will be used if there is an incompatible change in the protocol. The required versions of each dependency will be given in each spec. -

-
- -
-

- Other Deliverables -

-

- Other non-normative documents may be created such as: -

-
-
Test Suite and Implementation Report
-
-

- The Working Group will develop a test suite and implementation report to test and document conformance levels achieved by implementors. -

-
-
-
- -
-

Timeline (TBD)

- - - - - - - - - - - - - - - - - - - - -
- Note: The group will document significant changes from this initial schedule on the group home page. -
Specification - FPWD - - CR - - PR - - Rec -
- Solid Protocol - - Month YYYY -
- -
-
- - -
-

Coordination

-

- For all specifications, this Working Group will seek horizontal review - for accessibility, internationalization, performance, privacy, and -security with the relevant Working and Interest Groups, and with the TAG. Invitation for review must be issued during each major standards-track document transition, including the FPWD and at least 3 months before the CR, and should be issued when major changes occur in a specification. -

- -

- Additional technical coordination with the following Groups will be made, per the W3C Process Document: -

- -
-

W3C Groups

- -
-
- Verifiable Credentials Working Group -
-
- Coordination on mechanisms for granting access to resources. -
-
- DID Working Group -
-
- Coordination on mechanisms for decentralized identifier use in Solid. -
-
- Credentials Community Group -
-
- Coordination on other specifications related to Decentralized Identifiers. -
-
- JSON-LD Working Group -
-
- Coordination to ensure that the JSON-LD syntax meets the Solid Working Group's needs. -
-
- Web Authentication Working Group -
-
- Coordination to ensure that Web Authentication primitives align with Solid principles and aims. -
-
- -
- - -
- -
-

- Participation -

-

- To be successful, this Working Group is expected to have - 6 or more active participants for its duration, including -representatives from the key implementors of this specification, and -active Editors and Test Leads for each specification. The Chairs, -specification Editors, and Test Leads are expected to contribute half of - a working day per week towards the Working Group. There is no minimum -requirement for other Participants. -

-

- The group encourages questions, comments and issues on -its public mailing lists and document repositories, as described in Communication. -

-

- W3C Members are invited to join this Working Group. Individuals who wish to participate as Invited Experts (i.e., they do not represent a W3C Member) should refer to the policy for approval of Invited Experts. - The group also welcomes non-Members to contribute technical submissions - for consideration upon their agreement to the terms of the W3C Patent Policy. -

-
- -
-

- Communication -

-

- Technical discussions for this Working Group are conducted in public: - the meeting minutes from teleconference and face-to-face meetings will -be archived for public review, and technical discussions and issue -tracking will be conducted in a manner that can be both read and written - to by the general public. Working Drafts and Editor's Drafts of -specifications will be developed on a public repository, and may permit -direct public contribution requests. The meetings themselves are not -open to public participation, however. -

-

- Information about the group (including details about -deliverables, issues, actions, status, participants, and meetings) will -be available from the Solid Working Group home page (LINK TBD). -

-

- Most Working Group -teleconferences will focus on discussion of particular specifications, -and will be conducted on an as-needed basis. -

-

- This group primarily conducts its technical work on the public mailing list public-solid-wg@w3.org (LINK TBD) ( archive (LINK TBD)) or on GitHub issues (LINK TBD) - (and specification-specific GitHub repositories and issue trackers). -The public is invited to review, discuss and contribute to this work. -

-

- The group will publish minutes for each teleconference at https://github.com/w3c/solid-wg/Meeting/Minutes/ (LINK TBD). -

-
- -
-

- Decision Policy -

-

- This group will seek to make decisions through consensus and due process, per the W3C Process Document (section 3.3). - Typically, an editor or other participant makes an initial proposal, -which is then refined in discussion with members of the group and other -reviewers, and consensus emerges with little formal voting being -required. -

-

- However, if a decision is necessary for timely progress, - but consensus is not achieved after careful consideration of the range -of views presented, the Chairs may call for a group vote, and record a -decision along with any objections. -

-

- To afford asynchronous decisions and organizational -deliberation, any resolution (including publication decisions) taken in a - face-to-face meeting or teleconference will be considered provisional. -

-

- A call for consensus (CfC) will be issued for all -resolutions (for example, via email and/or web-based survey), with a -response period from one week to 10 working days, depending on the -chair's evaluation of the group consensus on the issue. -

-

- If no objections are raised on the mailing list by the -end of the response period, the resolution will be considered to have -consensus as a resolution of the Working Group. -

-

- All decisions made by the group should be considered -resolved unless and until new information becomes available, or unless -reopened at the discretion of the Chairs or the Director. -

-

- This charter is written in accordance with the W3C Process Document (Section 3.4, Votes), and includes no voting procedures beyond what the Process Document requires. -

-
- -
-

- Patent Policy -

-

- This Working Group operates under the W3C Patent - Policy (Version of 15 September 2020). To -promote the widest adoption of Web standards, W3C seeks to issue -Recommendations that can be implemented, according to this policy, on a -Royalty-Free basis. -

-

- For more information about disclosure obligations for this group, please see the W3C Patent Policy Implementation. -

-
- -
-

Licensing

-

- This Working Group will use the W3C Software and Document license for all its deliverables. -

-
- -
-

- About this Charter -

-

- This charter has been created according to section 5.2 of the Process Document. - In the event of a conflict between this document or the provisions of -any charter and the W3C Process, the W3C Process shall take precedence. -

- -
-

-Charter History -

- -

The following table lists details of all changes from the initial charter, per the W3C Process Document (section 5.2.3):

- - - - - - - - - - - - - - - - -
Charter Period Start Date End Date Changes
Initial Charter Month YYYY Month YYYY none
-
-
-
- -
- - - diff --git a/draft-working-group-charter/pubrules-style.css b/draft-working-group-charter/pubrules-style.css deleted file mode 100644 index c71ee6d..0000000 --- a/draft-working-group-charter/pubrules-style.css +++ /dev/null @@ -1,138 +0,0 @@ -@import url("http://www.w3.org/StyleSheets/base.css"); - -/* Copyright 1997-2005 W3C (MIT, ERCIM, Keio). All Rights Reserved. - The following software licensing rules apply: - http://www.w3.org/Consortium/Legal/copyright-software */ - -/* $Id: pubrules-style.css,v 1.1 2018/01/25 15:52:23 plehegar Exp $ */ - -body { - margin: 2em 1em 2em 70px; - font-family: sans-serif; - color: black; - background-color: white; - background-position: top left; - background-attachment: fixed; - background-repeat: no-repeat; -} - -h1, h2, h3, h4, h5 { - text-align: left; - font-family: sans-serif; - font-weight: normal; - color: #005a9c; - margin-left: 0 -} - -h4, h5, blockquote { margin-left: 1em } - -div.head p { margin-left: 0 } - -.first { margin: 3em 4em 2em 3em} - -div.head img { - color: white; - border: none; - float:left; - padding-right: 1em; - padding-bottom: 1em; - margin-left: 0 -} - -p { clear: left } - -/*p, ul, ol, blockquote, dl { margin-left: 2em }*/ - -th { text-align: left } - -.rfc2119 { - text-transform: lowercase; - font-weight: bold -} - -/* Navigation styles from Eric Meyer */ -/* -http://www.complexspiral.com/events/archive/2003/seybold/cssnav.html -*/ - -/* Shared */ -li.label { - list-style: none; - margin: 0; - padding: .15em 0 .15em .5em; - border-top: 1px solid gray; - text-align: left; - color: white; - background: #0050B2; - font-weight: bold; - } - -/* highlighting and border effects */ -#navbar {float:right} -#navbar {padding: 0 1px 2em 1em; margin: 0; - font: bold 10px sans-serif; - background: white; width: 13em;} -#navbar li {list-style: none; margin: 0; border-top: 1px solid gray; - text-align: left;} -#navbar li#current {list-style: none; margin: 0; border-top: 1px solid gray; - text-align: left; background: #CCD; color: black; padding: 0.25em 0.5em 0.25em 0.75em; - border-left: 1em solid #AAB; text-decoration: none;} -#navbar li a {display: block; padding: 0.25em 0.5em 0.25em 0.75em; - border-left: 1em solid #AAB; text-decoration: none;} -/*#navbar li a:link {color: #448; }*/ -#navbar li a:visited {color: #667; } -#navbar li a:hover {border-color: #FE3; color: #FFF; background: #332;} - -/* Same for class version */ - -.navbar {float:right} -.navbar {padding: 0 1px 2em 1em; margin: 0; - font: bold 10px sans-serif; - background: white; width: 13em;} -.navbar li {list-style: none; margin: 0; border-top: 1px solid gray; - text-align: left;} -.navbar li#current {list-style: none; margin: 0; border-top: 1px solid gray; - text-align: left; background: #CCD; color: black; padding: 0.25em 0.5em 0.25em 0.75em; - border-left: 1em solid #AAB; text-decoration: none;} -.navbar li a {display: block; padding: 0.25em 0.5em 0.25em 0.75em; - border-left: 1em solid #AAB; text-decoration: none;} -/*.navbar li a:link {color: #448; }*/ -.navbar li a:visited {color: #667; } -.navbar li a:hover {border-color: #FE3; color: #FFF; background: #332;} - -/* tabbed styles */ -#navigation {padding: 3px 0; margin: 0; - border-bottom: 1px solid #778; - font: bold 10px sans-serif;} -#navigation li {list-style: none; margin: 0; - display: inline; line-height: 250%} -#navigation li a {padding: 3px 0.5em; margin-left: 3px; - border: 1px solid #778; border-bottom: none; - background: #DDE; - text-decoration: none;} -#navigation li a:link {color: #448; } -#navigation li a:visited {color: #667; } -#navigation li a:hover {color: #000; background: #AAE; - border-color: #227;} - -/* Same thing for class navigation */ -.navigation {padding: 3px 0; margin: 0; - border-bottom: 1px solid #778; - font: bold 10px sans-serif; } -.navigation li {list-style: none; margin: 0; - display: inline; line-height: 250%} -.navigation li a {padding: 3px 0.5em; margin-left: 3px; - border: 1px solid #778; border-bottom: none; - background: #DDE; - text-decoration: none;} -.navigation li a:link {color: #448; } -.navigation li a:visited {color: #667; } -.navigation li a:hover {color: #000; background: #AAE; - border-color: #227;} - - -/* "current tab" style */ -#navigation li a#current {background: white; border-bottom: 1px solid white;} -/* Same thing for class navigation */ -.navigation li a#current {background: white; border-bottom: 1px solid white;} - diff --git a/draft-working-group-charter/w3c_home.svg b/draft-working-group-charter/w3c_home.svg deleted file mode 100644 index 3924d01..0000000 --- a/draft-working-group-charter/w3c_home.svg +++ /dev/null @@ -1,9 +0,0 @@ - - - - - - - - - diff --git a/draft-working-group-charter/w3cdoc.css b/draft-working-group-charter/w3cdoc.css deleted file mode 100644 index 9f1a120..0000000 --- a/draft-working-group-charter/w3cdoc.css +++ /dev/null @@ -1,270 +0,0 @@ -a:link img, a:visited img { - border-style: none -} - -html{ - background-color: #fff; - color: #000; - margin:0; - border:0;} - -body -{ - background-color: #fff; - padding: 0em 2em; - font-family: "Gill Sans"; -} - -h4, h5, h6 {border: none;} -body.team -{ -margin:0; -border-right: 30px solid #FFEEC2; -border-left: 30px solid #FFEEC2;} - -body.team:before {content:"Team confidential"; - font-size: 2em; - color: #F00; - padding: 5px; - font-weight: bold;} - -body.ab -{ -margin:0; -border-right: 30px solid #E2EDFE; ; -border-left: 30px solid #E2EDFE;;} - -body.ab:before {content:"AB+Team confidential"; - font-size: 2em; - color: #F00; - padding: 5px; - font-weight: bold;} - -#content { background-color: #fff;} -/*quotes*/ -blockquote -{ - background: #c8e3ea; - padding: 0.5em; - border-left: #999; - border-width: 0 0 0 1px; - border-style: none none none solid; - font-family: "Gill Sans"; - font-style: italic; -} -q -{ - background: #c8e3ea; - font-family: "Gill Sans"; - font-style: italic; -} -blockquote:after { - display: block; - content: attr(cite); - text-align: right; - font-size: 0.7em; -} - -blockquote cite.title, -blockquote cite.author { - font-style: italic; - font-size: 0.8em -} -blockquote cite.title:before { - content: "-- "; -} - -/*PRE style*/ -pre -{ - padding: 0.5em; - border-color: #c8e3ea; - border-width: 1px 1px 1px 3px; - border-style: solid; - font-family: "Courier", fixed; -} - -/*From http://www.w3.org/2005/09/table.css*/ -table -{ - border-collapse: collapse; - margin: 1em auto; -} - -table caption -{ - margin-left: auto; - margin-right: auto; -} - -table, tr, th, td { border: 1px solid black; } -th, td { padding: 5px 1em; } - -th -{ - background: #005a9c; - color: #fff; -} - -th a:link { - color: #fff; -} - -th a:visited { - color: #aaa; -} - -#Icons { float: right; } - -#footer -{ - border-color: #333; - border-width: 1px 0 0 0; - border-style: solid none none none; - clear: both; - font-size: 0.9em; -} - -/* Stolen from /Stylesheets/activities.css */ -ul#Navigate { font-size: 0.86em; } -#Icons img { vertical-align: top; } -.trail { vertical-align: bottom; } - -.boldblack -{ - font-weight: bold !important; - background: transparent; - color: #000 !important; -} - -/* right column */ -#Contents -{ - float: left; - width: 70%; - margin: 0 1% 1em 4%; -} - -h1, h2, h3, h4, h5, h6 -{ - margin-bottom: 0; - padding-bottom: 0.15em; - border-bottom: 1px solid #ccc; - background: transparent; - color: #005a9c; - font-weight: normal; -} - -h1 -{ - margin-top: 1em; - margin-bottom: 0; - padding-bottom: 0.15em; - border-bottom: none; - background: transparent; - color: #000; -} - -p.firstelement, table, address { margin-top: 0.7em; } - -/* left column */ -ul#Navigate, ul.nav -{ - margin: 0; - padding: 0.2em 0 0 0; -} - -ul#Navigate -{ - float: left; - width: 13em; - margin: 1em 0 0 0.2em; - border-right: 1px solid gray; - background: #c8e3ea; - color: #000; - text-indent: 2px; -} - -ul#Navigate li, ul.nav li -{ - padding: 0.2em 0 0.2em 0.3em; - list-style: none; - font-weight: normal; -} - -ul.nav li { border-top: 1px solid gray; } - -ul#Navigate a, ul.nav li a -{ - padding-right: 0.1em; - background: transparent; - color: #000; - text-decoration: none; -} - -ul#Navigate li.navcurrent, ul.nav li.navcurrent -{ - list-style: disc; - background: #fff; - color: #000; -} - -ul#Navigate li a:hover, .nav li a:hover, -ul#Navigate li a:focus, .nav li a:focus -{ - background: transparent; - color: #00e; - text-decoration: underline; -} - -/* print */ - -@media print -{ - body, html { font-family: sans-serif; } - - h1, h2, h3, h4, h5, h6 - { - page-break-after: avoid; - page-break-inside: avoid; - } - - blockquote, pre, table { page-break-inside: avoid; } - ul, ol, dl { page-break-before: avoid; } - .whiteout, .trail, ul#Navigate, p#Validate { display: none; } - - div#Contents - { - float: none; - width: 100%; - } -} - -.whiteout, .whiteout a:link, .whiteout a:visited -{ - background: #fff; - color: #fff; -} - -.whiteout a:hover, .whiteout a:focus -{ - background: #fff; - color: #00e; -} - -.whiteout a:active -{ - background: #fff; - color: #f00; -} - -div.whiteout -{ - margin: -10px 0 0 0; - padding: 0; -} - -/*#status { - padding: .5em 2em; - background-color: #FCC; - margin: 0 auto;}*/ \ No newline at end of file