Merge pull request #289 from opengeospatial/fix_for_issue_204

Fix for issue 204
opengeospatial · Jul 19, 2024 · 8996831 · 8996831
2 parents fb9e678 + bccc997
commit 8996831
Show file tree

Hide file tree

Showing 3 changed files with 19 additions and 1 deletion.
diff --git a/...meTypeSpecificationForSpecificationElements/clause_4_terms_and_definitions.adoc b/...meTypeSpecificationForSpecificationElements/clause_4_terms_and_definitions.adoc
@@ -8,6 +8,12 @@ expression in the content of a document conveying criteria to be fulfilled if co
 
 (Source: ISO Directives Part 2)
 
+=== *requirements module*
+
+aggregate of requirements and recommendations of a specification against a single standardization target type
+
+(Source: OGC 08-131r3)
+
 === *requirements class*
 aggregate of all requirement modules that must all be satisfied to satisfy a conformance test class
 
@@ -19,3 +25,4 @@ set of conformance test modules that must be applied to receive a single certifi
 NOTE: When no ambiguity is possible, the word 'test' may be left out, so *conformance test class* maybe called a *conformance class*.
 
 (Source: OGC 08-131r3)
+
diff --git a/...es/OGCNANameTypeSpecificationForSpecificationElements/clause_6_naming_rule.adoc b/...es/OGCNANameTypeSpecificationForSpecificationElements/clause_6_naming_rule.adoc
@@ -33,7 +33,7 @@ An OGC name for a normative specification element shall be produced using the fo
   ResourceSpecificPath = standard "/" version [ "/" class "/" name *("/" name) ]
   standard             = segment-nz-nc ; value registered as a doc-name for an OGC standard according to [OGC-NA Name type specification – documents]
   version              = 1*DIGIT "." 1*DIGIT ["." 1*DIGIT] ; value registered as a doc-version for an OGC implementation standard according to [OGC-NA Name type specification – documents]
-  class                = "req" / "conf"
+  class                = "req" / "conf"  / "rm"
   name                 = segment-nz-nc
 
 
@@ -46,6 +46,7 @@ This policy considers each segment along the path of a specification element URI
 . The URI `\http://www.opengis.net/spec/<standard>` shall return information describing this URI as the namespace for specification elements of the standard named by the `<standard>` segment.
 . The URI `\http://www.opengis.net/spec/<standard>/<version>` shall return information describing this URI as the namespace for specification elements of version `<version>` of standard `<standard>`.
 . The URI `\http://www.opengis.net/spec/<standard>/<version>/req` shall return information describing this URI as the namespace for requirements and requirements classes in version `<version>` of standard `<standard>`.
+. The URI `\http://www.opengis.net/spec/<standard>/<version>/rm` shall return information describing this URI as the namespace for requirements modules in version `<version>` of standard `<standard>`.
 . The URI `\http://www.opengis.net/spec/<standard>/<version>/conf` shall return information describing this URI as the namespace for conformance classes and conformance tests in version `<version>` of standard `<standard>`.
 
 === Explanation

diff --git a/...dures/OGCNANameTypeSpecificationForSpecificationElements/clause_8_examples.adoc b/...dures/OGCNANameTypeSpecificationForSpecificationElements/clause_8_examples.adoc
@@ -39,3 +39,13 @@ Example 5: A conformance test within the previous conformance-class
   http://www.opengis.net/spec/OMXML/2.0/conf/measurement/result-measure
 
 NOTE: The second step after the /conf/ field provides the name of a conformance-module or conformance-test.
+
+=== Requirements module
+
+Example 6: A requirements module
+
+http://www.opengis.net/spec/ogcapi-common-2/1.0/rm/datetime
+
+NOTE: Instead of the /req/ segment, /rm/ is used.
+
+NOTE: This is based on the example of https://docs.ogc.org/is/20-057/20-057.html#_datetime_query_parameter_request_and_response