opengeospatial / opengeospatial/ogcapi-processes
RFC: Part 2 DRU - Missing Profile URI for deployment
@pvretano is already working on this.
Since Aug 31, 2026.
- Dominant language
- AsciiDoc
- Stars
- 63
- Forks
- 46
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
In Part 1 v2, Profile URIs are defined for the various JSON contents (process description, execution, job status, etc.).
In Part 2, there is no profile provided for the Deploy structure containing processDescription/executionUnit.
I think we should provide a https://www.opengis.net/def/profile/OGC/0/ogc-deploy-process or similar to allow metadata resolution of this distinct JSON content. That would be necessary for cases such as ad-hoc Deploy/Execute (eg: https://github.com/opengeospatial/ogcapi-processes/pull/607) where both https://www.opengis.net/def/profile/OGC/0/ogc-deploy-process and https://www.opengis.net/def/profile/OGC/0/ogc-execute-request could be simultaneously provided (as separate parts), such to allow disambiguation of the two JSON structures.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.