RE: Track kinds

> Once the HTML5 spec is released, these will not change again.

My proposal is that the URIs would be frozen when HTML5 goes into Candidate Recommendation.  I am not sure what "released" means here.

/paulc

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (425) 705-9596 Fax: (425) 936-7329


-----Original Message-----
From: Silvia Pfeiffer [mailto:silviapfeiffer1@gmail.com] 
Sent: Thursday, June 09, 2011 6:42 PM
To: Mark Watson
Cc: Paul Cotton; Janina Sajka; Judy Brewer <jbrewer@w3.org> (jbrewer@w3.org); Philippe Le Hegaret (plh@w3.org); HTML Accessibility Task Force
Subject: Re: Track kinds

On Fri, Jun 10, 2011 at 3:21 AM, Mark Watson <watsonm@netflix.com> wrote:
> Sorry I missed the call yesterday.
>
> The URIs for the 3GPP and DASH descriptors can be URLs or URNs. The idea is that the URI identifies a "naming scheme" for the kinds, rather than having a separate URI for each actual kind value. Are there URIs which identify the name space, rather than the individual values ?
>
> For example
>> http://www.w3.org/TR/html5/the-iframe-element.html#attr-track-kind-keyword

This one is:
http://www.w3.org/TR/html5/the-iframe-element.html#attr-track-kind

> and
>> http://www.w3.org/TR/html5/the-iframe-element.html#dom-tracklist-getkind

and this one is:
http://www.w3.org/TR/html5/the-iframe-element.html#dom-TrackList-getKind-categories


> The only issue with URLs is that they are not guaranteed to continue to mean the same thing over time. Even domains can change ownership (even if that is unlikely for w3.org). The 3GPP/MPEG specification suggest including a year/month in URLs to avoid this problem.


Once the HTML5 spec is released, these will not change again.

Cheers,
Silvia.

Received on Friday, 10 June 2011 18:38:25 UTC