Phase 6: Pre-Submission Audit - CSAPI Implementation vs OGC Specs & Maintainer Feedback

[Sam-Bolling]

Phase 6: Pre-Submission Audit - Master Plan

Status: 🔴 NOT STARTED (0/18 Complete)
Created: Jan 26, 2026
Target: Complete before upstream PR to camptocamp/ogc-client

---

Overview

This master issue coordinates the comprehensive audit of the Connected Systems API implementation across 18 detailed verification plans before upstream submission. Each item below links to a dedicated child issue containing detailed checklists and verification methodology.

---

Audit Progress Dashboard

Tier 1: OGC Official Specifications (NORMATIVE COMPLIANCE) ⚖️

Status: 0/8 Complete

• T1.1 Part 1 HTML Specification 🔴 NOT STARTED
• T1.2 Part 1 OpenAPI YAML 🔴 NOT STARTED
• T1.3 Part 2 HTML Specification 🔴 NOT STARTED
• T1.4 Part 2 OpenAPI YAML 🔴 NOT STARTED
• T1.5 SWE Common 3.0 HTML Specification 🔴 NOT STARTED
• T1.6 SWE Common 3.0 JSON Schemas 🔴 NOT STARTED
• T1.7 SensorML 3.0 HTML Specification 🔴 NOT STARTED
• T1.8 SensorML 3.0 JSON Schemas 🔴 NOT STARTED

Tier 2: Maintainer Requirements (CRITICAL INTEGRATION) 🎯

Status: 0/2 Complete

• T2.9 PR #131 Senior Dev Feedback 🔴 NOT STARTED
• T2.10 PR #114 Pattern Alignment 🔴 NOT STARTED

Tier 3: Reference Implementations (VALIDATION) ✓

Status: 0/3 Complete

• T3.11 osh-js Reference Library 🔴 NOT STARTED
• T3.12 oscar-viewer TypeScript Implementation 🔴 NOT STARTED
• T3.13 osh-viewer JavaScript Implementation 🔴 NOT STARTED

Tier 4: Upstream Patterns (CONSISTENCY) 🔄

Status: 0/2 Complete

• T4.14 WFS Implementation Pattern 🔴 NOT STARTED
• T4.15 STAC Implementation Pattern 🔴 NOT STARTED

Tier 5: Exploratory Work Baseline (IMPROVEMENT DOCUMENTATION) 📊

Status: 0/3 Complete

• T5.16 PR #131 Initial Submission Baseline 🔴 NOT STARTED
• T5.17 Homework Repository History 🔴 NOT STARTED
• T5.18 Cleaned Repository Evolution 🔴 NOT STARTED

---

Implementation Context

• Repository: OS4CSAPI/ogc-client-CSAPI
• Lines of Code: ~10,000 TypeScript
• Test Coverage: 549 tests, 84.20% overall, 97.63% resources.ts
• Implementation Period: Jan 24-25, 2026
• Key Features:
  • 70+ URL builders and parsers
  • Full CRUD operations (create/read/update/delete)
  • Batch operations (addMembers, removeMembers, etc.)
  • Query builders (bbox, datetime, properties, limit, offset)
  • Nested resource resolution
  • JSON/GeoJSON format support
  • Comprehensive link relation handling

---

Audit Approach

Evidence Requirements

Each audit must provide:

1. Specification References: Section/page numbers from official docs
2. Code Evidence: File paths and line numbers
3. Test Coverage: Test file references proving verification
4. Gap Documentation: Any non-compliance with remediation plans

Pass Criteria

• ✅ All specification requirements implemented
• ✅ Patterns match PR #114 and upstream conventions
• ✅ Maintainer feedback addressed
• ✅ Reference implementations aligned
• ✅ Test coverage validates behavior
• ✅ No critical gaps remain

Execution Flow

1. Execute audits (can be done in parallel)
2. Document findings in each child issue
3. Identify critical gaps
4. Create remediation action items if needed
5. Re-audit after fixes
6. Final sign-off when all 18 pass

---

Timeline

• Phase 6 Start: Jan 26, 2026
• Audit Completion Target: TBD
• Upstream PR Submission: After all audits pass

---

Related Issues

• Sprint Goal #1 Feedback about using the OGC API - Connected Systems Parts 1& 2 YAML files #1 - Phase 1: Foundation Classes
• Sprint Goal #2 Feedback about connecting OGC API - Features Clients to OGC API - Connected Systems Servers #2 - Phase 2: Endpoint Classes
• Evaluate Interoperability for Generic Features Clients with CSAPI Server #3 - Phase 3: Collection-Level Methods
• OGC Code Sprint 26 End of Day One Consolidated Report #4 - Phase 4: Resource-Level Methods
• OGC Code Sprint 26 End of Day Two Consolidated Report #5 - Phase 5: Search & Test Coverage

---

Notes

• Each child issue (Audit T1.1: Part 1 HTML Specification #17-34) contains detailed checklists and verification methodology
• Audit findings and evidence should be added as comments in child issues
• Update checkboxes in this master plan as audits complete
• Critical gaps may generate new action item issues