RFC Part 1 Core v2: Per-output Collection Outputs?

This was briefly mentioned during SWG meeting 2026-08-17, and most probably discussed at other times in issues/comments.

Currenly, Part 1: Core (v2) - Collection Output provides disposition for single-output and multi-output processes. However, both seem to assume that everything can be converted to a collection to work. If the process contains multiple outputs, and that different collection handling is needed for each, there is no way to specify which ones are targetted for the output collection creation.

Another issue is that all Collection Output requests currently rely on ?response=collection query. Provided that an execution request is sent with a JSON execute.yaml body, it seems more appropriate to have a response field in the body. The ?response query is relevant in the case of KVP execution.

If per-output selection allowed for distinct Collection Output, using the JSON body becomes even more adequate.
One could do the following:

outputs:
  output-features:
    profile: https://www.opengis.net/def/profile/OGC/0/ogc-collection  # to be defined, acts like response=collection
    format: 
      mediaType: application/json
      schema: https://geojson.org/schema/FeatureCollection.json
  output-log:
    format:
      mediaType: text/plain

Currently, Requirement 70 /req/collection-output/response-response-many requires the use of results.yaml (i.e.: using profile https://www.opengis.net/def/profile/OGC/0/ogc-results), but it is not really clear how "Req 70-D: Each collection output in the response SHALL be a link to a collection description document." is handled when not all outputs are collections-capable/relevant (such as the above output-log case).