<scribe> scribe: Nilo

The architecture chapter is now finalized

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

we should start to review the chapter and provide comments on clarity etc.

Review it in the next two weeks

Either send public comments or correct minor mistakes directly in the wiki

We'll discuss the changes in the next meeting, two weeks from now.

Chapter should be finalized before TPAC

Colin: some of the terminology seems interchangeable
... look more closely at the differences between the text and images, e.g., what does "input data" mean?
... This way those who use our pictures (e.g., GSMA) will not have pictures which are not properly explained

Alexandra has also updated the TF page

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

Added Colin's text on introduction to the cloud browser.

<alexandra> https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/Introduction_cloud_browser

Colin notes that this is his perspective and would appreciate more input from others.

cloud browser should not have any special APIs. This way applications do not have to change.

Colin's second point is that the client should have a small addition, the RTE, which needs to communicate with the orchestration

<colin> A Cloud Browser is unspecified. i.e. it could be everything from a html5 enabled browser to an android OS

<colin> The client device should be agnostic only a small addition is needed called a RTE

<colin> The RTE only provide input but doesn't interpreted it

<colin> The RTE communicated with the Orchestration

Aexandra notes that these points seem like requirements.

The first point could be stated as a requirements: the browser should not be extended with any APIs.

The signaling between the RTE and Orchestration needs to be standardized.

Also, we should focus on the gaps in W3C specs to see if gaps exists. For example, a vibrate API might not work if the interaction is synchronous.

Another example might be the determination of quality metrics at a client rather than at the browser.

Colin suggests looking at W3C specs to identify cases where these might not work for certain use cases.

There might be gaps found for accessibility in a cloud browser environment.

Alexandra willl contact John F on accessibility use cases.

<alexandra> https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/UseCases

Colin suggests splitting this so that at TPAC we finalize the architecture while after TPAC we concentrate on completing the use cases and requirements

Alexandra also proposes finalizing the first 4 use cases

Alexandra sill also provide a status document for presentation to TPAC

Kaz mentioned if WebTV could meet with WoT IG at TPAC.

(all are interested)

Kaz will get back to the WoT IG and suggest we have a joint meeting between the Cloud Browser TF and the WoT IG.

Colin asked in the concept of split browser could also be discussed with the TAG at TPAC. will get back to the WoT IG and suggest we have a joint meeting between the Cloud Browser TF and the WoT IG.

Kaz will generate an agenda for the Web TV IG meeting

No further items for discussion. So meeting closed. Meet again in 2 weeks.