You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 23, 2025. It is now read-only.
<h1id="title"><iclass=todo>DRAFT</i> JSON-LD Working Group Charter</h1>
76
+
<!-- replace DRAFT with PROPOSED when the AC review starts -->
77
+
<!-- delete PROPOSED after AC review completed -->
76
78
77
79
<pclass="mission">The <strong>mission</strong> of the <ahref="https://www.w3.org/groups/wg/json-ld">JSON-LD Working Group</a> is to maintain and extend the <ahref="https://www.w3.org/groups/wg/json-ld/publications">family of JSON-LD 1.1 Recommendations</a> and related Working Group Notes.</p>
78
80
79
81
<divclass="noprint">
80
82
<pclass="join"><ahref="https://www.w3.org/groups/wg/json-ld/join">Join the JSON-LD Working Group.</a></p>
81
83
</div>
82
84
85
+
<!-- replace "draft charter" with "proposed charter" when the AC review starts -->
86
+
<!-- replace GitHub link and issues link to the specific charter in GH and its issues repo -->
87
+
<!-- delete the GH link after AC review completed -->
<p>This growth in the applied use of JSON-LD has resulted in community interest in additional expressions of
155
-
JSON-LD's underlying Linked Data structure into other formats. YAML-LD has been created by the
163
+
JSON-LD's underlying Linked Data structure in other formats. YAML-LD has been created by the
156
164
<ahref="https://www.w3.org/community/json-ld/">JSON for Linking Data Community Group</a> for easing human
157
165
authoring and providing a clearer path for using Linked Data applied to popular YAML-based documents such as
158
-
infrastructure as code, static site front matter, and API documentation formats.
166
+
infrastructure as code, static site front matter, and API documentation formats. Additionally, a need arose
167
+
in the Verifiable Credentials space for providing a more compressed expression of JSON-LD, and work on
168
+
CBOR-LD was begun in the JSON-LD CG.
159
169
</p>
160
170
161
171
<p>
@@ -170,8 +180,8 @@ <h2>Motivation and Background</h2>
170
180
</p>
171
181
172
182
<p>
173
-
The hope of this new more inclusively focused JSON-LD WG is to meet the demand of the broader
174
-
JSON-LD community by strengthening the foundational JSON-LD specifications and aligning it with the latest
183
+
The goal of this new more inclusively focused JSON-LD WG is to meet the demand of the broader
184
+
JSON-LD community by strengthening the foundational JSON-LD specifications and aligning them with the latest
175
185
RDF 1.2 specifications, growing the family of JSON-LD related formats which orbit around the JSON-LD
176
186
processing model, and specifying improved context retrieval methods for greater clarity and stability.
177
187
</p>
@@ -184,7 +194,8 @@ <h2>Scope</h2>
184
194
with the features introduced by <ahref="https://www.w3.org/TR/rdf12-concepts">RDF 1.2</a>
185
195
in addition to open Errata and requested features
186
196
as noted on the groups <ahref="https://github.com/orgs/w3c/projects/84">Project Management Page</a>.
187
-
These specifications together provide a JSON format for Linked Data to interoperate in a method which is familiar to and usable by software engineers.
197
+
Together, these specifications provide a JSON format for Linked Data,
198
+
enabling interoperation in a way which is familiar to and usable by software engineers.
188
199
<!-- Note that the JSON-LD APIs are not browser specific; while appropriate for use within browsers, they are not limited to such use, and there is no requirement for browsers to implement them natively. -->
189
200
</p>
190
201
<p>
@@ -222,7 +233,8 @@ <h2>
222
233
223
234
<p>Updated document status is available on the <ahref="https://www.w3.org/groups/wg/json-ld/publications">group publication status page</a>.</p>
224
235
225
-
<p><i>Draft state</i> indicates the state of the deliverable at the time of the charter approval.</p>
236
+
<p><i>Draft state</i> indicates the state of the deliverable at the time of the charter approval.
237
+
<i>Expected completion</i> indicates when the deliverable is projected to become a Recommendation, or otherwise reach a stable state.</p>
226
238
227
239
<sectionid="normative">
228
240
<h3>
@@ -232,61 +244,69 @@ <h3>
232
244
The Working Group will deliver the following W3C normative specifications:
Associated <ahref="https://lists.w3.org/Archives/Member/member-cfe/2019Dec/0003.html">Call for Exclusion</a> 12 December 2019, ended on 10 February 2020<br>
257
-
Produced under Working Group Charter: <ahref="https://www.w3.org/2018/03/jsonld-wg-charter.html">https://www.w3.org/2018/03/jsonld-wg-charter.html</a>
258
-
</dd>
259
-
</dl>
260
-
<p>
261
-
The Working Group will also deliver the following W3C normative specifications:
262
-
</p>
263
-
<dl>
264
-
<dt><strong>CBOR-LD 1.0</strong></dt>
265
-
<dd>
266
-
<p>CBOR is a compact binary data serialization and messaging format. This specification defines CBOR-LD, a CBOR-based format to serialize Linked Data. The encoding is designed to leverage the existing JSON-LD ecosystem, to provide a compact serialization format for those seeking efficient encoding schemes for Linked Data.</p>
<iclass=todo>Final Community Group Report</i> (<iclass=todo>2024-xx-xx</i>), adopted from the JSON for Linking Data Community Group
272
-
<li><ahref="https://w3c.github.io/json-ld-cbor/">JSON-LD 1.1. in CBOR</a>,
273
-
Editor's Draft (2022-12-06), adopted from previous JSON-LD Working Group
274
-
</ul>
275
-
</div>
276
-
<p><b>Expected completion:</b> CR in Q4 2026</p>
277
-
</dd>
278
-
<dt><strong>YAML-LD 1.0</strong></dt>
279
-
<dd>
280
-
<p>This document defines YAML-LD, a set of conventions built on top of YAML, which outlines how to serialize Linked Data as YAML based on JSON-LD syntax, semantics, and APIs.</p>
<p><b>Adopted Draft:</b> JSON-LD 1.1, <ahref="https://www.w3.org/TR/2020/REC-json-ld11-20200716/">https://www.w3.org/TR/2020/REC-json-ld11-20200716/</a>, 16 July 2020.</p>
256
+
257
+
<p><b>Exclusion Draft:</b> JSON-LD 1,1, <ahref="https://www.w3.org/TR/2020/CR-json-ld11-20200305/">https://www.w3.org/TR/2020/CR-json-ld11-20200305/</a>, 5 March 2020. Exclusion period <b>2020-03-05</b>; Exclusion period <b>2020-05-04</b>.</p>
<dtid="json-ld-api-12" class="spec">JSON-LD 1.2 Processing Algorithms and API</dt>
263
+
<dd>
264
+
<p>This specification will define new version of JSON-LD Processing Algorithms and API, fully compatible with <ahref="https://www.w3.org/TR/rdf12-concepts">RDF 1.2</a>.</p>
265
+
266
+
<pclass="draft-status"><b>Draft state:</b><ahref="https://www.w3.org/TR/json-ld11-api/">Adopted from JSON-LD 1.1 Processing Algorithms and API Recommendation</a>.</p>
<p><b>Adopted Draft:</b> JSON-LD 1.1, <ahref="https://www.w3.org/TR/2020/REC-json-ld11-api-20200716/">https://www.w3.org/TR/2020/REC-json-ld11-api-20200716/</a>, 16 July 2020.</p>
271
+
272
+
<p><b>Exclusion Draft:</b> JSON-LD 1,1, <ahref="https://www.w3.org/TR/2020/CR-json-ld11-api-20200305/">https://www.w3.org/TR/2020/CR-json-ld11-api-20200305/</a>, 5 March 2020. Exclusion period <b>2020-03-05</b>; Exclusion period <b>2020-05-04</b>.</p>
<p><b>Adopted Draft:</b> JSON-LD 1.1, <ahref="https://www.w3.org/TR/2020/REC-json-ld11-framing-20200716/">https://www.w3.org/TR/2020/REC-json-ld11-framing-20200716/</a>, 16 July 2020.</p>
287
+
288
+
<p><b>Exclusion Draft:</b> JSON-LD 1,1, <ahref="https://www.w3.org/TR/2020/CR-json-ld11-framing-20200305/">https://www.w3.org/TR/2020/CR-json-ld11-framing-20200305/</a>, 5 March 2020. Exclusion period <b>2020-03-05</b>; Exclusion period <b>2020-05-04</b>.</p>
<p>This document defines YAML-LD, a set of conventions built on top of YAML, which outlines how to serialize Linked Data as YAML based on JSON-LD syntax, semantics, and APIs.</p>
297
+
298
+
<pclass="draft-status"><b>Draft state:</b><ahref="https://www.w3.org/community/reports/json-ld/CG-FINAL-yaml-ld-20231206/">YAML-LD</a>, Final Community Group Report (2023-12-06), adopted from the JSON for Linking Data Community Group.</p>
<p>This specification defines CBOR-LD, a CBOR-based format to serialize Linked Data. The encoding is designed to leverage the existing JSON-LD ecosystem, to provide a compact serialization format for those seeking efficient encoding schemes for Linked Data.</p>
305
+
306
+
<pclass="draft-status"><b>Draft state:</b><ahref="https://json-ld.github.io/cbor-ld-spec/">CBOR-LD</a>, Community Group Draft Report (2025-05-09), adopted from the JSON for Linking Data Community Group.</p>
<p>In order to advance to <ahref="https://www.w3.org/policies/process/#RecsPR" title="Proposed Recommendation">Proposed Recommendation</a>, each normative specification is expected to have <ahref="https://www.w3.org/policies/process/#implementation-experience">at least two independent interoperable implementations</a> of every feature defined in the specification, where interoperability can be verified by passing open test suites.</p>
373
+
<p>In order to advance beyond
374
+
<ahref="https://www.w3.org/policies/process/#RecsCR" title="Candidate Recommendation">Candidate Recommendation</a>, each normative specification is expected to have <ahref="https://www.w3.org/policies/process/#implementation-experience">at least two independent interoperable implementations</a> of every feature defined in the specification, where interoperability can be verified by passing open test suites. In order to advance beyond Candidate Recommendation, each normative specification must have an open test suite of every feature defined in the specification.</p>
375
+
354
376
<p>There should be testing plans for each specification, starting from the earliest drafts.</p>
377
+
355
378
<p>To promote interoperability, all changes made to specifications
356
379
in Candidate Recommendation
357
380
or to features that have deployed implementations
@@ -362,10 +385,13 @@ <h2>Success Criteria</h2>
362
385
363
386
<p>Each specification should contain separate sections detailing all known security and privacy implications for implementers, Web authors, and end users.</p>
364
387
365
-
<!-- Design principles -->
366
-
<p>This Working Group expects to follow the
367
-
TAG <ahref="https://www.w3.org/TR/design-principles/">Web Platform Design Principles</a>.
368
-
</p>
388
+
<!-- W3C Statements and Web Platform Design Principles -->
389
+
<p>This group is expected to be guided by the following documents:</p>
390
+
<ul>
391
+
<li><ahref="https://www.w3.org/TR/ethical-web-principles/">Ethical Web Principles</a>,</li>
The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in <ahref='#communication'>Communication</a>.
446
+
The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the <ahref="https://www.w3.org/policies/patent-policy/">W3C Patent Policy</a>.
420
447
</p>
448
+
421
449
<p>
422
-
The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the <ahref="https://www.w3.org/policies/patent-policy/">W3C Patent Policy</a>.
450
+
The Chairs should periodically look through the non-Members who have contributed to the Working Group or the JSON for Linking Data Community Group and consider whether each one should be invited to participate as an <ahref="https://www.w3.org/invited-experts/">Invited Expert</a>. If a non-Member contributor would like to participate in meetings, they are encouraged to <ahref="https://www.w3.org/groups/wg/json-ld/instructions/">apply to be an Invited Expert</a>.
423
451
</p>
452
+
424
453
<p>Participants in the group are required (by the <ahref="https://www.w3.org/policies/process/#ParticipationCriteria">W3C Process</a>) to follow the
425
454
W3C <ahref="https://www.w3.org/policies/code-of-conduct/">Code of Ethics and Professional Conduct</a>.</p>
426
455
</section>
@@ -436,7 +465,7 @@ <h2>
436
465
The meetings themselves are not open to public participation, however.
437
466
</p>
438
467
<p>
439
-
Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <ahref="">JSON-LD Working Group home page.</a>
468
+
Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <ahref="https://www.w3.org/groups/wg/json-ld">JSON-LD Working Group home page.</a>
440
469
</p>
441
470
<p>
442
471
Most JSON-LD Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.
0 commit comments