| CARVIEW |
Select Language
HTTP/2 200
server: GitHub.com
content-type: text/html; charset=utf-8
last-modified: Mon, 07 Oct 2024 15:57:33 GMT
access-control-allow-origin: *
etag: W/"670404ed-19e9"
expires: Wed, 08 Oct 2025 13:18:12 GMT
cache-control: max-age=600
content-encoding: gzip
x-proxy-cache: MISS
x-github-request-id: 7118:17D88D:6205F:6E515:68E6623B
accept-ranges: bytes
age: 0
date: Wed, 08 Oct 2025 13:08:12 GMT
via: 1.1 varnish
x-served-by: cache-bom-vanm7210072-BOM
x-cache: MISS
x-cache-hits: 0
x-timer: S1759928892.472574,VS0,VE296
vary: Accept-Encoding
x-fastly-request-id: 4a8939a3c45b9e1be07b3ebdd00543adb02e8e9a
content-length: 2415
Open Errata for the Dataset Exchange Working Group
Open Errata for the Dataset Exchange Working Group
- 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 group‘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 SHOULD also include the label corresponding to the document on which the erratum is raised, i.e., “dcat”. (Please, consult the list of available labels.) It is o.k. for an erratum to have several labels. In some, exceptional, cases, i.e., when the erratum is very general, it is also acceptable not to have a reference to a document. - 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). - If the community rejects the issue as an erratum, the issue should be closed.
- Each errata may be labelled as “
Editorial”; editorial errata are listed separately from the substantial ones.
This report contains a reference to all open issues with the label Errata, displayed in the sections below. Each section collects the issues for a specific document, with a separate section for the issues not assigned to any.
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, Dave Raggett.
Open Errata on the “Data Catalog Vocabulary (DCAT) - Version 2” Recommendation
- Latest Published Version:
- https://www.w3.org/TR/vocab-dcat-2
- Editor’s draft:
- https://w3c.github.io/dxwg/dcat
- Latest Publication Date:
- 4 February, 2020