OGC Architecture Board Review and Public Comment

[maxrjones]

Summary

Submit the GeoZarr candidate Standard to the OGC Architecture Board (OAB) for technical review, followed by a public comment period.

Background

Per the OGC Standards Process, candidate Standards undergo OAB review before being put to a vote. The OAB reviews the specification for technical soundness, consistency with other OGC standards, and adherence to OGC policies.

From the GeoZarr charter (Section 4):

"The SWG expects to have a candidate Standard ready for OGC Architecture Board (OAB) review and public comment within nine months of creation of the SWG."

Process Overview

1. Pre-Submission Checklist

Before submitting to OAB:

• Candidate Standard document complete in OGC format
• All v1-rc milestone issues resolved
• Reference implementations documented
• SWG internal review completed

2. OAB Submission

• Submit candidate Standard to OAB via OGC portal
• Provide supporting materials (examples, test suite, implementation reports)
• Designate SWG contact for OAB questions

3. OAB Review

The OAB will review for:

• Technical soundness and completeness
• Consistency with OGC standards baseline
• Relationship to other standards (Zarr, CF conventions, etc.)
• IPR compliance

Timeline: Typically 4-6 weeks

4. Public Comment Period

• Candidate Standard published for public comment
• Comment period announced (typically 30-60 days)
• Comments collected via OGC portal

5. Comment Resolution

• All comments reviewed by SWG
• Responses prepared for each comment
• Necessary revisions made to specification
• Comment resolution document prepared

Acceptance Criteria

• OAB review completed with no blocking issues
• Public comment period completed
• All comments addressed with documented responses
• Any required revisions incorporated
• OAB approval to proceed to vote

What to Expect

For SWG Members:

• Be available to respond to OAB questions
• Review and respond to public comments
• Participate in comment resolution discussions

For Community:

• Public comment period is an opportunity to provide feedback
• Comments should be specific and actionable
• All comments will receive a documented response

Dependencies

• All v1-rc issues must be complete

References

• Technical Committee Policies and Procedures