1. Maps For HTML Extending the Web with Maps

2. Introduction  Web mapping today is complicated and requires advanced and specialised skills  Author must know how to program in a complex Web / network environment  Many development choices, no obvious best  Maps4HTML objective: browser will have specialised skills  Author must know how to use basic HTML

3. Why Do We Need Maps for HTML?  To lower technical barriers to use of geospatial information (GI)  Lower barriers are vital  To fairly spread the benefits of existing and on-going public investments in (open) geospatial information and technology

4. Why Do Governments Invest in (open) GI?  Information  Markets work more efficiently with equal / non-discriminatory access to information  Location is information that facilitates many / most economic “transactions”

5. Web mapping today  Modern Web Map: Modern Web Map:

6. Web mapping in the Future  Maps for HTML Objective: Future Web Map in HTML #circle {fill: white; stroke: aqua; stroke-width: 5px;fill-opacity: 0.0;} #triangle {fill: pink; stroke: blue; stroke-width: 3px;fill-opacity: 0.4;}

7. Web Mapping History  First Web site: CERN 1989 – still online! First Web site: CERN 1989 – still online!

9. Web Mapping History  First Web site: CERN 1989  First Web mapping site:  Xerox PARC Map Viewer 1994  Oldest Web mapping site:  NRCan (NAISMap) 1994 to present (Atlas)present (Atlas)

11. The Nature of the Web  Standard: HTTP, HTML, CSS, SVG, JS, URI  Simple, Declarative: HTML, CSS, SVG, MathML  Open: View source  Linked: URI, HTTP, Hypertext  Styled: CSS  Extensible: JS

13. The Nature of the Web  Standard: HTTP, HTML, CSS, SVG, JS, URI  Simple, Declarative: HTML, CSS, SVG, MathML  Open: View source  Linked: URI, HTTP, Hypertext  Styled: CSS  Extensible: JS

16. The Nature of the Web January 2016:  40% of the world’s population – or  3 billion users .25 billion active domains  1 billion registered domain names  At least 4.82 billion pages  About 2 billion smartphones  About 2 billion personal computers

17. Does The Web Change ? Yes. But… how?  Who’s in charge here, anyway? W3C?  Not really.  Old way: Browser wars  New way: Community groups -> Browser devs -> WHATWG -> HTML / W3C WG  A community of practice is a pre-requisite to any change to Web standards  Community is facilitated, not created by SDOs

18. Case Study: RICG and the Element  Original proposal: blog post, 2011blog post, 2011  RICG crowdfunded fork of the Blink browser engine early 2014 RICGBlink  Chrome 38, FF 33, Opera 25 released late 2014 with support  MS EdgeHTML 13, Nov 2015  Safari/Webkit released Jan 2016.

19. Maps4HTML Community Group  Maps for HTML Community Group 2014 Maps for HTML Community Group  POC/ Prototype release Github mid-2015 POC/ Prototype release  Iteration, community building  Please join, or implement!  Release 1.0 2016  Crossing the chasm

20. Demo

21. Fin