From Maps for HTML Community Group Wiki
Bar Camp notes for #lgd14 #maps4html discussion and summary:
- Concept of a (new) <map> element for html
- acknowledged that <map> already exists in html, but does not have the appropriate meaning.
- With the introduction of Web Components, it should be possible to prototype a <geo-map> custom element implemented in js which supports the target functionality. Such a prototype could be eventually standardized as (for example) <m> or <geomap> actual html element.
- Syntax would have to be simple so that markup complexity would not be a barrier to use. For example, inspired by the audio, video (and other) html elements:
<geomap id="aMap" width="250" height="250" cenx="..." ceny="..."> <source src="http://maps.example.org/foo/barcamp" type="application/map;..."/> <source src="http://another.example.org/bar/foocamp" type="application/map;..."/> </geomap>
Clients (browsers) would not be required to understand specific services (i.e. no URL construction required), only the media type with embedded links.
- The media type referenced by the source@type attribute would need to be a custom hypermedia type for maps and would incorporate lessons learned from HTML, Atom , KML, GeoJSON, GML and others.
- Map 'furniture' (i.e. pan/zoom/scalebar etc) could be provided by the client, and could be a point of distinction / differentiation between implementations.
- State transitions specific to maps could be represented by link relations i.e. east, west, north, south, northeast, northwest, southeast, southwest, zoomin, zoomout, zoomto (etc)
- because of the declarative nature, web pages with <geomap> linking to geospatial data and/or maps could be crawled by search engines and other agents, allowing geolocation of web pages/ geosearch.
- The experience / history of KML was discussed briefly, and it was noted that KML integrates presentation and content and that this was perhaps not an optimal solution. CSS or "CSS Lite" (uncertain of reference) was mentioned as a desirable technology to apply to the problem of map feature styling, due to its compatibility with mainstream Web technology.
- Discussion of issues of Cross Origin Resource Sharing. Further discussion required.
- URI fragment scheme defined by the media type could be used on the client side.
- To be further discussed on email, if the discussion participants create a W3C Community Group "#maps4html".