Merge pull request #1597 from w3c/EditorialChancesForMovingToPR

Editorial chances to pushish pr
w3c · May 22, 2024 · 079a07e · 079a07e
2 parents 8b4dbe4 + 91d0f7f
commit 079a07e
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 18 deletions.
diff --git a/dcat/config.js b/dcat/config.js
@@ -2,12 +2,12 @@ var respecConfig = {
     doJsonLd: true,
 //	preProcess: [dfn_index],
 //    subtitle: "Version 2",
-    specStatus: "ED",
+  specStatus: "ED",
     errata: "https://w3c.github.io/dxwg/errata/",
 //    specStatus: "ED",
-//    specStatus: "CR",
-//    crEnd: "2023-11-28",
-//    implementationReportURI: "https://w3c.github.io/dxwg/dcat3-implementation-report/",
+// specStatus: "CR",
+    crEnd: "2024-02-15",
+    implementationReportURI: "https://w3c.github.io/dxwg/dcat3-implementation-report/",
     shortName: "vocab-dcat-3",
     prevRecShortname: "vocab-dcat-2",
     canonicalURI: "TR",

diff --git a/dcat/index.html b/dcat/index.html
@@ -63,23 +63,9 @@
     <p>
         This new version of the vocabulary updates and expands the original but preserves backward compatibility. A full list of the significant changes (with links to the relevant GitHub issues) is described in <a href="#changes"></a>.
     </p>
-    <p>
-        The exit criteria for <abbr title="Candidate Recommendation">CR</abbr> focused on v3 new features that replicate features that were included in application profiles of v2 as a way of remedying missing and necessary elements. <!--The exit criteria also included recent commitments by organisations such as EC Joinup to <a href='https://joinup.ec.europa.eu/solution/abr-specification-registry-registries/document/specification-registry-registries-version-meeting-september'>adopt the DCAT v2 model</a> in their work.-->
-        Implementation will be evidenced by showing use of the new properties/classes (or terms with equivalent meaning) in implementations of catalogs.
-    </p>
     <p>
         <a href="https://github.com/w3c/dxwg/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3Adcat+">Issues, requirements, and features</a> 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 <a href="https://github.com/w3c/dxwg/milestone/31">DCAT Future Priority Work</a>.
     </p>
-    <p>
-    The following terms are at-risk, and may be dropped during the CR period:
-    </p>    
-  <ul>
-    <li> <a href="#Property:resource_first"></a></li>
-    <li> <a href="#Property:resource_last"></a> </li>
-  </ul>
-    <p>
-        “At-risk” is a W3C <a href="https://www.w3.org/2021/Process-20211102/#at-risk">Process term-of-art</a>, 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.
-    </p>
 
 
     <h3 id="dcat_history">DCAT history</h3>