[cloud browser] minutes - 20 February 2018

available at:
  https://www.w3.org/2018/02/20-me-minutes.html

also as text below.

Thanks,

Kazuyuki

---

   [1]W3C

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

                               - DRAFT -

             Media and Entertainment IG - Cloud Browser TF

20 Feb 2018

Attendees

   Present
          Kaz_Ashimura, Chris_O'Brien, Colin_Meerveld

   Regrets
          Alexandra

   Chair
          Kaz

   Scribe
          kaz

Contents

     * [2]Topics
         1. [3]Agenda
         2. [4]GitHub
         3. [5]Use cases
         4. [6]More participation
         5. [7]Use cases (revisited)
         6. [8]Notes on the next TF call and the next IG call
     * [9]Summary of Action Items
     * [10]Summary of Resolutions
     __________________________________________________________

Agenda

   kaz: use case discussion?

   colin: and github usage

GitHub

   colin: made some changes to the github

   <colin> [11]https://www.w3.org/TR/cloud-browser-arch/

     [11] https://www.w3.org/TR/cloud-browser-arch/

   <colin>
   [12]https://w3c.github.io/Web-and-TV-IG/cloud-browser-tf/

     [12] https://w3c.github.io/Web-and-TV-IG/cloud-browser-tf/

   <colin> [13]https://w3c.github.io/me-cloud-browser/

     [13] https://w3c.github.io/me-cloud-browser/

   kaz: we should use the latter repo (me-cloud-browser)

   colin: right
   ... but still wrong link

   [14]official Note

     [14] https://www.w3.org/TR/cloud-browser-arch/

   [15]old repo

     [15] https://w3c.github.io/Web-and-TV-IG/cloud-browser-tf/

   [16]new repo

     [16] https://w3c.github.io/me-cloud-browser/

   colin: the official published Note has a link to the old repo

   kaz: we should leave it as is because we can't change it
   ... on the other hand, we should use the new repo URL for our
   next publication

   colin: ok

   kaz: that implies the new Editor's draft at:
   [17]https://w3c.github.io/me-cloud-browser/
   ... should have the link to itself
   ... [18]https://w3c.github.io/me-cloud-browser/
   ... for the "Editor's draft" link

     [17] https://w3c.github.io/me-cloud-browser/
     [18] https://w3c.github.io/me-cloud-browser/

Use cases

   colin: put use cases on the draft Note at:
   [19]https://w3c.github.io/me-cloud-browser/
   ... would be better to have accessibility use cases as a
   separate Note
   ... so that we can easily reuse it for the other specs

     [19] https://w3c.github.io/me-cloud-browser/

   chris: for the accessibility framework in addition to all the
   possible use case areas
   ... but how to handle it?
   ... could be reused for smart fridge, etc.
   ... binding accessibility framework for various industries
   ... make sense to do that as part of some specific group?
   ... or dedicated new task force?

   kaz: possibly WoT WG might be going to have a TF for
   accessibility
   ... you might want to join their telco and f2f meeting

   chris: maybe join remotely?

   kaz: ok
   ... I'd like to introduce you to Graeme and the WoT Chairs

   chris: ok
   ... anything could be a WoT device
   ... given everything is connected to the Web

   kaz: user preference, etc., should be also considered for WoT

   chris: right

   colin: possibly extension and other capability

   chris: something cloud browser could leverage also

   colin: even if the current WoT doesn't handle accessibility,
   the goal should include accessibility as well

   chris: abstracted layer for orchestration?

   colin: yes
   ... could make the service accessible even when the (original)
   mechanism itself is not accessibly

   chris: could help people speed up making systems accessible

   colin: good to work with the WoT guys about this point
   ... and other use cases on the updated draft Note

   [20]use case description

     [20] https://w3c.github.io/me-cloud-browser/#use-cases

More participation

   chris: how to get more people?

   kaz: let's talk with the ME Chairs
   ... and if it's ok by them, we can send a cfp message to the
   whole group
   ... fyi, there was some discussion on media timed event
   ... possibly some relationship with the cloud browser work

   chris+colin: right

   kaz: will talk with the ME Chairs CCing you
   ... also check with Alexandra
   ... anything else for today?

Use cases (revisited)

   kaz: do you want to review the use case description?

   colin: same content when we reviewed using the wiki

   kaz: ok
   ... in that case, another question is if we want to use another
   detailed use case template
   ... or simply continue to use this style?

   colin: started some refinement

   kaz: do you want to refine the description a bit more before
   getting the whole IG review?

   colin: we discussed some of the use cases already
   ... within the TF
   ... already good enough from the TF viewpoint
   ... so we could go ahead and ask the whole IG for review

   kaz: so need Alexandra's confirmation
   ... anything else for today?

   (nothing)

Notes on the next TF call and the next IG call

   kaz: the next TF call will be in 2 weeks on March 6 (at 6am US
   Eastern)
   ... notes the updated whole IG call will be also on Tuesday
   right after this slot (=7am US Eastern) starting with March 6
   ... the IG call is a monthly call and held on the first Tuesday

   [adjourned]

Summary of Action Items

Summary of Resolutions

   [End of minutes]
     __________________________________________________________


    Minutes formatted by David Booth's [21]scribe.perl version
    1.152 ([22]CVS log)
    $Date: 2018/02/20 14:53:51 $

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

Received on Tuesday, 20 February 2018 14:58:25 UTC