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.
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>
253
-
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>
254
-
</dd>
255
-
</dl>
256
-
<p>
257
-
The Working Group will also deliver the following W3C normative specifications:
258
-
</p>
259
-
<dl>
260
-
<dt><strong>CBOR-LD 1.0</strong></dt>
261
-
<dd>
262
-
<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
268
-
<li><ahref="https://w3c.github.io/json-ld-cbor/">JSON-LD 1.1. in CBOR</a>,
269
-
Editor's Draft (2022-12-06), adopted from previous JSON-LD Working Group
270
-
</ul>
271
-
</div>
272
-
<p><b>Expected completion:</b> CR in Q4 2026</p>
273
-
</dd>
274
-
<dt><strong>YAML-LD 1.0</strong></dt>
275
-
<dd>
276
-
<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>
240
+
241
+
<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>
247
+
<dd>
248
+
<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>
249
+
250
+
<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>
285
255
256
+
<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>
271
+
272
+
<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>
281
+
282
+
<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>
289
+
290
+
<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>
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 <iclass="todo">[update this link] <ahref="https://www.w3.org/groups/wg/TODO/instructions/">apply to be an Invited Expert</a></i>.
434
+
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>.
427
435
</p>
428
436
429
437
<p>Participants in the group are required (by the <ahref="https://www.w3.org/policies/process/#ParticipationCriteria">W3C Process</a>) to follow the
0 commit comments