Merge pull request #420 from opengeospatial/update-doc-number-20-004r1

update doc number
opengeospatial · Jan 6, 2025 · 5365c90 · 5365c90
2 parents 94cff91 + ab5107a
commit 5365c90
Show file tree

Hide file tree

Showing 8 changed files with 8 additions and 8 deletions.
diff --git a/README.md b/README.md
@@ -4,7 +4,7 @@
 
 This GitHub repository contains the OGC API - Records for discovering geospatial information on the web. It focuses on a simple RESTful core specified as reusable [OpenAPI](http://openapis.org) components with responses in JSON and HTML.
 
-The latest Editor's Draft version of _OGC API - Records - Part 1: Core_ is found here in [HTML](https://docs.ogc.org/DRAFTS/20-004.html) or [PDF](https://docs.ogc.org/DRAFTS/20-004.pdf).
+The latest Editor's Draft version of _OGC API - Records - Part 1: Core_ is found here in [HTML](https://docs.ogc.org/DRAFTS/20-004r1.html) or [PDF](https://docs.ogc.org/DRAFTS/20-004r1.pdf).
 
 Draft(s) are built daily based on the configuration contained in the [asciidoctor.json](https://github.com/opengeospatial/ogcapi-records/blob/master/asciidoctor.json) file.
 

diff --git a/asciidoctor.json b/asciidoctor.json
@@ -1,6 +1,6 @@
 {
         "0":  {
-                "OGC_doc_number": "20-004",
+                "OGC_doc_number": "20-004r1",
                 "urn":"http://www.opengis.net/doc/is/ogcapi-records-1/1.0",
                 "title":"OGC API - Records - Part 1: Core",
                 "path":"core/standard/20-004.adoc",

diff --git a/core/openapi/ogcapi-records-1-building-blocks.yaml b/core/openapi/ogcapi-records-1-building-blocks.yaml
@@ -3,7 +3,7 @@ info:
   title: "Building Blocks specified in OGC API - Features - Part 1: Core"
   description: |-
     Common components used in the
-    [OGC standard "OGC API - Records - Part 1: Core"](https://docs.opengeospatial.org/is/20-004/20-004.html).
+    [OGC standard "OGC API - Records - Part 1: Core"](https://docs.opengeospatial.org/is/20-004r1/20-004r1.html).
 
     OGC API - Records - Part 1: Core 1.0 is an OGC Standard.
     Copyright (c) 2019 Open Geospatial Consortium.

diff --git a/core/release-notes.md b/core/release-notes.md
@@ -2,7 +2,7 @@
 
 |Status: |Published
 | --- | --- |
-|Document reference: |[OGC 20-004](https://docs.ogc.org/DRAFTS/20-004.html)
+|Document reference: |[OGC 20-004r1](https://docs.ogc.org/DRAFTS/20-004r1.html)
 |Date: |2024-12-20
 
 This version is the first release.
diff --git a/core/standard/20-004.adoc b/core/standard/20-004.adoc
@@ -26,7 +26,7 @@
 |Approval Date: <yyyy-mm-dd>
 |Publication Date: 2024-05-14
 |External identifier of this OGC(R) document: http://www.opengis.net/doc/is/ogcapi-records-1/1.0
-|Internal reference number of this OGC(R) document: 20-004
+|Internal reference number of this OGC(R) document: 20-004r1
 |Version: 1.0.0
 |Category: OGC(R) Implementation Standard
 |Editors:  Panagiotis (Peter) A. Vretanos, Tom Kralidis, Angelos Tzotsos, Charles Heazel

diff --git a/core/standard/README.md b/core/standard/README.md
@@ -9,7 +9,7 @@ This specification addresses only those parts of an API which are specific to Re
 
 The latest drafts of each standard in this repository are built daily (based on the configuration contained in the [asciidoctor.json](https://github.com/opengeospatial/ogcapi-records/blob/master/asciidoctor.json) file):
 
-* [Part 1: Core](https://docs.ogc.org/DRAFTS/20-004.html)
+* [Part 1: Core](https://docs.ogc.org/DRAFTS/20-004r1.html)
 
 To generate HTML and PDF representations of the standard yourself, asciidoctor is required.  To install:
 

diff --git a/docs/ogc-web-api-guidelines-assessment.md b/docs/ogc-web-api-guidelines-assessment.md
@@ -13,7 +13,7 @@ This document outlines the support by OGC API Records of the design principles o
   - records and catalogs are resource types that have been in use for many years
   - IANA registered media types are used, except in the OpenAPI case, where [no registered media type exists yet](https://github.com/OAI/OpenAPI-Specification/issues/110)
 - [x] Principle #4 – Construct consistent URIs
-  - the resources are structured in a [simple path structure](https://docs.ogc.org/DRAFTS/20-004.html#api-path-table) that is intuitive and at the same time extensible (both for additional parts of Records that will make use of other HTTP methods beyond GET, HEAD, OPTIONS or add resources as well as for other top-level OGC API resource types)
+  - the resources are structured in a [simple path structure](https://docs.ogc.org/DRAFTS/20-004r1.html#api-path-table) that is intuitive and at the same time extensible (both for additional parts of Records that will make use of other HTTP methods beyond GET, HEAD, OPTIONS or add resources as well as for other top-level OGC API resource types)
   - the path structure is consistent with the examples in Principle #4
 - [x] Principle #5 – Use HTTP Methods consistent with RFC 9110
   - Part 1 uses GET (and recommend support for HEAD and OPTIONS). All methods are used in conformance with the requirements and semantics specified in RFC 9110

diff --git a/extensions/OpenSearch/clause_1_scope.adoc b/extensions/OpenSearch/clause_1_scope.adoc
@@ -1,7 +1,7 @@
 == Scope
 
 This document specifies the requirements for adding an OpenSearch interface to
-a https://docs.ogc.org/DRAFTS/20-004.html#clause-searchable-catalogue[searchable OGC API - Records] implementation.
+a https://docs.ogc.org/DRAFTS/20-004r1.html#clause-searchable-catalogue[searchable OGC API - Records] implementation.
 
 The document defines requirements for retrieving an https://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/os/part4-opensearch/searchRetrieve-v1.0-os-part4-opensearch.html#_Toc313525766[OpenSearch description document] from the service.