Architecture

<JF> scribe: JF

alex: has posted content to the wiki page

Alex, I cannot share the arch page

on last call we arrived at the aim, which is to get more people to assist with use-case writing

proposal last call to write an elevator pitch - high level

have written a few sentences (draft)

<alexanda-mikityuk> https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/Architecture#Technology_Pitch

Alex: cloud browser addresses gaps in hardware on large screens today
... after posting the wiki page, received feedback on an accessibility question

so added the note that must meet accessibility standards

alex: also referenced the different approaches

also noted that this is a server(?) site

alos noted the issue of out-of-band streaming - so this has been addressed as well

alex: there was also an issue around re-encryption from the cloud-browser server system, so that any other CDM and encryption could be applied at that level
... feeling that the pitch helps address any confusion/questions

feel free to continue to offer comments / proposed edits

alex: also discovered the history function in the wiki - apologies for missing that in the past

<alexanda-mikityuk> https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/Architecture#Architecture

alex: discussion/issue with flexible architecture - but feels overly complex for now

colin: agree - useful but not required for today

alex: will do a final review of the architecture page, to be sure there is no inconsistencies

Use Cases

alex: now we can work on the actual usecases

<alexanda-mikityuk> https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/UseCases

alex: looking to assign use-cases now

need to look at the MSE/EME issues after first draft

wondering if Colin can pick up another use-case

:)

<alexanda-mikityuk> https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/UseCases/communication

Alex: asking JF to add user-stories based on disabilities
... add user-stories to wiki page and please copy to the mailing list
... that wraps my agenda items

colin: referencing the TV Control API group

Alex: there is a concern that we may need to build something new, or relate to standards already done

JF: this will likely have an impact on accessibilityissues as well, as alternative inputs will be an issue

kaz: provide some suplimentary info
... the TV control group met for the first time earlier
... discussing client side tuner capabilities
... provided comments to that group
... we should consider how to handle that and the local browser client side
... the cloud server may want to use this API on the server side
... so that then opens the question what will it need/want to access
... discussion on the TV control Working Group and Community Group

alex: is there anybody from the TV Control grop we can work with?

kaz: Colin is participating in the TV Control CG, so he could be the contact if it's OK by him.
... and I can help him.

colin: OK

alex: that seems it, see all in 2 weeks

<kaz> [ adjourned ]