29 Jun 2012

See also: IRC log


+1.510.367.aaaa, John_Foliot, +49.795.aabb, hober, silvia, eric_carlson


<hober> good morning

<hober> what's the zakim passcode to use?


<hober> cool

<scribe> scribe: JF

Silvia is providing an over-view of her lastest CP

<silvia> we've removed the aria-describedby attributes in the examples because they are not key to the solution

<silvia> Eric's concerns:

<silvia> 1. why have a different approach for our two different use cases

EC: using the URL mechanism does not allow for linking to multiple transcripts - you can not associate other meta-data to it either

<silvia> 2. a single link does not allow to provide multiple transcripts

if the concern is the copy-paste loss, then the solution is to put the URL inside of the video element itself

this avoids the loss

SP: for multiple transcripts - we could come up with a complex solution (similar to track) with menus etc.

but having a transcript is usually done on the same page as the video, so the switching there could be handled there

one link, and leave all the user/interface behavior to the author

<silvia> hober: concern about UI possibilities with the URL approach in comparison to IDREFs approach

<silvia> JF: I'm very concerned about a workable UI for blind users

Silvia: having a difficult time parsing IDREFs for a menu

the thought would be easier to use the word "Transcrip" in the menu and then it woulod just be a link

then all we need is a browser-side translation of that word of i18n uses

as for multiple-languages and the complexity for non-sighted users

Hober: but if there is no meta-data then how do we know what language the transcript is in?

Silvia: I would expect the transcript would come up in the language of the main page

Hober: reluctant to simply show a URL in a context menu

without knowing the language

EC: when we talk about the UI, it has nothing to do with the vision of the user - it is waht is presented to the end user

the UI to someone who cannot see is the description provided by the AT

to silvias point to try and parse the content of the element, I was suggesting just to use attributes there instead

<eric_carlson> if an author takes the time to translate the dialog of a movie, why wouldn't they translate the trascript?

<silvia> Eric: put the list of present transcripts inside the video element to provide multiple transcript links

EC: there is a real vague indication in the spec about how/what video controls should look like

<silvia> Eric: if there is no way to tag the transcript with the language that it is provided in then it's not possible to switch to it in the browser

allows fopr absolute and relative urls with or without media fragments, allows for other metadata, is "native to include as a child element of video...

<eric_carlson> JF: except that an author may want to have a visible transcript link, and <track> can not be made visible

<tracks> go into the contextual menu

<eric_carlson> multiple transcripts it not rare, silvia pointed out that is done today at YouTube and Ted at least

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.136 (CVS log)
$Date: 2012/06/29 18:12:57 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/ook/look/
Found Scribe: JF
Inferring ScribeNick: JF

WARNING: No "Topic:" lines found.

Default Present: +1.510.367.aaaa, John_Foliot, +49.795.aabb, hober, silvia, eric_carlson
Present: +1.510.367.aaaa John_Foliot +49.795.aabb hober silvia eric_carlson

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 29 Jun 2012
Guessing minutes URL: http://www.w3.org/2012/06/29-media-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report

[End of scribe.perl diagnostic output]