Skip to content

Commit c64be62

Browse files
ihermaniherman
authored
Merge pull request #9 from w3c/Finalizing-the-new-version
Another editorial round
2 parents d64caef + 23ba48c commit c64be62

File tree

1 file changed

+59
-41
lines changed

1 file changed

+59
-41
lines changed

‎index.html‎

Lines changed: 59 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -86,8 +86,8 @@ <h1 id="title"><i class=todo>DRAFT</i> JSON-LD Working Group Charter</h1>
8686
<!-- replace GitHub link and issues link to the specific charter in GH and its issues repo -->
8787
<!-- delete the GH link after AC review completed -->
8888
<p class=todo style="padding: 0.5ex; border: 1px solid green">
89-
This draft charter is available on <a href="https://github.com/json-ld/json-ld-wg-charter">GitHub</a>.
90-
Feel free to raise <a href="https://github.com/json-ld/json-ld-wg-charter/issues">issues</a>.
89+
This draft charter is available on <a href="https://github.com/w3c/json-ld-charter-2025">GitHub</a>.
90+
Feel free to raise <a href="https://github.com/w3c/json-ld-charter-2025/issues">issues</a>.
9191
</p>
9292

9393
<div id="details">
@@ -156,22 +156,22 @@ <h2>Motivation and Background</h2>
156156
structured data in Web pages using <a href="https://schema.org">schema.org</a>. JSON-LD has also become a foundational format for social media
157157
(<a href="https://www.w3.org/TR/activitystreams-core/">ActivityStreams</a>),
158158
Internet of Things data (<a href="https://www.w3.org/TR/wot-thing-description11/">Web of Things Description</a>),
159-
<a href="https://www.w3.org/TR/vc-data-model-2.0/">Verifiable Credentials</a>, and Software Bill of Materials
159+
<a href="https://www.w3.org/TR/vc-data-model-2.0/">Verifiable Credentials</a>, or Software Bill of Materials
160160
(<a href="https://spdx.github.io/spdx-spec/v3.0.1/serializations/#serialization-in-json-ld">SPDX</a>).
161161
</p>
162162

163163
<p>This growth in the applied use of JSON-LD has led to a community interest in additional expressions of
164164
JSON-LD's underlying Linked Data structure in other formats. YAML-LD has been created by the
165-
<a href="https://www.w3.org/community/json-ld/">JSON for Linking Data Community Group</a> for easing human
166-
authoring and providing a clearer path for using Linked Data applied to popular YAML-based documents such as
165+
<a href="https://www.w3.org/community/json-ld/">JSON for Linking Data Community Group</a> to ease human
166+
authoring and to provide a clearer path for using Linked Data applied to popular YAML-based documents such as
167167
infrastructure as code, static site front matter, and API documentation formats.
168168
</p>
169169

170170
<p>
171171
For a number of application areas, the size of JSON-LD content is an obstacle. Size constraints may be
172172
encountered when storing data as a QR or in a barcode, transmitting data over low bandwidth channels, or when relying
173173
on high volume data storage. These constraints are not only significant for existing applications, but are also
174-
obstacles when enabling new application areas (e.g., in embedded systems). CBOR-LD, based on
174+
obstacles to enable new application areas (e.g., in embedded systems). CBOR-LD, based on
175175
<a href="https://cbor.io/spec.html">CBOR</a> (which already has a large user and tool base), can exploit
176176
the linked data features of JSON-LD, and provide a high level and easily reversible compression of
177177
JSON-LD data. Work on CBOR-LD has begun in the <a href="https://www.w3.org/community/json-ld/">JSON
@@ -190,14 +190,14 @@ <h2>Motivation and Background</h2>
190190
<section id="scope" class="scope">
191191
<h2>Scope</h2>
192192
<p>
193-
The Working Group will evolve the recommendations defining the JSON-LD specifications
193+
The Working Group will evolve the recommendations defining JSON-LD
194194
(i.e., <a href="https://www.w3.org/TR/json-ld11/">JSON-LD 1.1</a>,
195195
<a href="https://www.w3.org/TR/json-ld11-api/">JSON-LD 1.1 API</a>, and
196196
<a href="https://www.w3.org/TR/json-ld11-framing/">JSON-LD 1.1 Framing</a>) by handling Errata
197-
and by adding requested features as recorded on the group's
197+
and by adding requested features, as recorded on the group's
198198
<a href="https://github.com/orgs/w3c/projects/84">Project Management Page</a>. In order to handle these,
199199
the Working Group will issue new versions of these recommendations, possibly with new features,
200-
in order to render future usage and evolutions easier. In particular, the Working Group will handle
200+
in order to make future usage and evolutions easier. In particular, the Working Group will handle
201201
two important security related problems:
202202
</p>
203203

@@ -208,7 +208,7 @@ <h2>Scope</h2>
208208
those environments have more restrictive requirements than others on how unmapped terms should be treated (i.e.,
209209
when JSON keys present in the document have no term definition in the context). The current
210210
JSON-LD API stipulates that the unknown term is silently ignored. The Working Group will specify
211-
a "safe mode", that will detect these situations and cause the processing to fail. This mode is
211+
a "safe mode", that will detect these situations and cause the processing to fail instead. This mode is
212212
already available in some JSON-LD API implementations, such as
213213
<a href="https://github.com/digitalbazaar/jsonld.js?tab=readme-ov-file#safe-mode">jsonld.js</a> and
214214
<a href="https://dotnetrdf.org/2025-07-03-dn4-3-4-0-released/#:~:text=This%20release%20also%20introduces%20a,rather%20than%20silently%20ignoring%20them.">dotNetRDF</a>,
@@ -219,12 +219,12 @@ <h2>Scope</h2>
219219
pattern across many technologies that has, at times, confused implementers who
220220
expect that they should always use these identifiers as locators, and dereference them. This
221221
assumption can create risks and vulnerabilities that have been documented, but also often overlooked, in previous versions of JSON-LD.
222-
The Working Group intends to address this problem through more
223-
specification text, and exploration of options such as the addition of a hash fragment to be used
224-
with the application/ld+json media type responses. This fragment conveys a content hash which
225-
may be used by implementations to further confirm and handle the intentions of the original
226-
document author. (This has already been discussed by the Working Group, see, for example,
227-
the open issues <a href="https://github.com/w3c/json-ld-syntax/issues/108">108</a>,
222+
The Working Group intends to address this problem through more explanatory
223+
specification text, but also through the exploration of options such as the addition of a hash
224+
fragment to be used with the application/ld+json media type responses. This fragment conveys a
225+
content hash which may be used by implementations to further confirm and handle the intentions
226+
of the original document author. (This has already been discussed by the Working Group, see,
227+
for example, the open issues <a href="https://github.com/w3c/json-ld-syntax/issues/108">108</a>,
228228
<a href="https://github.com/w3c/json-ld-syntax/issues/436">436</a> or
229229
<a href="https://github.com/w3c/json-ld-syntax/issues/422">422</a>.)
230230
</li>
@@ -236,7 +236,7 @@ <h2>Scope</h2>
236236
<p>
237237
Development of the 1.2 versions of the JSON-LD specifications will follow the principle of
238238
backward compatibility. This means that any valid JSON-LD 1.1 document will remain valid
239-
for JSON-LD 1.2, and that the algorithms of the JSON-LD 1.2 API will yield
239+
for JSON-LD 1.2, and that the algorithms defined by the JSON-LD 1.2 API specification will yield
240240
<a href="https://www.w3.org/TR/rdf11-concepts/#graph-isomorphism">isomorphic</a> results to
241241
those of the JSON-LD 1.1 API — barring any bug or inconsistency of the JSON-LD 1.1
242242
specifications identified in the errata.
@@ -257,8 +257,8 @@ <h2>Scope</h2>
257257
concepts (primarily triple terms and directional language-tagged string), into the JSON-LD syntax, API, and Framing. The final goal is to
258258
have, eventually, a version of JSON-LD that is fully compatible with the upcoming RDF 1.2
259259
version, and provides shortcuts similar to those in
260-
<a href="https://www.w3.org/TR/rdf12-turtle/">RDF 1.2 Turtle</a> (e.g., reifying triple, triple annotation).
261-
This will be done in strong cooperation with the
260+
<a href="https://www.w3.org/TR/rdf12-turtle/">RDF 1.2 Turtle</a> (e.g., reifying triple or
261+
triple annotations). This will be done in strong cooperation with the
262262
<a href="https://www.w3.org/groups/wg/rdf-star">RDF &amp; SPARQL Working Group</a>.
263263
</p>
264264

@@ -378,7 +378,7 @@ <h3>
378378
<dt id="json-ld-13" class="spec">JSON-LD 1.3</dt>
379379
<dd>
380380
<p>
381-
This specification will define a new version of JSON-LD, fully compatible with <a href="https://www.w3.org/TR/rdf12-concepts">RDF 1.2</a>.
381+
This specification will define a new version of JSON-LD, fully compatible with JSON-LD 1.2 and <a href="https://www.w3.org/TR/rdf12-concepts">RDF 1.2</a>.
382382
</p>
383383
<p class="draft-status"><b>Draft state:</b>
384384
Proposal in <a href="https://json-ld.github.io/json-ld-star/">JSON-LD Star</a>, JSON for Linked Data Community Group Draft Report.
@@ -387,7 +387,7 @@ <h3>
387387
<dt id="json-ld-13" class="spec">JSON-LD 1.3 Processing Algorithms and API</dt>
388388
<dd>
389389
<p>
390-
This specification will define a new version of JSON-LD API, fully compatible with <a href="https://www.w3.org/TR/rdf12-concepts">RDF 1.2</a>.
390+
This specification will define a new version of JSON-LD API, fully compatible with JSON-LD 1.2 API and <a href="https://www.w3.org/TR/rdf12-concepts">RDF 1.2</a>.
391391
</p>
392392
<p class="draft-status"><b>Draft state:</b>
393393
Proposal in <a href="https://json-ld.github.io/json-ld-star/">JSON-LD Star</a>, JSON for Linked Data Community Group Draft Report.
@@ -396,7 +396,7 @@ <h3>
396396
<dt id="json-ld-13" class="spec">JSON-LD 1.3 Framing</dt>
397397
<dd>
398398
<p>
399-
This specification will define a new version of JSON-LD Framing, fully compatible with <a href="https://www.w3.org/TR/rdf12-concepts">RDF 1.2</a>.
399+
This specification will define a new version of JSON-LD Framing, fully compatible with JSON-LD 1.2 Framing and <a href="https://www.w3.org/TR/rdf12-concepts">RDF 1.2</a>.
400400
</p>
401401
<p class="draft-status"><b>Draft state:</b>
402402
Proposal in <a href="https://json-ld.github.io/json-ld-star/">JSON-LD Star</a>, JSON for Linked Data Community Group Draft Report.
@@ -405,7 +405,7 @@ <h3>
405405
<dt id="json-ld-13" class="spec">YAML-LD 1.1</dt>
406406
<dd>
407407
<p>
408-
This specification will define a new version of YAML-LD, fully compatible with <a href="https://www.w3.org/TR/rdf12-concepts">RDF 1.2</a>.
408+
This specification will define a new version of YAML-LD, fully compatible with YAML-LD 1.0 and <a href="https://www.w3.org/TR/rdf12-concepts">RDF 1.2</a>.
409409
</p>
410410
<p class="draft-status"><b>Draft state:</b>
411411
Proposal in <a href="https://json-ld.github.io/json-ld-star/">JSON-LD Star</a>, JSON for Linked Data Community Group Draft Report.
@@ -414,7 +414,7 @@ <h3>
414414
<dt id="json-ld-13" class="spec">CBOR-LD 1.1</dt>
415415
<dd>
416416
<p>
417-
This specification will define a new version of CBOR-LD, fully compatible with <a href="https://www.w3.org/TR/rdf12-concepts">RDF 1.2</a>.
417+
This specification will define a new version of CBOR-LD, fully compatible with CBOR-LD 1.0 and <a href="https://www.w3.org/TR/rdf12-concepts">RDF 1.2</a>.
418418
</p>
419419
<p class="draft-status"><b>Draft state:</b>
420420
Proposal in <a href="https://json-ld.github.io/json-ld-star/">JSON-LD Star</a>, JSON for Linked Data Community Group Draft Report.
@@ -433,25 +433,25 @@ <h3>
433433
<ul>
434434
<li>Application profile of JSON-LD to enable efficient streaming parsers.</li>
435435
<li>Test suites and implementation reports for the specifications.</li>
436-
<li>Best practices for use and implementation of JSON-LD 1.1 and 1.2.</li>
436+
<li>Best practices for use and implementation of JSON-LD 1.1, 1.2 and, possibly, 1.3.</li>
437437
</ul>
438438
</section>
439439

440440
<section id="timeline">
441441
<h3>Timeline</h3>
442442
<ul>
443-
<li>November 2025: First teleconference</li>
443+
<li>January 2026: First teleconference</li>
444444
<li>Q2 2026
445445
<ul>
446446
<li>FPWD of CBOR-LD</li>
447447
<li>FPWD of YAML-LD</li>
448+
<li>FPWD of JSON-LD 1.2</li>
449+
<li>FPWD of JSON-LD 1.2 API</li>
450+
<li>FPWD of JSON-LD 1.2 Framing</li>
448451
</ul>
449452
</li>
450453
<li>Q4 2026
451454
<ul>
452-
<li>FPWD of JSON-LD 1.2</li>
453-
<li>FPWD of JSON-LD 1.2 API</li>
454-
<li>FPWD of JSON-LD 1.2 Framing</li>
455455
<li>Candidate Recommendation of CBOR-LD</li>
456456
<li>Candidate Recommendation of YAML-LD</li>
457457
</ul>
@@ -527,10 +527,14 @@ <h2>Coordination</h2>
527527
<h3 id="w3c-coordination">W3C Groups</h3>
528528
<dl>
529529
<dt><a href='https://www.w3.org/community/json-ld/'>JSON for Linking Data Community Group</a></dt>
530-
<dd>As mentioned in the scope section, the Working group is expected to coordinate with this Community Group on consensus-based proposals related to content changes for the JSON-LD Working Group Deliverables. The Chairs of this group may choose to reject proposals that are incompatible with this Charter.</dd>
530+
<dd>As mentioned in the scope section, the Working Group is expected to coordinate with this Community Group on consensus-based proposals related to content changes for the JSON-LD Working Group Deliverables. The Chairs of the Working Group may choose to reject proposals that are incompatible with this Charter.</dd>
531531

532-
<dt><a href="https://www.w3.org/groups/wg/rdf-star">RDF & SPARQL Working Group</a></dt>
533-
<dd>The work of this Group will the ability to concisely represent and query statements about statements.</dd>
532+
<dt><a href="https://www.w3.org/groups/wg/rdf-star">RDF &amp; SPARQL Working Group</a></dt>
533+
<dd>
534+
The work of this Group will provide the ability to concisely represent in JSON-LD all features defined in
535+
<a href="https://www.w3.org/TR/rdf12-concepts">RDF 1.2</a>, and this will be done in cooperation with the
536+
RDF &amp; SPARQL Working Group.
537+
</dd>
534538

535539
<dt><a href="https://www.w3.org/groups/wg/dc">Verifiable Credentials Working Group</a></dt>
536540
<dd>Coordination on named graph indexing and other concerns regarding support for normalization and digital signatures.</dd>
@@ -542,7 +546,8 @@ <h3 id="w3c-coordination">W3C Groups</h3>
542546
<dd>Coordination of various topics concerning the use of JSON-LD by the WoT Thing Description.</dd>
543547

544548
<dt><a href="https://www.w3.org/community/credentials/">Credentials Community Group</a></dt>
545-
<dd>Coordination on various concerns regarding the usage of JSON-LD in Verifiable Credentials.</dd>
549+
<dd>Coordination on various concerns regarding the usage of JSON-LD in Verifiable Credentials
550+
and related Community Group specifications.</dd>
546551

547552
</dl>
548553
</section>
@@ -576,7 +581,7 @@ <h2 id="participation">
576581
</p>
577582

578583
<p>Participants in the group are required (by the <a href="https://www.w3.org/policies/process/#ParticipationCriteria">W3C Process</a>) to follow the
579-
W3C <a href="https://www.w3.org/policies/code-of-conduct/">Code of Ethics and Professional Conduct</a>.</p>
584+
<a href="https://www.w3.org/policies/code-of-conduct/">Positive Work Environment at W3C: Code of Conduct</a>.</p>
580585
</section>
581586

582587

@@ -699,9 +704,9 @@ <h3>
699704
</tr>
700705
<tr>
701706
<th>Change of staff contact</th>
702-
<td><i>23 June 2021</i></td>
703-
<td><i>31 August 2022</i></td>
704707
<td></td>
708+
<td></td>
709+
<td>Philippe le Hégaret appointed as new staff contact</td>
705710
</tr>
706711
<tr>
707712
<th>Extension</th>
@@ -727,19 +732,32 @@ <h3>
727732
<th>Change of staff contact</th>
728733
<td></td>
729734
<td></td>
730-
<td>09 February 2024, Pierre-Antoine Champin appointed as new staff contact</td>
735+
<td>Pierre-Antoine Champin appointed as new staff contact</td>
731736
</tr>
732737
<tr>
733738
<th><a href="https://lists.w3.org/Archives/Member/w3c-ac-members/2024JanMar/0005.html">Chair re-appointed</a></th>
734739
<td></td>
735740
<td></td>
736-
<td>17 January 2024, Benjamin Young re-appointed as the group chair</td>
741+
<td>Benjamin Young re-appointed as the group chair</td>
742+
</tr>
743+
<tr>
744+
<th>Extension</th>
745+
<td>01 February 2025</td>
746+
<td>31 July 2025</td>
747+
<td></td>
748+
</tr>
749+
<tr>
750+
<th>Extension, new co-chair</th>
751+
<td>07 August 2025</td>
752+
<td>30 November 2025</td>
753+
<td>Gregg Kellogg appointed as co-chair</td>
737754
</tr>
755+
738756
<tr>
739757
<th><a href="">Rechartered <i class=todo>LINK TBD</i></a></th>
740-
<td><i class=todo>TBD</i></td>
741-
<td><i>30 March 2026</i></td>
742-
<td><i>Add new deliverable</i></td>
758+
<td><i class=todo>01 January 2026</i></td>
759+
<td><i class="todo">31 December 2027</i></td>
760+
<td><i class="todo">New charter with new deliverables. Change of co-chairs: Benjamin Young and @@@@</i></td>
743761
</tr>
744762
</tbody>
745763
</table>

0 commit comments

Comments
 (0)