Review of the previous call discussion

Apr 19 minutes

alex: didn't attend the previous call and briefly review the discussion from that call

colin: discussed publication preparation for the Note
... there was questions from the W3C Team
... about what Cloud Browser was like
... e.g., difference from X Window system

Cloud Browser Architecture Note publication update

kaz explains what happened so far

and ask all if it's ok to add a note about our publication plan (=publishing this architecture note first; and then publish use cases/requirements and comparison documents next; and compile all those documents as one updated Note later) to the introduction section of this architecture Note

it would be even clearer to add that note

all agree we add a note for that purpose

given it's ok by us all, Kaz will get back to the W3C Management and work for publication

Use cases

chris: wondering about the accessibility use cases

alex: we can add them to the use case wiki

chris: would like to add a section to the wiki

all: ok

alex: question on accessibility use cases

chris: there are limited opportunity for disabled people
... would like to clarify the outline of people's requirements

colin: would be really useful

use case wiki

colin: there is a section for accessibility there

(currently just include links to resources)

alex: use cases for basic interaction is blue (within the diagram)
... and the green line is "impact use cases"
... you can start your work on accessibility and add use cases
... you can expand your use cases on a separate wiki page like the one for "Tuner"

https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/UseCases/Tuner

Main TF page

alex: on the main page, we have a list of documents
... would like to extend it
... e.g., difference between cloud browser and other technologies

main TF page

kaz: are you talking about the "Resources" section?

alex: (goes through "Success Criteria" section and "Deliverables")
... maybe we should add some description about our plan for documents

colin: we're publishing the architecture note
... and have resources for use cases/requirements and comparison
... maybe one/two sentence about the structure/plan would suffice

kaz: to which section do you want to add that description?
... maybe the "Deliverables" section?

alex: yeah

kaz: maybe we can simply add a subsection to "Deliveralbles" section
... saying "Publication plan"
... mentioning "architecture note first, and uc/req and comparison next"

alex: we have resource on comparison to split browser, X Window, etc.
... would be better to clarify the difference from split browser

kaz: btw, maybe it would be clearer to make the current "Resources" section a subsection of the "Deliverables" section
... because it's a list of our own resources for our deliverable documents

alex: yes, those are our own resources

Use cases (revisited)

alex: next, what about the use cases?

colin: would like to update the use cases for the next call

alex: ok
... I've put QoE/QoS use cases under "Impact Use Cases"
... from my viewpoint, this list is ok

kaz: regarding the title, I personally think it would be easier to understand if we said "advanced use cases" instead of "impact use cases" and "basic use cases" instead of "cloud browser use cases"

chris: was also not sure what "impact use cases" meant
... maybe we could change the category name at some point

colin: we thought these names were a bit more friendly than "issues", etc.

alex: green line includes how to work with legacy framework

kaz: ok. we can revisit naming issue later.

alex: colin working on the impact use cases
... I'll be working on HbbTV signaling
... to be discussed at the next call
... Chris will work on the accessibility

kaz: at some point I can help accessibility and user interface

alex: any other business?

chris: will be travelling and maybe can't make the next calls
... will try to join, though

[ adjourned ]