update on liaison letter

Clarke: Giuseppe is absent
... so proceed to next agenda

review and get requirement from use cases

Clarke: last week we reviewed all existing use cases, and approved all of them
... then I extracted the requirement from them. That's what we want to discuss today

Chair presented requirement in GotoMeeting

From 1st use case: we need standardized API for test hooks

Clarke: 2nd one is the ecosystem to get feedback from community etc.

Mark: agree. Another point is that we also need developer community to be part of it

Chair when the new capability is developed, we need to integrate the new capability into the test suite

Clarke: 3rd is to provide one home for all W3C test
... #4 is performance measurement
... several metrics
... Bryan had several very good comment on it
... different applications, and performance n each of them
... to measure the performance more accurately on them
... people general agree to do performance measurement
... but we need more specifics
... anyone else has anything on them?
... next one is the testing of various codecs and encoding schemes,e.g. adaptive bit rate
... another one from MSE is the synchronization, e.g. adaptive bit rate from different sources,
... such as ad insertion, to synchronize the different streams (advertising and normal video)
... and feedback mechanism to let you know the switch of blocks there
... in the test tool, it might mean the network traffic
... another one is different encryption

Mark: you mean the CDM ones?
... the tricky part is that you cannot use clear key to test
... W3C needs to rely on 3rd party plug-ins

Sheau: let's assume 2 browsers running concurrently, and use the same stream

Clarke: that's a different requirement: 2nd screen, 2 CDMs on 2 different browsers, on 2 different device even
... thinking if it is an application issue, or needs to be taken of inside spec

<Sheau> It may two browsers, two separate streams, both using different CDMs.

Clarke: recognize it is really an issue, but not sure if it is app issue. Not convinced yet. But will write down this issue

new use cases and new requirement

Clarke: maybe the synchronization of 2 screens
... what about continuous streams

Sheau: maybe mapping to 2nd sreen / 2nd browsers, the continuous stream issue will pop up

Clarke: Sheau, can you take those 2 issues, and add to the use case page, we can extract the necessary requirement from it

<kaz> ACTION: Sheau to update the IG wiki with his use cases [recorded in http://www.w3.org/2013/04/17-webtv-minutes.html#action01]

<trackbot> Created ACTION-110 - Update the IG wiki with his use cases [on Sheau Ng - due 2013-04-24].

Clarke: this will be action item. kaz creates an action item

Bin briefed the testing meeting last time, and will send to the mailing list the information of next meeting on Friday, and the link to slides of last meeting

<scribe> ... new slides of Friday's meeting probably won't be available until the start of meeting on Friday

Clarke: AOB?
... for next meeting, we take the requrement that we discussed, and put them into our requirement document.
... we can review what's going on of Friday's meeting of general testing group
... that's general agenda next CC

Your are welcome

<kaz> [ adjourned ]

<Clarke> Thanks for scribing , Bin