Detailed planning BP document

From Spatial Data on the Web Working Group
Jump to: navigation, search

Work on the Spatial Data on the Web Best Practices is done in shortish cycli we call sprints. Three more sprints are expected until the end of April, resulting in a new version of the BP document every 6 weeks or so. Outline:

December 2016 - beginning of February 2017

Sprint plan:

  • Action 242: Restructure the document to move the summary to the top and remove the template.
  • Action 232, 233, and 234: Further work on BP 4 (indexable spatial data), including addition of examples and a description on what is indexed.
  • Action 247: Rewrite of section 7 Coordinate Reference Systems.
  • Action 248: Further work on BP7 (use HTTP URIs) + BP14 (Links to related resources) based on discussion at the december 2016 face to face meeting in London.
  • Action 240: Remove BP17 (crowdsourcing) from BP document.
  • Outreach to get review from wider public at the end of this sprint (Ed).
    • Including horizontal review by W3C groups on accessibility, security, internationalization etc. (Phil)

Backlog - To do

February - mid March 2017:

Dataset metadata

  • BP2: Remove (but retain stub for now so numbering of BPs does not change) and move content / problem description to Conclusions where we will discuss remaining gaps.
  • BP2 owner: Jeremy Tandy

Spatial data vocabularies and file-formats


  • BP10: priority provide guidance on choice of vocabulary for describing spatial data; inevitably will need to talk about file formats too; aim to include @BillRobert’s thoughts about “balancing performance against operating costs” when making those choices; key aspect is the use of MULTIPLE FORMATS (and/or multiple vocabularies) - see DWBP BP14: Provide data in multiple formats
  • BP10 owner: Bill Roberts


  • do we want/need to introduce a “samePlaceAs” property?
  • Jeremy Tandy to seek consensus via mailing list


  • BP14: describing the links between spatial things is dependent on the vocabulary choices (see BP10); update in light of amendments to BP10 etc.; add references to Appendix B “auth sources of geographic identifiers”; @lars said he check up about the Beacon format; we also need to consider the “hypermedia” implications of links (e.g. what can we do to help data consumers know what to do with the resource at the end of the link); also see below proposal to delete BP15 and migrate any remaining useful content from there into BP14
  • incorporate the following "linking" topics from BP9: vocabularies / properties for describing topological spatial relationships / “spatial predicates” (e.g. equals, disjoint, intersects, touches, within, contains, overlaps and crosses); lack of evident best practice in using common vocabularies / properties for direction and distance relationships (distance relations “at”, “nearby” & “far away”; directional relations “left”, “in front of” & “astern”)
  • BP14 owner: Jeremy Tandy



  • Decide if Appendix A still provides value; if so then update else remove it
  • move to following sprint?

Spatial data access and APIs

  • BP11: use of “convenience APIs” is covered in DWBP §8.10.1; review SDW best practice to determine what is different (seems to be talking about how you might conveniently expose data in an SDI through Web-friendly APIs?) and update content such that it ties back _properly_ to DWBP
  • BP11 owner: Clemens Portele (assisted by Bart van Leeuwen)
  • Remove contents of BP12 and BP13 but retain stubs in order to keep BP numbering intact for now.
  • Remove section 12.8 Dealing with large datasets - this is already sufficiently well covered in the revised BP11.

Coordinate Reference Systems

describing properties that change over time

  • BP6 is pretty much complete except for two examples (approach #2: version history of change to extent of city of Amsterdam, approach #3: GPS track (data stream?) from an alpine marathon runner) … @linda thinks Geonovum might be able to craft these examples
  • BP6 owner: Linda van den Brink

Editorial

  • note: the editors plan to re-order the best practices during the next sprint; so where we are removing best practices this time around we will leave empty "stubs" so make sure that the numbering remains consistent for the upcoming WD release ... @jtandy thinks that his brain can't cope with number changes just at the moment!


  • update CRS introductory material to refer to engineering CRS (used for built environment) and relating these back to geographic CRS; and that SRS used in things like cellular microscopy is out of scope
  • owner: Ed Parsons


  • BP9: update to reflect use of local and relative coordinate reference systems used to reflect the built environment; reflecting the best practices evident in the large body of information already published about built infrastructure; noting that sensors are often described using these "engineering" CRS; objective is to provide sufficient information for users (?) to relate the engineering coordinate positions to geographic coordinate positions; include insights from AR community and their "egocentric" perspective (ref. discussions with @cperey; ACTION #128); which is increasingly important in order to see spatial things rendered / represented in AR tools & browsers
  • BP9 owner: Josh Lieberman


  • Remove BP2: (provide context required to interpret data values) We had a HUGE discussion on the mailing-list about UoM etc., but don’t think we made any conclusions; currently this best practice is vague and not actionable; propose to remove BP2 in this sprint _unless_ someone can write content to make this (i) specifically relevant to spatial data, (ii) actionable, and (iii) best practice that is evident in the wild
  • Jeremy Tandy to seek consensus via mailing list


  • Remove BP15: (use links to find related data) this is (i) the flip side of BP14, and doesn’t really say anything new, (ii) consumer oriented rather than for data publishers (so out of our amended scope) … migrate any useful content to BP14 and delete
  • owner: Jeremy Tandy


  • Remove §14 Narrative but parse for useful information that may be incorporated elsewhere in the BP doc before we discard it to the annals of GitHub history
  • owner: Linda van den Brink


  • Remove §13 Other best practices - pending merge of BP16 into BP10, and consolidation of CRS material in BP3 and BP17
  • owner: Linda van den Brink


  • Resolve the 3 ReSpec warnings currently showing on the Editor's Draft; this may require the material on privacy concerns (added following discussion during London F2F) to be extracted from the Scope and put into a separate section.
  • owner: Linda van den Brink


Mid March - end of April 2017:

Only editorial changes - nothing substantive


"how to use" section


Provide Geometries in a web friendly way


Spatial data vocabularies and file-formats

  • BP10: - work continues
  • BP10 owner: Bill Roberts


Positional accuracy


“how to test”, "Evidence" (e.g. Requirements x-ref), "Benefits" (do we even need this section in the BP template?) and examples

  • strong drive to get these populated … but if you’ve got material, don’t wait, please provide it NOW!


open ISSUES

Review public comments


Editorial

  • Add list of namespace prefixes of the vocabularies/schemas used in the BP
  • Update Appendix C (cross ref with requirements): @payam is reviewing both SDW-BP and DWBP against the requirements in the UCR doc to make sure we’ve covered everything … and if we find gaps, we’ll need to call these out explicitly
  • Add new Appendix with mapping from SDWBP to DWBP: @payam is drafting material on the wiki at BP Mapping
  • Populate §15 Conclusions once we have the majority of the content in place; should we talk about the big changes that these BPs drive? or gaps in best practice? or echo DWBP’s §10 Data on the web challenges graphic? … topic for discussion at Delft F2F
  • Re-order the best practices

May - June 2017:

  • Time buffer period
  • Publish final version of BP document.