See also: IRC log
clarke states we will review what was not complete last week, open bugs and open issues in bugzilla
if there is time discuss what the group wants to do
going forward
from last week what is left to do
is to put the requirements into a real draft
still open
clarke to contact david singer to check if adaptive streaming is disadvantaged
need some more time to give david more time to respond
next item is discussion over requirment 10
error reporting
additional errors to feed back
ads and splicing
using another video element
need for a use case to handle position timeframe
<KevinStreeter> It should be possible to seamlessly splice content with a discontinuous timeline (such as advertising) into the presentation [this requirement may conflict with (2)?]
this req may conflict with req 2
continous timeline is required
lets have some more discussion
need a common time reference
Aaron pointed out that use cases that are overlapping should be considered and timeshift
need to be considered to properly support the use case
need to keep a buffer to handle trickplay
need a master timeline to insert ads into
possibly need to adjust or map to the master timeline
may need to expose a timestamp offsetting to the API
2 is indep requirement
it is fully addressed by the proposal
11 is an additional requirement
any thing else on the abr requirements?
between here and next week clarke to add clarification before sending req to html5
next subject is bugs
<kaz> Bugs section
profile group has decided to use bugzilla to handle issues raised to the task force
bug 13625
<scribe> In process. Hixie needs to read provided materials.
bug 12399
<scribe> In process. Should this be generalized beyond video? Maybe start with video and consider a broader scope in any solution.
bug 13359
<scribe> In process. Discussions on parameters and whether changes are necessary. "Must be human readable" requirement.
bugs 13357 and 14492 have not been address since filed
2 new bugs
david: bugs came from discussions in profiling TF
bug 16479
<giuseppe> https://www.w3.org/Bugs/Public/show_bug.cgi?id=16479
<David_Corvoysier> https://www.w3.org/Bugs/Public/show_bug.cgi?id=16479
bug relates not being able to piping multiple streams
<joesteele> +q
nothing is stated as to how resources are freed
what webkit does the resource are not released when video tag is unloaded
only when garbage collection actually removes the resources
joe points that decryption resources are not released
david: video decoder has been the main issue
aeren: what is issue, if opening multiple videos
some content depending on decryption may require hardware
which is locked
there are 2 errors, if there are policy concerns and there should be a warning if software is going to be used as fallback
many audio tracks may be opened at the same time in order to give special effects which may confuse what should be handled
david: when listening audio may be persisted
when should resources be released
javascript may remove tag from dom and reinsert it
same media element may be used when transferring it
david: may some use cases are required
gius: add the use cases into the bug
next bug
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16480
when needing to have broadcast channel where there is a mosaic of the channels
may want an interface to select one of the channels
need to draw borders in order to select channel or everything is done in javascript
map element would be a much easier solution to be used but it is not available for the video element
only images
<bryan> is there anyway to use SVG as an scalable overlay frame, and trigger events from it?
for each of the elements need to put the source to handle the multiple stream types
<bryan> just a random idea
wiht map you can associated anchors
gius: investigate if there are better solutions
bryan: there might be markup language like svg that can help in providing a solution
giuseppe to explain how bugzilla to be used
bugzilla to be used to collect issues
and it is a better way to monitor questions and share with other groups
it is a prefilter of the raised issues
if agreed then it is pushed into the different WG's
there is a template for filling out issues
it is in the main wiki webpage
<giuseppe> http://www.w3.org/2011/webtv/wiki/Main_Page#Template_for_Use_Cases
use template to describe use case
clarke: what could be useful to
add the template to the mptf as a reference
... once the discussion is started it is necessary to highlight
to clarke to be discussed
... person who filed bug has responsibility to highlight
it
... general discussion
... in next couple of week finishup the requirements
documents
... use time every week to discuss opened bugs
... soon to limit the number of phone conferences
... if any suggestions forward them to clarke as to how to
progress
move to phone conf every 2 weeks
adhock would make it harder to plan attending
<bryan> I like the building of the agenda on the wiki. It's easy to keep up as the topics for discussion are collected.
clarke: plan to continue phone conf every week until req done
joe to be scribe next week
<bryan> That approach can help make the calls more adhoc but keep people engaged on the agenda as it builds.
could use wiki agenda to identify critical mass of issues to be discussed
<kaz> [ adjourned ]