JSON-LD Working Group Charter

The mission of the JSON-LD Working Group is to maintain the family of JSON-LD 1.1 Recommendations and related Working Group Notes.

Join the JSON-LD Working Group

Start date 2020-08-12
End date 2023-01-31
Chairs Benjamin Young (Wiley)
Team Contacts Philippe le Hégaret (0.01 FTE)
Meeting Schedule Teleconferences: On an as-needed basis, at least every quarter.
Face-to-face: None expected.


The Working Group will maintain the JSON-LD specifications (i.e., JSON-LD 1.1, JSON-LD 1.1 API, JSON-LD 1.1 Framing) that together provide a JSON format for Linked Open Data to interoperate at web-scale, in a method which is familiar to and usable by web-focused software engineers.

Out of Scope

The following features are out of scope, and will not be addressed by this Working Group.

  • RDF Dataset Normalization.
  • Linked Data Signatures.


Normative Specifications

The Working Group will maintain the following W3C normative specifications:

Latest publication: 07 May 2020
Reference Draft: https://www.w3.org/TR/2020/REC-json-ld11-20200716/
Associated Call for Exclusion 5 March 2020, ended on 4 May 2020
Produced under Working Group Charter: https://www.w3.org/2018/03/jsonld-wg-charter.html
JSON-LD 1.1 Processing Algorithms and API
Latest publication: 07 May 2020
Reference Draft: https://www.w3.org/TR/2020/REC-json-ld11-api-20200716/
Associated Call for Exclusion 5 March 2020, ended on 4 May 2020
Produced under Working Group Charter: https://www.w3.org/2018/03/jsonld-wg-charter.html
JSON-LD 1.1 Framing
Latest publication: 07 May 2020
Reference Draft: https://www.w3.org/TR/2020/REC-json-ld11-framing-20200716/
Associated Call for Exclusion 12 December 2019, ended on 10 February 2020
Produced under Working Group Charter: https://www.w3.org/2018/03/jsonld-wg-charter.html

Other Deliverables

Other non-normative documents may be created and/or maintained such as:

  • Application profile of JSON-LD to enable efficient streaming parsers.
  • Test suites and implementation reports for the specifications.
  • JSON-LD 1.1 specified in other serializations like YAML or CBOR.
  • Best practices for use and implementation of JSON-LD 1.1.

Success Criteria

In order to update the Recommendation, each substantive change is expected to have at least two independent implementations.

Each substantive change should contain a section detailing all known security and privacy implications for implementers, Web authors, and end users.

To promote interoperability, all normative changes made to specifications must have tests.


This group is expected to coordinate with the JSON for Linking Data 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.

For all substantive change, this Working Group will seek horizontal review for accessibility, internationalization, performance, privacy, and security with the relevant Working and Interest Groups, and with the TAG. Invitation for review must be issued during each major standards-track document transition. The Working Group is encouraged to engage collaboratively with the horizontal review groups throughout development of each specification. The Working Group is advised to seek a review at least 3 months before first entering CR and is encouraged to proactively notify the horizontal review groups when major changes occur in a specification following a review.

Additional technical coordination with the following Groups will be made, per the W3C Process Document:

W3C Groups

Verifiable Credentials Working Group
Coordination on named graph indexing and other concerns regarding support for normalization and digital signatures.
Credentials Community Group
Coordination on various concerns regarding the usage of JSON-LD in Verifiable Credentials.
Schema.org Community Group
The Schema.org CG will be regularly solicited for reviews and comments throughout the advancement of the JSON-LD 1.1 Recommendation.
Decentralized Identifiers Working Group
Coordination on various concerns regarding the JSON-LD encoding of DID Documents.
Web of Things Working Group
Coordination of various topics concerning the use of JSON-LD by the WoT Thing Description.
RDF JavaScript Libraries CG
Coordination on various opportunities for JSON-LD support in RDF.js related libraries and community projects.
Coordination on various aspects of future RDF core specifications.


To be successful, this Working Group is expected to have 6 or more active participants for its duration, including representatives from the key implementors of this specification, and active Editors and Test Leads for each specification. The Chairs, specification Editors, and Test Leads are expected to contribute half of a working day per week towards the Working Group. There is no minimum requirement for other Participants.

The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in Communication.

The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the W3C Patent Policy.

Participants in the group are required (by the W3C Process) to follow the W3C Code of Ethics and Professional Conduct.


Technical discussions for this Working Group are conducted in public: the meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed on a public repository and may permit direct public contribution requests. The meetings themselves are not open to public participation, however.

Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the JSON-LD Working Group home page.

Most JSON-LD Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.

This group primarily conducts its technical work on GitHub issues. The public is invited to review, discuss and contribute to this work.

The group may use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a participant requests such a discussion.

Decision Policy

This group will seek to make decisions through consensus and due process, per the W3C Process Document (section 3.3). Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required.

However, if a decision is necessary for timely progress and consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote and record a decision along with any objections.

To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional. A call for consensus (CfC) will be issued for all resolutions (for example, via email and/or web-based survey), with a response period from 5 to 10 working days, depending on the chair's evaluation of the group consensus on the issue. If no objections are raised on the mailing list by the end of the response period, the resolution will be considered to have consensus as a resolution of the Working Group.

All decisions made by the group should be considered resolved unless and until new information becomes available or unless reopened at the discretion of the Chairs or the Director.

This charter is written in accordance with the W3C Process Document (Section 3.4, Votes) and includes no voting procedures beyond what the Process Document requires.

Patent Policy

This Working Group operates under the W3C Patent Policy (Version of 5 February 2004 updated 1 August 2017). To promote the widest adoption of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis. For more information about disclosure obligations for this group, please see the W3C Patent Policy Implementation.


This Working Group will use the W3C Software and Document license for all its deliverables.

About this Charter

This charter has been created according to section 5.2 of the Process Document. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.

Charter History

The following table lists details of all changes from the initial charter, per the W3C Process Document (section 5.2.3):

Charter Period Start Date End Date Changes
Initial Charter 15 June 2018 15 June 2020 none
Maintenance WG Charter 12 August 2020 31 August 2022 New Charter approved on 12 August 2020
Change of staff contact 23 June 2021 31 August 2022
Charter Extension 31 August 2022 30 November 2022
Charter Extension 01 December 2022 31 January 2023