This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27370 - Add explanation for generating references to defined Keywords that can be used as URNs
Summary: Add explanation for generating references to defined Keywords that can be use...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-19 16:59 UTC by Bob Lund
Modified: 2016-04-27 21:35 UTC (History)
6 users (show)

See Also:


Attachments

Description Bob Lund 2014-11-19 16:59:03 UTC
Add text in the HTML spec for how to generate the URI to identify an HTML track kind so that the URI can be used in other contexts such as the In-band sourcing spec [1], DASH [2] and the new ISOBMFF kind box. A form for the URI was proposed [3]. Rules should be defined for all track types - text, audio and video.

[1] http://dev.w3.org/html5/html-sourcing-inband-tracks/
[2] http://lists.w3.org/Archives/Public/www-tag/2014Jun/0033.html
[3] http://lists.w3.org/Archives/Public/www-tag/2014Jun/0039.html
Comment 1 Silvia Pfeiffer 2014-11-20 01:02:25 UTC
The discussion concluded that we should actually have a more generic solution for pointing to any defined keyword in the HTML spec, not just the @kind values, see http://lists.w3.org/Archives/Public/www-tag/2014Jun/0047.html .

In fact, this solution already exists, but is merely undocumented.

For example, the "URNs" for the track kinds are:

http://www.w3.org/TR/html/#attr-track-kind-subtitles
http://www.w3.org/TR/html/#attr-track-kind-captions
http://www.w3.org/TR/html/#attr-track-kind-descriptions
http://www.w3.org/TR/html/#attr-track-kind-chapters
http://www.w3.org/TR/html/#attr-track-kind-metadata

These can be made to persist across different HTML versions, as explained by Robin in:
http://lists.w3.org/Archives/Public/www-tag/2014Jun/0038.html
and
http://lists.w3.org/Archives/Public/www-tag/2014Jun/0045.html

Works for other keywords, too, e.g. http://www.w3.org/TR/html/embedded-content-0.html#attr-media-preload-none .
Comment 2 Bob Lund 2014-12-01 20:14:43 UTC
(In reply to Silvia Pfeiffer from comment #1)
> The discussion concluded that we should actually have a more generic
> solution for pointing to any defined keyword in the HTML spec, not just the
> @kind values, see
> http://lists.w3.org/Archives/Public/www-tag/2014Jun/0047.html .

So, something along the following lines?

A Uniform Resource Identifier (URI) that points to an HTML defined keyword, created using the Definition element (<dfn>), should be of the form http://www.w3.org/TR/html/#ID_value where ID_value is the value of the <dfn> ‘id’ attribute. For example, a URI for the audio and video track ‘kind’ attribute value “alternative” would be http://www.w3.org/TR/html/#value-track-kind-alternate. A URI for the text track ‘kind’ attribute value “captions” would be http://www.w3.org/TR/html/#attr-track-kind-keyword-captions.

> 
> In fact, this solution already exists, but is merely undocumented.
> 
> For example, the "URNs" for the track kinds are:
> 
> http://www.w3.org/TR/html/#attr-track-kind-subtitles
> http://www.w3.org/TR/html/#attr-track-kind-captions
> http://www.w3.org/TR/html/#attr-track-kind-descriptions
> http://www.w3.org/TR/html/#attr-track-kind-chapters
> http://www.w3.org/TR/html/#attr-track-kind-metadata
> 
> These can be made to persist across different HTML versions, as explained by
> Robin in:
> http://lists.w3.org/Archives/Public/www-tag/2014Jun/0038.html
> and
> http://lists.w3.org/Archives/Public/www-tag/2014Jun/0045.html
> 
> Works for other keywords, too, e.g.
> http://www.w3.org/TR/html/embedded-content-0.html#attr-media-preload-none .
Comment 3 Arron Eicholz 2016-04-27 21:35:32 UTC
HTML5.1 Bugzilla Bug Triage: With the switch to bikeshed spec generation all linking mechanisms have changed. If you have specific issues following the bikeshed conversion please open an issue on github.

If this resolution is not satisfactory, please copy the relevant bug details/proposal into a new issue at the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new where it will be re-triaged. Thanks!