See also: IRC log
kaz: sent the transition request
for the Note out
... and got some comment from W3C Team mates
<coln> https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/cloud_browser_vs_split_browser
kaz: I'll respond to that but maybe we might want to add references for existing mechanisms similar to the Cloud Browser, e.g., X Window System and Opera Mini
colin: there is some description on the wiki about the similarity/difference
kaz: what do you think about event exchange within X Window?
colin: maybe the similarity is entity A renders the graphics and entity B handles user input
kaz: ok
colin: was planning to publish another note for split browser
kaz: maybe would be better to put both within one document and explain the similarity and difference
cloud browser vs split browser
kaz: does ActiveVideo provide Split Browser as well as Cloud Browser?
colin: our approach is kind of hybrid
kaz: this wiki page is a good resource for our future discussions
kaz: maybe we might want to think
about extensibility for UI for accessibility
... using various cloud services
chris: using additional cloud
services
... voice recognition, etc.
kaz: it would be much easier than client-side browsers
chris: any kind of devices can use that capability regardless of their own types
colin: good to have that kind of use cases
chris: applicable to any kind of
devices like mobile
... device-agnostic approach
kaz: there is a possibility that
a cloud browser application can work on a smartphone
... would it be OK if Chris and I add some use cases?
colin: great to have typical
examples
... would be good to keep the scope within TV area
kaz: ok to consider "accessible TV" by extending TV capability using accessibility portion?
chris: should be ok
colin: note that some other standardization bodies also handle accessibility standards
chris: tree of connected devices and serialized resources
colin: web technology allows you
create accessible pages/apps
... using assistive technologies
... orchestration should handle accessibility
kaz: Chris can provide some use
cases for accessibility
... btw, how to combine broadcasting signals and IP-based video
signal might be one use case for hybrid TV?
colin: maybe out of scope of this TF?
kaz: in that case, who would combine those signals?
colin: there is only video element within Cloud Browser
kaz: in that case, cloud browser doesn't care the source of video signals?
colin: it depends
... there could be double stream approach
kaz: how should we update this use case wiki?
colin: we already have some use cases linked from this wiki
kaz: so the expected next step is
not only adding new use cases
... but analyzing the existing use cases and think about which
are the "Impact Use Cases"?
colin: yes
... and we need more people for that purpose
kaz: wondering which would be our
preference
... publishing a use case note based on this wiki right
away
... or publishing a note after updating/analyzing the wiki
colin: let's continue the discussion during the next call
kaz: ok
[ adjourned ]