Skip to content
This repository was archived by the owner on Sep 23, 2025. It is now read-only.

Commit 9a58336

Browse files
committed
Fix various small things.
Found (as ever) by @TallTed: #10 (review)
1 parent 2ea218c commit 9a58336

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

2024/json-ld-wg/index.html

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -152,23 +152,23 @@ <h2>Motivation and Background</h2>
152152
JSON-LD (JavaScript Object Notation for Linked Data) is a widely used method of encoding Linked Data using JSON.
153153
Use of JSON-LD has grown and expanded over the last decade (since it's first publication as a
154154
<a href="https://www.w3.org/TR/json-ld-api1/">W3C Recommendation in 2014</a>).
155-
JSON-LD remains a popular choice for ecoding <abbr title="Seach Engine Optimization">SEO</abbr>-focused
155+
JSON-LD remains a popular choice for encoding <abbr title="Seach Engine Optimization">SEO</abbr>-focused
156156
structured data in Web pages. JSON-LD has also become a foundational format for social media (ActivityStreams),
157157
Internet of Things data (Web of Things Description), Verifiable Credentials, and Software Bill of Materials (SPDX).
158158
</p>
159159
<p>This growth in the applied use of JSON-LD has resulted in community interest in additional expressions of
160-
JSON-LD's underlying Linked Data structure into other formats. YAML-LD has been created by the
160+
JSON-LD's underlying Linked Data structure in other formats. YAML-LD has been created by the
161161
<a href="https://www.w3.org/community/json-ld/">JSON for Linking Data Community Group</a> for easing human
162162
authoring and providing a clearer path for using Linked Data applied to popular YAML-based documents such as
163-
infrastructure as code, static site front matter, and API documentation formats. Additionally, a need has
164-
arised in the Verifiable Credentials space for providing a more compressed expression of JSON-LD, and work on
163+
infrastructure as code, static site front matter, and API documentation formats. Additionally, a need arose
164+
in the Verifiable Credentials space for providing a more compressed expression of JSON-LD, and work on
165165
CBOR-LD was begun in the JSON-LD CG.
166166
</p>
167167
<p>
168-
The hope of this new more inclusively focused JSON-LD WG is to meet the demand of the broader
169-
JSON-LD community by strengthening the foundational JSON-LD specifications and aligning it with the latest
168+
The goal of this new more inclusively focused JSON-LD WG is to meet the demand of the broader
169+
JSON-LD community by strengthening the foundational JSON-LD specifications and aligning them with the latest
170170
RDF 1.2 specifications, growing the family of JSON-LD related formats which orbit around the JSON-LD
171-
processing model, and specifing improved context retrieval methods for greater clarity and stability.
171+
processing model, and specifying improved context retrieval methods for greater clarity and stability.
172172
</p>
173173
</div>
174174

@@ -179,7 +179,8 @@ <h2>Scope</h2>
179179
with the features introduced by <a href="https://www.w3.org/TR/rdf12-concepts">RDF 1.2</a>
180180
in addition to open Errata and requested features
181181
as noted on the groups <a href="https://github.com/orgs/w3c/projects/84">Project Management Page</a>.
182-
These specifications together provide a JSON format for Linked Data to interoperate in a method which is familiar to and usable by software engineers.
182+
Together, these specifications provide a JSON format for Linked Data,
183+
enabling interoperation in a way which is familiar to and usable by software engineers.
183184
<!-- 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. -->
184185
</p>
185186
<p>

0 commit comments

Comments
 (0)