TPAC 2019 Agenda
From Maps for HTML Community Group Wiki
Contents
Maps for HTML Community Group - TPAC 2019 Agenda
Venue: W3C TPAC
Location: Fukuoka Japan
Date: September 20, 2019
Time: 8:30 - 10:30
IRC: http://irc.w3.org/?channels=#m4h
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
Introductions.
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
Overall
- Integrate Web map support into browsers (native map viewer, ability to process map media types)
For this meeting
- Identify requirements for implementer support
- Invite implementers to participate and advise our CG
- 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
- 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?
- Summary of the existing spec proposals
- Map Markup Language - MapML
- <map> and <layer> elements for HTML proposal
- SVGMap: Summary from stakagi : https://github.com/satakagi/TPAC2019-docs/blob/master/MAP.md
- Iteration: reviews of the current spec proposals & what has changed in response
- OGC Testbed reviews — 2018 (Testbed 14) report, 2017 (Testbed 13) report
- Current: spec proposal design review based on Web standards architecture & best practices
- Geospatial / Web Community Engagement
- Prototypes - Polyfills - Validation: summary of software work
- Custom elements for <map> and <layer> - can / should we polyfill the whole language with custome elements?
- GeoServer MapML Community Module
- MapServer MapML project
- GDAL / OGR MapML project
- MapML validator fork of validator.nu
- Custom elements for <map> and <layer> - can / should we polyfill the whole language with custome elements?
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?
- Who can be liaisons with these teams?
- Demonstrating need: Has the case for browser implementer interest been made convincingly?
- If not, what are the next steps?
- 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?
- How do we design a web component that can transition to a native feature?
- 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?
- Where is the best split between HTML and MapML? Is it better to work on the two separately, for different use cases?
Wrap up
5 min