opengeospatial · jerstlouis · Nov 25, 2024 · Sep 30, 2024 · Nov 25, 2024
diff --git a/...s/workflows/recommendations/collection-output/PER_collection-output_expiry.adoc b/...s/workflows/recommendations/collection-output/PER_collection-output_expiry.adoc
@@ -1,7 +1,7 @@
 [permission]
 ====
 [%metadata]
-label:: /per/collection-output/expiry
+identifier:: /per/collection-output/expiry
 description:: Collection output resources are ephemeral in nature:
 part:: An Implementation MAY return a _410 Gone_ HTTP status code for resources associated with a previous _Collection Output_ response (i.e., a landing page, a collection, or any resources linked from either) if a significant period of time has elapsed since both the original request and any further associated data access request from the client.
 part:: An Implementation MAY redirect a client re-posting an identical or equivalent execution request for _Collection Output_ (e.g., after having received a 410 gone status) to the same location as a previous execution (expired and reinstated, or still valid), or to a new location.

diff --git a/...flows/requirements/collection-input/REQ_collection-input_collection-access.adoc b/...flows/requirements/collection-input/REQ_collection-input_collection-access.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/collection-input/collection-access
+identifier:: /req/collection-input/collection-access
 description:: For executing workflow definitions referencing a collection as an input to a process:
 part:: The Implementation SHALL support accessing local collections (as defined by _OGC API - Common - Part 2: Geospatial data_) accessible using at least one OGC API data access mechanisms (e.g., _OGC API - Tiles, Coverages, DGGS, Features, EDR, Maps_) as an input to a process.
 ====

diff --git a/...s/requirements/collection-input/REQ_collection-input_referenced-collection.adoc b/...s/requirements/collection-input/REQ_collection-input_referenced-collection.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/collection-input/referenced-collection
+identifier:: /req/collection-input/referenced-collection
 description:: For referencing a collection as an input to a process:
 part:: The Implementation SHALL support execution requests containing a `"collection"` key and a corresponding URI or Relative-URI value identifying an OGC API collection as an input to a process.
 part:: The Implementation SHALL interpret Relative-URIs as relative to the parent process within which the containing collection object is nested.

diff --git a/...s/requirements/collection-output/REQ_collection-output_collection-response.adoc b/...s/requirements/collection-output/REQ_collection-output_collection-response.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/collection-output/collection-response
+identifier:: /req/collection-output/collection-response
 description:: For initiating the execution of a workflow and retrieving its output as an OGC API collection:
 part:: For requests generating or selecting a single output, the Implementation SHALL return a 303 _See Other_ HTTP status code together with a _Location:_ response header redirecting to a collection description document as defined in _OGC API - Common - Part 2: Geospatial data_ as a response to a request specifying a `response=collection` query parameter.
 part:: For requests generating multiple outputs which do not select a particular output, the Implementation SHALL return a 400 status error as a response to a request specifying a `response=collection` query parameter.

diff --git a/...equirements/collection-output/REQ_collection-output_data-access-mechanisms.adoc b/...equirements/collection-output/REQ_collection-output_data-access-mechanisms.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/collection-output/data-access-mechanisms
+identifier:: /req/collection-output/data-access-mechanisms
 description:: For triggering processing and returning resulting output data as a response to data access requests:
 part:: The Implementation SHALL support at least one OGC API data access mechanisms (e.g., _OGC API - Tiles, Coverages, DGGS, Features, EDR, Maps_) corresponding to the links returned from a a `response=collection` or `response=landingPage` request.
 part:: The Implementation SHALL trigger the processing required to respond to the request with considerations for the area, time and/or resolution of interest associated with the request.

diff --git a/...requirements/collection-output/REQ_collection-output_landing-page-response.adoc b/...requirements/collection-output/REQ_collection-output_landing-page-response.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/collection-output/landing-page-response
+identifier:: /req/collection-output/landing-page-response
 description:: For initiating the execution of a workflow and retrieving its output as an OGC API dataset landing page:
 part:: The Implementation SHALL return a 303 _See Other_ HTTP status code together with a _Location:_ response header redirecting to an OGC API dataset landing page as defined in _OGC API - Common - Part 1: Core_ as a response to a request specifying a `response=landingPage` query parameter.
 part:: The landing page towards which the client is redirected SHALL contain at link to a list of available collections at `../collections` as defined in _OGC API - Processes - Part 2: Geospatial data_.

diff --git a/...orkflows/requirements/collection-output/REQ_collection-output_landing-page.adoc b/...orkflows/requirements/collection-output/REQ_collection-output_landing-page.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/collection-output/landing-page
+identifier:: /req/collection-output/landing-page
 description:: For initiating the execution of a workflow and retrieving its output as an OGC API dataset landing page:
 part:: The Implementation SHALL return an OGC API dataset landing page as defined in _OGC API - Common - Part 1: Core_ as a response to a request specifying a `response=landingPage` query parameter.
 part:: The returned landing page SHALL contain at link to a list of available collections at `../collections` as defined in _OGC API - Processes - Part 2: Geospatial data_.

diff --git a/...uirements/collection-output/REQ_collection-output_response-query-parameter.adoc b/...uirements/collection-output/REQ_collection-output_response-query-parameter.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/collection-output/response-query-parameter
+identifier:: /req/collection-output/response-query-parameter
 description:: For initiating the execution of a workflow and retrieving its output as an OGC API collection:
 part:: The Implementation SHALL support the `response` query parameter with `collection` and `landingPage` as possible values.
 ====
diff --git a/...workflows/requirements/cwl-workflows/REQ_cwl-workflows_adhoc-cwl-execution.adoc b/...workflows/requirements/cwl-workflows/REQ_cwl-workflows_adhoc-cwl-execution.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/cwl-workflows/adhoc-cwl-execution
+identifier:: /req/cwl-workflows/adhoc-cwl-execution
 description:: For executing a workflow defined using the Common Workflow Language (CWL) definition:
 part:: The Implementation SHALL support ad-hoc execution of a CWL workflow definition (`Content-Type: application/cwl+json`) POSTed to `/processes/CWL/execution`.
 ====

diff --git a/...uirements/deployable-workflows/REQ_deployable-workflows_deploying-workflow.adoc b/...uirements/deployable-workflows/REQ_deployable-workflows_deploying-workflow.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/deployable-workflows/deploying-workflow
+identifier:: /req/deployable-workflows/deploying-workflow
 description:: For deploying workflow definitions defined as an execution request:
 part:: The Implementation SHALL support deploying a workflow definition as a process using the POST method mechanism described in _OGC API - Processes - Part 2: Deploy, Replace, Undeploy_ with a payload consisting of an _OGC API - Processes - Part 1: Core_ execution request (`Content-Type: application/json`, unless a specific media type execution requests is allocated), with support for any any extensions defined in this specification for which conformance is declared.
 part:: If the _OGC Application Package_ conformance class is supported, the Implementation SHALL also support deploying a workflow definition as a process using the POST method mechanism described in _OGC API - Processes - Part 2: Deploy, Replace, Undeploy_ with the `executionUnit` of the OGC Application Package payload (`Content-Tyep: application/ogcapppkg+json`) consisting of an _OGC API - Processes - Part 1: Core_ execution request, with support for any any extensions defined in this specification for which conformance is declared.

diff --git a/...rements/deployable-workflows/REQ_deployable-workflows_parameterized-inputs.adoc b/...rements/deployable-workflows/REQ_deployable-workflows_parameterized-inputs.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/deployable-workflows/parameterized-inputs
+identifier:: /req/deployable-workflows/parameterized-inputs
 description:: For deploying workflow definitions defined as an execution request:
 part:: The Implementation SHALL support defining a parameterizable input using the `"$input"` key and a corresponding input name value as part of an input to a process (within the `inputs` of an execution request or nested input process).
 part:: The deployed process SHALL have a corresponding input for each input selected using the `"$input"` using the specified name.

diff --git a/...equirements/deployable-workflows/REQ_deployable-workflows_selected-outputs.adoc b/...equirements/deployable-workflows/REQ_deployable-workflows_selected-outputs.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/deployable-workflows/parameterized-outputs
+identifier:: /req/deployable-workflows/parameterized-outputs
 description:: For deploying workflow definitions defined as an execution request:
 part:: The Implementation SHALL support selecting specific outputs of processess involved in workflow definition using the `"$output"` key and a corresponding output name value as part of an output of a process (within the `outputs` of an execution request or nested input process).
 part:: The deployed process SHALL have a corresponding output for each output selected using the `"$output"` using the specified name.

diff --git a/...uirements/input-fields-modifiers/REQ_input-fields-modifiers_derived-fields.adoc b/...uirements/input-fields-modifiers/REQ_input-fields-modifiers_derived-fields.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/input-fields-modifiers/derived-fields
+identifier:: /req/input-fields-modifiers/derived-fields
 description:: For selecting and/or deriving new fields from the input data to a process:
 part:: As part of an input to a process, the Implementation SHALL support specifying a `"properties"` key and a corresponding set of selected fields as an array of field names.
 part:: As part of an input to a process, the Implementation SHALL support specifying a `"properties"` key and a corresponding set of derived fields expressions as a key / value pair object mapping expressions to field names.

diff --git a/...s/requirements/input-fields-modifiers/REQ_input-fields-modifiers_filtering.adoc b/...s/requirements/input-fields-modifiers/REQ_input-fields-modifiers_filtering.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/input-fields-modifiers/filtering
+identifier:: /req/input-fields-modifiers/filtering
 description:: For filtering the data coming in as an input to a process:
 part:: The Implementation SHALL support specifying a `"filter"` key and a corresponding filter predicate as part of an input to a process.
 part:: The Implementation SHALL support one or more expression languages to define the filter, such as the OGC Common Query Language (CQL2).

diff --git a/...ows/requirements/input-fields-modifiers/REQ_input-fields-modifiers_sorting.adoc b/...ows/requirements/input-fields-modifiers/REQ_input-fields-modifiers_sorting.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/input-fields-modifiers/sorting
+identifier:: /req/input-fields-modifiers/sorting
 description:: For sorting the input data to a process according to its data fields:
 part:: The Implementation SHALL support specifying a `"sortBy"` key and a corresponding comma-separated sequence of expressions defining the order in which to sort the data coming in as an input to a process.
 part:: The Implementation SHALL support one or more expression languages to define the sorting expressions, such as the OGC Common Query Language (CQL2).

diff --git a/...flows/requirements/nested-processes/REQ_nested-processes_process-execution.adoc b/...flows/requirements/nested-processes/REQ_nested-processes_process-execution.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/nested-processes/process-execution
+identifier:: /req/nested-processes/process-execution
 description:: For executing workflow definitions referencing a nested process:
 part:: The Implementation SHALL support executing local processes which can be executed using _OGC API - Process - Part 1: Core_ as a process nested as an input to another process.
 part:: The Implementation SHALL consider the selected output (using the "outputs" key), or default to the only or first output of the process as the input.

diff --git a/...lows/requirements/nested-processes/REQ_nested-processes_referenced-process.adoc b/...lows/requirements/nested-processes/REQ_nested-processes_referenced-process.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/nested-processes/referenced-process
+identifier:: /req/nested-processes/referenced-process
 description:: For referencing a process as an input to another process:
 part:: The Implementation SHALL support execution requests containing a `"process"` key and a corresponding URI or Relative-URI value identifying a process as an input to another process.
 part:: The Implementation SHALL interpret Relative-URIs as relative to the parent process within which the containing process object is nested.

diff --git a/.../requirements/openeo-workflows/REQ_openeo-workflows_adhoc-openeo-execution.adoc b/.../requirements/openeo-workflows/REQ_openeo-workflows_adhoc-openeo-execution.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/openeo-workflows/adhoc-openeo-execution
+identifier:: /req/openeo-workflows/adhoc-openeo-execution
 description:: For executing a workflow defined as an OpenEO Process Graph:
 part:: The Implementation SHALL support ad-hoc execution of a workflow defined using an OpenEO Process Graph POSTed to `/processes/OpenEO/execution`
 ====

diff --git a/...rements/output-fields-modifiers/REQ_output-fields-modifiers_derived-fields.adoc b/...rements/output-fields-modifiers/REQ_output-fields-modifiers_derived-fields.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/output-fields-modifiers/derived-fields
+identifier:: /req/output-fields-modifiers/derived-fields
 description:: For selecting and/or deriving new fields returned as a data output from a process:
 part:: As part of a nested process or top-level execution request object, the Implementation SHALL support specifying a `"properties"` key and a corresponding set of selected fields as an array of field names.
 part:: As part of a nested process or top-level execution request object, the Implementation SHALL support specifying a `"properties"` key and a corresponding set of derived fields expressions as a key / value pair object mapping expressions to field names.

diff --git a/...requirements/output-fields-modifiers/REQ_output-fields-modifiers_filtering.adoc b/...requirements/output-fields-modifiers/REQ_output-fields-modifiers_filtering.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/output-fields-modifiers/filtering
+identifier:: /req/output-fields-modifiers/filtering
 description:: For filtering the data returned as a data output from  a process:
 part:: The Implementation SHALL support specifying a `"filter"` key and a corresponding filter predicate as part of a nested process or top-level execution request.
 part:: The Implementation SHALL support one or more expression languages to define the filter, such as the OGC Common Query Language (CQL2).

diff --git a/...s/requirements/output-fields-modifiers/REQ_output-fields-modifiers_sorting.adoc b/...s/requirements/output-fields-modifiers/REQ_output-fields-modifiers_sorting.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/output-fields-modifiers/sorting
+identifier:: /req/output-fields-modifiers/sorting
 description:: For sorting the data returned as an output from a process according to its data fields:
 part:: The Implementation SHALL support specifying a `"sortBy"` key and a corresponding comma-separated sequence of expressions defining the order in which to sort the data returned as part of a nested process or top-level execution request.
 part:: The Implementation SHALL support one or more expression languages to defined the sorting expressions, such as the OGC Common Query Language (CQL2).

diff --git a/...s/requirements/remote-collections/REQ_remote-collections_collection-access.adoc b/...s/requirements/remote-collections/REQ_remote-collections_collection-access.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/collection-input/collection-access
+identifier:: /req/remote-collections/collection-access
 description:: For executing workflow definitions referencing a collection as an input to a process:
 part:: The Implementation SHALL support accessing a remote OGC API collection using one or more OGC API data access mechanisms (e.g., _OGC API - Tiles, Coverages, DGGS, Features, EDR, Maps_...) as an input to a process.
 ====

diff --git a/...quirements/remote-collections/REQ_remote-collections_referenced-collection.adoc b/...quirements/remote-collections/REQ_remote-collections_referenced-collection.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/remote-collections/referenced-collection
+identifier:: /req/remote-collections/referenced-collection
 description:: For referencing a remote collection as an input to a process:
 part:: The Implementation SHALL support execution requests containing a `"collection"` key and a corresponding URI or Relative-URI value identifying an authorized OGC API collection as an input to a process.
 part:: If the Implementation conforms to the _Nested Process_ conformance class, it SHALL also support execution requests containing a `"process"` key and a corresponding URI or Relative-URI value identifying an authorized remote process supporting the _Collection Output_ conformance class as an input to another process.

diff --git a/...irements/remote-core-processes/REQ_remote-core-processes_process-execution.adoc b/...irements/remote-core-processes/REQ_remote-core-processes_process-execution.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/nested-processes/process-execution
+identifier:: /req/remote-core-processes/process-execution
 description:: For executing workflow definitions referencing a nested remote process:
 part:: The Implementation SHALL support executing remote processes which can be executed using _OGC API - Process - Part 1: Core_ as a process nested as an input to another process.
 part:: The Implementation SHALL support executing remote processes and retrieving their output using the _Core_ conformance class of the _OGC API - Processes - Part 1: Core_.

diff --git a/...rements/remote-core-processes/REQ_remote-core-processes_referenced-process.adoc b/...rements/remote-core-processes/REQ_remote-core-processes_referenced-process.adoc
@@ -1,7 +1,7 @@
 [requirement]
 ====
 [%metadata]
-label:: /req/nested-processes/referenced-process
+identifier:: /req/remote-core-processes/referenced-process
 description:: For referencing a remote process as an input to another process:
 part:: The Implementation SHALL support execution requests containing a `"process"` key and a corresponding URI or Relative-URI value identifying an authorized remote process as an input to another process.
 ====

diff --git a/extensions/workflows/requirements/requirements_class_collection-input.adoc b/extensions/workflows/requirements/requirements_class_collection-input.adoc
@@ -2,7 +2,7 @@
 [requirements_class]
 ====
 [%metadata]
-label:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/collection-input
+identifier:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/collection-input
 subject:: Collection Input
 inherit:: http://www.opengis.net/spec/ogcapi-processes-1/1.0/req/core
 inherit:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/input-fields-modifiers (optional)

diff --git a/extensions/workflows/requirements/requirements_class_collection-output.adoc b/extensions/workflows/requirements/requirements_class_collection-output.adoc
@@ -2,7 +2,7 @@
 [requirements_class]
 ====
 [%metadata]
-label:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/collection-output
+identifier:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/collection-output
 subject:: Collection Output
 inherit:: http://www.opengis.net/spec/ogcapi-processes-1/1.0/req/core
 inherit:: http://www.opengis.net/spec/ogcapi-common-2/1.0/req/collections

diff --git a/extensions/workflows/requirements/requirements_class_cwl-workflows.adoc b/extensions/workflows/requirements/requirements_class_cwl-workflows.adoc
@@ -2,7 +2,7 @@
 [requirements_class]
 ====
 [%metadata]
-label:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/cwl-workflows
+identifier:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/cwl-workflows
 subject:: Common Workflow Language Definitions
 inherit:: http://www.opengis.net/spec/ogcapi-processes-1/1.0/req/core
 inherit:: Common Workflow Language <<Common_Workflow_Language>>

diff --git a/extensions/workflows/requirements/requirements_class_deployable-workflows.adoc b/extensions/workflows/requirements/requirements_class_deployable-workflows.adoc
@@ -2,7 +2,7 @@
 [requirements_class]
 ====
 [%metadata]
-label:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/deployable-workflows
+identifier:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/deployable-workflows
 subject:: Deployable Workflows
 inherit:: http://www.opengis.net/spec/ogcapi-processes-2/0.0/req/deploy-replace-undeploy
 inherit:: http://www.opengis.net/spec/ogcapi-processes-2/0.0/req/ogcapppkg (optional)

diff --git a/extensions/workflows/requirements/requirements_class_input-fields-modifiers.adoc b/extensions/workflows/requirements/requirements_class_input-fields-modifiers.adoc
@@ -2,7 +2,7 @@
 [requirements_class]
 ====
 [%metadata]
-label:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/input-fields-modifiers
+identifier:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/input-fields-modifiers
 subject:: Input Fields Modifiers
 inherit:: http://www.opengis.net/spec/ogcapi-processes-1/1.0/req/core
 inherit:: http://www.opengis.net/spec/ogcapi-features-3/0.0/req/features-filter (optional)

diff --git a/extensions/workflows/requirements/requirements_class_nested-processes.adoc b/extensions/workflows/requirements/requirements_class_nested-processes.adoc
@@ -2,7 +2,7 @@
 [requirements_class]
 ====
 [%metadata]
-label:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/nested-processes
+identifier:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/nested-processes
 subject:: Nested Processes
 inherit:: http://www.opengis.net/spec/ogcapi-processes-1/1.0/req/core
 inherit:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/input-fields-modifiers (optional)

diff --git a/extensions/workflows/requirements/requirements_class_openeo-workflows.adoc b/extensions/workflows/requirements/requirements_class_openeo-workflows.adoc
@@ -2,7 +2,7 @@
 [requirements_class]
 ====
 [%metadata]
-label:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/openeo-workflows
+identifier:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/openeo-workflows
 subject:: OpenEO Process Graphs Workflows
 inherit:: http://www.opengis.net/spec/ogcapi-processes-1/1.0/req/core
 inherit:: OpenEO Process Graphs <<OpenEO_Process_Graphs>>

diff --git a/extensions/workflows/requirements/requirements_class_output-fields-modifiers.adoc b/extensions/workflows/requirements/requirements_class_output-fields-modifiers.adoc
@@ -2,7 +2,7 @@
 [requirements_class]
 ====
 [%metadata]
-label:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/output-fields-modifiers
+identifier:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/output-fields-modifiers
 subject:: Output Fields Modifiers
 inherit:: http://www.opengis.net/spec/ogcapi-processes-1/1.0/req/core
 ====
diff --git a/extensions/workflows/requirements/requirements_class_remote-collections.adoc b/extensions/workflows/requirements/requirements_class_remote-collections.adoc
@@ -2,7 +2,7 @@
 [requirements_class]
 ====
 [%metadata]
-label:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/remote-collections
+identifier:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/remote-collections
 subject:: Remote Collections
 inherit:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/collection-input
 inherit:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/nested-process (optional)

diff --git a/extensions/workflows/requirements/requirements_class_remote-core-processes.adoc b/extensions/workflows/requirements/requirements_class_remote-core-processes.adoc
@@ -2,7 +2,7 @@
 [requirements_class]
 ====
 [%metadata]
-label:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/remote-core-processes
+identifier:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/remote-core-processes
 subject:: Remote Core Processes
 inherit:: http://www.opengis.net/spec/ogcapi-processes-3/0.0/req/nested-processes
 ====