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.

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

clarify relationship between requirements 4 and 59 #629

Closed
jyutzler opened this issue May 31, 2022 · 2 comments · Fixed by #656
Closed

clarify relationship between requirements 4 and 59 #629

jyutzler opened this issue May 31, 2022 · 2 comments · Fixed by #656
Labels
Substantive Change Requires a minor revision
Milestone

Comments

@jyutzler
Copy link
Contributor

We got a question regarding Requirement 4 being untestable because the GeoPackage was determined to be an Extended GeoPackage as described by Requirement 59. We could make the relationship between these requirements more clear.

@jyutzler jyutzler added the Administrative Change Requires a Corrigendum label May 31, 2022
@jyutzler
Copy link
Contributor Author

This topic came up again during today's CITE SC meeting.

@jyutzler jyutzler added Substantive Change Requires a minor revision and removed Administrative Change Requires a Corrigendum labels Mar 29, 2023
@jyutzler jyutzler added this to the 1.4.0 milestone Mar 29, 2023
@jyutzler
Copy link
Contributor Author

We discussed this again during the March 28 SWG meeting and agreed to relax the Requirement 4. In 2023, GeoPackages aren't particularly viable unless they have at least some extensions. The existence of this requirement, as written, is just confusing people.

The plan is to relax the requirement, specifying the minimum schema for a GeoPackage. We didn't discuss this in the SWG, but in retrospect, I believe it would also be appropriate to indicate that a GeoPackage have at least some content as features, tiles, or attributes. I'll propose it as a warning. We will see how the participants react to that.

This is somewhere in the middle between a substantive change and an administrative change, but since we plan to do a minor revision anyway, the SWG decided to be safe and call it a substantive change.

@jyutzler jyutzler linked a pull request Mar 30, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Substantive Change Requires a minor revision
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant