W3C

- DRAFT -

Web&TV IG - Cloud Browser TF

08 Jun 2016

See also: IRC log

Attendees

Present
Alexandra, Nilo, Colin, Kaz, So
Regrets
Chair
Alexandra
Scribe
colin, alexandra-mikityuk

Contents


<alexandra-mikityuk> agenda

<alexandra-mikityuk> http://www.gsma.com/

<inserted> scribenick: colin

alexandra: contacted GSMA and invite them to the TF. They are discussing cloud browsing topics and could have valuable input
... plan for now finishing up architecture
... summarise discussions in email

<inserted> scribenick: alexandra-mikityuk

colin: last email Colin sent on the proposal of CB archs
... explanations on SS CLoud Player and DS Local Player
... If you have out of band media you still can control it from the cloud
... in band media - you can control it in the cloud, ot locally

<kaz> s

colin: not sure its more understandable
... now its better
... Nilo - main concern - if someone else is reading this page
... Its very hard to understand for other ppl
... combine - from 1 place
... separate - from different places
... Nilo - we have to make it cristal clear
... could you explain more?
... either you send it together for a single stream
... or you separate them - so they come from DIFFERENT places
... Alexandra's task - to make it clear
... implementation case: 1st scenario - UI is sent to the client directly, media delivered separatly
... 2nd - they are mixed together - and control then are sent by the cloud browser
... end user request is sent to the CB
... we could use 2 scenarios: SS CLoud Player, DS Local Player
... Nilo: 1st case - over the CB, 2nd case - directly to the client

<colin> alexandra: will update approaches section on the wiki

colin: Nilo: out of band case - 2 cases: one - client is sending state to the CB, another - client sends the key strokes to the CB
... what is about the state that we send to the CB?
... Colin: we have a broadcast signal - CB needs to know what channel you are on
... then the client will send the state to the CB
... Nilo - could we use this example for both?
... Nilo - trickplay -
... Nilo: what is equivalent of that for the 2nd approach?
... colin: its the state

<inserted> scribenick: colin

alexandra: will put an example what happens on the client and what happens in the cloud.

<NiloMitra> https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/Architecture

nilo: bothered with a few words in the terminology such as rendering. Some words are not clear. Ask the team to to explain.

alexandra; explains why they choice the terms.

Nilo: rendering is done in every stage.

alexandra: different terms ui rendering, video rendering. broad term indeed. should use different terms for that
... nilo will update the wiki and will update the mailing list
... will update the terminology for an application
... question to the group. remove discovery use case.

colin: thinks is still needed

alexandra: do we need different levels of requirements?

kaz: up to the group. Could try and revisit the requirements

alexandra: we don't have a lot af requirements. Propose not to use levels. maybe ofter TPAC?
... put section synchronisation for use cases

colin: will update communication use cases according to the template

<kaz> [ adjourned ]

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/06/08 14:19:16 $