Align OGC API - Processes ruleset with latest v2.0 draft (18-062r3) - #813
Merged
Conversation
The Processes rulesets were based on an earlier draft. Reconcile the four
covered conformance classes with the latest v2.0 draft (18-062r3, not yet a
final/published standard):
- Bump conformance-class and requirement URIs from 1.0 to 2.0 (core, job-list,
json, ogc-process-description).
- Fix requirement identifiers to match the spec (slash -> hyphen for
process-exception-no-such-process and the job-results-exception-* rules) and
correct the underscore doc-link anchors.
- Resolve the ogc-process-description v2 schema TODO (point process.yaml at the
master branch, which tracks 2.0; the schemas.opengis.net 2.0 tree is not
published yet).
- Drop the execution POST from the JSON media-type rule; v2 no longer lists it
(execution output is content-negotiated).
- Add the two new statically-checkable requirements: job-result-op-0th (path
/jobs/{jobID}/results/{outputID}/0) and job-results-exception-no-such-output.
- Add type: object to the example results schema so it validates against the
v2 results.yaml, and add the /0 path to the example.
Update and extend tests accordingly.
joostfarla
force-pushed
the
align-processes-ruleset-to-v2
branch
from
July 9, 2026 09:03
27f9da8 to
01edc51
Compare
joostfarla
changed the title
Reconcile the requirement table with 18-062r3: fix the renamed identifiers (process-exception-no-such-process, job-results-exception-*, process-execute-sync-one-default-content, process-execute-success-sync-empty-outputs), and add the missing requirements including the two new statically-checkable rules (job-result-op-0th, job-results-exception-no-such-output).
joostfarla
force-pushed
the
align-processes-ruleset-to-v2
branch
from
July 9, 2026 09:18
074f363 to
fb75463
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #809.
The OGC API — Processes rulesets were based on an earlier draft of 18-062r3. This reconciles the four covered conformance classes with the latest v2.0 draft (18-062r3 is the latest revision, not yet a final/published standard).
Changes
Version bump 1.0 → 2.0 across all four conformance-class URIs and
documentationUrls (core,job-list,json,ogc-process-description). The ruleset-index keys are the conformance-class URIs the linter matches against a server'sconformsTo, so it now matches servers advertising the 2.0 classes.processes-core.tsprocess-exception/no-such-process→process-exception-no-such-process, and the fourjob-results-exception/*→ hyphenatedjob-results-exception-*.…exception_invalid-query-parameter-value,…_results-not-ready,…_results-not-available)./req/core/job-result-op-0th(new path/jobs/{jobID}/results/{outputID}/0) and/req/core/job-results-exception-no-such-output(400 on/jobs/{jobID}/results).processes-json.ts— removed the executionPOSTfrom/req/json/definition; v2 lists only/,/conformance,/processes,/processes/{processID},/jobs/{jobID}(execution output is content-negotiated and need not be JSON).processes-ogc-process-description.ts— resolved the// TODO: Upgrade to v2.0 schema;process.yamlnow points at the v2 schema.examples/processes.json— addedtype: objectto theresultsschema so it validates against v2results.yaml, and added the new/jobs/{jobID}/results/{outputID}/0path.Tests — renamed the three changed rule codes, added tests for the two new rules, and removed the obsolete JSON execution-endpoint test.
Deliberate scope decisions
masterGitHub branch. The v2 schemas atschemas.opengis.net/…/part1/2.0/…are not published yet (r3 is still a draft — they 404).mastertracks the 2.0 revision and is the live source.coreadded ~30 requirements, but most (execution modes, inline-input handling, content negotiation, response headers) aren't observable in an OpenAPI definition, which is all this linter inspects. The brand-new conformance classes (dismiss, oas30/oas31, html, kvp-execute, collection-input/output, remote-collections, callback, query-param-profile) were not scaffolded; this PR aligns the existing coverage to v2. Any follow-up for the additional v2 conformance classes can be tracked separately.Verification
pnpm lint: clean.