Skip to content

Commit 37846d2

Browse files
authored
Merge pull request #206 from nchan0154/master
Continue to fill out supplementary sections for client side capabilities
2 parents dd32019 + f95006f commit 37846d2

File tree

1 file changed

+101
-12
lines changed

1 file changed

+101
-12
lines changed

index.html

Lines changed: 101 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -2970,8 +2970,19 @@ <h5>Uses beyond mapping</h5>
29702970

29712971
<h5>Related web specifications</h5>
29722972
<p>
2973-
<!-- Any existing/proposed specs that address similar needs or otherwise interact.
2974-
Include links with proper ReSpec references. -->
2973+
<a data-cite="SVG2#">SVG</a> contains a number of elements that are positioned on a coordinate system.
2974+
The coordinates and dimensions of the element are defined in markup,
2975+
as attributes on the element.
2976+
</p>
2977+
<p>
2978+
The <a data-cite="HTML#the-canvas-element">HTML Canvas2D API</a> also offers the ability to draw points on a coordinate system,
2979+
but images are drawn by passing coordinates into a JavaScript method,
2980+
instead of an element such as in SVG.
2981+
This method of drawing features is more similar to existing mapping libraries,
2982+
which are also reliant on JavaScript.
2983+
However, the Canvas API offers a very low level of abstraction in comparison to mapping libraries.
2984+
Depending on the complexity of the marker,
2985+
the code to draw it may be very verbose.
29752986
</p>
29762987

29772988
<h5>Conclusion</h5>
@@ -3043,8 +3054,20 @@ <h5>Uses beyond mapping</h5>
30433054

30443055
<h5>Related web specifications</h5>
30453056
<p>
3046-
<!-- Any existing/proposed specs that address similar needs or otherwise interact.
3047-
Include links with proper ReSpec references. -->
3057+
<a data-cite="SVG2#">SVG</a> contains both a <code>polyline</code> and a <code>polygon</code> element.
3058+
A comma separated list of coordinates is assigned to the <code>points</code> attribute to generate the shape.
3059+
</p>
3060+
<p>
3061+
The way that polylines and polygons are created in the <a data-cite="HTML#the-canvas-element">HTML Canvas2D API</a> is much more manual,
3062+
requiring a sequence of calls to the <code>moveTo</code> and <code>lineTo</code> methods.
3063+
Like other aspects of the Canvas API,
3064+
this syntax can be quite verbose.
3065+
</p>
3066+
<p>
3067+
TODO: Mention HTML <code>area</code> and CSS <code>polygon()</code> function.
3068+
</p>
3069+
<p>
3070+
TODO: describe how polyline/polygon are represented in the important geospatial specs.
30483071
</p>
30493072

30503073
<h5>Conclusion</h5>
@@ -3109,13 +3132,28 @@ <h5>Supported use cases</h5>
31093132

31103133
<h5>Uses beyond mapping</h5>
31113134
<p>
3112-
<!-- What other web content could use this specific capability? Be brief but specific. -->
3135+
This functionality can be used to provide hyperlink support for diagrams.
3136+
Any case where an image map may have been appropriate can also benefit from this capability.
31133137
</p>
31143138

31153139
<h5>Related web specifications</h5>
31163140
<p>
3117-
<!-- Any existing/proposed specs that address similar needs or otherwise interact.
3118-
Include links with proper ReSpec references. -->
3141+
<a data-cite="HTML#image-maps">HTML Image Maps</a> consist of a large graphic with various subregions,
3142+
which serve as links.
3143+
A subregion is defined by passing a shape, coordinates, a link target and alt text to an <code>area</code> element.
3144+
A significant limitation of image maps is that the coordinates of the area elements
3145+
are always defined in pixels and do not automatically scale to match changes in scale of the image
3146+
(see <a href="https://github.com/whatwg/html/issues/389">issue discussion on the HTML spec</a>),
3147+
and this limits its usage in modern web development.
3148+
</p>
3149+
<p>
3150+
The <a data-cite="SVG2/linking.html#Links">SVG2 specification</a> supports <code>href</code> attributes on <code>a</code> elements within SVGs,
3151+
previously, the SVG 1.1 specification required <code>href</code> attributes to be specified within the XLink namespace.
3152+
</p>
3153+
<p>
3154+
Though it is not visible,
3155+
<a data-cite="HTML#the-canvas-element">Canvas elements</a> can include keyboard focusable links as a part of a navigable sub DOM.
3156+
In order to make links within the canvas work on click, JavaScript is still neccessary.
31193157
</p>
31203158

31213159
<h5>Conclusion</h5>
@@ -3176,6 +3214,26 @@ <h5>Existing implementations</h5>
31763214
<dd><a>supported, with limitations</a>: attribution is automatically generated,
31773215
but it is not keyboard accessible.</dd>
31783216
</dl>
3217+
3218+
<h5>Supported use cases</h5>
3219+
<ul data-ucr-role="capability-uses"><!-- auto-generated from use case required capabilities --></ul>
3220+
3221+
<h5>Uses beyond mapping</h5>
3222+
<p>
3223+
</p>
3224+
3225+
<h5>Related web specifications</h5>
3226+
<p>
3227+
Website authors can use <a data-cite="Microdata">Microdata</a> and other related formats to provide attribution data in a standardized format.
3228+
How and whether or not this content is displayed is up to the website author,
3229+
but the goal is to provide a machine-readable format for important document content.
3230+
</p>
3231+
<p>
3232+
The <a data-cite="HTML#the-cite-element">cite element</a> is for describing references to a cited creative work.
3233+
The HTML <code>blockquote</code> and <code>q</code> elements have a <code>cite</code> attribute
3234+
where you can pass a URL as the source of a quote,
3235+
but browsers currently do not display this information to the end user.
3236+
</p>
31793237
</section>
31803238

31813239
</section>
@@ -3229,11 +3287,6 @@ <h5>Existing implementations</h5>
32293287
<h5>Supported use cases</h5>
32303288
<ul data-ucr-role="capability-uses"><!-- auto-generated from use case required capabilities --></ul>
32313289

3232-
<h5>Uses beyond mapping</h5>
3233-
<p>
3234-
3235-
</p>
3236-
32373290
<h5>Related web specifications</h5>
32383291
<p>
32393292
The <a data-cite="geolocation-API">Geolocation API</a>
@@ -3300,6 +3353,42 @@ <h5>Existing implementations</h5>
33003353
<dt>bing-maps-embed</dt>
33013354
<dd><a>partial support</a>: does not support markers for a single location, but it is possible to display a map centered around a particular street address with no marker</dd>
33023355
</dl>
3356+
3357+
3358+
<h5>Uses beyond mapping</h5>
3359+
<p>
3360+
There are many cases where a website may expect an address from a user.
3361+
An input type specifically for addresses has a wide variety applications other than displaying a map,
3362+
such as reducing user error when facilitating e-commerce and delivery services.
3363+
</p>
3364+
3365+
<h5>Related web specifications</h5>
3366+
<p>
3367+
TODO: mention attempts to standardize what an “address” is,
3368+
in HTML autocomplete attribute
3369+
and Payment Request API.
3370+
</p>
3371+
<h5>Conclusion</h5>
3372+
<!-- Cost, benefits, and recommendation on whether this should be a requirement.
3373+
Should include an `<a>` element with attribute `data-ucr-role="conclusion"`
3374+
whose text content or `data-lt` value matches one of the conclusions (requirement, enhancement, impractical, undecided).
3375+
See examples.
3376+
-->
3377+
<p>
3378+
Based on the limited data, we are <a data-ucr-role="conclusion">undecided</a> about whether this should be a requirement.
3379+
</p>
3380+
<ul data-ucr-role="conclusion-notes">
3381+
<li>
3382+
<a data-ucr-role="tag" href="#i18n-difficult"></a>
3383+
There are significant regional differences when it comes to how addresses are formatted.
3384+
A good implementation of this would need to take these regional variations into account.
3385+
</li>
3386+
<li>
3387+
<a data-ucr-role="tag" href="#privacy-personal-data"></a>
3388+
It is unlikely that this capability could be supported in a fully client-side way,
3389+
the inputted address may be revealed to the browser or website author.
3390+
</li>
3391+
</ul>
33033392
</section>
33043393

33053394
<section id="capability-tile-coordinate-systems" data-ucr-role="capability">

0 commit comments

Comments
 (0)