-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
area/serverCore server (protocols, query, edits)Core server (protocols, query, edits)edition/communityCommunity edition (free)Community edition (free)effort/L🌳 L: 1-2 days (complex feature, multiple components)🌳 L: 1-2 days (complex feature, multiple components)phase/GAGA scopeGA scopepriority/P3📋 Low priority - nice to have in phase, can be deferred📋 Low priority - nice to have in phase, can be deferred
Milestone
Description
Problem
We run OGC CITE conformance tests locally/in CI, but there is no documented path for official OGC certification or published baseline results.
Evidence
- OGC Features conformance guide:
docs/cite-conformance-testing.md:1. - OGC API Tiles conformance guide:
docs/cite-tiles-conformance-testing.md:1.
Goal
Decide whether to pursue formal OGC certification and document the process/baseline results if so.
Tasks
- Decide scope: OGC API Features (Core/Transactions), Tiles, etc.
- Document submission steps and required artifacts.
- Publish baseline conformance results (versions + pass/fail summary).
Acceptance criteria
- Clear go/no‑go decision on certification.
- Documentation updated with submission steps or rationale for deferring.
- Baseline results published if proceeding.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/serverCore server (protocols, query, edits)Core server (protocols, query, edits)edition/communityCommunity edition (free)Community edition (free)effort/L🌳 L: 1-2 days (complex feature, multiple components)🌳 L: 1-2 days (complex feature, multiple components)phase/GAGA scopeGA scopepriority/P3📋 Low priority - nice to have in phase, can be deferred📋 Low priority - nice to have in phase, can be deferred
Type
Projects
Status
Todo