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.
Copy file name to clipboardExpand all lines: 2024/json-ld-wg/index.html
+36-36Lines changed: 36 additions & 36 deletions
Original file line number
Diff line number
Diff line change
@@ -76,7 +76,7 @@ <h1 id="title"><i class=todo>DRAFT</i> JSON-LD Working Group Charter</h1>
76
76
<!-- replace DRAFT with PROPOSED when the AC review starts -->
77
77
<!-- delete PROPOSED after AC review completed -->
78
78
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>
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 Recommendations</a> and related Working Group Notes.</p>
80
80
81
81
<divclass="noprint">
82
82
<pclass="join"><ahref="https://www.w3.org/groups/wg/json-ld/join">Join the JSON-LD Working Group.</a></p>
@@ -97,7 +97,7 @@ <h1 id="title"><i class=todo>DRAFT</i> JSON-LD Working Group Charter</h1>
97
97
Charter Status
98
98
</th>
99
99
<td>
100
-
See the <ahref="https://www.w3.org/groups/wg/json-ld/charters">group status page</A> and <ahref="#history">detailed change history</a>.
100
+
See the <ahref="https://www.w3.org/groups/wg/json-ld/charters">group status page</a> and <ahref="#history">detailed change history</a>.
101
101
</td>
102
102
</tr>
103
103
<trid="Duration">
@@ -153,14 +153,14 @@ <h2>Motivation and Background</h2>
153
153
Use of JSON-LD has grown and expanded over the last decade (since it's first publication as a
154
154
<ahref="https://www.w3.org/TR/json-ld-api1/">W3C Recommendation in 2014</a>).
155
155
JSON-LD remains a popular choice for encoding <abbrtitle="Seach Engine Optimization">SEO</abbr>-focused
156
-
structured data in Web pages. JSON-LD has also become a foundational format for social media
156
+
structured data in Web pages using <ahref="https://schema.org">schema.org</a>. JSON-LD has also become a foundational format for social media
<p>This growth in the applied use of JSON-LD has resulted in community interest in additional expressions of
163
+
<p>This growth in the applied use of JSON-LD has led to a community interest in additional expressions of
164
164
JSON-LD's underlying Linked Data structure in other formats. YAML-LD has been created by the
165
165
<ahref="https://www.w3.org/community/json-ld/">JSON for Linking Data Community Group</a> for easing human
166
166
authoring and providing a clearer path for using Linked Data applied to popular YAML-based documents such as
@@ -179,36 +179,42 @@ <h2>Motivation and Background</h2>
179
179
</p>
180
180
181
181
<p>
182
-
The goal of this new more inclusively focused JSON-LD WG is to meet the demand of the broader
182
+
The goal of this new, more inclusively focused JSON-LD WG is to meet the demand of the broader
183
183
JSON-LD community by strengthening the foundational JSON-LD specifications, growing the family
184
184
of JSON-LD related formats which orbit around the JSON-LD processing model, and specifying improved
185
185
context retrieval methods for greater clarity and stability.
186
186
</p>
187
+
187
188
</div>
188
189
189
190
<sectionid="scope" class="scope">
190
191
<h2>Scope</h2>
191
192
<p>
192
-
The Working Group will evolve the recommendations defining the JSON-LD specifications (i.e., <ahref="https://www.w3.org/TR/json-ld11/">JSON-LD 1.1</a>, <ahref="https://www.w3.org/TR/json-ld11-api/">JSON-LD 1.1 API</a>, <ahref="https://www.w3.org/TR/json-ld11-framing/">JSON-LD 1.1 Framing</a>) by handling Errata and by adding requested features as recorded on the
193
-
group's <ahref="https://github.com/orgs/w3c/projects/84">Project Management Page</a>. In order to handle these,
194
-
the Working Group will issue new versions of these recommendations, possibly with new features,
195
-
in order to render future usage and evolutions easier. In particular, the Working Group will handle two important
196
-
security related issues:
193
+
The Working Group will evolve the recommendations defining the JSON-LD specifications
<ahref="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
198
+
<ahref="https://github.com/orgs/w3c/projects/84">Project Management Page</a>. In order to handle these,
199
+
the Working Group will issue new versions of these recommendations, with possibly with new features,
200
+
in order to render future usage and evolutions easier. In particular, the Working Group will handle
201
+
two important security related problems:
197
202
</p>
198
203
199
204
200
205
<ol>
201
206
<li>[Placeholder: safe mode]</li>
202
207
<li>[Placeholder: context file hash, and related stuff]</li>
203
208
</ol>
204
-
<!--
205
-
with the features introduced by <a href="https://www.w3.org/TR/rdf12-concepts">RDF 1.2</a>
206
-
in addition to open Errata and requested features
207
-
as noted on the groups <a href="https://github.com/orgs/w3c/projects/84">Project Management Page</a>.
208
-
Together, these specifications provide a JSON format for Linked Data,
209
-
enabling interoperation in a way which is familiar to and usable by software engineers.
210
-
-->
211
-
<!-- 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. -->
209
+
210
+
<!-- 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. -->
211
+
212
+
<p>
213
+
The development of the 1.2 versions of the JSON-LD specification will follow the principle of
214
+
backward compatibility. This means that any valid JSON-LD 1.1 document will remain valid for
215
+
JSON-LD 1.2, and the RDF graphs generated by the 1.1 and 1.2 versions of the JSON-LD API
216
+
specifications, respectively, will be <ahref="https://www.w3.org/TR/rdf11-concepts/#graph-isomorphism">isomorphic</a>.
217
+
</p>
212
218
213
219
<p>
214
220
The Working Group will also develop new Recommendation Track deliverables, based on work incubated by the <ahref="https://www.w3.org/community/json-ld/">JSON for Linking Data Community Group</a>,
@@ -220,23 +226,16 @@ <h2>Scope</h2>
220
226
</p>
221
227
222
228
<p>
223
-
Finally, the Working Group will start working on the introduction of the new <ahref="https://www.w3.org/TR/rdf12-concepts">RDF 1.2</a>
224
-
concepts (primarily triple terms), into the JSON-LD syntax, API, and Framing. The final goal is to have, eventually, an updated version of JSON-LD fully compatible with the upcoming RDF 1.2 version but also with the concepts introduced in
225
-
<ahref="https://www.w3.org/TR/rdf12-turtle/">RDF 1.2 Turtle</a> (e.g., annotation syntax). This will be done in a strong
226
-
cooperation with the <ahref="https://www.w3.org/groups/wg/rdf-star">RDF & SPARQL Working Group</a>.
229
+
Finally, the Working Group will start working on the introduction of the new
0 commit comments