RE: [Cloud Browser] Terminology section update/ Extended pics for fat-, thin- and zero-client terms

I took the liberty of changing the term “Fat client” to “Thick client”, as the latter is the more normal usage.
Thanks,
Nilo

From: Alexandra.Mikityuk@telekom.de [mailto:Alexandra.Mikityuk@telekom.de]
Sent: Tuesday, March 15, 2016 1:16 PM
To: paul_higgs@hotmail.com
Cc: john.foliot@deque.com; public-web-and-tv@w3.org
Subject: RE: [Cloud Browser] Terminology section update/ Extended pics for fat-, thin- and zero-client terms

Deal Paul,

Thank you for your comments.

I like your idea about data driven and application centric models. As I do not want to extend the terminology section, I have put your explanations into the Evolution of the TV UI section. You can find it here [1].

The updated pictures you can find in [2], [3] and [4]. I have put my comments in your email below.

[1] https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/Architecture#Evolution_of_the_TV_UI

[2] https://www.w3.org/2011/webtv/wiki/File:Fat-client-01.png

[3] https://www.w3.org/2011/webtv/wiki/File:Thin-client-01.png

[4] https://www.w3.org/2011/webtv/wiki/File:Zero-client-01.png


Mit freundlichen Grüßen / Viele Grüße / Best Regards
Alexandra Mikityuk


DEUTSCHE TELEKOM AG
T-Labs (Research & Innovation)
Alexandra Mikityuk
Winterfeldtstr. 21, 10781 Berlin
+4930835358151 (Tel.)
+4930835358408 (Fax)
E-Mail: alexandra.mikityuk@telekom.de<mailto:alexandra.mikityuk@telekom.de>
www.telekom.com<http://www.telekom.com/>
Erleben, was verbindet.

Die gesetzlichen Pflichtangaben finden Sie unter: www.telekom.com/pflichtangaben<http://www.telekom.com/pflichtangaben>

Grosse Veränderungen fangen klein an – Ressourcen schonen und nicht jede E-Mail drucken.


From: Paul Higgs [mailto:paul_higgs@hotmail.com]
Sent: Dienstag, 15. März 2016 16:28
To: Mikityuk, Alexandra; john.foliot@deque.com<mailto:john.foliot@deque.com>; public-web-and-tv@w3.org<mailto:public-web-and-tv@w3.org>
Subject: RE: [Cloud Browser] Terminology section update/ Extended pics for fat-, thin- and zero-client terms

Hi Alexandra

These Fat, Thin and Zero definitions are a good high level start, but here are some points that you may want to try to incorporate.


·        The Fat model is typically "data driven" in that data is supplied to some generally static code on the STB.

·        The Thin model is "application centric" with data being incorporated into the application in the server (when the application is prepared) or in the STB. In this model, it is likely that many different applications comprise the user experience.

·        The Thin model is also likely to make use of service side/cloud processing of logic or data set analysis.

o   Perhaps the Thin-client.jpg should at least show an "App" within the "Browser"



è Sure, I have added an Application Block for LiveTV, VOD, EPG, etc services.


o   Using the colour coding from Fat-client.jpg, the "Browser" box in Thin-client.jpg should be coloured Blue especially for the STB scenario as there are some tight integrations there.


è Thank you for your comment, you are right. I have looked into this and decided to rebuild the pictures without any separation into which parts are supplied by which vendor. I think it makes the whole thing more complex and is not that important at that point



o   Given that some of the application logic runs in the cloud/server in the thin-client model, some "off-STB" processing should also be depicted.


è I have extended the picture with the Application Server.



·        Given that the definition of the Zero Client states that "Rendering and execution of the UI resides in the cloud", the image needs to show a presentation/interaction layer above the "Driver Layer" "Operating System" and "Secured Link" boxes, since that is what this effort is attempting to harmonize. Perhaps this presentation/interaction layer is the "Cloud Browser/Media Player"


è I have extended the picture with the Media Player block and the Cloud browser RTE block.

Hope, its getting better now.

Paul

From: Alexandra.Mikityuk@telekom.de<mailto:Alexandra.Mikityuk@telekom.de> [mailto:Alexandra.Mikityuk@telekom.de]
Sent: Tuesday, March 15, 2016 10:18 AM
To: john.foliot@deque.com<mailto:john.foliot@deque.com>; public-web-and-tv@w3.org<mailto:public-web-and-tv@w3.org>
Subject: [Cloud Browser] Terminology section update/ Extended pics for fat-, thin- and zero-client terms

Dear John, dear all,

first of all thank you for the job done. Great!

In the meanwhile, I have extended the table you have provided. You can file the updated version here [1].
@all: please, take a look at the terminology section, whether it makes sense for you or not. Your comments are very very welcome.

For better understanding, I have also provided small explanation pictures for the three different client concepts. You can find them in the table or separate for the fat client [2], thin client [3] and zero client [4] accordingly.

[1] https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/Architecture#Terminology

[2] https://www.w3.org/2011/webtv/wiki/File:Fat-client.png

[3] https://www.w3.org/2011/webtv/wiki/File:Thin-client.png

[4] https://www.w3.org/2011/webtv/wiki/File:Zero-client.png


Mit freundlichen Grüßen / Viele Grüße / Best Regards
Alexandra Mikityuk


DEUTSCHE TELEKOM AG
T-Labs (Research & Innovation)
Alexandra Mikityuk
Winterfeldtstr. 21, 10781 Berlin
+4930835358151 (Tel.)
+4930835358408 (Fax)
E-Mail: alexandra.mikityuk@telekom.de<mailto:alexandra.mikityuk@telekom.de>
www.telekom.com<http://www.telekom.com/>
Erleben, was verbindet.

Die gesetzlichen Pflichtangaben finden Sie unter: www.telekom.com/pflichtangaben<http://www.telekom.com/pflichtangaben>

Grosse Veränderungen fangen klein an – Ressourcen schonen und nicht jede E-Mail drucken.


From: John Foliot [mailto:john.foliot@deque.com]
Sent: Mittwoch, 2. März 2016 17:23
To: public-web-and-tv@w3.org<mailto:public-web-and-tv@w3.org>
Subject: [Cloud Browser] My To-Do's

Hi all,

As discussed on today’s call, I’ve made some changes to the wiki:

Moved Terminology into a table to accommodate alternative names/terms for concepts being discussed: https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/Architecture#Terminology


Added a new section to Use Cases for accessibility, and provided some backgrounder links there: https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/UseCases#accessibility


Linked the Architecture page to the main Cloud Browser page (because it wasn’t there before):
https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF#Resources



I also mentioned Shadow DOM on the call today, and more details about that can be found at:
https://www.w3.org/TR/shadow-dom/


I’m not sure at this point whether this is relevant or not, but as explained, this concept was worked out to address accessibility requirements for the <canvas> element in HTML5, which essentially allowed the browser to ‘paint’ pixels to the screen (and animate them, both via JavaScript), but lacked any kind of scaffolding or framework that the Accessibility APIs could interact with. Shadow DOM addressed that problem, and is in production today. I’ve also added a link from Steve Faulkner that provides a primer on the accessibility tree requirements, as well as a link to the Core Accessibility API mappings – hope this helps.

Cheers!

JF
​--
John Foliot
Principal Accessibility Strategist
Austin, TX

Deque Systems Inc.
2121 Cooperative Way, Suite 210,
Herndon, VA 20171-5344
Office: 703-225-0380
john.foliot@deque.com<mailto:john.foliot@deque.com>

Advancing the mission of digital accessibility and inclusion