From a3eb1b163dd0a722447710ca6b85024db67b9af3 Mon Sep 17 00:00:00 2001 From: Gobe Hobona Date: Fri, 9 Feb 2024 14:51:03 +0000 Subject: [PATCH] Delete document.html --- .../document.html | 1721 ----------------- 1 file changed, 1721 deletions(-) delete mode 100644 policyAndProcedures/OGCBuildingBlocksRegistration/document.html diff --git a/policyAndProcedures/OGCBuildingBlocksRegistration/document.html b/policyAndProcedures/OGCBuildingBlocksRegistration/document.html deleted file mode 100644 index a6170515..00000000 --- a/policyAndProcedures/OGCBuildingBlocksRegistration/document.html +++ /dev/null @@ -1,1721 +0,0 @@ - - -Policy for Registration of OGC Standards Building Blocks - - - - - - - - - - - - - - - - -
-

Draft

-
- -
-

OGC Policy

-
- - - -
•
- -
- - -
-
- -
- -
- Policy for Registration of OGC Standards Building Blocks - -
-
- - - - - -
- - - - - - - Gobe Hobona Editor - - Jane Doe Editor - - -
- -
- Submission Date: 2019-03-28 - Approval Date: 2999-05-29 - Publication Date: 2029-06-03 - External identifier of this OGC® document: http://www.opengis.net/doc/pol/tcpnp/27.0 - Internal identifier of this OGC® document: 05-020r27 - - -
- -
- - Version: 27.0
- - -
- -
- -
- -
-
- OGC Policy -
- -
-

Draft

-
-
- -
-
- -

Notice

- -

This document is not an OGC Standard. This document is an OGC Policy and is therefore not an official position of the OGC membership. It is distributed for review and comment. It is subject to change without notice and may not be referred to as an OGC Standard.

- -

Further, an OGC Policy should not be referenced as required or mandatory technology in procurements.

-
-
-
- - - -
- - - - - - -
Document number:05-020r27
Document type:OGC Policy
Document subtype:
Document stage:Draft
Document language:English
-
- -
-
-
- -

Copyright notice

- -

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

-
- -

Note

- -

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.

- -

Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.

-
-
-
- -
-
-
-

-
- -

License Agreement

- -

Use of this document is subject to the license agreement at https://www.ogc.org/license

-
-
- - - -
- - - - -
-

- - - - - -
- -
-


I.  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.

II.  Keywords

The following are keywords to be used by search engines and document catalogues.

keyword_1, keyword_2, keyword_3, etc.


III.  Preface

This document describes the procedures used by the OGC Naming Authority for the registration of OGC Standards Building Blocks.

IV.  Security Considerations

No security considerations have been made for this Standard.

V.  Submitters

Additional contributors to this Standard include the following:

Individual name(s), Organization

NOTE:    If you need to place any further sections in the preface area -use the [.preface] attribute.

VI.  Submitters

All questions regarding this submission should be directed to the editor or the submitters:

NameAffiliationOGC member
Steve LiangUniversity of Calgary, Canada / SensorUp Inc.Yes

1.  Introduction

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.”__

2.  Terms definitions and abbreviated terms

2.1.  Terms and definitions

- -

2.1.1.  conformance test

- -

test, abstract or real, of one or more requirements contained within a standard, or set of standards (source: OGC 08-131r3)

-
- -

2.1.2.  conformance test class

- -

set of conformance test modules that must be applied to receive a single certificate of conformance (source: OGC 08-131r3)

NOTE:    When no ambiguity is possible, the word “test” may be left out, so conformance test class maybe called a conformance class.

- - -
- -

2.1.3.  requirement

- -

expression in the content of a document conveying criteria to be fulfilled if compliance with the document is to be claimed and from which no deviation is permitted (source: ISO/IEC Directives Part 2)

-
- -

2.1.4.  requirements class

- -

aggregate of all requirement modules that must all be satisfied to satisfy a conformance test class (source: OGC 08-131r3)

NOTE:    There is some confusion possible here, since the testing of indirect dependencies seems to violate this definition. But the existence of an indirect dependency implies that the test is actually a test of the existence of the relationship from the original target to something that has a property (satisfies a condition or requirement from another requirements class).

- - -
-

3.  Roles

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

RoleAssignee
Control BodyOGC Naming Authority
Register OwnerOGC Architecture Board
Submitting OrganizationStandards Working Group
Register ManagerOGC-NA Chair
Registry ManagerOGC Staff
Register UserGeneral Public

4.  Processes

4.1.  Review by the OAB

- -

During the OAB review of the Standard, it is the responsibility of the SWG to seek a recommendation from the OAB on the granularity of the building block.

- -

Trigger: SWG submits a candiate Standard or a previously approved Standard for OAB review.

- -

Inputs:

- -

  • candiate Standard or a previously approved Standard

    -
    • -
- -

Process:

- -

  1. TBA

    -
    2. -

  2. TBA

    -
    3. -

  3. TBA

    -
    4. -
- -

Outputs:

- -

  • Recommendation from the OAB on the granularity of the building block

    -
    • -
-

4.2.  Approval for registration

- -

Trigger: SWG submits a TC-approved Standard for registration as building blocks.

- -

Inputs:

- -

  • Approved and publish Standard

    -
    • -

  • Recommendation from the OAB on the granularity of the building block

    -
    • -
- -

Process:

- -

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

    -
    2. -

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

    -
    3. -

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

    -
    4. -

  4. If the vote fails to pass, then OGC-NA Chair shall ask the SWG to revise the proposal before resubmission.

    -
    5. -
- -

Outputs:

- -

  • Registered Building Block displayed on the registry

    -
    • -
-

4.3.  Appeals

- -

TBA

-

Annex A
(normative)
Annex Title

Annex content.

NOTE:    Place annex material in sequential order and set obligation attribute as “normative” (default) or “informative” according to the case.

- - - - - - - - - - - - - - - - - - -