Merge branch 'capabilities-wip' of https://github.com/NickFitz/HTML-Map-Element-UseCases-Requirements into capabilities-wip

� Conflicts:
�	index.html

Author: NickFitz

index.html

@@ -1704,7 +1704,8 @@ <h4>Reposition or scale a map to find more context for the displayed locations</
 
 <h5>Required capabilities</h5>
 <ul data-ucr-role="required-capabilities">
-<li><a href="#capability-pan-zoom-or-re-centre-map"></a></li>
+<li><a href="#capability-pan-map-or-re-centre-map"></a></li>
+<li><a href="#capability-zoom-map-in-or-out"></a></li>
 </ul>
 </section>
 
@@ -1738,7 +1739,8 @@ <h5>Required capabilities</h5>
 <ul data-ucr-role="required-capabilities">
 <li>As a custom application feature:
   <ul>
-  <li><a href="#capability-pan-zoom-or-re-centre-map"></a></li>
+  <li><a href="#capability-pan-map-or-re-centre-map"></a></li>
+  <li><a href="#capability-zoom-map-in-or-out"></a></li>
   </ul>
 </li>
 </ul>
@@ -1991,6 +1993,8 @@ <h4>Add a custom control to a map</h4>
 <h5>Required capabilities</h5>
 <ul data-ucr-role="required-capabilities">
 <li><a href="#capability-implement-a-custom-control"></a></li>
+<li><a href="#capability-add-control-map"></a></li>
+<li><a href="#capability-remove-control-map"></a></li>
 </ul>
 </section>
 
@@ -4543,8 +4547,8 @@ <h5>Existing implementations</h5>
 <dd><a>full support</a>:
 <p>
 All of these implementations fully support the concept of controls,
-including support for control implementations to be notified when they are added to or removed from the map,
-so they can update their own internal state accordingly.
+including support for control implementations to be notifed when they are added to or removed from the map,
+so they can update their own internal state acordingly.
 They also allow controls to request their desired positioning within the map's UI,
 and will position controls using sensible defaults if developers choose not to implement that capability.
 </p>
@@ -4614,7 +4618,7 @@ <h5>Conclusion</h5>
 -->
 <p>
 It might seem that, as controls are implemented using existing interactive HTML elements,
-there is no pressing need for them to be supported by additional APIs.
+there is no pressing need for them to be supported by additional APIS.
 However, the need for them to be closely integrated with a map's own UI, state, and lifecycle
 suggests that this functionality is a <a data-ucr-role="conclusion">requirement</a> for modern web maps.
 </p>
@@ -4628,6 +4632,153 @@ <h5>Conclusion</h5>
 </ul>
 </section>
 
+<section id="capability-add-control-map" data-ucr-role="capability">
+<h4>Add a control to a map</h4>
+<p>
+Description to follow
+</p>
+<p class="issue discussion" data-number="58">
+Discuss this section on GitHub.
+</p>
+
+<h5>Existing implementations</h5>
+<p>
+Existing implementation support:
+</p>
+<dl data-ucr-role="implementation-notes">
+<!-- Use dt elements to name the implementation, using the id string to create an auto-link.
+Give details about what is/isn't supported in the dd element,
+starting with a link to one of the implementation levels.
+List full implementations first.
+Group implementations (multiple dt for the same dd) when they have the same support.
+-->
+<dt>google-maps-api</dt>
+<dt>bing-maps-api</dt>
+<dt>apple-mapkit-js-api</dt>
+<dt>mapbox-gl-api</dt>
+<dt>leaflet-api</dt>
+<dt>open-layers-api</dt>
+<dt>tomtom</dt>
+<dt>d3-geographies-api</dt>
+<dd>
+<p><a>full support</a>:
+Google, Bing, MapKit and TomTom  allow straightforward creation of a map
+with configuration options.
+</p>
+<p>
+Leaflet, OpenLayers, and MapBox require explicit construction of objects defining the map layers
+and viewport, with sensible defaults for creation of, for example, a map showing OpenStreetMap tiles
+in a standard [[[WGS84]]] projection.
+This provides added flexibility, at the expense of increasing the complexity of code that uses these libraries.
+</p>
+</dd>
+</dl>
+
+<h5>Supported use cases</h5>
+<ul data-ucr-role="capability-uses"><!-- auto-generated from use case required capabilities --></ul>
+
+<h5>Uses beyond mapping</h5>
+<p>
+Leaflet, OpenLayers, and MapBox allow for the creation of layers displaying non-geographical imagery.
+</p>
+
+<h5>Related web specifications</h5>
+<p>
+<a data-cite="HTML">HTML</a> specifies a number of aspects of elements
+that embed media in a web page and expose JavaScript APIs to enable interaction and dynamic configuration.
+</p>
+<p>
+The <a data-cite="DOM">DOM</a> provides interfaces for creating
+HTML elements, which are what these implementations are using under the hood.
+<!-- Any existing/proposed specs that address similar needs or otherwise interact.
+Include links with proper ReSpec references. -->
+</p>
+<p>
+[[[DOM]]] [[[HTML]]]
+</p>
+
+<h5>Conclusion</h5>
+<!-- Cost, benefits, and recommendation on whether this should be a requirement.
+Should include an `<a>` element with attribute `data-ucr-role="conclusion"`
+whose text content or `data-lt` value matches one of the conclusions (requirement, enhancement, impractical, undecided).
+See examples.
+-->
+<p>
+Based on the limited data, we are <a data-ucr-role="conclusion">undecided</a> about whether this should be a requirement.
+</p>
+<ul data-ucr-role="conclusion-notes">
+<!-- bullet-point notes summarizing implementation details / blocking issues.
+Add tags to the start of a point with an empty `<a data-ucr-role="tag"></a>` where the text content or href matches a tag `id` value. -->
+<li><a data-ucr-role="tag" href=""></a>
+<!-- short summary of how the tag applies -->
+</li>
+</ul>
+</section>
+
+<section id="capability-remove-control-map" data-ucr-role="capability">
+<h4>Remove a control from a map</h4>
+<p>
+Description to follow
+</p>
+<p class="issue discussion" data-number="59">
+Discuss this section on GitHub.
+</p>
+
+<h5>Existing implementations</h5>
+<p>
+Existing implementation support:
+</p>
+<dl data-ucr-role="implementation-notes">
+<!-- Use dt elements to name the implementation, using the id string to create an auto-link.
+Give details about what is/isn't supported in the dd element,
+starting with a link to one of the implementation levels.
+List full implementations first.
+Group implementations (multiple dt for the same dd) when they have the same support.
+-->
+<dt>google-maps-api</dt>
+<dt>bing-maps-api</dt>
+<dt>apple-mapkit-js-api</dt>
+<dt>mapbox-gl-api</dt>
+<dt>leaflet-api</dt>
+<dt>open-layers-api</dt>
+<dt>d3-geographies-api</dt>
+<dd><a>full support</a>:
+<!-- details about what is/isn't supported -->
+</dd>
+</dl>
+
+<h5>Supported use cases</h5>
+<ul data-ucr-role="capability-uses"><!-- auto-generated from use case required capabilities --></ul>
+
+<h5>Uses beyond mapping</h5>
+<p>
+ToDo
+</p>
+
+<h5>Related web specifications</h5>
+<p>
+<!-- Any existing/proposed specs that address similar needs or otherwise interact.
+Include links with proper ReSpec references. -->
+</p>
+
+<h5>Conclusion</h5>
+<!-- Cost, benefits, and recommendation on whether this should be a requirement.
+Should include an `<a>` element with attribute `data-ucr-role="conclusion"`
+whose text content or `data-lt` value matches one of the conclusions (requirement, enhancement, impractical, undecided).
+See examples.
+-->
+<p>
+Based on the limited data, we are <a data-ucr-role="conclusion">undecided</a> about whether this should be a requirement.
+</p>
+<ul data-ucr-role="conclusion-notes">
+<!-- bullet-point notes summarizing implementation details / blocking issues.
+Add tags to the start of a point with an empty `<a data-ucr-role="tag"></a>` where the text content or href matches a tag `id` value. -->
+<li><a data-ucr-role="tag" href=""></a>
+<!-- short summary of how the tag applies -->
+</li>
+</ul>
+</section>
+
 <section id="capability-add-layer-map" data-ucr-role="capability">
 <h4>Add a layer to a map</h4>
 <p>
@@ -5191,7 +5342,7 @@ <h5>Conclusion</h5>
 </section>
 
 <section id="capability-pan-zoom-or-re-centre-map" data-ucr-role="capability">
-<h4>Pan, zoom, or re-centre a map</h4>
+<h4>Pan, zoom or re-centre a map</h4>
 <p>
 Developers expect to be able to control a map by changing its centre and/or zoom level,
 and may also wish to support the capability of resetting a map to its view as originally presented.