From 2a57375be31e1fcb62ec7f28c606588f1ffdd4c4 Mon Sep 17 00:00:00 2001 From: ghobona Date: Wed, 30 Oct 2024 03:51:09 +0000 Subject: [PATCH] Updates to draft building blocks policy Fixes https://github.com/opengeospatial/NamingAuthority/issues/305 --- .../document.adoc | 12 +- .../document.html | 188 ++++++++++-------- .../relaton/cache/ietf/rfc_7946.xml | 92 --------- .../relaton/cache/ietf/version | 1 - .../relaton/cache/iso/iso_iec_10918-1.xml | 127 ------------ .../relaton/cache/iso/iso_iec_15948.xml | 111 ----------- .../relaton/cache/iso/version | 1 - .../relaton/cache/ogc/08-131r3.xml | 4 +- .../relaton/cache/ogc/09-046r6.xml | 4 +- .../relaton/cache/ogc/10-090r3.xml | 38 ---- .../relaton/cache/ogc/17-083r4.xml | 44 ---- .../relaton/cache/ogc/19-008r4.xml | 68 ------- .../relaton/cache/ogc/19-014r3.xml | 42 ---- .../relaton/cache/ogc/19-072.xml | 39 ---- .../relaton/cache/ogc/ogc_05-020r29.notfound | 2 +- .../relaton/cache/ogc/ogc_06-030r12.notfound | 2 +- .../relaton/cache/ogc/ogc_10-090r3.redirect | 1 - .../relaton/cache/ogc/ogc_17-083r4.redirect | 1 - .../relaton/cache/ogc/ogc_19-008r4.redirect | 1 - .../relaton/cache/ogc/ogc_19-014r3.redirect | 1 - .../relaton/cache/ogc/ogc_19-072.redirect | 1 - .../relaton/cache/ogc/ogc_20-024.notfound | 1 - .../relaton/cache/ogc/version | 2 +- .../sections/00-preface.adoc | 2 +- .../sections/01-scope.adoc | 2 - .../sections/04-considerations.adoc | 38 ---- .../sections/{05-roles.adoc => 04-roles.adoc} | 0 .../sections/05-considerations.adoc | 25 +++ 28 files changed, 143 insertions(+), 707 deletions(-) delete mode 100644 policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ietf/rfc_7946.xml delete mode 100644 policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ietf/version delete mode 100644 policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/iso/iso_iec_10918-1.xml delete mode 100644 policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/iso/iso_iec_15948.xml delete mode 100644 policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/iso/version delete mode 100644 policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/10-090r3.xml delete mode 100644 policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/17-083r4.xml delete mode 100644 policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/19-008r4.xml delete mode 100644 policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/19-014r3.xml delete mode 100644 policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/19-072.xml delete mode 100644 policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_10-090r3.redirect delete mode 100644 policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_17-083r4.redirect delete mode 100644 policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_19-008r4.redirect delete mode 100644 policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_19-014r3.redirect delete mode 100644 policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_19-072.redirect delete mode 100644 policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_20-024.notfound delete mode 100644 policyAndProcedures/OGCBuildingBlocksRegistration/sections/04-considerations.adoc rename policyAndProcedures/OGCBuildingBlocksRegistration/sections/{05-roles.adoc => 04-roles.adoc} (100%) create mode 100644 policyAndProcedures/OGCBuildingBlocksRegistration/sections/05-considerations.adoc diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/document.adoc b/policyAndProcedures/OGCBuildingBlocksRegistration/document.adoc index 3fdb533d..5b34e22b 100644 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/document.adoc +++ b/policyAndProcedures/OGCBuildingBlocksRegistration/document.adoc @@ -8,12 +8,12 @@ :comment: ### Internal reference number; mandatory :docnumber: 24-005 :comment: ### Date on which the standard was updated; mandatory -:received-date: 2019-03-28 +:received-date: 2024-10-30 :comment: ### Date on which the standard was approved by the issuing authority; mandatory :issued-date: 2999-05-29 :comment: ### Date on which the standard was published; mandatory -:published-date: 2029-06-03 -:copyright-year: 2019 +:published-date: 2999-06-03 +:copyright-year: 2024 :comment: ### Version number; optional. Dot-delimited, preferably with this structure . :edition: 27.0 :comment: ### External link referencing the document; optional. If not provided, a default value is created following this structure: "http://www.opengis.net/doc/{abbrevation of doctype}/{abbrev}/{version}" @@ -25,7 +25,7 @@ :comment: ### Role of the authors; optional. Supply only if corresponding author is an editor :role_2: editor :comment: ### Comma delimited keywords; mandatory -:keywords: keyword_1, keyword_2, keyword_3, etc. +:keywords: ogcdoc, OGC document, policy, naming authority, building blocks :comment: ### Metanorma flavor; mandatory :mn-document-class: ogc :comment: ### Directory name used as prefix for the location of image files; optional @@ -46,9 +46,9 @@ include::sections/02-terms-and-definitions.adoc[] include::sections/03-references.adoc[] // Add clause files as needed -include::sections/04-considerations.adoc[] +include::sections/04-roles.adoc[] -include::sections/05-roles.adoc[] +include::sections/05-considerations.adoc[] include::sections/06-processes.adoc[] diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/document.html b/policyAndProcedures/OGCBuildingBlocksRegistration/document.html index 4f257434..c016a737 100644 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/document.html +++ b/policyAndProcedures/OGCBuildingBlocksRegistration/document.html @@ -226,6 +226,46 @@ .inline-header:hover > a.anchor { visibility: visible; } +/* collapsible snippets: collapsible before hidable */ +.hidable { + max-height: 0; + overflow: hidden; + transition: max-height 0.2s ease-out; } + +.collapsible { + background-color: #777; + color: white; + cursor: pointer; + padding: 3px 0; + margin: 0; + width: 100%; + border: none; + text-align: left; + outline: none; + font-size: 15px; } + +.active, .collapsible:hover { + background-color: #555; } + +.collapsible:after { + content: '\25bc'; + color: white; + font-weight: bold; + float: right; + margin-left: 12px; + margin-right: 12px; } + +.active:after { + content: "\25b2"; } + +/* collapsible: */ +.collapsible + .hidable { + margin-top: 0; } + +.collapsible:not(.active) + .hidable { + overflow: hidden; + padding: 0; } + #standard-band { background-color: #3D9970; } @@ -1041,7 +1081,7 @@ font-size: 24px; margin-top: 1em; } -span.AdmittedLabel { +span.AdmittedLabel, span.DeprecatedLabel { color: #00335b; background-color: #CFE2F3; font-size: 70%; @@ -1071,7 +1111,7 @@ margin-left: 2em; } /* Blocks */ -.SourceTitle { +.SourceTitle, .FigureTitle { font-weight: 700; font-size: 1em; text-align: center; } @@ -1351,8 +1391,8 @@ - - + + @@ -1409,9 +1449,9 @@
- Submission Date: 2019-03-28 + Submission Date: 2024-10-30 Approval Date: 2999-05-29 - Publication Date: 2029-06-03 + Publication Date: 2999-06-03 External identifier of this OGC® document: http://www.opengis.net/doc/pol/tcpnp/27.0 Internal identifier of this OGC® document: 24-005 @@ -1469,7 +1509,7 @@

Copyright notice

-

Copyright © 2019 Open Geospatial Consortium
To obtain additional rights of use, visithttps://www.ogc.org/legal

+

Copyright © 2024 Open Geospatial Consortium
To obtain additional rights of use, visithttps://www.ogc.org/legal

Note

@@ -1498,11 +1538,11 @@

6.2.  Review by the OGC Naming Authority SubCommittee

+

6.2.  Review by the OGC Naming Authority SubCommittee

The mission of the OGC Naming Authority (OGC-NA) is to provide the means through which OGC resources such as OGC documents, namespaces and ontologies can be controlled and managed such that they can provide clear and well-defined names and definitions (OGC 09-046r6).

@@ -1734,13 +1724,13 @@

Process:

-

  1. OGC-NA Chair begins a period of review by the OGC-NA

    +

    1. OGC-NA Chair begins a period of review by the OGC-NA

      2. -

    2. OGC-NA Chair conducts a vote on registration of the building block or as a group of building blocks

      +

    3. OGC-NA Chair conducts a vote on registration of the building block or as a group of building blocks

      4. -

    4. If the vote passes, OGC Staff register the building block or group of building blocks in the register.

      +

    5. If the vote passes, OGC Staff register the building block or group of building blocks in the register.

      6. -

    6. If the vote fails to pass, then OGC-NA Chair asks the SWG to revise the proposal before resubmission.

      +

    7. If the vote fails to pass, then OGC-NA Chair asks the SWG to revise the proposal before resubmission.

    @@ -1749,7 +1739,7 @@

    • Registered Building Block displayed on the registry

    -

6.3.  Appeals

+

6.3.  Appeals

A SWG may appeal to the TC Chair if it disagrees with the decisions of the Architecture DWG or OGC-NA regarding building block registration.

@@ -1767,13 +1757,13 @@

Process:

-

  1. SWG submits appeal form to the TC Chair

    +

    1. SWG submits appeal form to the TC Chair

      2. -

    2. TC Chair convenes an Appeals Panel consisting of members of the OGC Architecture Board (OAB) and invites the SWG

      +

    3. TC Chair convenes an Appeals Panel consisting of members of the OGC Architecture Board (OAB) and invites the SWG

      4. -

    4. TC Chair invites the chairs of the Architecture DWG and OGC-NA

      +

    5. TC Chair invites the chairs of the Architecture DWG and OGC-NA

      6. -

    6. The Appeals Panel votes on whether to uphold the decisions of the Architecture DWG and OGC-NA

      +

    7. The Appeals Panel votes on whether to uphold the decisions of the Architecture DWG and OGC-NA

    @@ -1794,7 +1784,7 @@

  2. a statement of the impact if the appeal is not successful

-

Annex A
(informative)
Revision History

Table A.1 — Revision History

DateReleaseEditorPrimary clauses modifiedDescription
2024-02-040.0.1G. HobonaallInitial draft
- + + + + + diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ietf/rfc_7946.xml b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ietf/rfc_7946.xml deleted file mode 100644 index c5ccf774..00000000 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ietf/rfc_7946.xml +++ /dev/null @@ -1,92 +0,0 @@ - - 2024-02-09 - The GeoJSON Format - https://www.rfc-editor.org/info/rfc7946 - RFC 7946 - 10.17487/RFC7946 - RFC7946 - - 2016-08 - - - - - - H. Butler - - - - - - - - M. Daly - - - - - - - - A. Doyle - - - - - - - - S. Gillies - - - - - - - - S. Hagen - - - - - - - - T. Schaub - - - - - - - RFC Publisher - - - - - - RFC Series - - - en - - -

GeoJSON is a geospatial data interchange format based on JavaScript Object Notation (JSON). It defines several types of JSON objects and the manner in which they are combined to represent data about geographic features, their properties, and their spatial extents. GeoJSON uses a geographic coordinate reference system, World Geodetic System 1984, and units of decimal degrees.

- - - RFC - 7946 - - - IETF - - JSON - Geospatial - JavaScript Object Notation - - - geojson - - IETF - - \ No newline at end of file diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ietf/version b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ietf/version deleted file mode 100644 index b3b95af0..00000000 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ietf/version +++ /dev/null @@ -1 +0,0 @@ -a03026b6e0501d55c0b281625ab5eb34 \ No newline at end of file diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/iso/iso_iec_10918-1.xml b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/iso/iso_iec_10918-1.xml deleted file mode 100644 index a774bd28..00000000 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/iso/iso_iec_10918-1.xml +++ /dev/null @@ -1,127 +0,0 @@ - - 2024-02-09 - Information technology - Digital compression and coding of continuous-tone still images: Requirements and guidelines - Information technology - Digital compression and coding of continuous-tone still images: Requirements and guidelines - https://www.iso.org/standard/18902.html - https://www.iso.org/obp/ui/en/#!iso:std:18902:en - https://www.iso.org/contents/data/standard/01/89/18902.detail.rss - ISO/IEC 10918-1 - ISO/IEC 10918-1(E) - urn:iso:std:iso-iec:10918:-1:stage-90.60:ed-1 - 10918 - - - - International Organization for Standardization - ISO - www.iso.org - - - - - - International Electrotechnical Commission - IEC - www.iec.ch - - - 1 - en - - - 90 - 60 - - - 1994 - - - ISO/IEC - - - - - - ISO/IEC 10918-1:1994/Cor 1:2005 - ISO/IEC 10918-1:1994/Cor 1:2005 - - 2022-06-14 - - - - - - 2024-02-09 - Information technology - Digital compression and coding of continuous-tone still images: Requirements and guidelines - Information technology - Digital compression and coding of continuous-tone still images: Requirements and guidelines - https://www.iso.org/standard/18902.html - https://www.iso.org/obp/ui/en/#!iso:std:18902:en - https://www.iso.org/contents/data/standard/01/89/18902.detail.rss - ISO/IEC 10918-1:1994 - ISO/IEC 10918-1:1994(E) - urn:iso:std:iso-iec:10918:-1:stage-90.60:ed-1 - 10918 - - 1994-02 - - - - - International Organization for Standardization - ISO - www.iso.org - - - - - - International Electrotechnical Commission - IEC - www.iec.ch - - - 1 - en - - Specifies processes for converting source image data to compressed image data, processes for converting compressed image data to reconstructed image data, coded representations for compressed image data, and gives guidance on how to implement these processes in practice. Is applicable to continuous-tone - grayscale or colour - digital still image data and to a wide range of applications which require use of compressed images. Is not applicable to bi-level image data. - - 90 - 60 - - - 1994 - - - ISO/IEC - - - - - - ISO/IEC 10918-1:1994/Cor 1:2005 - ISO/IEC 10918-1:1994/Cor 1:2005 - - 2022-06-14 - - - - Geneva - - - Geneva - - international-standard - - Coding of audio, picture, multimedia and hypermedia information - - - 35.040.30 - Coding of graphical and photographical information - - - ISO 10918 - - - \ No newline at end of file diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/iso/iso_iec_15948.xml b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/iso/iso_iec_15948.xml deleted file mode 100644 index 346129f3..00000000 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/iso/iso_iec_15948.xml +++ /dev/null @@ -1,111 +0,0 @@ - - 2024-02-09 - Information technology - Computer graphics and image processing - Portable Network Graphics (PNG): Functional specification - Information technology - Computer graphics and image processing - Portable Network Graphics (PNG): Functional specification - https://www.iso.org/standard/29581.html - https://www.iso.org/obp/ui/en/#!iso:std:29581:en - https://www.iso.org/contents/data/standard/02/95/29581.detail.rss - ISO/IEC 15948 - ISO/IEC 15948(E) - urn:iso:std:iso-iec:15948:stage-90.93:ed-1 - 15948 - - - - International Organization for Standardization - ISO - www.iso.org - - - - - - International Electrotechnical Commission - IEC - www.iec.ch - - - 1 - en - - - 90 - 93 - - - 2004 - - - ISO/IEC - - - - - - 2024-02-09 - Information technology - Computer graphics and image processing - Portable Network Graphics (PNG): Functional specification - Information technology - Computer graphics and image processing - Portable Network Graphics (PNG): Functional specification - https://www.iso.org/standard/29581.html - https://www.iso.org/obp/ui/en/#!iso:std:29581:en - https://www.iso.org/contents/data/standard/02/95/29581.detail.rss - ISO/IEC 15948:2004 - ISO/IEC 15948:2004(E) - urn:iso:std:iso-iec:15948:stage-90.93:ed-1 - 15948 - - 2004-03 - - - - - International Organization for Standardization - ISO - www.iso.org - - - - - - International Electrotechnical Commission - IEC - www.iec.ch - - - 1 - en - - ISO/IEC 15948:2004 specifies a datastream and an associated file format, Portable Network Graphics (PNG, pronounced "ping"), for a lossless, portable, compressed individual computer graphics image transmitted across the Internet. Indexed-colour, greyscale, and truecolour images are supported, with optional transparency. Sample depths range from 1 to 16 bits. PNG is fully streamable with a progressive display option. It is robust, providing both full file integrity checking and simple detection of common transmission errors. PNG can store gamma and chromaticity data as well as a full ICC colour profile for accurate colour matching on heterogenous platforms. ISO/IEC 15948:2004 defines the Internet Media type "image/png". The datastream and associated file format have value outside of the main design goal. - - 90 - 93 - - - 2004 - - - ISO/IEC - - - - Geneva - - - Geneva - - international-standard - - Computer graphics, image processing and environmental data representation - - - 35.140 - Computer graphics - - - ISO 15948 - - - \ No newline at end of file diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/iso/version b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/iso/version deleted file mode 100644 index b3b95af0..00000000 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/iso/version +++ /dev/null @@ -1 +0,0 @@ -a03026b6e0501d55c0b281625ab5eb34 \ No newline at end of file diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/08-131r3.xml b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/08-131r3.xml index a8edd03d..2b35fbd5 100644 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/08-131r3.xml +++ b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/08-131r3.xml @@ -1,5 +1,5 @@ - - 2024-02-15 + + 2024-10-30 The Specification Model Standard for Modular specifications The Specification Model - Standard for Modular specifications diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/09-046r6.xml b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/09-046r6.xml index 25bfdf74..a001cd16 100644 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/09-046r6.xml +++ b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/09-046r6.xml @@ -1,5 +1,5 @@ - - 2024-02-09 + + 2024-10-30 OGC Naming Authority Procedures OGC Naming Authority - Procedures diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/10-090r3.xml b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/10-090r3.xml deleted file mode 100644 index 65f1ea22..00000000 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/10-090r3.xml +++ /dev/null @@ -1,38 +0,0 @@ - - 2024-02-09 - OGC Network Common Data Form (NetCDF) Core Encoding Standard version 1.0 - OGC Network Common Data Form (NetCDF) Core Encoding Standard version 1.0 - - https://portal.ogc.org/files/?artifact_id=43732 - 10-090r3 - - 2011-04-05 - - - - - - Ben Domenico - - - - - - - Open Geospatial Consortium - - - 3 - en - - This document specifies the network Common Data Form (netCDF) core standard and extension mechanisms. The OGC netCDF encoding supports electronic encoding of geospatial data, specifically digital geospatial information representing space and time-varying phenomena. -NetCDF is a data model for array-oriented scientific data. A freely distributed collection of access libraries implementing support for that data model, and a machine-independent format are available. Together, the interfaces, libraries, and format support the crea-tion, access, and sharing of multi-dimensional scientific data. - - - standard - implementation - - technical - - - \ No newline at end of file diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/17-083r4.xml b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/17-083r4.xml deleted file mode 100644 index 5e422bd6..00000000 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/17-083r4.xml +++ /dev/null @@ -1,44 +0,0 @@ - - 2024-02-09 - OGC Two Dimensional Tile Matrix Set and Tile Set Metadata - OGC Two Dimensional Tile Matrix Set and Tile Set Metadata - http://www.opengis.net/doc/IS/tms/2.0 - https://docs.ogc.org/is/17-083r4/17-083r4.html - 17-083r4 - - 2022-09-09 - - - - - - Joan Masó - - - - - - - - Jérôme Jacovella-St-Louis - - - - - - - Open Geospatial Consortium - - - 4 - en - - The OGC Two Dimensional Tile Matrix Set and Tile Set Metadata Standard defines the rules and requirements for a tile matrix set as a way to index space based on a set of regular grids defining a domain (tile matrix) for a limited list of scales in a Coordinate Reference System (CRS) as defined in OGC 18-005r5 Abstract Specification Topic 2: Referencing by Coordinates. This content was initially included in the OGC 07-057r7 OpenGIS Web Map Tile Service Implementation Standard (WMTS) and was separated out into the OGC 17-083r2 OGC Two Dimensional Tile Matrix Set Standard version 1.0, to support reusability in other data formats of services that need a tiling scheme. This document is a revision of the OGC 17-083r2 document and the general tile matrix set concept is inherited from it with small additions. In a tile matrix set, each tile matrix is divided into regular tiles. In a tile matrix set, a tile can be univocally identified by a tile column, a tile row, and a tile matrix identifier. The OGC Two Dimensional Tile Matrix Set and Tile Set Metadata Standard describes a data structure defining the properties of the tile matrix set in both Unified Modeling Language (UML) diagrams and in tabular form. This document also defines a new data structure, called tile set metadata, that can be used to describe a particular set of tiles following a tile matrix set. Extensible Markup Language (XML) and JavaScript Object Notation (JSON) encodings are described both for tile matrix sets and tile matrix set metadata. It includes tile matrix set limits, links to the tile matrix set, details of the original data represented by the tile set and a nice point of origin to start exploring the tile set. Finally, the document offers practical examples of tile matrix sets both for common global projections and for specific regions. - - standard - implementation - - technical - - - \ No newline at end of file diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/19-008r4.xml b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/19-008r4.xml deleted file mode 100644 index 69b9f0da..00000000 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/19-008r4.xml +++ /dev/null @@ -1,68 +0,0 @@ - - 2024-02-09 - OGC GeoTIFF Standard - OGC GeoTIFF Standard - http://www.opengis.net/doc/IS/GeoTIFF/1.1 - https://docs.ogc.org/is/19-008r4/19-008r4.html - 19-008r4 - - 2019-09-14 - - - - - - Emmanuel Devys - - - - - - - - Ted Habermann - - - - - - - - Chuck Heazel - - - - - - - - Roger Lott - - - - - - - - Even Rouault - - - - - - - Open Geospatial Consortium - - - 4 - en - - This OGC Standard defines the Geographic Tagged Image File Format (GeoTIFF) by specifying requirements and encoding rules for using the Tagged Image File Format (TIFF) for the exchange of georeferenced or geocoded imagery. The OGC GeoTIFF 1.1 standard formalizes the existing community GeoTIFF specification version 1.0 and aligns it with the continuing addition of data to the EPSG Geodetic Parameter Dataset. - - standard - implementation - - technical - - - \ No newline at end of file diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/19-014r3.xml b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/19-014r3.xml deleted file mode 100644 index 1de725e4..00000000 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/19-014r3.xml +++ /dev/null @@ -1,42 +0,0 @@ - - 2024-02-09 - Topic 22 - Core Tiling Conceptual and Logical Models for 2D Euclidean Space - Topic 22 - Core Tiling Conceptual and Logical Models for 2D Euclidean Space - http://www.opengis.net/doc/AS/2D-tiles/1.0 - https://docs.ogc.org/as/19-014r3/19-014r3.html - 19-014r3 - - 2020-10-22 - - - - - - Carl Reed - - - - - - - Open Geospatial Consortium - - - 3 - en - - This OGC Abstract Specification (AS) defines: - -A conceptual model for tiling space in any dimension and; - -A logical model for 2D tiled structures and by extension tiling. The logical model is based on the conceptual model. - -The conceptual model specified in this Abstract Specification could be a sub-class in a more comprehensive Spatial Partitioning Conceptual Model. Additional Parts may be added to this AS for other dimensions, such as 3D, or other uses cases. - - abstract-specification-topic - - technical - - - \ No newline at end of file diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/19-072.xml b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/19-072.xml deleted file mode 100644 index 74bb729c..00000000 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/19-072.xml +++ /dev/null @@ -1,39 +0,0 @@ - - 2024-02-09 - OGC API - Common - Part 1: Core - OGC API - Common - Part 1: Core - http://www.opengis.net/doc/is/ogcapi-common-1/1.0 - https://docs.ogc.org/is/19-072/19-072.html - 19-072 - - 2023-03-28 - - - - - - Charles Heazel - - - - - - - Open Geospatial Consortium - - - en - - The OGC has extended its suite of Standards to include Resource Oriented Architectures and Web APIs. In the course of developing these Standards, some practices proved to be common across multiple OGC Web API Standards. These common practices are documented in the OGC API — Common Standard. The OGC API - Common Standard is a multi-part standard that specifies reusable building-blocks that can be used in the construction of OGC API Standards. This document presents Part 1, the Core, of the OGC API – Common Standard. Standards developers will use these building-blocks in the construction of other OGC Standards that relate to Web APIs. The result is a modular suite of coherent API standards which can be adapted by a system designer for the unique requirements of their system. - -The purpose of the OGC API — Common — Part 1: Core Standard (API-Core) is to define those fundamental building blocks and requirements which are applicable to all OGC Web API Standards. - - standard - implementation - - technical - - - \ No newline at end of file diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_05-020r29.notfound b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_05-020r29.notfound index 6b9920b8..a1a9c006 100644 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_05-020r29.notfound +++ b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_05-020r29.notfound @@ -1 +1 @@ -not_found 2024-02-15 \ No newline at end of file +not_found 2024-10-30 \ No newline at end of file diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_06-030r12.notfound b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_06-030r12.notfound index a4b27a5c..a1a9c006 100644 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_06-030r12.notfound +++ b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_06-030r12.notfound @@ -1 +1 @@ -not_found 2024-02-09 \ No newline at end of file +not_found 2024-10-30 \ No newline at end of file diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_10-090r3.redirect b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_10-090r3.redirect deleted file mode 100644 index 0d9e71af..00000000 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_10-090r3.redirect +++ /dev/null @@ -1 +0,0 @@ -redirection OGC(10-090r3) \ No newline at end of file diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_17-083r4.redirect b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_17-083r4.redirect deleted file mode 100644 index 35d5925a..00000000 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_17-083r4.redirect +++ /dev/null @@ -1 +0,0 @@ -redirection OGC(17-083r4) \ No newline at end of file diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_19-008r4.redirect b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_19-008r4.redirect deleted file mode 100644 index e5b2b8f9..00000000 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_19-008r4.redirect +++ /dev/null @@ -1 +0,0 @@ -redirection OGC(19-008r4) \ No newline at end of file diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_19-014r3.redirect b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_19-014r3.redirect deleted file mode 100644 index 1e4caccb..00000000 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_19-014r3.redirect +++ /dev/null @@ -1 +0,0 @@ -redirection OGC(19-014r3) \ No newline at end of file diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_19-072.redirect b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_19-072.redirect deleted file mode 100644 index 9910e44c..00000000 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_19-072.redirect +++ /dev/null @@ -1 +0,0 @@ -redirection OGC(19-072) \ No newline at end of file diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_20-024.notfound b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_20-024.notfound deleted file mode 100644 index a4b27a5c..00000000 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/ogc_20-024.notfound +++ /dev/null @@ -1 +0,0 @@ -not_found 2024-02-09 \ No newline at end of file diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/version b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/version index c2c9f64c..e9cdaf0b 100644 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/version +++ b/policyAndProcedures/OGCBuildingBlocksRegistration/relaton/cache/ogc/version @@ -1 +1 @@ -870165bd9aeeb46bb7c5b7906f472c8d \ No newline at end of file +b4f88dfa16a39dfa412b1cc164a82606 \ No newline at end of file diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/sections/00-preface.adoc b/policyAndProcedures/OGCBuildingBlocksRegistration/sections/00-preface.adoc index 3e9d65d2..a1d2b8b6 100644 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/sections/00-preface.adoc +++ b/policyAndProcedures/OGCBuildingBlocksRegistration/sections/00-preface.adoc @@ -27,7 +27,7 @@ Recipients of this document are requested to submit, with their comments, notifi [abstract] == Abstract -The mission of the OGC Naming Authority (OGC-NA) is to provide the means through which OGC resources such as OGC documents, namespaces and ontologies can be controlled and managed such that they can provide clear and well-defined names and definitions. In the terminology defined in ISO 19135, OGC-NA is the Control Body for the register of OGC Names. This document describes the framework of documents, registers and other resources required for OGC-NA to execute that role. +This OGC Policy specifies the governance rules and procedures for the registration of OGC Standards Building Blocks. The policy can be considered a profile of https://docs.ogc.org/pol/09-046r6.html[OGC 09-046r6], OGC Naming Authority - Procedures policy. [.preface] == Security Considerations diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/sections/01-scope.adoc b/policyAndProcedures/OGCBuildingBlocksRegistration/sections/01-scope.adoc index f2b2a876..2db0f610 100644 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/sections/01-scope.adoc +++ b/policyAndProcedures/OGCBuildingBlocksRegistration/sections/01-scope.adoc @@ -1,8 +1,6 @@ == Scope -This OGC Policy specifies the governance rules and procedures for the registration of OGC Standards Building Blocks. The policy can be considered a profile of https://docs.ogc.org/pol/09-046r6.html[OGC 09-046r6], OGC Naming Authority - Procedures policy. - Clause 7.2.1 of the OGC Technical Committee's Policies and Procedures (https://docs.ogc.org/pol/05-020r29/05-020r29.html[OGC 05-020r29]) defines a Standard Building Block as follows: "Many OGC Standards are structured with modular sets of requirements (or requirement classes) that collectively function as a reusable building block. There is no firm definition for the content or scope of a building block, but the building block must fulfill a function that can operate in the larger context of an implementation, including combination with other OGC building blocks to create novel implementations. diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/sections/04-considerations.adoc b/policyAndProcedures/OGCBuildingBlocksRegistration/sections/04-considerations.adoc deleted file mode 100644 index b4dd1239..00000000 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/sections/04-considerations.adoc +++ /dev/null @@ -1,38 +0,0 @@ -[[considerations]] -== Considerations for Registration - -=== Granularity - -OGC Standards are composed of specification elements as defined in the OGC Standard for Modular specifications (OGC 08-131r3), also known as the ModSpec. These specification elements include requirements classes, requirements, conformance classes, and abstract tests. Each one of these specification elements may reference other constructs or artifacts such as schema documents, schema fragments, parameters, API definition documents, or others. Those constructs or artifacts may themselves reference others. Therefore, a key consideration for the registration of Standards Building Blocks is at what level of granularity a building block should be registered. The following are the levels of granularity that may be considered for registration. - -==== Level 1: Conformance Classes and Requirements Classes - -TBA - -==== Level 2: Requirements and Abstract Tests - -TBA - -==== Level 3: Schema documents and API definition documents - -TBA - -==== Level 4: Schema fragments and Parameters - -TBA - -=== Reusability - -TBA - -==== TBA - -TBA - -=== Interfacing between Standards Building Blocks - -TBA - -==== TBA - -TBA \ No newline at end of file diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/sections/05-roles.adoc b/policyAndProcedures/OGCBuildingBlocksRegistration/sections/04-roles.adoc similarity index 100% rename from policyAndProcedures/OGCBuildingBlocksRegistration/sections/05-roles.adoc rename to policyAndProcedures/OGCBuildingBlocksRegistration/sections/04-roles.adoc diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/sections/05-considerations.adoc b/policyAndProcedures/OGCBuildingBlocksRegistration/sections/05-considerations.adoc new file mode 100644 index 00000000..fa064f24 --- /dev/null +++ b/policyAndProcedures/OGCBuildingBlocksRegistration/sections/05-considerations.adoc @@ -0,0 +1,25 @@ +[[considerations]] +== Considerations for Registration + +OGC Standards are composed of specification elements as defined in the OGC Standard for Modular specifications (OGC 08-131r3), also known as the ModSpec. These specification elements include requirements classes, requirements, conformance classes, and abstract tests. Each one of these specification elements may reference other constructs or artifacts such as schema documents, schema fragments, parameters, API definition documents, or others. Those constructs or artifacts may themselves reference others. Therefore, the following factors shall be considered during the review of a proposal to register a building block. + +This section presents requirements for reviewers involved the Architecture DWG approval of building blocks. + +.Requirements for Architecture DWG approval of building blocks +[cols=",",options="header"] +|=== +|Ref. |Description +|1 | The level of granularity of a building block SHALL only be approved if its definition is equal to or smaller than that of its originating Conformance Class or Requirements Class. +|2 | The reusability of a building block SHALL only be approved if the building block can be shown to usable by two or more OGC Standards. +|3 | The interfacing of a building block SHALL only be approved if it is well defined in the source Standard. +|=== + +This section presents requirements for reviewers involved the OGC-NA approval of building blocks. + +.Requirements for reviewers involved in OGC-NA approval of building blocks +[cols=",",options="header"] +|=== +|Ref. |Description +|1 | The description of a building block SHALL only be approved if the description matches that specified in the originating OGC Standards. +|2 | The identification of a building block SHALL only be approved if the identification matches that specified in the originating OGC Standards. This includes the case format and pattern of the name of the building block. +|===