| CARVIEW |
Select Language
HTTP/2 200
server: GitHub.com
content-type: text/html; charset=utf-8
last-modified: Thu, 05 Jun 2025 14:14:46 GMT
access-control-allow-origin: *
etag: W/"6841a656-12d6"
expires: Tue, 15 Jul 2025 08:30:51 GMT
cache-control: max-age=600
content-encoding: gzip
x-proxy-cache: MISS
x-github-request-id: 7357:CDF64:41509:4CA1A:68760F63
accept-ranges: bytes
age: 0
date: Tue, 15 Jul 2025 08:20:51 GMT
via: 1.1 varnish
x-served-by: cache-bom4744-BOM
x-cache: MISS
x-cache-hits: 0
x-timer: S1752567651.270663,VS0,VE236
vary: Accept-Encoding
x-fastly-request-id: beb93a28a4a722fb0692c7a7543c24aa148a7f21
content-length: 1997
Open Errata for the JSON-LD Specification Published by the JSON-LD Working Group
Open Errata for the JSON-LD Specification
- Latest errata update:
- Number of recorded errata:
- Link to all errata:
How to Submit an Erratum?
Errata are introduced and stored in the issue list of the document‘s GitHub repository. The workflow to add a new erratum is as follows:
- An issue is raised for a possible erratum. The label of the issue SHOULD be set to “
ErratumRaised”. It is o.k. for an erratum to have several labels. - Issues labeled as “
Editorial” are displayed separately, to make it easier to differentiate editorial errata from substantial ones. - The community discusses the issue. If it is accepted as a genuine erratum, the label “
Errata” is added to the entry and the “ErratumRaised” label should be removed. Additionally, a new comment on the issue MAY be added, beginning with the word "Summary:" (if such a summary is useful based on the discussion). - All issues, labeled by “
Errata”, are displayed in this report, whether they are opened or closed. Their status is added to the report on the individual errata. - If the community rejects the issue as an erratum, the issue should be closed.
- Each errata may be labeled as “
Editorial”; editorial errata are listed separately from the substantial ones. - ALL substantive errata are generally expected to have corresponding test(s), either in the form of new tests or modifications to existing tests, or must include the rationale for why test updates are not required for the erratum.
If you have problems following this process, but you want nevertheless to report an error, you can also contact the staff contact of the Working Group, Ivan Herman.
Open Errata on the “JSON-LD 1.1” Recommendation
- Latest Published Version:
- https://www.w3.org/TR/json-ld11/
- Editor’s draft:
- https://w3c.github.io/json-ld-syntax/
- Latest Publication Date:
- 16 July, 2020