W3C home > Mailing lists > Public > public-web-and-tv@w3.org > March 2016

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

From: <Alexandra.Mikityuk@telekom.de>
Date: Tue, 15 Mar 2016 15:18:25 +0100
To: <john.foliot@deque.com>, <public-web-and-tv@w3.org>
Message-ID: <DFCEF737B0F85B46B6CD03C6CEE84178DCB6F89C7D@HE111642.emea1.cds.t-internal.com>
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
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
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

Received on Tuesday, 15 March 2016 14:19:18 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 15 March 2016 14:19:19 UTC