From 9d1039a5ed65592927b6c428a66b1232d0b002bc Mon Sep 17 00:00:00 2001 From: RiccardoAlbertoni Date: Tue, 21 Mar 2023 14:48:23 +0100 Subject: [PATCH 1/4] added commenters listed in the issues --- dcat/index.html | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/dcat/index.html b/dcat/index.html index 9525464e..477d8c1a 100644 --- a/dcat/index.html +++ b/dcat/index.html @@ -6023,15 +6023,18 @@

Acknowledgments

Claus Stadler, Cristiano Longo, + Christophe Dzikowski, Dimitris Zeginis, Dominik Schneider, + Emidio Stani, Ivo Velitchkov, Jakob Voß, Jakub Klímek, + Jan Voskuil, Jim J. Yang, Joep Meindertsma, @@ -6042,7 +6045,9 @@

Acknowledgments

Ludger A. Rinsche, Marielle Adam, - Mathias Bonduel, + Martial Honsberger, + Mathias Bonduel, + Mathias Richter, Matthias Palmér, @@ -6064,13 +6069,16 @@

Acknowledgments

Simson L. Garfinkel, Siri Jodha S. Khalsa, + Stefan Ollinger, Stephen Richard, Stian Soiland-Reyes, Stig B. Dørmænen, Susheel Varma, Sidney Cox, + Thomas Francart, + Vittorio Meloni, Wouter Beek, Yves Coene. From 3d218e0041824943b7a7477b11a9967446c7f000 Mon Sep 17 00:00:00 2001 From: RiccardoAlbertoni Date: Tue, 28 Mar 2023 18:03:12 +0200 Subject: [PATCH 2/4] Adding paragraph with Terms at Risk --- dcat/index.html | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/dcat/index.html b/dcat/index.html index 9525464e..601e6ac7 100644 --- a/dcat/index.html +++ b/dcat/index.html @@ -70,6 +70,18 @@

Issues, requirements, and features that have been considered and discussed by the Data eXchange Working Group but have not been addressed due to lack of maturity or consensus are collected in GitHub. Those believed to be a priority for a future release are in the milestone DCAT Future Priority Work.

+

+ The following terms are at-risk, and may be dropped during the CR period: +

+ +

+ “At-risk” is a W3C Process term-of-art, and does not necessarily imply that the feature is in danger of being dropped or delayed. It means that the WG believes the feature may have difficulty being interoperably implemented in a timely manner, and marking it as such allows the WG to drop the feature if necessary when transitioning to the Proposed Rec stage, without having to publish a new Candidate Rec without the feature first. +

+ +

DCAT history

The original DCAT vocabulary was developed and hosted at the Digital Enterprise Research Institute (DERI), then refined by the eGov Interest Group, and finally standardized in 2014 [[?VOCAB-DCAT-1]] by the Government Linked Data (GLD) Working Group.

A second recommended revision of DCAT, DCAT 2 [[?VOCAB-DCAT-2]], was developed by the Dataset Exchange Working Group in response to a new set of Use Cases and Requirements [[?DCAT-UCR]] gathered from peoples' experience with the DCAT vocabulary from the time of the original version, and new applications that were not considered in the first version.

From 986fcb9908a08478507129e695b83d8d89ac124e Mon Sep 17 00:00:00 2001 From: RiccardoAlbertoni Date: Tue, 28 Mar 2023 18:45:56 +0200 Subject: [PATCH 3/4] deleting the issue section --- dcat/index.html | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/dcat/index.html b/dcat/index.html index 601e6ac7..492663b2 100644 --- a/dcat/index.html +++ b/dcat/index.html @@ -96,10 +96,7 @@

External terms

Please send comments

The Working Group invited publishers to describe their catalogs and datasets with the revised version of DCAT described in this document and to report their implementations following the instruction to reporting DCAT revised implementations. This information and subsequent analysis is published in the implementation report. - - -
-
+
From 65e22faa144d82863ae533f00d196c03ca9d2191 Mon Sep 17 00:00:00 2001 From: Riccardo Albertoni Date: Thu, 30 Mar 2023 14:22:07 +0200 Subject: [PATCH 4/4] Update dcat/index.html Co-authored-by: Pierre-Antoine Champin --- dcat/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dcat/index.html b/dcat/index.html index 492663b2..e1017067 100644 --- a/dcat/index.html +++ b/dcat/index.html @@ -78,7 +78,7 @@

    • - “At-risk” is a W3C Process term-of-art, and does not necessarily imply that the feature is in danger of being dropped or delayed. It means that the WG believes the feature may have difficulty being interoperably implemented in a timely manner, and marking it as such allows the WG to drop the feature if necessary when transitioning to the Proposed Rec stage, without having to publish a new Candidate Rec without the feature first. + “At-risk” is a W3C Process term-of-art, and does not necessarily imply that the feature is in danger of being dropped or delayed. It means that the WG believes the feature may have difficulty being interoperably implemented in a timely manner, and marking it as such allows the WG to drop the feature if necessary when transitioning to the Proposed Rec stage, without having to publish a new Candidate Rec without the feature first.