TPAC 2019 Agenda

From Maps for HTML Community Group Wiki
Jump to: navigation, search

Maps for HTML Community Group - TPAC 2019 Agenda

Venue: W3C TPAC
Location: Fukuoka Japan
Date: September 20, 2019
Time: 8:30 - 10:30

Note: We have 2 hours, and lots to talk about! We have linked to background documents worth reading below, and some discussion will likely continue online after the meeting.

Who we are

5 min


Who has contributed:

  • A global network of open geospatial data providers
  • Standards developers
  • Geospatial technology developers
  • Web mappers (app-developers & geographic data viz specialists)
  • Join us or find out more
Our objectives - Overall - For this meeting

5 min


  1. Integrate Web map support into browsers (native map viewer, ability to process map media types)

For this meeting

  1. Identify requirements for implementer support
  2. Invite implementers to participate and advise our CG
  3. Establish collaboration/coordination with related Web standards efforts
Why we’re doing this

5 min

A brief review of motivations, including: accessibility, performance, privacy, usability, barriers to use of location information

What we’ve done so far

40 - 60 min

  1. Use Cases and Requirements: summary of report reviewing existing web map tools
    • What are the common capabilities & patterns for web map frameworks? (AKA, where are the cow paths?)
    • Which use cases (for website authors or for website users/visitors) aren’t well served with the current options?
    • How do these capabilities compare against best practices & principles for web standards: accessibility, privacy, consistency, localizability, etc.?
    • Where could things be improved by switching to standardized, native browser features?
    • Which low-level capabilities have applications beyond web maps? Are there existing or proposed web standards to coordinate with?
  2. Summary of the existing spec proposals
  3. Iteration: reviews of the current spec proposals & what has changed in response
  4. Geospatial / Web Community Engagement
  5. Prototypes - Polyfills - Validation: summary of software work
What’s Next

45 - 60 min

  • Browser / Standards Developer Community Engagement
    • Who can be liaisons with these teams?
    • Possible face-to-face within 6 months or so?
  • Demonstrating need: Has the case for browser implementer interest been made convincingly?
    • If not, what are the next steps?
  • Best strategies for a “speculative polyfill” (polyfill for a proposal, meaning a JS prototype implementation of a spec)
    • How do we design a web component that can transition to a native feature?
    • How best to build a test suite for future integration with Web Platform Tests?
    • How do we get wide use while preserving flexibility for iterative design?
  • Improving the specifications: Markup & API design
    • Where is the best split between HTML and MapML? Is it better to work on the two separately, for different use cases?
    • Is it better to reuse/enhance existing HTML elements (e.g. <map>, <area>, <input>), or create from scratch?
    • Which HTML/SVG markup patterns are best practices to follow? Which are legacy mistakes that we should we avoid repeating?
    • How to handle namespaces for MapML DOM?
    • What DOM API methods are required beyond elements, attributes & event handling?
Wrap up

5 min