Skip to content

Collapse extensions information under single annex #132

Closed

Description

@jyutzler

There are currently a number of separate annexes (J through P) in the specification, each describing a different extension. This information all overlaps with what is in section 3. Since this information is not part of the core, it could all be moved into a single annex.

Activity

  1. added this to the tiles-corrigendum milestone on Aug 14, 2015
  2. jyutzler commented on Aug 18, 2015

    @jyutzler
    ContributorAuthor

    In today's SWG we agreed to do this.

  3. bradh commented on Nov 16, 2015

    @bradh
    Contributor

    If this hasn't already been done, I'd like to ask that it not be applied. This is just churn for no real value - breaks references (e.g. in code samples), and does not make it easier for future implementers.

  4. jyutzler commented on Nov 16, 2015

    @jyutzler
    ContributorAuthor

    I understand your concern here but I don't think it will be a big deal. Section anchor names are automatically generated based on section titles so if entire sections are moved, the anchor names should remain the same.

    Right now the bigger issue is that information regarding a specific extension is scattered around the document. Having to flip back and forth between Section 3 and an annex has proven painful. This will only get worse as new extensions are added, requiring more and more annexes (and forcing the annex IDs to change each time).

  5. bradh commented on Nov 16, 2015

    @bradh
    Contributor

    From the spatialite GeoPackage source:

    gpkg_add_spatial_index.c
    203:                            "'GeoPackage 1.0 Specification Annex L', 'write-only')",
    
    gpkg_add_geometry_triggers.c
    167:                            "'GeoPackage 1.0 Specification Annex N', 'write-only')",
    180:                            "'GeoPackage 1.0 Specification Annex N', 'write-only')",
    

    From libgpkg:

    gpkg/gpkg_db.c
    766:             db_name, table_name, geometry_column_name, "gpkg_rtree_index", "GeoPackage 1.0 Specification Annex L", "write-only"
    
  6. jyutzler commented on Nov 26, 2015

    @jyutzler
    ContributorAuthor

    @bradh I'm sorry but it had to be done. Right now the information about a particular extension is spread across at least 4 different parts of the document. It is unreasonable to expect a reader to be able to find all of the relevant information.

    This is pain for me too. I'm going to have to review every reference in the abstract test suite because they are hard-coded, not linked. I'm sure there are other parts to this that will bite me too.

  7. added a commit that references this issue on Nov 26, 2015
  8. modified the milestones: tiles-corrigendum, on Nov 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions