Skip to content

Rework as the Linked Data Formats WG #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 2 commits into
base: json-ld-wg
Choose a base branch
from
+28 −11
Draft

Rework as the Linked Data Formats WG #10

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ca9cf57
Rename the WG to Linked Data Formats.
BigBlueHat Jul 14, 2025
83c1d62
Rewrite the background section.
BigBlueHat Jul 14, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 28 additions & 11 deletions 2024/json-ld-wg/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
<head>
<meta charset="utf-8">

<title>JSON-LD Working Group Charter</title>
<title>Linked Data Formats Working Group Charter</title>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed during our last meeting, I believe that "JSON-LD" should still appear in the name of the WG. @BigBlueHat proposed "JSON-LD data formats" (or simply "JSON-LD formats", as D alteady means "data" 😉 )

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Upon first reading the name "Linked Data Formats", I thought the goal was also to bring other formats such as Turtle, RDF/XML, and so on under the scope of this WG. But this doesn't seem to be the cause. I would suspect similar confusion to be raised outside of the WG.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What brings the these formats under the same roof is the fact that these formats add an rdf (a.k.a. linked data) layer on top of an existing and widespread data syntax. On could argue that this is the case of rdf/xml, and that would be true, except that people hardly care about that format anyway.

I am sure someone will find a nice term for that.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What brings the these formats under the same roof is the fact that these formats add an rdf (a.k.a. linked data) layer on top of an existing and widespread data syntax.

Perhaps something along the direction of Embedded Linked Data Formats?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We discussed this on the last call. We need to find a good name, but basically it’s appropriate for polyglot formats that can be reduced to some variation of our internal representation. This explicitly does not include other established RDF formats.

“Embedded” is a loaded term, and also describes how scripts may be embedded in HTML using the script element.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

formats that can be reduced to some variation of our internal representation

I believe this is the core criteria, and that's one of my argument for keeping JSON-LD in the name (in addition to showing continuity and avoiding confusion).


<link rel="stylesheet" href="https://www.w3.org/2005/10/w3cdoc.css" type="text/css" media="screen">
<link rel="stylesheet" type="text/css" href="https://www.w3.org/OldGuide/pubrules-style.css">
Expand Down Expand Up @@ -72,12 +72,12 @@


<main>
<h1 id="title"><i class=todo>DRAFT</i> JSON-LD Working Group Charter</h1>
<h1 id="title"><i class=todo>DRAFT</i> Linked Data Formats Working Group Charter</h1>

<p class="mission">The <strong>mission</strong> of the <a href="https://www.w3.org/groups/wg/json-ld">JSON-LD Working Group</a> is to maintain and extend the <a href="https://www.w3.org/groups/wg/json-ld/publications">family of JSON-LD 1.1 Recommendations</a> and related Working Group Notes.</p>
<p class="mission">The <strong>mission</strong> of the <a href="https://www.w3.org/groups/wg/json-ld">Linked Data Formats Working Group</a> is to extend the <a href="https://www.w3.org/groups/wg/json-ld/publications">family of JSON-LD Recommendations</a> to provide Linked Data expressions in a range of formats and sizes.</p>

<div class="noprint">
<p class="join"><a href="https://www.w3.org/groups/wg/json-ld/join">Join the JSON-LD Working Group.</a></p>
<p class="join"><a href="https://www.w3.org/groups/wg/json-ld/join">Join the Linked Data Formats Working Group.</a></p>
</div>

<p class=todo style="padding: 0.5ex; border: 1px solid green">
Expand Down Expand Up @@ -144,9 +144,26 @@ <h1 id="title"><i class=todo>DRAFT</i> JSON-LD Working Group Charter</h1>
<div id="background" class="background">
<h2>Motivation and Background</h2>
<p>
JSON-LD (JavaScript Object Notation for Linked Data) is a method of encoding linked data using JSON.
The encoding is used used mostly for search engine optimization activities but also for applications such as
biomedical informatics, and representing provenance information.
JSON-LD (JavaScript Object Notation for Linked Data) is a widely used method of encoding Linked Data using JSON.
Use of JSON-LD has grown and expanded over the last decade (since it's first publication as a
<a href="https://www.w3.org/TR/json-ld-api1/">W3C Recommendation in 2014</a>).
JSON-LD remains a popular choice for ecoding <abbr title="Seach Engine Optimization">SEO</abbr>-focused
structured data in Web pages. JSON-LD has also become a foundational format for social media (ActivityStreams),
Internet of Things data (Web of Things Description), Verifiable Credentials, and Software Bill of Materials (SPDX).
</p>
<p>This growth in the applied use of JSON-LD has resulted in community interest in additional expressions of
JSON-LD's underlying Linked Data expression into other formats. YAML-LD has been created by the
Comment on lines +154 to +155
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"expression" used twice, making the sentence cumbersome.

Suggested change
<p>This growth in the applied use of JSON-LD has resulted in community interest in additional expressions of
JSON-LD's underlying Linked Data expression into other formats. YAML-LD has been created by the
<p>This growth in the applied use of JSON-LD has resulted in community interest in additional expressions of
JSON-LD's underlying Linked Data structure into other formats. YAML-LD has been created by the

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe just keep the group title "JSON-LD Working Group" and then expand in the group description, and/or in a subtitle, that it is for JSON and related formats.

<a href="https://www.w3.org/community/json-ld/">JSON for Linking Data Community Group</a> for easing human
authoring and providing a clearer path for using Linked Data applied to popular YAML-based documents such as
infrastructure as code, static site front matter, and API documentation formats. Additionally, a need has
arised in the Verifiable Credentials space for providing a more compressed expression of JSON-LD, and work on
CBOR-LD was begun in the JSON-LD CG.
</p>
<p>
The hope of this new more inclusively focused Linked Data Formats WG is to meet the demand of the broader
JSON-LD community by strengthening the foundational JSON-LD specifications and aligning it with the latest
RDF 1.2 specifications, growing the family of Linked Data formats which orbit around the JSON-LD data model,
and specify additional processing and context retrieval methods for greater clarity and stability.
</p>
</div>

Expand All @@ -164,7 +181,7 @@ <h2>Scope</h2>
It will also develop new Recommendation Track deliverables, based on work incubated by the <a href="https://www.w3.org/community/json-ld/">JSON for Linking Data Community Group</a>,
specifying the use of JSON-LD algorithms with similar formats (YAML, CBOR, and more).
</p>
<p>The Working group is expected to coordinate with the <a href='https://www.w3.org/community/json-ld/'>JSON for Linking Data Community Group</a> 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.</p>
<p>The Working group is expected to coordinate with the <a href='https://www.w3.org/community/json-ld/'>JSON for Linking Data Community Group</a> on consensus-based proposals related to content changes for the Linked Data Formats Working Group Deliverables. The Chairs of this group may choose to reject proposals that are incompatible with this Charter.</p>

<section id="section-feature-updates">
<h3 id="in-scope">In Scope</h3>
Expand Down Expand Up @@ -422,7 +439,7 @@ <h2>Coordination</h2>
<h3 id="w3c-coordination">W3C Groups</h3>
<dl>
<dt><a href='https://www.w3.org/community/json-ld/'>JSON for Linking Data Community Group</a></dt>
<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>
<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 Linked Data Formats Working Group Deliverables. The Chairs of this group may choose to reject proposals that are incompatible with this Charter.</dd>

<dt><a href="https://www.w3.org/groups/wg/dc">Verifiable Credentials Working Group</a></dt>
<dd>Coordination on named graph indexing and other concerns regarding support for normalization and digital signatures.</dd>
Expand Down Expand Up @@ -483,10 +500,10 @@ <h2>
The meetings themselves are not open to public participation, however.
</p>
<p>
Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <a href="">JSON-LD Working Group home page.</a>
Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <a href="">Linked Data Formats Working Group home page.</a>
</p>
<p>
Most JSON-LD Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.
Most Linked Data Formats Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.
</p>
<p>
This group primarily conducts its technical work on <a id="public-github" href="https://www.w3.org/groups/wg/json-ld/tools">GitHub issues</a>.
Expand Down