add Abstract Test Suite

cportele · cportele · commit 7da4f5852f5e · 2025-08-19T12:29:15.000+02:00
diff --git a/extensions/schemas/standard/annex_ats.adoc b/extensions/schemas/standard/annex_ats.adoc
diff --git a/extensions/schemas/standard/annex_history.adoc b/extensions/schemas/standard/annex_history.adoc
@@ -8,4 +8,5 @@
 |2023-10-22 |1.0.0-SNAPSHOT |C. Portele |all |initial version
 |2024-03-07 |1.0.0-draft.1 |C. Portele |all |draft for OAB review
 |2024-06-04 |1.0.0-draft.2 |P. Vretanos, C. Portele |all |draft for Public Comment
+|2025-09-xx |1.0.0-draft.3 |P. Vretanos, C. Portele |all |draft for OGC approval process
 |===
diff --git a/extensions/schemas/standard/clause_10_returnables_and_receivables.adoc b/extensions/schemas/standard/clause_10_returnables_and_receivables.adoc
@@ -14,23 +14,23 @@ The Requirements Class "Returnables and Receivables" specifies the web resources
 This requirements class supports clients that want to discover the list of resource properties with their types and constraints that is returned when fetching a representation of the resource or when creating a new or updating an existing resource.
 
 :req: link
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
 ^|A |A Returnables and Receivables resource SHALL be referenced from all Collection resources with a link with the link relation type `\http://www.opengis.net/def/rel/ogc/1.0/schema`.
 |===
 
 :req: op
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
 ^|A |The Returnables and Receivables resource SHALL support the HTTP GET operation and the media type `application/schema+json`.
 |===
 
 :req: response
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
diff --git a/extensions/schemas/standard/clause_11_queryables.adoc b/extensions/schemas/standard/clause_11_queryables.adoc
@@ -18,23 +18,23 @@ OGC API Standards do not assume that the content schema of a resource being quer
 In addition, a <<publisher-def,publisher>> may want to support <<queryable-def,queryables>> that are not directly represented as resource properties in the content schema of the resource. Or the <<publisher-def,publisher>> may want to restrict filtering on certain properties. For example, because the backend datastore has not been configured to allow high-performance queries on those properties.
 
 :req: link
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
 ^|A |A Queryables resource SHALL be referenced from all Collection resources with a link with the link relation type `\http://www.opengis.net/def/rel/ogc/1.0/queryables`.
 |===
 
 :req: op
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
 ^|A |The Queryables resource SHALL support the HTTP GET operation and the media type `application/schema+json`.
 |===
 
 :req: response
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
diff --git a/extensions/schemas/standard/clause_12_sortables.adoc b/extensions/schemas/standard/clause_12_sortables.adoc
@@ -18,23 +18,23 @@ OGC API Standards do not assume that the content schema of a resource being quer
 In addition, a <<publisher-def,publisher>> may want to support <<sortable-def,sortable>> that are not directly represented as resource properties in the content schema of the resource. Or the <<publisher-def,publisher>> may want to restrict sorting on certain properties. For example, because the backend datastore has not been configured to allow high-performance queries on those properties.
 
 :req: link
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
 ^|A |A Sortables resource SHALL be referenced from all Collection resources with a link with the link relation type `\http://www.opengis.net/def/rel/ogc/1.0/sortables`.
 |===
 
 :req: op
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
 ^|A |The Sortables resource SHALL support the HTTP GET operation and the media type `application/schema+json`.
 |===
 
 :req: response
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
diff --git a/extensions/schemas/standard/clause_13_profile_parameter.adoc b/extensions/schemas/standard/clause_13_profile_parameter.adoc
@@ -19,7 +19,7 @@ A profile is defined not to alter the semantics of the resource representation i
 To request one or more profiles, a query parameter "profile" can be used:
 
 :req: profile-param
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
@@ -67,7 +67,7 @@ Different media types have different characteristics. A consequence is that it c
 The server will select the profile(s) of the response, if any, from the list of profiles supported for the media type and resource.
 
 :rec: profile-negotiation
-[#{req-class}_{rec}]
+[#rec_{req-class}_{rec}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Recommendation {counter:rec-num}* |/rec/{req-class}/{rec}
@@ -76,7 +76,7 @@ The server will select the profile(s) of the response, if any, from the list of
 |===
 
 :req: profile-param-response
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
@@ -85,7 +85,7 @@ The server will select the profile(s) of the response, if any, from the list of
 |===
 
 :rec: profile-link-header
-[#{req-class}_{rec}]
+[#rec_{req-class}_{rec}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Recommendation {counter:rec-num}* |/rec/{req-class}/{rec}
diff --git a/extensions/schemas/standard/clause_14_profile_references.adoc b/extensions/schemas/standard/clause_14_profile_references.adoc
@@ -16,7 +16,7 @@ The requirements stated in this Standard cover only simple cases. More complex c
 |===
 
 :req: ref-profiles
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
@@ -26,11 +26,11 @@ The requirements stated in this Standard cover only simple cases. More complex c
 For features, the query parameter "profile" will be applicable to the GET operation on the paths `/collections/{collectionId}/items` and `/collections/{collectionId}/items/{resourceId}`.
 
 :req: rel-as-key
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
-^|A |In the profile "rel-as-key" (`\http://www.opengis.net/def/profile/OGC/0/rel-as-key`) a reference in the response SHALL be represented by the `resourceId` of the referenced resource (a string or integer, depending on the type of the identifier property in the referenced collection), if the property with role "reference" has the keyword "x-ogc-collectionId" with a string value (a fixed collection).
+^|A |In the profile "rel-as-key" (`\http://www.opengis.net/def/profile/OGC/0/rel-as-key`) a reference in the response SHALL be represented by the `resourceId` of the referenced resource (a string or integer, depending on the type of the identifier property in the referenced collection), if the property with role "reference" has the keyword "x-ogc-collectionId".
 |===
 
 [[example_14_1]]
@@ -67,7 +67,7 @@ The examples in this Clause use the <<example_9_1,example road accident feature
 ====
 
 :req: rel-as-uri
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
@@ -106,7 +106,7 @@ The examples in this Clause use the <<example_9_1,example road accident feature
 ====
 
 :req: rel-as-link
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
@@ -156,7 +156,7 @@ Servers will typically not support the profile "rel-as-link" for media types tha
 "rel-as-link" will typically be the most useful representation, if a human user interacts with the resource. This is because of the possibility to include a descriptive label of the referenced resource. Of course, this only applies if the server can provide a meaningful title for each link, in which case this information can help the user to understand the referenced resource.
 
 :rec: default
-[#{req-class}_{rec}]
+[#rec_{req-class}_{rec}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Recommendation {counter:rec-num}* |/rec/{req-class}/{rec}
diff --git a/extensions/schemas/standard/clause_15_profile_codelists.adoc b/extensions/schemas/standard/clause_15_profile_codelists.adoc
@@ -21,23 +21,23 @@ The two profiles are:
 |===
 
 :req: consistency
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
 ^|A |All codelist-valued properties in a schema SHALL use the same profile. 
 |===
 
 :rec: profile-link-header
-[#{req-class}_{rec}]
+[#rec_{req-class}_{rec}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Recommendation {counter:rec-num}* |/rec/{req-class}/{rec}
 ^|A |The response SHOULD include a link to the applied codelist profile in the HTTP response headers.
 |===
 
 :req: codelist-inline
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
@@ -46,7 +46,7 @@ The two profiles are:
 |===
 
 :rec: codelist-inline-title
-[#{req-class}_{rec}]
+[#rec_{req-class}_{rec}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Recommendation {counter:rec-num}* |/req/{req-class}/{rec}
@@ -88,7 +88,7 @@ The two profiles are:
 ====
 
 :req: codelist-ref
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
diff --git a/extensions/schemas/standard/clause_16_profile_domains.adoc b/extensions/schemas/standard/clause_16_profile_domains.adoc
@@ -51,23 +51,23 @@ The valid domain is static and can be cached for longer periods of time. Dependi
 |===
 
 :req: consistency
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
 ^|A |All properties with constraint keywords in a schema SHALL use the same profile. 
 |===
 
 :rec: profile-link-header
-[#{req-class}_{rec}]
+[#rec_{req-class}_{rec}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Recommendation {counter:rec-num}* |/rec/{req-class}/{rec}
 ^|A |The response SHOULD include a link to the applied domain profile in the HTTP response headers.
 |===
 
 :req: actual-domain
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
diff --git a/extensions/schemas/standard/clause_7_schemas.adoc b/extensions/schemas/standard/clause_7_schemas.adoc
@@ -21,7 +21,7 @@ The schema represents a logical model, independent of the format in which the da
 === Schema representation
 
 :req: json-schema
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
@@ -36,17 +36,18 @@ The schema represents a logical model, independent of the format in which the da
 In addition to the JSON Schema data types, geospatial data typically also uses spatial and temporal data types.
 
 :req: properties
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
 ^|A |Each property SHALL include a "type" member, except for spatial properties.
 ^|B |Each spatial property SHALL not include a "type" or "$ref" member.
 ^|C |Each spatial property SHALL include a "format" member with a string value "geometry", followed by a hyphen, followed by the name of the geometry type in lower case. I.e., the values for the core Simple Feature geometry types are: "geometry-point", "geometry-multipoint", "geometry-linestring", "geometry-multilinestring", "geometry-polygon", "geometry-multipolygon", and "geometry-geometrycollection". In addition, the following special values are supported: "geometry-any" as the wildcard for any geometry type, "geometry-point-or-multipoint" for a Point or MultiPoint, "geometry-linestring-or-multilinestring" for a LineString or MultiLineString, and "geometry-polygon-or-multipolygon" for a Polygon or MultiPolygon.
-^|D |Each temporal property SHALL be a "string" literal with the appropriate format (e.g., "date-time" or "date" for instances, depending on the temporal granularity).
-^|E |As a general rule, if the data type of a property has to be more specific than the JSON Schema data types ("number", "integer", "string"), the "format" keyword SHALL be used.
-^|F |Properties that are only applicable when creating new data or updating existing data SHALL include "writeOnly: true".
-^|G |Properties that are only applicable when data is fetched SHALL include "readOnly: true".
+^|D |Each temporal property that represents an instant (including the start or end of an interval) SHALL be a "string" literal with the appropriate format (e.g., "date-time" or "date", depending on the temporal granularity).
+^|E |Each temporal property that represents an interval SHALL either be a "string" literal with format "interval-iso8601" (two instants with the same granularity separated by a "/") or an array with format "interval-array" consisting of two "string"s representing the interval start and end instants. In both variants, unbounded interval ends are represented by the string "..".
+^|F |As a general rule, if the data type of a property has to be more specific than the JSON Schema data types ("number", "integer", "string"), the "format" keyword SHALL be used.
+^|G |Properties that are only applicable when creating new data or updating existing data SHALL include "writeOnly: true".
+^|H |Properties that are only applicable when data is fetched SHALL include "readOnly: true".
 |===
 
 The following recommendations are intended to simplify parsing a schema and to help understanding the meaning and representation of the properties:
@@ -88,7 +89,7 @@ NOTE: The OGC format register needs to be established.
 In order to be able to map the logical schema to a format-specific schema, extensions to the JSON Schema vocabulary are needed.
 
 :req: additional-keywords
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
@@ -100,7 +101,7 @@ CAUTION: The next version of JSON Schema will likely restrict the use of additio
 ==== Properties with a specific role
 
 :req: role
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
@@ -109,7 +110,7 @@ CAUTION: The next version of JSON Schema will likely restrict the use of additio
 |===
 
 :req: role-id
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
@@ -127,7 +128,7 @@ For cases, where the properties of the resource should be ordered in some repres
 - the representation of the data in a format that requires a specific order of properties (e.g., XML based on an XML Schema that uses a `sequence` for the property elements).
 
 :req: property-seq
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
@@ -136,7 +137,7 @@ For cases, where the properties of the resource should be ordered in some repres
 |===
 
 :rec: property-seq-unique
-[#{req-class}_{rec}]
+[#rec_{req-class}_{rec}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Recommendation {counter:rec-num}* |/req/{req-class}/{rec}
@@ -148,7 +149,7 @@ For cases, where the properties of the resource should be ordered in some repres
 In geospatial data, numeric property values often represent a measurement and have a unit of measure. For fixed units, this can be expressed in the schema using the keyword "x-ogc-unit".
 
 :req: unit
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
@@ -169,7 +170,7 @@ NOTE: For example, the value for hectopascal is `hPa` in UCUM and `\https://qudt
 ==== Semantic definition of a property
 
 :req: definition
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
@@ -180,7 +181,7 @@ NOTE: For example, the value for hectopascal is `hPa` in UCUM and `\https://qudt
 ==== Special null values
 
 :req: nullvalues
-[#{req-class}_{req}]
+[#req_{req-class}_{req}]
 [width="90%",cols="2,7a"]
 |===
 ^|*Requirement {counter:req-num}* |/req/{req-class}/{req}
diff --git a/extensions/schemas/standard/clause_8_advanced_property_roles.adoc b/extensions/schemas/standard/clause_8_advanced_property_roles.adoc
diff --git a/extensions/schemas/standard/clause_9_references.adoc b/extensions/schemas/standard/clause_9_references.adoc
