-
Notifications
You must be signed in to change notification settings - Fork 2
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
1 changed file
with
22 additions
and
0 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
[[modspec-policy]] | ||
== ModSpec Policy Requirements | ||
|
||
The following requirement states that in OGC Standards development, the ModSpec model will be used. | ||
|
||
[[req-01]] | ||
[requirement,model=ogc,type="general"] | ||
[width="90%",cols="2,6"] | ||
|=== | ||
|*REQ001* | */req/policy/conformance-with-modspec* + | ||
Any new OGC Standard, abstract specification that contains requirements, or major revision of an existing OGC Standard _SHALL_ comply with the requirements stated in the OGC ModSpec. | ||
|=== | ||
|
||
Any OGC Standards document will specify the standardization goal. | ||
|
||
[[req-02]] | ||
[requirement,model=ogc,type="general"] | ||
[width="90%",cols="2,6"] | ||
|=== | ||
|*REQ002* | */req/policy/standardization-goal* + | ||
Any new OGC Standard, abstract specification that contains requirements, or major revision of an existing OGC Standard _SHALL_ clearly state the stanrdization goal for the standard or abstract specification. This statement _SHOULD_ be in the `Abstract` or `Scope` clauses of the standard. | ||
|=== |