-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
7 changed files
with
42 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
22 changes: 22 additions & 0 deletions
22
policyAndProcedures/OGCBuildingBlocksRegistration/sections/04-considerations.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
[[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 |
File renamed without changes.
File renamed without changes.
11 changes: 11 additions & 0 deletions
11
policyAndProcedures/OGCBuildingBlocksRegistration/sections/annex-history.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,11 @@ | ||
[appendix] | ||
:appendix-caption: Annex | ||
== Revision History | ||
|
||
[#revision-history,reftext='{table-caption} {counter:table-num}'] | ||
.Revision History | ||
[cols="12,18,12,12,46",options="header"] | ||
|=== | ||
|Date |Release |Editor | Primary clauses modified |Description | ||
|2024-02-04 |0.0.1 |G. Hobona |all |Initial draft | ||
|=== |