gpkg_contents should have title column.

[cclark1984]

Similar to gpkg_data_columns which has a title and a description, I believe it is useful for gpkg_contents to also have a title. "A human-readable formal title for the table_name content"

[jyutzler]

Right now we have "identifier" and "description" (instead of title and abstract). According to the table description these are supposed to be human readable. Isn't that sufficient?

This issue has been sitting out here for almost 18 months. We should make a decision one way or another.

[jyutzler]

I wonder if this can be resolved using views and triggers using the paradigm that is being proposed with a Tile Matrix Set extension. Basically we create an extension with the following:

1. create a gpkgext_contents table that has everything we want
2. copy existing rows from gpkg_contents into gpkgext_contents
3. drop the existing gpkg_contents table
4. create a view called gpkg_contents which recreates the original table
5. create a set of triggers that allows the view to be updated by redirecting the insert statements into gpkgext_contents

[bosborn]

Just an alternate option to consider...

Update the specification with new columns and provide an upgrade script between each GeoPackage version (as needed). Optionally used by implementations to upgrade GeoPackages. If an implementation chooses not to run them, they can continue to operate on the same base columns or check for optional columns. If an implementation chooses to run them, they can operate on the GeoPackage without the need to check for optional columns.

This only works for adding new columns. Would not work for deleting, renaming, or updating existing columns.