Skip to content

Commit 91b97a1

Browse files
AmeliaBRAmeliaBR
authored
Merge pull request #217 from NickFitz/capabilities-removal
Merge “Capability: Zoom a map in or out” into “Capability: Pan a map or re-centre a map”
2 parents 675cd8d + 3a53639 commit 91b97a1

File tree

1 file changed

+4
-219
lines changed

1 file changed

+4
-219
lines changed

‎index.html

+4-219
Original file line numberDiff line numberDiff line change
@@ -1704,8 +1704,7 @@ <h4>Reposition or scale a map to find more context for the displayed locations</
17041704

17051705
<h5>Required capabilities</h5>
17061706
<ul data-ucr-role="required-capabilities">
1707-
<li><a href="#capability-pan-map-or-re-centre-map"></a></li>
1708-
<li><a href="#capability-zoom-map-in-or-out"></a></li>
1707+
<li><a href="#capability-pan-zoom-or-re-centre-map"></a></li>
17091708
</ul>
17101709
</section>
17111710

@@ -1739,8 +1738,7 @@ <h5>Required capabilities</h5>
17391738
<ul data-ucr-role="required-capabilities">
17401739
<li>As a custom application feature:
17411740
<ul>
1742-
<li><a href="#capability-pan-map-or-re-centre-map"></a></li>
1743-
<li><a href="#capability-zoom-map-in-or-out"></a></li>
1741+
<li><a href="#capability-pan-zoom-or-re-centre-map"></a></li>
17441742
</ul>
17451743
</li>
17461744
</ul>
@@ -1993,8 +1991,6 @@ <h4>Add a custom control to a map</h4>
19931991
<h5>Required capabilities</h5>
19941992
<ul data-ucr-role="required-capabilities">
19951993
<li><a href="#capability-implement-a-custom-control"></a></li>
1996-
<li><a href="#capability-add-control-map"></a></li>
1997-
<li><a href="#capability-remove-control-map"></a></li>
19981994
</ul>
19991995
</section>
20001996

@@ -4632,153 +4628,6 @@ <h5>Conclusion</h5>
46324628
</ul>
46334629
</section>
46344630

4635-
<section id="capability-add-control-map" data-ucr-role="capability">
4636-
<h4>Add a control to a map</h4>
4637-
<p>
4638-
Description to follow
4639-
</p>
4640-
<p class="issue discussion" data-number="58">
4641-
Discuss this section on GitHub.
4642-
</p>
4643-
4644-
<h5>Existing implementations</h5>
4645-
<p>
4646-
Existing implementation support:
4647-
</p>
4648-
<dl data-ucr-role="implementation-notes">
4649-
<!-- Use dt elements to name the implementation, using the id string to create an auto-link.
4650-
Give details about what is/isn't supported in the dd element,
4651-
starting with a link to one of the implementation levels.
4652-
List full implementations first.
4653-
Group implementations (multiple dt for the same dd) when they have the same support.
4654-
-->
4655-
<dt>google-maps-api</dt>
4656-
<dt>bing-maps-api</dt>
4657-
<dt>apple-mapkit-js-api</dt>
4658-
<dt>mapbox-gl-api</dt>
4659-
<dt>leaflet-api</dt>
4660-
<dt>open-layers-api</dt>
4661-
<dt>tomtom</dt>
4662-
<dt>d3-geographies-api</dt>
4663-
<dd>
4664-
<p><a>full support</a>:
4665-
Google, Bing, MapKit and TomTom allow straightforward creation of a map
4666-
with configuration options.
4667-
</p>
4668-
<p>
4669-
Leaflet, OpenLayers, and MapBox require explicit construction of objects defining the map layers
4670-
and viewport, with sensible defaults for creation of, for example, a map showing OpenStreetMap tiles
4671-
in a standard [[[WGS84]]] projection.
4672-
This provides added flexibility, at the expense of increasing the complexity of code that uses these libraries.
4673-
</p>
4674-
</dd>
4675-
</dl>
4676-
4677-
<h5>Supported use cases</h5>
4678-
<ul data-ucr-role="capability-uses"><!-- auto-generated from use case required capabilities --></ul>
4679-
4680-
<h5>Uses beyond mapping</h5>
4681-
<p>
4682-
Leaflet, OpenLayers, and MapBox allow for the creation of layers displaying non-geographical imagery.
4683-
</p>
4684-
4685-
<h5>Related web specifications</h5>
4686-
<p>
4687-
<a data-cite="HTML">HTML</a> specifies a number of aspects of elements
4688-
that embed media in a web page and expose JavaScript APIs to enable interaction and dynamic configuration.
4689-
</p>
4690-
<p>
4691-
The <a data-cite="DOM">DOM</a> provides interfaces for creating
4692-
HTML elements, which are what these implementations are using under the hood.
4693-
<!-- Any existing/proposed specs that address similar needs or otherwise interact.
4694-
Include links with proper ReSpec references. -->
4695-
</p>
4696-
<p>
4697-
[[[DOM]]] [[[HTML]]]
4698-
</p>
4699-
4700-
<h5>Conclusion</h5>
4701-
<!-- Cost, benefits, and recommendation on whether this should be a requirement.
4702-
Should include an `<a>` element with attribute `data-ucr-role="conclusion"`
4703-
whose text content or `data-lt` value matches one of the conclusions (requirement, enhancement, impractical, undecided).
4704-
See examples.
4705-
-->
4706-
<p>
4707-
Based on the limited data, we are <a data-ucr-role="conclusion">undecided</a> about whether this should be a requirement.
4708-
</p>
4709-
<ul data-ucr-role="conclusion-notes">
4710-
<!-- bullet-point notes summarizing implementation details / blocking issues.
4711-
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. -->
4712-
<li><a data-ucr-role="tag" href=""></a>
4713-
<!-- short summary of how the tag applies -->
4714-
</li>
4715-
</ul>
4716-
</section>
4717-
4718-
<section id="capability-remove-control-map" data-ucr-role="capability">
4719-
<h4>Remove a control from a map</h4>
4720-
<p>
4721-
Description to follow
4722-
</p>
4723-
<p class="issue discussion" data-number="59">
4724-
Discuss this section on GitHub.
4725-
</p>
4726-
4727-
<h5>Existing implementations</h5>
4728-
<p>
4729-
Existing implementation support:
4730-
</p>
4731-
<dl data-ucr-role="implementation-notes">
4732-
<!-- Use dt elements to name the implementation, using the id string to create an auto-link.
4733-
Give details about what is/isn't supported in the dd element,
4734-
starting with a link to one of the implementation levels.
4735-
List full implementations first.
4736-
Group implementations (multiple dt for the same dd) when they have the same support.
4737-
-->
4738-
<dt>google-maps-api</dt>
4739-
<dt>bing-maps-api</dt>
4740-
<dt>apple-mapkit-js-api</dt>
4741-
<dt>mapbox-gl-api</dt>
4742-
<dt>leaflet-api</dt>
4743-
<dt>open-layers-api</dt>
4744-
<dt>d3-geographies-api</dt>
4745-
<dd><a>full support</a>:
4746-
<!-- details about what is/isn't supported -->
4747-
</dd>
4748-
</dl>
4749-
4750-
<h5>Supported use cases</h5>
4751-
<ul data-ucr-role="capability-uses"><!-- auto-generated from use case required capabilities --></ul>
4752-
4753-
<h5>Uses beyond mapping</h5>
4754-
<p>
4755-
ToDo
4756-
</p>
4757-
4758-
<h5>Related web specifications</h5>
4759-
<p>
4760-
<!-- Any existing/proposed specs that address similar needs or otherwise interact.
4761-
Include links with proper ReSpec references. -->
4762-
</p>
4763-
4764-
<h5>Conclusion</h5>
4765-
<!-- Cost, benefits, and recommendation on whether this should be a requirement.
4766-
Should include an `<a>` element with attribute `data-ucr-role="conclusion"`
4767-
whose text content or `data-lt` value matches one of the conclusions (requirement, enhancement, impractical, undecided).
4768-
See examples.
4769-
-->
4770-
<p>
4771-
Based on the limited data, we are <a data-ucr-role="conclusion">undecided</a> about whether this should be a requirement.
4772-
</p>
4773-
<ul data-ucr-role="conclusion-notes">
4774-
<!-- bullet-point notes summarizing implementation details / blocking issues.
4775-
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. -->
4776-
<li><a data-ucr-role="tag" href=""></a>
4777-
<!-- short summary of how the tag applies -->
4778-
</li>
4779-
</ul>
4780-
</section>
4781-
47824631
<section id="capability-add-layer-map" data-ucr-role="capability">
47834632
<h4>Add a layer to a map</h4>
47844633
<p>
@@ -5341,8 +5190,8 @@ <h5>Conclusion</h5>
53415190
</ul>
53425191
</section>
53435192

5344-
<section id="capability-pan-map-or-re-centre-map" data-ucr-role="capability">
5345-
<h4>Pan a map or re-centre a map</h4>
5193+
<section id="capability-pan-zoom-or-re-centre-map" data-ucr-role="capability">
5194+
<h4>Pan, zoom, or re-centre a map</h4>
53465195
<p>
53475196
Description to follow
53485197
</p>
@@ -5405,70 +5254,6 @@ <h5>Conclusion</h5>
54055254
</ul>
54065255
</section>
54075256

5408-
<section id="capability-zoom-map-in-or-out" data-ucr-role="capability">
5409-
<h4>Zoom a map in or out</h4>
5410-
<p>
5411-
Description to follow
5412-
</p>
5413-
<p class="issue discussion" data-number="68">
5414-
Discuss this section on GitHub.
5415-
</p>
5416-
5417-
<h5>Existing implementations</h5>
5418-
<p>
5419-
Existing implementation support:
5420-
</p>
5421-
<dl data-ucr-role="implementation-notes">
5422-
<!-- Use dt elements to name the implementation, using the id string to create an auto-link.
5423-
Give details about what is/isn't supported in the dd element,
5424-
starting with a link to one of the implementation levels.
5425-
List full implementations first.
5426-
Group implementations (multiple dt for the same dd) when they have the same support.
5427-
-->
5428-
<dt>google-maps-api</dt>
5429-
<dt>bing-maps-api</dt>
5430-
<dt>apple-mapkit-js-api</dt>
5431-
<dt>mapbox-gl-api</dt>
5432-
<dt>leaflet-api</dt>
5433-
<dt>open-layers-api</dt>
5434-
<dt>d3-geographies-api</dt>
5435-
<dd><a>not applicable</a>:
5436-
<!-- details about what is/isn't supported -->
5437-
</dd>
5438-
</dl>
5439-
5440-
<h5>Supported use cases</h5>
5441-
<ul data-ucr-role="capability-uses"><!-- auto-generated from use case required capabilities --></ul>
5442-
5443-
<h5>Uses beyond mapping</h5>
5444-
<p>
5445-
ToDo
5446-
</p>
5447-
5448-
<h5>Related web specifications</h5>
5449-
<p>
5450-
<!-- Any existing/proposed specs that address similar needs or otherwise interact.
5451-
Include links with proper ReSpec references. -->
5452-
</p>
5453-
5454-
<h5>Conclusion</h5>
5455-
<!-- Cost, benefits, and recommendation on whether this should be a requirement.
5456-
Should include an `<a>` element with attribute `data-ucr-role="conclusion"`
5457-
whose text content or `data-lt` value matches one of the conclusions (requirement, enhancement, impractical, undecided).
5458-
See examples.
5459-
-->
5460-
<p>
5461-
Based on the limited data, we are <a data-ucr-role="conclusion">undecided</a> about whether this should be a requirement.
5462-
</p>
5463-
<ul data-ucr-role="conclusion-notes">
5464-
<!-- bullet-point notes summarizing implementation details / blocking issues.
5465-
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. -->
5466-
<li><a data-ucr-role="tag" href=""></a>
5467-
<!-- short summary of how the tag applies -->
5468-
</li>
5469-
</ul>
5470-
</section>
5471-
54725257
<section id="capability-map-events" data-ucr-role="capability">
54735258
<h4>Subscribe to notifications of map events</h4>
54745259
<p>

0 commit comments

Comments
 (0)