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.
The following are keywords to be used by search engines and document catalogues.
keyword_1, keyword_2, keyword_3, etc.
This document describes the procedures used by the OGC Naming Authority for the registration of OGC Standards Building Blocks.
No security considerations have been made for this Standard.
All questions regarding this submission should be directed to the editor or the submitters:
| Name | Affiliation |
|---|---|
| Gobe Hobona | OGC |
| TBA | TBA |
| TBA | TBA |
| TBA | TBA |
| TBA | TBA |
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 OGC 09-046r6, OGC Naming Authority — Procedures policy.
Clause 7.2.1 of the OGC Technical Committee’s Policies and Procedures (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.
Building blocks developed for one Standard can be reused in another Standard. To facilitate such reuse, a Standard constructed of building blocks shall identify each building block and publish a definition of the building block to OGC’s Registries and web resources. The definition will be in the form most suitable for the type of building block (e.g., Open API for a Standardized API), reference the owning Standard, and be adequately documented to be used in reference.
OGC Standards that reuse building blocks from other Standards must include in the Normative References a reference to the owning Standard of the building block(s) and a direct reference to the registered building block(s) content. In this fashion, implementers of the Standard reusing these building blocks need to only access specific parts (the building blocks) of the referenced Standard, not the entire document.”__
NOTE: The planned revision of “The Specification Model — A Standard for Modular specifications” (OGC 08-131r3), also known as the ModSpec, is expected to include a more precise definition of a Standards Building Block.
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.
The following are keywords to be used by search engines and document catalogues.
keyword_1, keyword_2, keyword_3, etc.
This document describes the procedures used by the OGC Naming Authority for the registration of OGC Standards Building Blocks.
No security considerations have been made for this Standard.
All questions regarding this submission should be directed to the editor or the submitters:
| Name | Affiliation |
|---|---|
| Gobe Hobona | OGC |
| TBA | TBA |
| TBA | TBA |
| TBA | TBA |
| TBA | TBA |
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 OGC 09-046r6, OGC Naming Authority — Procedures policy.
Clause 7.2.1 of the OGC Technical Committee’s Policies and Procedures (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.
Building blocks developed for one Standard can be reused in another Standard. To facilitate such reuse, a Standard constructed of building blocks shall identify each building block and publish a definition of the building block to OGC’s Registries and web resources. The definition will be in the form most suitable for the type of building block (e.g., Open API for a Standardized API), reference the owning Standard, and be adequately documented to be used in reference.
OGC Standards that reuse building blocks from other Standards must include in the Normative References a reference to the owning Standard of the building block(s) and a direct reference to the registered building block(s) content. In this fashion, implementers of the Standard reusing these building blocks need to only access specific parts (the building blocks) of the referenced Standard, not the entire document.”__
NOTE: The planned revision of “The Specification Model — A Standard for Modular specifications” (OGC 08-131r3), also known as the ModSpec, is expected to include a more precise definition of a Standards Building Block.
The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.
@@ -1449,7 +1451,7 @@George Percivall: OGC 06-030r12, OGC Architecture Board (OAB) Policies and Procedures. Open Geospatial Consortium (2018), https://portal.ogc.org/files/?artifact_id=90860
Gobe Hobona, Simon Cox: OGC 09-046r6, OGC Naming Authority — Procedures. Open Geospatial Consortium (2021). http://www.opengis.net/doc/POL/OGC-NA/1.3.
Policy SWG: OGC 08-131r3, The Specification Model — Standard for Modular specifications. Open Geospatial Consortium (2009).
-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.
+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.
TBA
+TBA
TBA
+TBA
TBA
+TBA
TBA
+TBA
The following table identifies the roles involved in the registration and maintenance of the OGC Standards Building Blocks register and the registry that hosts the register.
Table 1
| Role | Assignee |
|---|---|
| Control Body | OGC Naming Authority |
| Register Owner | OGC Architecture Board |
| Submitting Organization | Standards Working Group |
| Register Manager | OGC-NA Chair |
| Registry Manager | OGC Staff |
| Appeals Lead | TC Chair |
| Register User | General Public |
TBA
+ +TBA
+TBA
+ +TBA
+The following table identifies the roles involved in the registration and maintenance of the OGC Standards Building Blocks register and the registry that hosts the register.
Table 1
| Role | Assignee |
|---|---|
| Control Body | OGC Naming Authority |
| Register Owner | OGC Architecture Board |
| Submitting Organization | Standards Working Group |
| Register Manager | OGC-NA Chair |
| Registry Manager | OGC Staff |
| Appeals Lead | TC Chair |
| Register User | General Public |
Each OGC candidate Standard goes through a series of stages on the way to approval by the TC. One of those stages is the review by the OGC Architecture Board (OAB).
@@ -1531,13 +1549,13 @@Process:
-OAB Chair begins a period of review by the OAB
+OAB Chair begins a period of review by the OAB
OAB evaludates the structure of the proposed building block(s)
+OAB evaludates the structure of the proposed building block(s)
OAB Chair conducts a vote on the approval of the proposed level of granularity, reusability, and interfacing of the building block(s)
+OAB Chair conducts a vote on the approval of the proposed level of granularity, reusability, and interfacing of the building block(s)
OAB Chair creates a ticket, on the OGC-NA Git repository, with the result of the OAB vote
+OAB Chair creates a ticket, on the OGC-NA Git repository, with the result of the OAB vote
A SWG may appeal to the TC Chair if it disagrees with the decisions of the OAB or OGC-NA regarding building block registration.
@@ -1609,11 +1627,11 @@Process:
-SWG submits appeal form to the TC Chair
+SWG submits appeal form to the TC Chair
TC Chair convenes an Appeals Panel consisting of OAB and OGC-NA members, and invites the SWG
+TC Chair convenes an Appeals Panel consisting of OAB and OGC-NA members, and invites the SWG
The Appeals Panel votes on whether to uphold the OAB/OGC-NA decision
+The Appeals Panel votes on whether to uphold the OAB/OGC-NA decision
a statement of the impact if the appeal is not successful
Table A.1 — Revision History
| Date | Release | Editor | Primary clauses modified | Description |
|---|---|---|---|---|
| 2024-02-04 | 0.0.1 | G. Hobona | all | Initial draft |