Delete separate zoom capability and combine with pan and re-centre, as they are all so closely related they should really be discussed together.

Author: NickFitz

index.html

@@ -1704,8 +1704,7 @@ <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-map-or-re-centre-map"></a></li>
-<li><a href="#capability-zoom-map-in-or-out"></a></li>
+<li><a href="#capability-pan-zoom-or-re-centre-map"></a></li>
 </ul>
 </section>
 
@@ -1739,8 +1738,7 @@ <h5>Required capabilities</h5>
 <ul data-ucr-role="required-capabilities">
 <li>As a custom application feature:
   <ul>
-  <li><a href="#capability-pan-map-or-re-centre-map"></a></li>
-  <li><a href="#capability-zoom-map-in-or-out"></a></li>
+  <li><a href="#capability-pan-zoom-or-re-centre-map"></a></li>
   </ul>
 </li>
 </ul>
@@ -5192,8 +5190,8 @@ <h5>Conclusion</h5>
 </ul>
 </section>
 
-<section id="capability-pan-map-or-re-centre-map" data-ucr-role="capability">
-<h4>Pan a map or re-centre a map</h4>
+<section id="capability-pan-zoom-or-re-centre-map" data-ucr-role="capability">
+<h4>Pan, zoom, or re-centre a map</h4>
 <p>
 Description to follow
 </p>
@@ -5256,70 +5254,6 @@ <h5>Conclusion</h5>
 </ul>
 </section>
 
-<section id="capability-zoom-map-in-or-out" data-ucr-role="capability">
-<h4>Zoom a map in or out</h4>
-<p>
-Description to follow
-</p>
-<p class="issue discussion" data-number="68">
-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>not applicable</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-map-events" data-ucr-role="capability">
 <h4>Subscribe to notifications of map events</h4>
 <p>