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: #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.
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-processor similar to allow metadata resolution of this distinct JSON content. That would be necessary for cases such as ad-hoc Deploy/Execute (eg: #607) where bothhttps://www.opengis.net/def/profile/OGC/0/ogc-deploy-processandhttps://www.opengis.net/def/profile/OGC/0/ogc-execute-requestcould be simultaneously provided (as separate parts), such to allow disambiguation of the two JSON structures.