W3C home > Mailing lists > Public > public-html-a11y@w3.org > March 2010

[media] Track vs. tracks

From: John Foliot <jfoliot@stanford.edu>
Date: Tue, 9 Mar 2010 11:27:24 -0800 (PST)
To: "'HTML Accessibility Task Force'" <public-html-a11y@w3.org>
Message-ID: <008901cabfbe$8c05c400$a4114c00$@edu>
Hello All,

Just a question (2 actually) for clarification:

In the Media MultitrackAPI document there is reference to 'tracks' in the
plural:
<q>
	if (video.tracks[1].role == "caption") video.tracks[1].enabled =
true;
		enables a caption track

	if (video.tracks[2].role == "subtitle" && video.tracks[2].language
== "fr") video.tracks[2].enabled = true;
		enables a French subtitle track
</q>

However in the Media TextAssociations we introduce an element <track>:
<q>
<video src="video.ogv">
  <track src="video_tad.srt" type="text/srt" language="en"
role="textaudesc"></track>
</video>
</q>

*****
Is this deliberate or intentional (mixing singular and plural)? Does it
matter?

Also, in the Media TextAssociations example, <track> currently has a
'closing' element (</track>) - is this necessary or mandatory? Could we
not also treat it like other non-closing elements (<img> for example?) -
in the XML serialization of HTML5 this could be thus rendered <track
src="" [etc.] />

Just thinking out loud...

JF
============================
John  Foliot
Program Manager
Stanford Online Accessibility Program
http://soap.stanford.edu
Stanford University
Tel: 650-862-4603

SOAP is a program directed by the
Vice Provost for Student Affairs
============================
Received on Tuesday, 9 March 2010 19:27:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:03 GMT