3-Workflows: Fixed duplicate identifiers

opengeospatial · Nov 25, 2024 · ae21066 · ae21066
1 parent 1db8323
commit ae21066
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
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]
-identifier:: /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/...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]
-identifier:: /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]
-identifier:: /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.
 ====