Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migration to full OGC Standard 2: Define an Abstract Test Suite in Annex A #177

Open
chris-little opened this issue Jul 11, 2024 · 0 comments
Open

Migration to full OGC Standard 2: Define an Abstract Test Suite in Annex A #177

chris-little opened this issue Jul 11, 2024 · 0 comments
Labels
Long Term Keeping track of important issues that may not be closed for some time Priority 3 Nice to have V1.0.0 Non-breaking change needed for initial Community Standard

Comments

@chris-little
Copy link
Contributor

For migration from an OGC Community Standard to a full OGC Standard, several things must happen:

  1. Define an Abstract Test Suite (ATS) in an Annex A, indicating how the Conformance Classes and their assertions would be tested.

This is mostly done, as most tests would be validation against the CoverageJSON Schema. Some tests could be just by inspection.
@chris-little chris-little added Long Term Keeping track of important issues that may not be closed for some time Priority 3 Nice to have V1.0.0 Non-breaking change needed for initial Community Standard labels Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Long Term Keeping track of important issues that may not be closed for some time Priority 3 Nice to have V1.0.0 Non-breaking change needed for initial Community Standard
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@chris-little