See also: IRC log
<scribe> scribenick: kaz
am: welcome, Chris!
... we're publishing an IG note for the CB architecture
... not a big document
... high level cloud browser description
<alexandra-mikityuk> https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/groupnote
co: accessibility officer from AMI
am: tx
<chris> thanks you - happy to be here
am: we can talk about accessibility part and the detail of the IG Note
Cloud Browser Architecture draft on the wiki
am: (explains the draft)
... discussion on the interface between the CB and the
client
... maybe Colin also can introduce himself?
cm: (explains his work)
... focusing on set-top-box
<chris> ok
am: explaining the draft would be helpful
cm: we're working on the draft
architecture document
... single stream approach and double stream approach
... how to make them accessible may be interesting to you
... set-top-box just provides media stream
... plugin assistive technology may be used
... there is a gap with accessibility
co: actual UI is handled by the Cloud Browser Client?
cm: yes
... key inputs like mouse events are transferred to the Cloud
Browser Server
... both the single stream approach and the double stream
approach are cloud browsers
am: if I go to the wiki page of
the TF
... there are use case descriptions as well
<alexandra-mikityuk> https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/UseCases
am: there is a section for
accessibility
... which includes resources provided by John
... we can provide some more wiki resources as well
<colin> https://www.w3.org/2011/webtv/wiki/Main_Page/Cloud_Browser_TF/Introduction_cloud_browser
cm: the above wiki also includes accessibility section
am: let's go back to the
Architecture note draft
... Colin has started to move the content to GitHub
cm: currently generating the draft HTML on my private GitHub repo
ka: can create a repo under the
W3C area
... let's wrap up the IG Call for Consensus first
... then talk with Mark about where/how to put the draft for publication
... and after getting his OK, copy Colin's draft to the IG github area
cm: what about Editors/Acknowledgements?
ka: Editors are those who edited the wiki and/or the HTML
... Authors are those who provided concrete text for the draft
... we can include all the people who provided ideas (on the ML and/or during the call)
cm: we can visit the TF
participants list and include them in the Acknowledgements
section
... who should be included in the ack section of the
architecture doc?
... Nilo, Kaz, Steve, Oliver
... will add the above people for the first version Note
am: question on the structure of the doc
cm: this initial version was
automatically generated
... can change the structure if needed
kaz: the structure should be same as the wiki version because the group review was done based on the wiki version
cm: will fix the structure
... and will send it to the repo location
kaz: repeats the proposed procedure:
... let's wrap up the IG Call for Consensus firstcm: sounds like a plan
am: btw, we used capital letter
for the section titles, e.g., "Client Device"
... so let's follow that notation
... ok
... let's continue the edit, wrap up the group approval and
talk with Mark about the next step
... let's check the progress at the next meeting in two weeks
(March 22)
kaz: ok
... btw, the IG charter runs out the end of April, and we need
extension
... will talk with Mark
am: ok
... questions?
(none)
kaz: please note the daylight
savings in US and EU
... will mention that point when I send the minutes out to the
group
[ adjourned ]