W3C

- DRAFT -

Web and TV IG: Cloud Browser TF call

02 Mar 2016

Agenda

See also: IRC log

Attendees

Present
Kaz, Alex, Colin, John, Yosuke, Louay, Harrison, Kumanan, Nilo, So, Julian, Bill
Regrets
Chair
Alexandra
Scribe
kaz

Contents


Introduction

<kaz> scribenick: kaz

alexandra: is Entrix people online?

kaz: not yet

(Harrison from Entrix joins)

harrison: from Entrix
... appreciate your have changed the time slot
... working for Entrix, one of the subsidiaries of SK Telecom
... targeting US, China and South Asia, etc.
... would like to make contribution as much as possible

alex: tx!
... please introduce yourself to Harrison :)

kaz: from W3C

colin: from Activevideo, Invited Expert

john: from Deque System, here for accessibility
... accessibility is like security and privacy, it needs to be architectural
... W3C WAI domain

kumanan: CTO from Espial
... server software for IPTV and Cable TV
... cloud browser technology

louay: from Fraunhofer FOKUS
... multi-screen domain
... relationship to W3C's second screen APIs

nilo: from Ericsson

so: head of advanced technology from NAB
... migrating broadcasting with IP platform

yosuke: from W3C
... also one of the co-Chairs of the Web&TV IG, TV Vertical Champion and Team Contact for the Media Extensions WG

alexandra: have short agenda
... architecture and use cases
... emails during the last 2 weeks
... use cases presented by Colin
... if you have any addition, please speak up

Architecture

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

alex: would see use cases and clarify what kind of architecture is required
... what kind of different architectures are possible
... the goal of this TF is not defining the architecture itself
... but to see use cases
... the terminology we use this time, e.g., in-band media
... you can see we've done so far
... there is some description on the wiki with some diagram

nilo: difficult to understand...
... regarding terminology
... TV local UI could be broken up into one version of a thin client

alex: much noise on your line...
... asking about the terminology section?
... would propose to see the email exchange
... good to have discussion now

nilo: we have to have definition clearly
... "zero client" makes sense
... but "TV local UI" using middleware is unclear
... the language "local" is a bit odd

<JF> +1 to a clearer understanding of native client

alex: within the cloud browser concept
... the thickness of the client matters
... bigger client functionality implies "local UI"

Colin: don't have strong opinion on the naming

nilo: the terminology is very important
... we're going to use the terminology

colin: agree

<JF> +1 to Nilo, shared terms and understanding is very important

yosuke: just fyi
... I'm familiar with terminology for TV
... can provide some language for the terminology definition

kaz: similar to John
... but would suggest we have a matrix table of idea vs. terminology
... also should consider the features for each idea

<yosuke> [From the PoV of TV manufactures, the first one => Middleware UI, the second one => Resident (Native) application if it's not HTML, HTML application if it's HTML]

john: would suggest we create a table with 3 columns, and put brief definition of what each terminology means
... people can make contribution to the wiki directly

<Zakim> JF, you wanted to propose a matrix, which shows this TF's term choices, and then a "thesaurus" of sorts

<yosuke> John: https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/Architecture#Terminology

alex: would suggest people put their ideas on the Terminology section directly

john: happy to put something
... and others also can make contribution

louay: comment on Runtime
... the current description "runs the cloud browser and usually exist on actual hardware"
... runtime environment is on the client side, isn't it?

alex: yes

louay: also missing user component
... capability to interact with user
... need to send user input to the cloud

alex: tx
... that's a good comment
... about user input, good to mention that within the architecture diagram
... very good to describe communication use cases
... would put that as my action item

<scribe> ACTION: alexandra to put use input into the architecture diagram [recorded in http://www.w3.org/2016/03/02-webtv-minutes.html#action01]

<trackbot> Created ACTION-215 - Put use input into the architecture diagram [on Alexandra Mikityuk - due 2016-03-09].

Use Cases (Communication)

-> https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/UseCases Use Case wiki

-> https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/UseCases/communication use case (communication)

colin: general use case of input
... and output

-> https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/UseCases/communication#input Input

-> https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/UseCases/communication#output Output

colin: is that a correct way?

alex: want you to briefly present the use cases
... let me share the screen
... (alex shares her screen)

-> https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/UseCases Main Use case wiki

alex: there is "communication" section
... for Use cases for communication
... signaling, session, video

(alex rejoined)

alex: video and audio
... user interface, service
... and security including EME and cloud ca

john: what is "Cloud CA"?

alex: different conditional access
... on the cloud side
... there are different systems
... some of them are downloadable

john: ok
... struggling to provide comments from accessibility
... trying get behind the display
... might want to use different modalities
... what if you can't use usual pointer devices?
... happy to provide those kind of use case stories

alex: got it
... where should we put that kind of requirements?
... interact with our systems
... accessibility use case?

john: want to be careful
... you have requirement in US
... people with disability to access video
... long-standing policy of all the specs from W3C have accessibility reviews
... the goal is avoiding accessibility barrier
... our plan is working with you from the early stage
... because you're doing requirements gathering
... would propose we understand the issues of accessibility as well
... think me as a resource for accessibility
... how things interact with people
... interested in your UA layer
... but the UI for blind person, etc., may affect additional software
... from architectural viewpoint, do you have vision on accessibility?

alex: have to read documents you provided
... accessibility API, etc.
... don't have answers now
... we can extend the requirements

<yosuke> [Yosuke: MSE in Video is a bit misleading. MSE also deals with audio and texttracks. EME in Security is also a bit strange. It's all about Content Protection.]

john: happy to contribute
... shadow DOM provides accessibility support for canvas
... was sort of background structure
... has accessibility API to connect to

alex: would put that as well on my action point

kaz: maybe we might want to consider media accessibility requirements as the part of this requirements document

john: provided some resources

alex: ok
... would proceed with the Use Case wiki
... we can add modification to this
... would like to open up questions
... you can update the wiki directly
... or send your comments to the list

colin: the structure is important
... important to have a couple of use cases
... would ask you all to put your use cases here

<JF> link to my previous email: https://lists.w3.org/Archives/Public/public-web-and-tv/2016Feb/0020.html

colin: would be good to have John's accessibility portion too

alex: Harrison, you may have some additions?

harrison: let me add one comment to the terminology

harrison: identify if the rendering is done whether on the client side or the server side

alex: tx

harrison: would suggest update the terminology section
... client-side rendering vs. cloud-side rendering

Terminology section of the Architecture wiki

harrison: regarding the use cases wiki
... HbbTV 2.0 started services including two kinds of categories
... two reasonable categories: broadcasting-dependent vs. broadcasting-independent

Use Case wiki

Use Case for Communication wiki

alex: related to service use cases?

harrison: right

alex: what "broadcast" here means?

harrison: implies linear video
... coming through the tuner
... the browser handles unicasting video
... but multicasting video is used for TV services
... linear video vs. multicast video

alex: in this TF, would try browser API
... not sure about HbbTV approach
... but good to have that idea as well
... would add "linear vs multicast" to the terminology

harrison: would try detailed description

alex: great
... also "client-side vs. cloud-side" as well?

harrison: yes

alex: question to Louay?
... multi-screen concept for cloud browser?

louay: already had discussion here with my colleagues
... advantage with cloud browser is that it would be easier to handle multiple screens
... need capability of discovery
... on the set-top box
... by just providing the link to the cloud browser
... regarding 360-degree video
... you can use your smartphone to control multiple screens

alex: synchronization locally
... important for gaming and cloud 360
... good to have an initial description

<JF> allowing a smart phone/device the ability to connect to your cloud browser *might* also help address many, if not all, of your accessibility concerns as well, as it becomes a physical connection point (that starts out pretty accessible already)

alex: so that people can extend it

louay: we identify new requirements for cloud browser

alex: as I proposed last time, during this week would have input for the architecture and use cases
... we got several action points during this call too
... we continue to work with the terminology section as well

<JF> https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/Architecture#Terminology

john: made a slight change to the wiki
... put a table with 3 columns, Term, Definition and Also known as

nilo: would make contribution
... might want to change the first column, Term, itself, though

kaz: we can start with putting our own ideas to the "Also Known As" field :)

alex: please put your name to the TF participants wiki
... if you don't have any questions, additions or comments, we are done today
... next call in 2 weeks on March 16th.

[ adjourned ]

Summary of Action Items

[NEW] ACTION: alexandra to put use input into the architecture diagram [recorded in http://www.w3.org/2016/03/02-webtv-minutes.html#action01]
 

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/03/02 15:46:53 $