Skip to content

Commit

Permalink
rename WG to 'Linked Web Storage'
Browse files Browse the repository at this point in the history 
following the result of the poll at #75
  • Loading branch information
@pchampin
pchampin committed Apr 29, 2024
1 parent 8f22f67 commit c575b82
Showing 1 changed file with 22 additions and 22 deletions.
44 changes: 22 additions & 22 deletions charter/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
<head>
<meta charset="utf-8"/>

<title>PROPOSED PUMPKIN Working Group Charter</title>
<title>PROPOSED Linked Web Storage Working Group Charter</title>

<link rel="stylesheet" href="https://www.w3.org/2005/10/w3cdoc.css" type="text/css" media="screen"/>
<link rel="stylesheet" type="text/css" href="https://www.w3.org/OldGuide/pubrules-style.css"/>
Expand Down Expand Up @@ -86,7 +86,7 @@


<main>
<h1 id="title">PROPOSED PUMPKIN Working Group Charter</h1>
<h1 id="title">PROPOSED Linked Web Storage Working Group Charter</h1>
<!-- delete PROPOSED after AC review completed -->

<div style="border: 1px solid darkred">
Expand All @@ -96,12 +96,12 @@ <h1 id="title">PROPOSED PUMPKIN Working Group Charter</h1>
<p>Any text rendered like <span class="todo">this</span> refers to content that must be updated when the final charter is published at the latest (e.g., adjusting hyperlinks).</p>
</div>

<p class="mission new">The <strong>mission</strong> of the <a href="">PUMPKIN Working Group <i class="todo">(LINK TBD)</i></a> is to
<p class="mission new">The <strong>mission</strong> of the <a href="">Linked Web Storage Working Group <i class="todo">(LINK TBD)</i></a> is to
enable the development of web applications where data storage, entity authentication, access control, and application provider are all loosely coupled, as opposed to the web of today where these are typically all tightly coupled and changing one requires changing all, sometimes at the price of all past data.
This will be achieved by standardizing a protocol between applications, on the one hand, and identity and storage servers, on the other hand.</p>

<div class="noprint">
<p class="join"><a href="">Join the PUMPKIN Working Group <i class="todo">(LINK TBD)</i>.</a></p>
<p class="join"><a href="">Join the Linked Web Storage Working Group <i class="todo">(LINK TBD)</i>.</a></p>
</div>

<p style="padding: 0.5ex; border: 1px solid green"> This proposed charter is available
Expand Down Expand Up @@ -206,7 +206,7 @@ <h2>Scope</h2>
Define a core web protocol specification for the secure and efficient operation of compliant servers and the behavior of compliant applications interacting with those servers.
</li>
<li>
Recommend a set of practices needed for data security for PUMPKIN storage, and for both server and client software, including use of appropriate authentication, authorization, access management life-cycle, verification, identity, and other standards, integrating existing outside efforts.
Recommend a set of practices needed for data security for Linked Web Storage storage, and for both server and client software, including use of appropriate authentication, authorization, access management life-cycle, verification, identity, and other standards, integrating existing outside efforts.
</li>
</ol>

Expand Down Expand Up @@ -244,13 +244,13 @@ <h3>
The Working Group will deliver the following W3C normative specifications:
</p>
<dl>
<dt id="PUMPKIN-protocol" class="spec">PUMPKIN Protocol v1.0</dt>
<dt id="lws-protocol" class="spec">Linked Web Storage Protocol v1.0</dt>
<dd>
<p>
The PUMPKIN Protocol specification aims to provide applications with secure and permissioned access to externally stored data in an interoperable way.
The Linked Web Storage Protocol specification aims to provide applications with secure and permissioned access to externally stored data in an interoperable way.
</p>
<p>
The PUMPKIN Protocol may include protocol details for integration with identity layers and mechanisms; access management and data integrity; notifications about resource changes; and authorization mechanisms.
The Linked Web Storage Protocol may include protocol details for integration with identity layers and mechanisms; access management and data integrity; notifications about resource changes; and authorization mechanisms.
</p>
<p>
<b>Input documents</b>:
Expand All @@ -275,7 +275,7 @@ <h3>
<section id="dependencies">
<h3>Dependencies</h3>

<p>The draft of the PUMPKIN Protocol proposed for adoption has a number of normative dependencies with maturity levels insufficient for a recommendation (e.g., Community Group reports, Editor's Drafts). To allow the PUMPKIN Protocol v1.0 to progress on the Recommendation track, the Working Group will need to decide how to deal with these dependencies. This may include downgrading some of these dependencies to non-normative references; specifying the required parts in the PUMPKIN Protocol itself; and/or relying on other specifications to fulfill the same purpose.</p>
<p>The draft of the Linked Web Storage Protocol proposed for adoption has a number of normative dependencies with maturity levels insufficient for a recommendation (e.g., Community Group reports, Editor's Drafts). To allow the Linked Web Storage Protocol v1.0 to progress on the Recommendation track, the Working Group will need to decide how to deal with these dependencies. This may include downgrading some of these dependencies to non-normative references; specifying the required parts in the Linked Web Storage Protocol itself; and/or relying on other specifications to fulfill the same purpose.</p>

<p>Depending on the Working Group progress, including consideration for <a href="https://www.w3.org/Consortium/Process/#adequate-implementation">
adequate implementation experience</a>, the Group may also decide to adopt the following dependencies as input documents:</p>
Expand Down Expand Up @@ -355,7 +355,7 @@ <h3>Timeline</h3>
</tr>
<tr>
<th rowspan="1" colspan="1">
PUMPKIN Protocol
Linked Web Storage Protocol
</th>
<td class="WD1" rowspan="1" colspan="1">
<i class="todo">START + 6M</i>
Expand Down Expand Up @@ -419,10 +419,10 @@ <h2>Coordination</h2>
<h3 id="w3c-coordination">W3C Groups</h3>
<dl>
<dt><a href="https://www.w3.org/groups/cg/credentials">Credentials Community Group</a></dt>
<dd>To explore and report on the application of creating, storing, presenting, verifying, and user control of credentials in the context of PUMPKIN Protocol.</dd>
<dd>To explore and report on the application of creating, storing, presenting, verifying, and user control of credentials in the context of Linked Web Storage Protocol.</dd>

<dt><a href="https://www.w3.org/groups/wg/did">Decentralized Identifier Working Group</a></dt>
<dd>To investigate whether existing DID methods should be adopted by the PUMPKIN Protocol (and related technical reports), and to advance an understanding of whether a specific DID method is needed.</dd>
<dd>To investigate whether existing DID methods should be adopted by the Linked Web Storage Protocol (and related technical reports), and to advance an understanding of whether a specific DID method is needed.</dd>

<dt><a href="https://www.w3.org/groups/cg/ldpnext">LDP Next Community Group</a></dt>
<dd>To transfer applicable design decisions and implementation experience towards the PUMKIN Protocol, and report back on components that can be adopted.</dd>
Expand All @@ -431,7 +431,7 @@ <h3 id="w3c-coordination">W3C Groups</h3>
<dd>To investigate the possibility of transferring PUMKIN Protocol's N3 Patch to the N3 Community Group where its standardization development can continue with broader applicability.</dd>

<dt><a href="https://www.w3.org/groups/wg/rdf-star">RDF-star Working Group</a></dt>
<dd>To reuse and report on recent extensions to RDF and SPARQL that can be incorporated with upstream specifications like the PUMPKIN Protocol.</dd>
<dd>To reuse and report on recent extensions to RDF and SPARQL that can be incorporated with upstream specifications like the Linked Web Storage Protocol.</dd>

<dt><a href="https://www.w3.org/groups/cg/socialcg">Social Web Incubator Community Group</a></dt>
<dd>To continue with the development of a shared understanding between Linked Data(-compatible) specifications and their reuse, e.g., ActivityPub, AS2, LDN.</dd>
Expand All @@ -440,30 +440,30 @@ <h3 id="w3c-coordination">W3C Groups</h3>
<dd>To maintain a separation of goals and transfer of incubated work items.</dd>

<dt><a href="https://www.w3.org/groups/cg/unhosted">Unhosted Web Community Group</a></dt>
<dd>To explore the overlaps (e.g., CORS, user-centric storage, JSON-LD container descriptions) and differences (e.g., OAuth instead of WAC/ACP) between the PUMPKIN Protocol draft and their work on <a href="https://datatracker.ietf.org/doc/draft-dejong-remotestorage/">remoteStorage</a>.</dd>
<dd>To explore the overlaps (e.g., CORS, user-centric storage, JSON-LD container descriptions) and differences (e.g., OAuth instead of WAC/ACP) between the Linked Web Storage Protocol draft and their work on <a href="https://datatracker.ietf.org/doc/draft-dejong-remotestorage/">remoteStorage</a>.</dd>

<dt><a href="https://www.w3.org/groups/wg/vc">Verifiable Credentials Working Group</a></dt>
<dd>To inquire on the suitability of credential data models and serializations, and their potential integration with the PUMPKIN Protocol.</dd>
<dd>To inquire on the suitability of credential data models and serializations, and their potential integration with the Linked Web Storage Protocol.</dd>

<dt><a href="https://www.w3.org/groups/cg/webid">WebID Community Group</a></dt>
<dd>To provide integration feedback on the use of WebIDs in PUMPKIN Protocol (and related technical reports) in order to stabilize the fundamental notions and behaviors.</dd>
<dd>To provide integration feedback on the use of WebIDs in Linked Web Storage Protocol (and related technical reports) in order to stabilize the fundamental notions and behaviors.</dd>

<dt><a href="https://www.w3.org/groups/wg/webauthn">Web Authentication Working Group</a></dt>
<dd>To ensure that Web Authentication primitives align with PUMPKIN principles and aims, as well as investigate areas to bridge with the WebAuthn API to improve user's privacy and consent.</dd>
<dd>To ensure that Web Authentication primitives align with Linked Web Storage principles and aims, as well as investigate areas to bridge with the WebAuthn API to improve user's privacy and consent.</dd>

<dt><a href="https://www.w3.org/groups/cg/wicg">Web Platform Incubator Community Group</a></dt>
<dd>To further develop a mutual understanding of how the federated credential management API and PUMPKIN can align better.</dd>
<dd>To further develop a mutual understanding of how the federated credential management API and Linked Web Storage can align better.</dd>

<dt><a href="https://www.w3.org/groups/wg/wot">Web of Things Working Group</a></dt>
<dd>To investigate the suitability of PUMPKIN Protocol in the context of IoT platforms and application domains, and ways to improve their integration.</dd>
<dd>To investigate the suitability of Linked Web Storage Protocol in the context of IoT platforms and application domains, and ways to improve their integration.</dd>
</dl>
</section>

<section>
<h3 id="external-coordination">External Organizations</h3>
<dl>
<dt><a href="https://httpwg.org/">IETF HTTP Working Group</a></dt>
<dd>To ensure that the PUMPKIN Protocol is following best practices, in particular <a href="https://httpwg.org/specs/rfc9205.html">BCP 56: Building Protocols with HTTP</a>.</dd>
<dd>To ensure that the Linked Web Storage Protocol is following best practices, in particular <a href="https://httpwg.org/specs/rfc9205.html">BCP 56: Building Protocols with HTTP</a>.</dd>
<dt><a href="https://openid.net/wg/connect/">OpenID Connect Work Group</a></dt>
<dd>Coordination on specifications related to OpenID Connect (OIDC).</dd>
</dl>
Expand Down Expand Up @@ -500,10 +500,10 @@ <h2>
The meetings themselves are not open to public participation, however.
</p>
<p>
Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <a class="todo" href="">PUMPKIN Working Group home page (LINK TBD).</a>
Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <a class="todo" href="">Linked Web Storage Working Group home page (LINK TBD).</a>
</p>
<p>
Most PUMPKIN Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.
Most Linked Web Storage Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.
</p>
<p>
This group primarily conducts its technical work: on the public mailing list <a class="todo" id="public-name" href="mailto:public-solid-wg@w3.org">public-solid-wg@w3.org (LINK TBD)</a> (<a class="todo" href="https://lists.w3.org/Archives/Public/public-solid-wg/">archive (LINK TBD)</a>)
Expand Down

0 comments on commit c575b82

Please sign in to comment.