Missing requirement regarding lowercase identifiers?

[heidivanparys]

According to clause Base,

geopackage/spec/core/1_base.adoc

Line 5 in 50a28dd

All specified table, view, column, trigger, and constraint name values SHALL be lowercase.

identifiers shall be lowercase. However, no separate, explicit, numbered requirement is present in the specification regarding this.

The line above that line also uses normative language, stating

geopackage/spec/core/1_base.adoc

Line 4 in 50a28dd

All gpkg_* tables and views and all tiles user data tables specified in this standard SHALL have only the specified columns and table constraints. Any features user data tables MAY have columns in addition to those specified.

but those statements are enforced by requirements, such as e.g. requirement 10 and requirement 29.

And because there is no explicit requirement, no test is present in the ATS, and GeoPackage files using uppercase or camelcase identifiers can pass the test.

[heidivanparys]

Note: some sample files in https://github.com/opengeospatial/geopackage/tree/gh-pages/data use uppercase identifiers, those should be updated as well if the statement regarding lowercase identifiers is actually a requirement.

[jyutzler]

I think we agreed that we would specify all lowercase for identifiers specified in the standard, but that this constraint does not apply to user-defined identifiers. User-defined identifiers are easily discoverable and must be discovered to be used so this should not be an interoperability issue.

However, I would agree to some additional explanatory text. Any suggestions?

[heidivanparys]

However, I would agree to some additional explanatory text. Any suggestions?

See heidivanparys@9839fa2 for a suggestion.

[jyutzler]

@heidivanparys The SWG concurs with this update. Please issue a pull request and we will accept it.