[Cloud Browser] minutes - 3 April 2017

available at:
  https://www.w3.org/2017/05/03-webtv-minutes.html

also as text below.

Thanks,

Kazuyuki

---

   [1]W3C

      [1] http://www.w3.org/

                               - DRAFT -

                      Web&TV IG - Cloud Browser TF

03 May 2017

   See also: [2]IRC log

      [2] http://www.w3.org/2017/05/03-webtv-irc

Attendees

   Present
          Kaz, Alexandra, Chris, Colin

   Regrets
   Chair
          Alexandra

   Scribe
          kaz

Contents

     * [3]Topics
         1. [4]Review of the previous call discussion
         2. [5]Cloud Browser Architecture Note publication update
         3. [6]Use cases
         4. [7]Main TF page
         5. [8]Use cases (revisited)
     * [9]Summary of Action Items
     * [10]Summary of Resolutions
     __________________________________________________________

Review of the previous call discussion

   [11]Apr 19 minutes

     [11] https://www.w3.org/2017/04/19-webtv-minutes.html

   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

   [12]use case wiki

     [12] https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/UseCases

   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"

   [13]https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_
   TF/UseCases/Tuner

     [13] 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

   [14]main TF page

     [14] https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF

   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 ]

Summary of Action Items

Summary of Resolutions

   [End of minutes]
     __________________________________________________________


    Minutes formatted by David Booth's [15]scribe.perl version
    1.152 ([16]CVS log)
    $Date: 2017/05/03 16:14:07 $

     [15] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [16] http://dev.w3.org/cvsweb/2002/scribe/


-- 
Kaz Ashimura, W3C Staff Contact for WoT, TV and Geo
Tel: +81 3 3516 2504

Received on Wednesday, 3 May 2017 16:24:43 UTC