├── .github
    └── ISSUE_TEMPLATE
    │   ├── blank.md
    │   ├── opposition.md
    │   └── support.md
├── .pr-preview.json
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── LICENSE.md
├── README.md
├── index.html
└── w3c.json


/.github/ISSUE_TEMPLATE/blank.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Standard issue
3 | about: Template for standard issue
4 | title: ''
5 | labels: ''
6 | assignees: ''
7 | 
8 | ---
9 | 


--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/opposition.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | name: Expression of opposition
 3 | about: Template for expression of opposition
 4 | title: '~organization~ is against the creation of the RDF-star working group'
 5 | labels: expression_of_opposition
 6 | assignees: ''
 7 | 
 8 | ---
 9 | 
10 | ~organization~ is against the creation of the RDF-star working group as described in the proposed charter.
11 | 
12 | <!--
13 | replace ~organization~ in the title and the first sentence with the name of your organization
14 | 
15 | add a few sentences describing why you think the working group should not be created
16 | 
17 | feel free to adapt this template if needed
18 | -->
19 | 


--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/support.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | name: Expression of support
 3 | about: Template for expression of support
 4 | title: '~organization~ supports the creation of the RDF-star working group'
 5 | labels: expression_of_support
 6 | assignees: ''
 7 | 
 8 | ---
 9 | 
10 | ~organization~ supports the creation of the RDF-star working group as described in the proposed charter.
11 | 
12 | <!--
13 | replace ~organization~ in the title and the first sentence with the name of your organization
14 | 
15 | add a few sentences describing why you are interested in seeing RDF-star standardized
16 | 
17 | feel free to adapt this template if needed
18 | -->
19 | 


--------------------------------------------------------------------------------
/.pr-preview.json:
--------------------------------------------------------------------------------
1 | {
2 |     "src_file": "index.html",
3 |     "type": "html"
4 | }
5 | 


--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Code of Conduct
2 | 
3 | All documentation, code and communication under this repository are covered by the [W3C Code of Ethics and Professional Conduct](https://www.w3.org/Consortium/cepc/).
4 | 


--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
 1 | # Charter development
 2 | 
 3 | Contributions to this repository are intended to become part of Recommendation-track documents governed by the
 4 | [W3C Patent Policy](https://www.w3.org/Consortium/Patent-Policy-20040205/) and
 5 | [Software and Document License](https://www.w3.org/Consortium/Legal/copyright-software). To make substantive contributions to specifications, you must either participate
 6 | in the relevant W3C Working Group or make a non-member patent licensing commitment.
 7 | 
 8 | If you are not the sole contributor to a contribution (pull request), please identify all 
 9 | contributors in the pull request comment.
10 | 
11 | To add a contributor (other than yourself, that's automatic), mark them one per line as follows:
12 | 
13 | ```
14 | +@github_username
15 | ```
16 | 
17 | If you added a contributor by mistake, you can remove them in a comment with:
18 | 
19 | ```
20 | -@github_username
21 | ```
22 | 
23 | If you are making a pull request on behalf of someone else but you had no part in designing the 
24 | feature, you can remove yourself with the above syntax.
25 | 


--------------------------------------------------------------------------------
/LICENSE.md:
--------------------------------------------------------------------------------
1 | All documents in this Repository are licensed by contributors
2 | under the 
3 | [W3C Software and Document License](https://www.w3.org/Consortium/Legal/copyright-software).
4 | 
5 | 


--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
 1 | # Charter for the RDF-star Working Group
 2 | 
 3 | This repository has two "main" branches:
 4 | 
 5 | - `active` should reflect the currently [active](https://www.w3.org/groups/wg/rdf-star/charters/active/) charter of the WG
 6 | - `upcoming` is the current state of the next proposed charter
 7 | 
 8 | In general, `active` should be equal or behind `upcoming`,
 9 | but it may happen that `active` diverges when the active charter is extended while a new one is being developped.
10 | 
11 | Preview of the charter:
12 | - [upcoming](https://raw.githack.com/w3c/rdf-star-wg-charter/refs/heads/upcoming/index.html)
13 | - [active](https://raw.githack.com/w3c/rdf-star-wg-charter/refs/heads/active/index.html)
14 | 


--------------------------------------------------------------------------------
/index.html:
--------------------------------------------------------------------------------
  1 | <!DOCTYPE html>
  2 | <html lang="en-US">
  3 |   <head>
  4 |     <meta charset="utf-8">
  5 | 
  6 |     <title>RDF &amp; SPARQL Working Group Charter</title>
  7 | 
  8 |     <link rel="stylesheet" href="https://www.w3.org/2005/10/w3cdoc.css" type="text/css" media="screen">
  9 |     <link rel="stylesheet" type="text/css" href="https://www.w3.org/OldGuide/pubrules-style.css">
 10 |     <link rel="stylesheet" type="text/css" href="https://www.w3.org/2006/02/charter-style.css">
 11 |     <style>
 12 |       main {
 13 |         max-width: 60em;
 14 |         margin: 0 auto;
 15 |       }
 16 | 
 17 |       ul#navbar {
 18 |         font-size: small;
 19 |       }
 20 | 
 21 |       dt.spec {
 22 |         font-weight: bold;
 23 |       }
 24 | 
 25 |       dt.spec new {
 26 |         background: yellow;
 27 |       }
 28 | 
 29 |       ul.out-of-scope > li {
 30 |         font-weight: bold;
 31 |       }
 32 | 
 33 |       ul.out-of-scope > li > ul > li{
 34 |         font-weight: normal;
 35 |       }
 36 | 
 37 |       .issue {
 38 |         background: plum;
 39 |         font-style: italic;
 40 |       }
 41 | 
 42 |       .todo {
 43 |         color: #900;
 44 |       }
 45 | 
 46 |       footer {
 47 |         font-size: small;
 48 |       }
 49 | 
 50 |       .note {
 51 |         background: #e9fbe9;
 52 |         color: black;
 53 |         color: var(--note-text);
 54 |         border: none;
 55 |         border-left: thick solid #52e052;
 56 |         padding: 1em;
 57 |       }
 58 | 
 59 |       dd > ul:last-child {
 60 |         margin-bottom: 1em;
 61 |       }
 62 | 
 63 |     </style>
 64 |   </head>
 65 |   <body>
 66 |     <header id="header">
 67 |       <aside>
 68 |         <ul id="navbar">
 69 |           <li><a href="#scope">Scope</a></li>
 70 |           <li><a href="#deliverables">Deliverables</a></li>
 71 | 		      <li><a href="#success-criteria">Success Criteria</a></li>
 72 |           <li><a href="#coordination">Coordination</a></li>
 73 |           <li><a href="#participation">Participation</a></li>
 74 |           <li><a href="#communication">Communication</a></li>
 75 |           <li><a href="#decisions">Decision Policy</a></li>
 76 |           <li><a href="#patentpolicy">Patent Policy</a></li>
 77 |           <li><a href="#licensing">Licensing</a></li>
 78 |           <li><a href="#about">About this Charter</a></li>
 79 |         </ul>
 80 |       </aside>
 81 |       <p>
 82 |         <a href="https://www.w3.org/"><img alt="W3C" height="48" src="https://www.w3.org/Icons/w3c_home" width="72"></a>
 83 |       </p>
 84 |     </header>
 85 | 
 86 | 
 87 |     <main>
 88 |       <h1 id="title">RDF &amp; SPARQL Working Group Charter</h1>
 89 | 
 90 |       <p class="mission">The <strong>mission</strong> of the <a href="https://www.w3.org/groups/wg/rdf-star">RDF &amp; SPARQL Working Group</a> is to update and maintain the set of RDF and SPARQL related recommendations, extending them with the ability to concisely represent and query statements about statements.</p>
 91 | 
 92 |       <div class="noprint">
 93 |         <p class="join"><a href="https://www.w3.org/groups/wg/rdf-star/join">Join the RDF &amp; SPARQL Working Group.</a></p>
 94 |       </div>
 95 | 
 96 |       <!--
 97 |          <p style="padding: 0.5ex; border: 1px solid green"> This proposed charter is available
 98 |       on <a href="https://github.com/w3c/rdf-star-wg-charter">GitHub</a>.
 99 | 
100 |     Feel free to raise <a href="https://github.com/w3c/rdf-star-wg-charter/issues">issues</a>.
101 |           </p>
102 |       -->
103 | 
104 |       <div id="details">
105 |         <table class="summary-table">
106 |           <tr id="Duration">
107 |             <th>
108 |               Start date
109 |             </th>
110 |             <td>
111 |               1 May 2025
112 |             </td>
113 |           </tr>
114 |           <tr id="CharterEnd">
115 |             <th>
116 |               End date
117 |             </th>
118 |             <td>
119 |               30 April 2027
120 |             </td>
121 |           </tr>
122 |           <tr>
123 |             <th>
124 |               Chairs
125 |             </th>
126 |             <td>
127 |               <a href="mailto:ktk@netlabs.org">Adrian Gschwend</a> (<a href="https://zazuko.com/">Zazuko</a>), <a href="mailto:ora@amazon.com">Ora Lassila</a> (<a href="https://www.amazon.com">Amazon</a>)
128 |             </td>
129 |           </tr>
130 |           <tr>
131 |             <th>
132 |               Team Contacts
133 |             </th>
134 |             <td>
135 |               <span><a href="mailto:pierre-antoine@w3.org">Pierre-Antoine Champin</a></span> (0.1 <abbr title="Full-Time Equivalent">FTE</abbr>)
136 |             </td>
137 |           </tr>
138 |           <tr>
139 |             <th>
140 |               Meeting Schedule
141 |             </th>
142 |             <td>
143 |               <strong>Teleconferences:</strong> 1 hour calls to be held weekly; extra topic-specific calls may also be held
144 |               <br>
145 |               <strong>Face-to-face:</strong> face-to-face meetings may be scheduled by consent of the participants, usually no more than 3 per year.
146 |             </td>
147 |           </tr>
148 |         </table>
149 |       </div>
150 | 
151 |       <div id="background" class="background">
152 |         <p>RDF-star (formerly spelled RDF*) is an extension of RDF that was <a href="https://arxiv.org/abs/1406.3399">initially proposed in 2014</a> by Olaf Hartig and Bryan Thompson, providing a concise way to make statements about statements. It has become quite popular, especially as a means to provide interoperability between RDF and Property Graphs, and has already been implemented to various extents by <a href="https://w3c.github.io/rdf-star/implementations.html">a number of vendors and open-source libraries</a>. A <a href="https://w3c.github.io/rdf-star/">subgroup</a> of the <a href="https://www.w3.org/community/rdf-dev/">RDF-DEV Community Group</a> then formed to gather feedback, <a href="https://w3c.github.io/rdf-star/UCR/rdf-star-ucr.html">use-cases</a>, and explore the possibility of <a href="https://www.w3.org/2021/12/rdf-star.html">integrating RDF-star</a> into the existing RDF standards.</p>
153 |       </div>
154 | 
155 |       <section id="scope" class="scope">
156 |         <h2>Scope</h2>
157 |         <p>The scope of this Working Group is to update the recommendations defining RDF 1.1 and SPARQL 1.1, extending them with the features introduced by RDF-star. More precisely, RDF-star introduces the notion of <em>quoted triple</em> to express statements about statements. The abstract and concrete syntaxes of RDF and SPARQL, as well as their respective semantics, are to be extended to support this new feature.
158 |         The group will then maintain the set of resulting recommendations (RDF 1.2 and SPARQL 1.2).</p>
159 | 
160 |         <p>The community group has identified, in its <a href="https://www.w3.org/2021/12/rdf-star.html">final report</a>, which recommendations should be updated, and a possible path for updating them. The Working Group may however reconsider this and proceed differently from the Community Group's proposal. For every recommendation updated by this Working Group, pending <a href="https://www.w3.org/policies/process/20231103/#errata">errata</a> will also be addressed. The Working Group will also consider <a href="https://www.w3.org/policies/process/#allow-new-features">allowing new features</a> in these recommendations, according to <a href="https://www.w3.org/policies/process/#revised-rec-features">Section 6.3.11.4 of the W3C process</a>, to ease and speed up future evolution.</p>
161 | 
162 |         <p>The group SHOULD ensure that any RDF 1.1 data remains valid in this new version. Furthermore, any RDF or RDFS entailment drawn under RDF 1.1 semantics SHOULD also remain valid in this new version.</p>
163 | 
164 |         <p class="note">This Working Group was formally named "RDF-star" to emphasize the new features that RDF 1.2 is providing compared to RDF 1.1. This caused some confusion with respect to the actual scope of the group, so it was decided to change it to a more general designation.</p>
165 | 
166 |         <section id="section-out-of-scope">
167 |           <h3 id="out-of-scope">Out of Scope</h3>
168 |             <p>The following features are out of scope, and will not be addressed by this Working group.</p>
169 | 
170 |             <ul class="out-of-scope">
171 |               <li>Adding other improvements or extensions to RDF or SPARQL. Given the number of recommendations that this Working Group needs to update, it is important to keep its scope very focused.</li>
172 |             </ul>
173 |         </section>
174 | 
175 |       </section>
176 | 
177 |       <section id="deliverables">
178 |         <h2>
179 |           Deliverables
180 |         </h2>
181 | 
182 |         <p>Updated document status is available on the <a href="https://www.w3.org/groups/wg/rdf-star/publications">group publication status page</a>.</p>
183 | 
184 |         <p><i>Draft state</i> indicates the state of the deliverable at the time of the charter approval.
185 |           <i>Expected completion</i> indicates when the deliverable is projected to become a Recommendation, or otherwise reach a stable state.</p>
186 | 
187 |         <section id="normative">
188 |           <h3>
189 |             Normative Specifications
190 |           </h3>
191 |           <p>
192 |             The Working Group will deliver the following W3C normative specifications, inherited from the
193 |             <a href="https://www.w3.org/groups/wg/rdf">RDF working group</a> and
194 |             <a href="https://www.w3.org/groups/wg/sparql">SPARQL working group</a>.
195 |           </p>
196 |           <section>
197 |             <h4>RDF family of specifications</h4>
198 |             <dl>
199 |             <dt id="rdf11-concepts" class="spec">RDF 1.2 Concepts and Abstract Syntax</dt>
200 |             <dd>
201 |               <p>This specification defines an abstract syntax (a data model) which serves to link all RDF-based languages and specifications. The abstract syntax has two key data structures: RDF graphs are sets of subject-predicate-object triples, where the elements may be IRIs, blank nodes, or datatyped literals. They are used to express descriptions of resources. RDF datasets are used to organize collections of RDF graphs, and comprise a default graph and zero or more named graphs. RDF 1.1 Concepts and Abstract Syntax also introduces key concepts and terminology, and discusses datatyping and the handling of fragment identifiers in IRIs within RDF graphs.</p>
202 | 
203 |               <p class="draft-status"><b>Draft state:</b> Working Draft</p>
204 |               <p class="milestone"><b>Expected completion:</b> Q3 2025</p>
205 |               <ul>
206 |                 <li><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2025/WD-rdf12-concepts-20250327/">https://www.w3.org/TR/2025/WD-rdf12-concepts-20250327/</a>
207 |                 <li><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2023/WD-rdf12-concepts-20230516/">https://www.w3.org/TR/2023/WD-rdf12-concepts-20230516/</a>
208 |                 <li><b>Exclusion Draft Charter:</b> <a href="https://www.w3.org/2022/08/rdf-star-wg-charter/">https://www.w3.org/2022/08/rdf-star-wg-charter/</a>
209 |               </ul>
210 |             </dd>
211 | 
212 |             <dt id="n-quads" class="spec">RDF 1.2 N-Quads</dt>
213 |             <dd>
214 |               <p>This specification defines a line-based, plain text format for encoding an RDF dataset.</p>
215 | 
216 |               <p class="draft-status"><b>Draft state:</b> Working Draft</p>
217 |               <p class="milestone"><b>Expected completion:</b> Q3 2025</p>
218 |               <ul>
219 |                 <li><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2025/WD-rdf12-n-quads-20250220/">https://www.w3.org/TR/2025/WD-rdf12-n-quads-20250220/</a>
220 |                 <li><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2023/WD-rdf12-n-quads-20230516/">https://www.w3.org/TR/2023/WD-rdf12-n-quads-20230516/</a>
221 |                 <li><b>Exclusion Draft Charter:</b> <a href="https://www.w3.org/2022/08/rdf-star-wg-charter/">https://www.w3.org/2022/08/rdf-star-wg-charter/</a>
222 |               </ul>
223 |             </dd>
224 | 
225 |             <dt id="n-triples" class="spec">RDF 1.2 N-Triples</dt>
226 |             <dd>
227 |               <p>This specification defines a line-based, plain text format for encoding an RDF graph.</p>
228 | 
229 |               <p class="draft-status"><b>Draft state:</b> Working Draft</p>
230 |               <p class="milestone"><b>Expected completion:</b> Q3 2025</p>
231 |               <ul>
232 |                 <li><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2024/WD-rdf12-n-triples-20241219/">https://www.w3.org/TR/2024/WD-rdf12-n-triples-20241219/</a>
233 |                 <li><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2023/WD-rdf12-n-triples-20230516/">https://www.w3.org/TR/2023/WD-rdf12-n-triples-20230516/</a>
234 |                 <li><b>Exclusion Draft Charter:</b> <a href="https://www.w3.org/2022/08/rdf-star-wg-charter/">https://www.w3.org/2022/08/rdf-star-wg-charter/</a>
235 |               </ul>
236 |             </dd>
237 | 
238 |             <dt id="rdf11-mt" class="spec">RDF 1.2 Semantics</dt>
239 |             <dd>
240 |               <p>This specification defines a precise semantics for the Resource Description Framework and RDF Schema. It defines a number of distinct entailment regimes and corresponding patterns of entailment.</p>
241 |               <p class="draft-status"><b>Draft state:</b> Working Draft</p>
242 |               <p class="milestone"><b>Expected completion:</b> Q3 2025</p>
243 |               <ul>
244 |                 <li><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2025/WD-rdf12-semantics-20250403/">https://www.w3.org/TR/2025/WD-rdf12-semantics-20250403/</a>
245 |                 <li><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2023/WD-rdf12-semantics-20230606/">https://www.w3.org/TR/2023/WD-rdf12-semantics-20230606/</a>
246 |                 <li><b>Exclusion Draft Charter:</b> <a href="https://www.w3.org/2022/08/rdf-star-wg-charter/">https://www.w3.org/2022/08/rdf-star-wg-charter/</a>
247 |               </ul>
248 |             </dd>
249 | 
250 |             <dt id="trig" class="spec">RDF 1.2 TriG</dt>
251 |             <dd>
252 |               <p>This specification defines a textual syntax for RDF called TriG that allows an RDF dataset to be completely written in a compact and natural text form, with abbreviations for common usage patterns and datatypes. TriG is an extension of the Turtle format.</p>
253 | 
254 |               <p class="draft-status"><b>Draft state:</b> Working Draft</p>
255 |               <p class="milestone"><b>Expected completion:</b> Q3 2025</p>
256 |               <ul>
257 |                 <li><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2024/WD-rdf12-trig-20241219/">https://www.w3.org/TR/2024/WD-rdf12-trig-20241219/</a>
258 |                 <li><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2023/WD-rdf12-trig-20230516/">https://www.w3.org/TR/2023/WD-rdf12-trig-20230516/</a>
259 |                 <li><b>Exclusion Draft Charter:</b> <a href="https://www.w3.org/2022/08/rdf-star-wg-charter/">https://www.w3.org/2022/08/rdf-star-wg-charter/</a>
260 |               </ul>
261 |             </dd>
262 | 
263 |             <dt id="turtle" class="spec">RDF 1.2 Turtle</dt>
264 |             <dd>
265 |               <p>This specification defines a textual syntax for RDF called Turtle that allows an RDF graph to be completely written in a compact and natural text form, with abbreviations for common usage patterns and datatypes. Turtle provides levels of compatibility with the N-Triples format as well as the triple pattern syntax of the SPARQL W3C Recommendation.</p>
266 | 
267 |               <p class="draft-status"><b>Draft state:</b> Working Draft</p>
268 |               <p class="milestone"><b>Expected completion:</b> Q3 2025</p>
269 |               <ul>
270 |                 <li><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2025/WD-rdf12-turtle-20250220/">https://www.w3.org/TR/2025/WD-rdf12-turtle-20250220/</a>
271 |                 <li><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2023/WD-rdf12-turtle-20230516/">https://www.w3.org/TR/2023/WD-rdf12-turtle-20230516/</a>
272 |                 <li><b>Exclusion Draft Charter:</b> <a href="https://www.w3.org/2022/08/rdf-star-wg-charter/">https://www.w3.org/2022/08/rdf-star-wg-charter/</a>
273 |               </ul>
274 |             </dd>
275 | 
276 |             <dt id="rdf-syntax-grammar" class="spec">RDF 1.2 XML Syntax</dt>
277 |             <dd>
278 |               <p>This specification defines an XML syntax for RDF called RDF/XML in terms of Namespaces in XML, the XML Information Set and XML Base.</p>
279 | 
280 |               <p class="draft-status"><b>Draft state:</b> Working Draft</p>
281 |               <p class="milestone"><b>Expected completion:</b> Q3 2025</p>
282 |               <ul>
283 |                 <li><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2025/WD-rdf12-xml-20250227/">https://www.w3.org/TR/2025/WD-rdf12-xml-20250227/</a>
284 |                 <li><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2023/WD-rdf12-xml-20230516/">https://www.w3.org/TR/2023/WD-rdf12-xml-20230516/</a>
285 |                 <li><b>Exclusion Draft Charter:</b> <a href="https://www.w3.org/2022/08/rdf-star-wg-charter/">https://www.w3.org/2022/08/rdf-star-wg-charter/</a>
286 |               </ul>
287 |               <p>This Working Group will update this normative references and address the errata in this document. Its content may also be revised to integrate RDF-star features, provided enough interest and manpower are available./p>
288 |             </dd>
289 | 
290 |             <dt id="rdf-schema" class="spec">RDF Schema 1.2</dt>
291 |             <dd>
292 |               <p>This specification describes how to use RDF to describe RDF vocabularies. This specification defines a vocabulary for this purpose and defines other built-in RDF vocabulary initially specified in the RDF Model and Syntax Specification.</p>
293 | 
294 |               <p class="draft-status"><b>Draft state:</b> Working Draft</p>
295 |               <p class="milestone"><b>Expected completion:</b> Q3 2025</p>
296 |               <ul>
297 |                 <li><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2025/WD-rdf12-schema-20250224/">https://www.w3.org/TR/2025/WD-rdf12-schema-20250224/</a>
298 |                 <li><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2023/WD-rdf12-schema-20230516/">https://www.w3.org/TR/2023/WD-rdf12-schema-20230516/</a>
299 |                 <li><b>Exclusion Draft Charter:</b> <a href="https://www.w3.org/2022/08/rdf-star-wg-charter/">https://www.w3.org/2022/08/rdf-star-wg-charter/</a>
300 |               </ul>
301 |             </dd>
302 |             </dl>
303 |           </section>
304 |           <section>
305 |             <h4>SPARQL family of specifications</h4>
306 |             <dl>
307 | <dt id="sparql11-overview" class="spec">SPARQL 1.2 Overview</dt>
308 |             <dd>
309 | 	            <p>
310 |                 This document is an overview of SPARQL 1.1. It provides an introduction
311 |                 to a set of W3C specifications that facilitate querying and manipulating
312 |                 RDF graph content on the Web or in an RDF store.
313 |               </p>
314 |               <p class="draft-status"><b>Draft state:</b> No Draft</p>
315 |               <p class="milestone"><b>Expected completion:</b> Q4 2025</p>
316 |               <p><b>Input Documentt:</b> <a href="https://www.w3.org/TR/2013/REC-sparql11-overview-20130321/">SPARQL 1.1 Overview</a>, ed. The W3C SPARQL Working Group, W3C Recommendation.</p>
317 |               </dd>
318 | 
319 |             <dt id="sparql11-query" class="spec">SPARQL 1.2 Query Language</dt>
320 |             <dd>
321 |               <p>This specification defines the syntax and semantics of the SPARQL query language for RDF. SPARQL can be used to express queries across diverse data sources, whether the data is stored natively as RDF or viewed as RDF via middleware. SPARQL contains capabilities for querying required and optional graph patterns along with their conjunctions and disjunctions. SPARQL also supports aggregation, subqueries, negation, creating values by expressions, extensible value testing, and constraining queries by source RDF graph. The results of SPARQL queries can be result sets or RDF graphs.</p>
322 | 
323 |               <p class="draft-status"><b>Draft state:</b> Working Draft</p>
324 |               <p class="milestone"><b>Expected completion:</b> Q4 2025</p>
325 |               <ul>
326 |                 <li><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2025/WD-sparql12-query-20250404/">https://www.w3.org/TR/2025/WD-sparql12-query-20250404/</a>
327 |                 <li><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2023/WD-sparql12-query-20230516/">https://www.w3.org/TR/2023/WD-sparql12-query-20230516/</a>
328 |                 <li><b>Exclusion Draft Charter:</b> <a href="https://www.w3.org/2022/08/rdf-star-wg-charter/">https://www.w3.org/2022/08/rdf-star-wg-charter/</a>
329 |               </ul>
330 |             </dd>
331 | 
332 |             <dt id="sparql11-update" class="spec">SPARQL 1.2 Update</dt>
333 |             <dd>
334 |               <p>This specification defines an update language for RDF graphs. It uses a syntax derived from the SPARQL Query Language for RDF. Update operations are performed on a collection of graphs in a Graph Store. Operations are provided to update, create, and remove RDF graphs in a Graph Store.</p>
335 | 
336 |               <p class="draft-status"><b>Draft state:</b> Working Draft</p>
337 |               <p class="milestone"><b>Expected completion:</b> Q4 2025</p>
338 |               <ul>
339 |                 <li><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2025/WD-sparql12-update-20250206/">https://www.w3.org/TR/2025/WD-sparql12-update-20250206/</a>
340 |                 <li><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2023/WD-sparql12-update-20230516/">https://www.w3.org/TR/2023/WD-sparql12-update-20230516/</a>
341 |                 <li><b>Exclusion Draft Charter:</b> <a href="https://www.w3.org/2022/08/rdf-star-wg-charter/">https://www.w3.org/2022/08/rdf-star-wg-charter/</a>
342 |               </ul>
343 |             </dd>
344 | 
345 |             <dt id="sparql11-results-json" class="spec">SPARQL 1.2 Query Results JSON Format</dt>
346 |             <dd>
347 |               <p>This specification defines a JSON format for the variable binding and boolean results formats provided by the SPARQL query language for RDF.</p>
348 | 
349 |               <p class="draft-status"><b>Draft state:</b> Working Draft</p>
350 |               <p class="milestone"><b>Expected completion:</b> Q4 2025</p>
351 |               <ul>
352 |                 <li><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2024/WD-sparql12-results-json-20241219/">https://www.w3.org/TR/2024/WD-sparql12-results-json-20241219/</a>
353 |                 <li><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2023/WD-sparql12-results-json-20230516/">https://www.w3.org/TR/2023/WD-sparql12-results-json-20230516/</a>
354 |                 <li><b>Exclusion Draft Charter:</b> <a href="https://www.w3.org/2022/08/rdf-star-wg-charter/">https://www.w3.org/2022/08/rdf-star-wg-charter/</a>
355 |               </ul>
356 |             </dd>
357 | 
358 |             <dt id="sparql11-results-xml" class="spec">SPARQL 1.2 Query Results XML Format</dt>
359 |             <dd>
360 |               <p>This specification defines an XML format for the variable binding and boolean results formats provided by the SPARQL query language for RDF.</p>
361 | 
362 |               <p class="draft-status"><b>Draft state:</b> Working Draft</p>
363 |               <p class="milestone"><b>Expected completion:</b> Q4 2025</p>
364 |               <ul>
365 |                 <li><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2024/WD-sparql12-results-xml-20241227/">https://www.w3.org/TR/2024/WD-sparql12-results-xml-20241227/</a>
366 |                 <li><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2023/WD-sparql12-results-xml-20230516/">https://www.w3.org/TR/2023/WD-sparql12-results-xml-20230516/</a>
367 |                 <li><b>Exclusion Draft Charter:</b> <a href="https://www.w3.org/2022/08/rdf-star-wg-charter/">https://www.w3.org/2022/08/rdf-star-wg-charter/</a>
368 |               </ul>
369 |             </dd>
370 |           </dl>
371 | 
372 |           <p>
373 |             The following additional SPARQL documents will be updated to align with changes
374 |             caused by the documents listed above and to incorporate errata.
375 |           </p>
376 | 
377 |           <dl>
378 |             <dt id="sparql11-service-description" class="spec">SPARQL 1.2 Service Description</dt>
379 |             <dd>
380 |               <p>This document describes SPARQL service description, a method for discovering, and vocabulary for describing SPARQL services made available via the SPARQL 1.1 Protocol for RDF.</p>
381 | 
382 |               <p class="draft-status"><b>Draft state:</b> Working Draft</p>
383 |               <p class="milestone"><b>Expected completion:</b> Q4 2025</p>
384 |               <ul>
385 |                 <li><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2024/WD-sparql12-service-description-20241219/">https://www.w3.org/TR/2024/WD-sparql12-service-description-20241219/</a>
386 |                 <li><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2023/WD-sparql12-service-description-20230516/">https://www.w3.org/TR/2023/WD-sparql12-service-description-20230516/</a>
387 |                 <li><b>Exclusion Draft Charter:</b> <a href="https://www.w3.org/2022/08/rdf-star-wg-charter/">https://www.w3.org/2022/08/rdf-star-wg-charter/</a>
388 |               </ul>
389 |             </dd>
390 | 
391 |             <dt id="sparql11-federated-query" class="spec">SPARQL 1.2 Federated Query</dt>
392 |             <dd>
393 |               <p>This specification defines the syntax and semantics of SPARQL 1.1 Federated Query for executing queries distributed over different SPARQL endpoints.</p>
394 | 
395 |               <p class="draft-status"><b>Draft state:</b> Working Draft</p>
396 |               <p class="milestone"><b>Expected completion:</b> Q4 2025</p>
397 |               <ul>
398 |                 <li><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2024/WD-sparql12-federated-query-20241219/">https://www.w3.org/TR/2024/WD-sparql12-federated-query-20241219/</a>
399 |                 <li><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2023/WD-sparql12-federated-query-20230516/">https://www.w3.org/TR/2023/WD-sparql12-federated-query-20230516/</a>
400 |                 <li><b>Exclusion Draft Charter:</b> <a href="https://www.w3.org/2022/08/rdf-star-wg-charter/">https://www.w3.org/2022/08/rdf-star-wg-charter/</a>
401 |               </ul>
402 |             </dd>
403 | 
404 |             <dt id="sparql11-entailment-regimes" class="spec">SPARQL 1.2 Entailment Regimes</dt>
405 |             <dd>
406 |               <p>There are different possible ways of defining a basic graph pattern matching extension for an entailment relation. This document specifies one such way for a range of standard semantic web entailment relations.</p>
407 | 
408 |               <p class="draft-status"><b>Draft state:</b> Working Draft</p>
409 |               <p class="milestone"><b>Expected completion:</b> Q4 2025</p>
410 |               <ul>
411 |                 <li><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2024/WD-sparql12-entailment-20241219/">https://www.w3.org/TR/2024/WD-sparql12-entailment-20241219/</a>
412 |                 <li><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2023/WD-sparql12-entailment-20230606/">https://www.w3.org/TR/2023/WD-sparql12-entailment-20230606/</a>
413 |                 <li><b>Exclusion Draft Charter:</b> <a href="https://www.w3.org/2022/08/rdf-star-wg-charter/">https://www.w3.org/2022/08/rdf-star-wg-charter/</a>
414 |               </ul>
415 |             </dd>
416 | 
417 |            <dt id="sparql-11-protocol" class="spec">SPARQL 1.2 Protocol</dt>
418 |             <dd>
419 |               <p>This document specifies the SPARQL Protocol; it describes a means for conveying SPARQL queries and updates to a SPARQL processing service and returning the results via HTTP to the entity that requested them.</p>
420 | 
421 |               <p class="draft-status"><b>Draft state:</b> Working Draft</p>
422 |               <p class="milestone"><b>Expected completion:</b> Q4 2025</p>
423 |               <ul>
424 |                 <li><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2024/WD-sparql12-protocol-20241219/">https://www.w3.org/TR/2024/WD-sparql12-protocol-20241219/</a>
425 |                 <li><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2023/WD-sparql12-protocol-20230516/">https://www.w3.org/TR/2023/WD-sparql12-protocol-20230516/</a>
426 |                 <li><b>Exclusion Draft Charter:</b> <a href="https://www.w3.org/2022/08/rdf-star-wg-charter/">https://www.w3.org/2022/08/rdf-star-wg-charter/</a>
427 |               </ul>
428 |             </dd>
429 | 
430 |            <dt id="sparql11-graph-store-http-protocol" class="spec">SPARQL 1.2 Graph Store HTTP Protocol</dt>
431 |             <dd>
432 |               <p>This document describes the use of HTTP operations for the purpose of managing a collection of RDF graphs.</p>
433 | 
434 |               <p class="draft-status"><b>Draft state:</b> Working Draft</p>
435 |               <p class="milestone"><b>Expected completion:</b> Q4 2025</p>
436 |               <ul>
437 |                 <li><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2024/WD-sparql12-graph-store-protocol-20241219/">https://www.w3.org/TR/2024/WD-sparql12-graph-store-protocol-20241219/</a>
438 |                 <li><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2023/WD-sparql12-graph-store-protocol-20230516/">https://www.w3.org/TR/2023/WD-sparql12-graph-store-protocol-20230516/</a>
439 |                 <li><b>Exclusion Draft Charter:</b> <a href="https://www.w3.org/2022/08/rdf-star-wg-charter/">https://www.w3.org/2022/08/rdf-star-wg-charter/</a>
440 |               </ul>
441 |             </dd>
442 | 
443 |             <dt id="sparql11-results-csv-and-tsv" class="spec">SPARQL 1.2 Query Results CSV and TSV Format</dt>
444 |             <dd>
445 |               <p>The formats CSV [RFC4180] (comma separated values) and TSV [IANA-TSV] (tab separated values) provide simple, easy to process formats for the transmission of tabular data. They are supported as input datat formats to many tools, particularly spreadsheets. This document describes their use for expressing SPARQL query results from SELECT queries.</p>
446 | 
447 |               <p class="draft-status"><b>Draft state:</b> Working Draft</p>
448 |               <p class="milestone"><b>Expected completion:</b> Q4 2025</p>
449 |               <ul>
450 |                 <li><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2024/WD-sparql12-results-csv-tsv-20241219/">https://www.w3.org/TR/2024/WD-sparql12-results-csv-tsv-20241219/</a>
451 |                 <li><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2023/WD-sparql12-results-csv-tsv-20230516/">https://www.w3.org/TR/2023/WD-sparql12-results-csv-tsv-20230516/</a>
452 |                 <li><b>Exclusion Draft Charter:</b> <a href="https://www.w3.org/2022/08/rdf-star-wg-charter/">https://www.w3.org/2022/08/rdf-star-wg-charter/</a>
453 |               </ul>
454 |             </dd>
455 |           </dl>
456 | 
457 |         </section>
458 | 
459 |         </section>
460 | 
461 |         <section id="ig-other-deliverables">
462 |           <h3>
463 |             Other Deliverables
464 |           </h3>
465 |           <p>
466 |             Other non-normative documents may be created such as:
467 |           </p>
468 |           <ul>
469 |             <li>Use case and requirement documents;</li>
470 |             <li>Test suite and implementation report for the specification;</li>
471 |             <li>Primer or Best Practice documents to support web developers when designing applications, 
472 |                 including an update of the <a href="https://www.w3.org/TR/rdf11-primer/">RDF 1.1 Primer</a></li>
473 |             <li>Guidelines about how and which <a href="https://www.w3.org/policies/process/#allow-new-features">new features</a> may be further added to the recommendations.</li>
474 |           </ul>
475 | 
476 |           <p>
477 |             Other normative deliverables might be considered by the Working Group during its lifetime.
478 |             For example, community efforts to integrate RDF-star into other RDF-related specifications might reach a maturity level justifying their adoption by this Working Group. Should this happen, a rechartering will be requested, involving a new review by the Advisory Committee.
479 |           </p>
480 |         </section>
481 | 
482 |         <section id="timeline">
483 |           <h3>Timeline</h3>
484 |             <ul>
485 |               <li>Q2 2025: Candidate Recommendation of RDF 1.2 deliverables</li>
486 |               <li>Q3 2025: Candidate Recommendation of SPARQL 1.2 deliverables</li>
487 |               <li>Q3 2025: Recommendation of RDF 1.2 deliverables</li>
488 |               <li>Q4 2025: Recommendation of SPARQL 1.2 deliverables</li>
489 |               <li>Afterwards: Maintenance of RDF 1.2 and SPARQL 1.2 recommendations</li>
490 |             </ul>
491 |         </section>
492 |       </section>
493 | 
494 | 	<section id="success-criteria">
495 | 	  <h2>Success Criteria</h2>
496 | 	  <p>In order to advance to <a href="https://www.w3.org/policies/process/#RecsPR" title="Proposed Recommendation">Proposed Recommendation</a>, each normative specification is expected to have <a href="https://www.w3.org/policies/process/#implementation-experience">at least two independent implementations</a> of every feature defined in the specification.</p>
497 | 	  <p>Each specification should contain separate sections detailing all known security and privacy implications for implementers, Web authors, and end users.</p>
498 | 	  <p>There should be testing plans for each specification, starting from the earliest drafts.</p>
499 | 	  <p>To promote interoperability, all changes made to specifications should have <a href='https://www.w3.org/2019/02/testing-policy.html'>tests</a>.</p>
500 | 	</section>
501 | 
502 |       <section id="coordination">
503 |         <h2>Coordination</h2>
504 |         <p>For all specifications, this Working Group will seek <a href="https://www.w3.org/Guide/documentreview/#how_to_get_horizontal_review">horizontal review</a> for
505 |           accessibility, internationalization, privacy, and security with the relevant Working and
506 |           Interest Groups, and with the <a href="https://www.w3.org/2001/tag/" title="Technical Architecture Group">TAG</a>.
507 |           Invitation for review must be issued during each major standards-track document transition, including
508 |           <a href="https://www.w3.org/policies/process/#RecsWD" title="First Public Working Draft">FPWD</a>.  The
509 |           Working Group is encouraged to engage collaboratively with the horizontal review groups throughout development of
510 |           each specification.  The Working Group is advised to seek a review at least 3 months before first entering
511 |           <a href="https://www.w3.org/policies/process/#RecsCR" title="Candidate Recommendation">CR</a> and is encouraged
512 |           to proactively notify the horizontal review groups when major changes occur in a specification following a review.</p>
513 | 
514 |         <p>Additional technical coordination with the following Groups will be made, per the <a href="https://www.w3.org/policies/process/#WGCharter">W3C Process Document</a>:</p>
515 | 
516 |         <section>
517 |           <h3 id="w3c-coordination">W3C Groups</h3>
518 |           <dl>
519 |             <dt><a href="https://www.w3.org/2017/dxwg/wiki/Main_Page">Data Exchange Working Group</a> (DXWG)</dt>
520 |             <dd>The work of the DXWG on Content Negotiation by Profile has been identified as a way to improve interoperability between RDF 1.2 applications and legacy application that do not support its new features.</dd>
521 | 
522 |             <dt><a href="https://www.w3.org/groups/wg/data-shapes/">Data Shapes Working Group</a></dt>
523 |             <dd>One of the primary goals of the Working Group is to provide SHACL handling of the new features introduced in RDF 1.2 (from RDF-star)</dd>
524 | 
525 |             <dt><a href="https://www.w3.org/2018/json-ld-wg/">JSON-LD Working Group</a></dt>
526 |             <dd>As a concrete syntax for RDF datasets, JSON-LD may also be updated to support RDF 1.2. <a href="https://json-ld.github.io/json-ld-star/">A proposal</a> from the JSON-LD Community Group based on RDF-star is already available.</dd>
527 | 
528 |             <dt><a href="https://www.w3.org/community/rdf-dev/">RDF-DEV Community Group</a></dt>
529 |             <dd>To synchronize with other incubation and standardization work related to RDF, for example <a href="https://w3c.github.io/rch-wg-charter/">canonicalization and hashing</a>.</dd>
530 | 
531 |             <dt><a href="https://www.w3.org/community/sparql-12/">SPARQL 1.2 Community Group</a></dt>
532 |             <dd>To synchronize with other possible incubation and standardization work related to SPARQL.</dd>
533 |             
534 |           </dl>
535 |         </section>
536 | 
537 |         <section>
538 |           <h3 id="external-coordination">External Organizations</h3>
539 |           <dl>
540 |             <dt><a href="https://ldbcouncil.org/gql-community/lex/">LDBC Extended GQL Schema (LEX) Working Group</a></dt>
541 |             <dd>To coordinate on possible bridges between RDF(-star) graphs and the unified model for Property Graphs proposed by this group.</dd>
542 | 
543 |             <dt><a href="https://www.iso.org/committee/45342.html">ISO/IEC JTC 1/SC 32</a> Data management and interchange</dt>
544 |             <dd>Through the <a href="https://www.w3.org/liaisons/#ISO">existing liaison with W3C</a>, to coordinate with the efforts around graph query languages
545 |               (<a href="https://www.iso.org/standard/76120.html">GQL</a> and <a href="https://www.iso.org/standard/79473.html">SQL/PGQ</a>).</dd>
546 |           </dl>
547 |         </section>
548 |       </section>
549 | 
550 | 
551 | 
552 |       <section class="participation">
553 |         <h2 id="participation">
554 |           Participation
555 |         </h2>
556 |         <p>
557 |           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.
558 |         </p>
559 |         <p>
560 |           The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in <a href='#communication'>Communication</a>.
561 |         </p>
562 |         <p>
563 |           The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the <a href="https://www.w3.org/policies/patent-policy/">W3C Patent Policy</a>.
564 |         </p>
565 |         <p>Participants in the group are required (by the <a href="https://www.w3.org/policies/process/#ParticipationCriteria">W3C Process</a>) to follow the
566 |           W3C <a href="https://www.w3.org/policies/code-of-conduct/">Code of Conduct</a>.</p>
567 |       </section>
568 | 
569 | 
570 | 
571 |       <section id="communication">
572 |         <h2>
573 |           Communication
574 |         </h2>
575 |         <p id="public">
576 |           Technical discussions for this Working Group are conducted in <a href="https://www.w3.org/policies/process/#confidentiality-levels">public</a>: 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 in public repositories and may permit direct public contribution requests.
577 |         The meetings themselves are not open to public participation, however.
578 |         </p>
579 |         <p>
580 |           Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <a href="">RDF &amp; SPARQL Working Group home page.</a>
581 |         </p>
582 |         <p>
583 |           Most RDF &amp; SPARQL Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.
584 |         </p>
585 |         <p>
586 |           This group primarily conducts its technical work on <a id="public-github" href="https://github.com/w3c/rdf-star-wg/">GitHub issues</a> or on the public mailing list <a id="public-name" href="mailto:public-rdf-star-wg@w3.org">public-rdf-star@w3.org</a> (<a href="https://lists.w3.org/Archives/Public/public-rdf-star-wg/">archive</a>).
587 |           The public is invited to review, discuss and contribute to this work.
588 |         </p>
589 |         <p>
590 |           The group may use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a participant requests such a discussion.
591 |         </p>
592 |       </section>
593 | 
594 | 
595 | 
596 |       <section id="decisions">
597 |         <h2>
598 |           Decision Policy
599 |         </h2>
600 |         <p>
601 |           This group will seek to make decisions through consensus and due process, per the <a href="https://www.w3.org/policies/process/#Consensus"> W3C Process Document (section 5.2.1, Consensus)</a>). 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.</p>
602 |         <p>
603 |            However, if a decision is necessary for timely progress and 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.
604 |         </p>
605 |         <p>
606 |           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.
607 | 
608 |           A call for consensus (CfC) will be issued for all resolutions (for example, via email, GitHub issue 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.
609 | 
610 |           If no objections are raised by the end of the response period, the resolution will be considered to have consensus as a resolution of the Working Group.
611 |         </p>
612 |         <p>
613 |           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.
614 |         </p>
615 |         <p>
616 |           This charter is written in accordance with the <a href="https://www.w3.org/policies/process/#Votes">W3C Process Document (Section 5.2.3, Deciding by Vote)</a> and includes no voting procedures beyond what the Process Document requires.
617 |         </p>
618 |       </section>
619 | 
620 | 
621 | 
622 |       <section id="patentpolicy">
623 |         <h2>
624 |           Patent Policy
625 |         </h2>
626 |         <p>
627 |           This Working Group operates under the <a href="https://www.w3.org/policies/patent-policy/">W3C Patent Policy</a> (Version of 15 September 2020). To promote the widest adoption of Web standards, W3C seeks to issue Web specifications that can be implemented, according to this policy, on a Royalty-Free basis.
628 | 
629 |           For more information about disclosure obligations for this group, please see the <a href="https://www.w3.org/groups/wg/rdf-star/ipr/">licensing information</a>.
630 |         </p>
631 |       </section>
632 | 
633 | 
634 | 
635 |       <section id="licensing">
636 |         <h2>Licensing</h2>
637 |         <p>This Working Group will use the <a href="https://www.w3.org/copyright/software-license/">W3C Software and Document license</a> for all its deliverables.</p>
638 |       </section>
639 | 
640 | 
641 | 
642 |       <section id="about">
643 |         <h2>
644 |           About this Charter
645 |         </h2>
646 |         <p>
647 |           This charter has been created according to <a href="https://www.w3.org/policies/process/#WG-and-IG">section 3.4</a> of the <a href="https://www.w3.org/policies/process/">Process Document</a>. 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.
648 |         </p>
649 | 
650 |         <section id="history">
651 |           <h3>
652 |             Charter History
653 |           </h3>
654 | 
655 |           <p>The following table lists details of all changes from the initial charter, per the <a href="https://www.w3.org/policies/process/#CharterReview">W3C Process Document (section 4.3, Advisory Committee Review of a Charter)</a>:</p>
656 | 
657 |           <table class="history">
658 |             <tbody>
659 |               <tr>
660 |                 <th>
661 |                   Charter Period
662 |                 </th>
663 |                 <th>
664 |                   Start Date
665 |                 </th>
666 |                 <th>
667 |                   End Date
668 |                 </th>
669 |                 <th>
670 |                   Changes
671 |                 </th>
672 |               </tr>
673 |               <tr>
674 |                 <th>
675 |                   <a href="https://www.w3.org/2022/08/rdf-star-wg-charter/">Initial Charter</a>
676 |                 </th>
677 |                 <td>
678 |                   29 August 2022
679 |                 </td>
680 |                 <td>
681 |                   28 August 2024
682 |                 </td>
683 |                 <td>
684 |                   N/A
685 |                 </td>
686 |               </tr>
687 |               <tr>
688 |                 <th>
689 |                   <a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2024JulSep/0031.html">Charter Extension</a>
690 |                 </th>
691 |                 <td>
692 |                   29 August 2024
693 |                 </td>
694 |                 <td>
695 |                   28 November 2024
696 |                 </td>
697 |                 <td>
698 |                  Current charter extended. A <a href="https://www.w3.org/2024/08/proposed-rdf-star-wg-charter.html">proposed new charter</a> (<a href="https://github.com/w3c/charter-drafts/blob/gh-pages/2024/rdf-star-wg.html">available on GitHub</a>) is under review.
699 |                 </td>
700 |               </tr>
701 |               <tr>
702 |                 <th>
703 |                   <a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2024OctDec/0070.html">Charter Extension</a>
704 |                 </th>
705 |                 <td>
706 |                   29 November 2024
707 |                 </td>
708 |                 <td>
709 |                   28 February 2025
710 |                 </td>
711 |                 <td>
712 |                  Current charter extended, pending the resolution of formal objections on the new proposed charter.
713 |                 </td>
714 |               </tr>
715 |               <tr>
716 |                 <th>
717 |                   <a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2025JanMar/0078.html">Charter Extension</a>
718 |                 </th>
719 |                 <td>
720 |                   01 March 2025
721 |                 </td>
722 |                 <td>
723 |                   30 April 2025
724 |                 </td>
725 |                 <td>
726 |                  Current charter extended, pending decision of the W3C council regarding the proposed recharter.
727 |                 </td>
728 |               </tr>
729 |               <tr>
730 |                 <th>
731 |                   <a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2025AprJun/0025.html">Rechartered</a>
732 |                 </th>
733 |                 <td>
734 |                   01 May 2025
735 |                 </td>
736 |                 <td>
737 |                   30 April 2027
738 |                 </td>
739 |                 <td>
740 |                   Rechartered for two more years, to 1) complete the work on RDF 1.2 and SPARQL 1.2 deliverables, and 2) switch to maintenance mode thereafter.
741 |                 </td>
742 |               </tr>
743 |               <!--
744 |               <tr>
745 |                 <th>
746 |                   <a class="todo" href="">Charter Extension</a>
747 |                 </th>
748 |                 <td>
749 |                   <i class="todo">[dd monthname yyyy]</i>
750 |                 </td>
751 |                 <td>
752 |                   <i class="todo">[dd monthname yyyy]</i>
753 |                 </td>
754 |                 <td>
755 |                   <i class="todo">none</i>
756 |                 </td>
757 |               </tr>
758 |               <tr>
759 |                 <th>
760 |                   <a class="todo" href="">Rechartered</a>
761 |                 </th>
762 |                 <td>
763 |                   <i class="todo">[dd monthname yyyy]</i>
764 |                 </td>
765 |                 <td>
766 |                   <i class="todo">[dd monthname yyyy]</i>
767 |                 </td>
768 |                 <td>
769 |                   <p class="todo">[description of change to charter, with link to new deliverable item in charter] <b>Note:</b> use the class <code>new</code> for all new deliverables, for ease of recognition.</p>
770 |                 </td>
771 |               </tr>
772 |             -->
773 |             </tbody>
774 |           </table>
775 |         </section>
776 | 
777 |         <!--
778 |         <section id="changelog">
779 |           <h3>Change log</h3>
780 | 
781 |           <!- Use this section for changes _after_ the charter was approved by the Director.
782 |           ->
783 |           <p>Changes to this document are documented in this section.</p>
784 |           <!-
785 |           <dl id='changes'>
786 |             <dt>YYYY-MM-DD</dt>
787 |             <dd>[changes]]</dd>
788 |           </dl>
789 |           ->
790 |         </section>
791 |         -->
792 |       </section>
793 |     </main>
794 | 
795 |     <hr>
796 | 
797 |     <footer>
798 |       <address>
799 |         <a href="mailto:pierre-antoine@w3.org">Pierre-Antoine Champin</a>
800 |       </address>
801 | 
802 |       <p class="copyright">Copyright © 2025 <a href="https://www.w3.org/">World Wide Web Consortium</a>.<br>
803 |         <abbr title="World Wide Web Consortium">W3C</abbr><sup>®</sup>
804 |         <a href="https://www.w3.org/policies/#disclaimers">liability</a>,
805 |         <a href="https://www.w3.org/policies/#trademarks">trademark</a> and
806 |             <a rel="license" href="https://www.w3.org/copyright/software-license/" title="W3C Software and Document Notice and License">permissive document license</a> rules apply.</p>
807 |       <hr>
808 |       <!--
809 |       <p class=todo><a href="https://github.com/w3c/rdf-star-wg-charter">Yes, it's on GitHub!</a>.</p>
810 |       -->
811 |     </footer>
812 | 
813 |   </body>
814 | </html>
815 | 


--------------------------------------------------------------------------------
/w3c.json:
--------------------------------------------------------------------------------
1 | {
2 |  "group": [139681],
3 |   "contacts": [
4 |     "pchampin"
5 |   ],
6 |   "policy": "open",
7 |   "repo-type": "process"
8 | }
9 | 


--------------------------------------------------------------------------------