Minutes IndieUI Teleconference 1 April 2015
http://www.w3.org/2015/04/01-indie-ui-minutes.html
Minuts IndieUI Teleconference 18 March 2015
http://www.w3.org/2015/03/18-indie-ui-minutes.html
Minutes IndieUI Teleconference 17 December 2014
http://www.w3.org/2014/12/17-indie-ui-minutes.html
[POSTPONED] Re: IndieUI Teleconference Agenda; 12 November at 22:00Z for 60 minutes
After discussion with Janina, we've had enough regrets on and off list that it seems we won't have quorum for today's IndieUI call. Therefore, we will postpone the call to next week. The next IndieUI call will be: Wednesday, 19 November at the usual time. Michael On 11/11/2014 8:44 PM, Janina Sajka wrote: Cross-posting as before ... What:IndieUI Task Force Teleconference When:Wednesday 12 November 2:00 PMSan Francisco -- U.S. Pacific (Standard) Time (PST: UTC -8) 4:00 PMAustin -- U.S. Central (Standard) Time (CST: UTC -6) 5:00 PMBoston -- U.S. Eastern (Standard) Time (EST: UTC -5) 10:00 PMLondon -- British (Standard) Time(BST: UTC +0) 11:00 PMParis -- Central European Time (CET: UTC +1) 6:00 AMBeijing -- China Standard Time (Thursday, 13 November CST: UTC +8) 7:00 AMTokyo -- Japan Standard Time(Thursday, 13 November JST: UTC +9) Where:W3C Teleconference--See Below * Time of day conversions Please verify the correct time of this meeting in your time zone using the Fixed Time Clock at: http://timeanddate.com/worldclock/fixedtime.html?msg=IndieUI+Teleconferenceiso=20141112T1700p1=43ah=1 ** Preliminary Agenda for IndieUI Task Force Teleconference 12 November 2014 Meeting: IndieUI Task Force Teleconference Chair:Janina_Sajka agenda+ preview agenda with items from two minutes agenda+ Holliday Scheduling; November-January agenda+Checkin with Web Apps' Editing TF [See below] agenda+ Editor's Report agenda+Requirements Use Cases Progress agenda+Testing Conversation; Polyfills agenda+ User Context Issues Actions https://www.w3.org/WAI/IndieUI/track/products/3 agenda+ Events Issues Actions https://www.w3.org/WAI/IndieUI/track/products/2 agenda+ Other Business agenda+Be Done Resource: TPAC Minutes Monday: http://www.w3.org/2014/10/27-indie-ui-minutes.html Tuesday:http://www.w3.org/2014/10/28-indie-ui-minutes.html Resource: Teleconference Minutes http://www.w3.org/2014/10/15-indie-ui-minutes.html Resource: Web Apps Editing TF Editing Explainer:http://w3c.github.io/editing-explainer/ User Intentions: http://w3c.github.io/editing-explainer/commands-explainer.html Resource: For Reference Home Page:http://www.w3.org/WAI/IndieUI/ Email Archive: http://lists.w3.org/Archives/Public/public-indie-ui/ Resource: Teleconference Logistics Dial the Zakim bridge using either SIP or the PSTN. PSTN: +1.617.761.6200 (This is a U.S. number). SIP: za...@voip.w3.org You should be prompted for a pass code, This is 46343# (INDIE#) Alternatively, bypass the Zakim prompts and SIP directly into our teleconference. SIP: 0046...@voip.w3.org Instructions for connecting using SIP: http://www.w3.org/2006/tools/wiki/Zakim-SIP Place for users to contribute additional VoIP tips. http://www.w3.org/2006/tools/wiki/Zakim-SIP-tips IRC: server: irc.w3.org, channel: #indie-ui. During the conference you can manage your participation with Zakim commands as follows: 61# to mute yourself 60# to unMute yourself 41# to raise your hand (enter speaking queue) 40# to lower your hand (exit speaking queue) The system acknowledges these commands with a rapid, three-tone confirmation. Mobile phone users especially should use the mute function if they don't have a mute function in their phone. But the hand-raising function is a good idea for anyone not using IRC. * IRC access An IRC channel will be available. The server is irc.w3.org, The port number is 6665 (Note this is not the normal default) and The channel is #indie-ui. * Some helpful Scribing and Participation Tips http://www.w3.org/WAI/PF/wiki/Teleconference_cheat_sheet For more on the IRC setup and the robots we use for agenda and speaker queuing and for posting the log to the web, see: - For RRSAgent, that captures and posts the log with special attention to action items: http://www.w3.org/2002/03/RRSAgent - For Zakim, the IRC interface to the bridge manager, that will maintain speaker and agenda queues: http://www.w3.org/2001/12/zakim-irc-bot - For a Web gateway to IRC you can use if your network administrators forbid IRC, see: http://www.w3.org/2001/01/cgi-irc - For more on W3C use of IRC see: http://www.w3.org/Project/IRC/
[No quorum] Re: IndieUI Teleconference Agenda; 3 September at 21:00Z for 60 minutes
Only Takeshi and I joined the call, with Jason for a brief hi. This is not enough quorum to discuss anything meaningful so we ended the call after 15 minutes. Michael On 02/09/2014 4:00 PM, Janina Sajka wrote: As before I'm cross-posting this IndieUI agenda As part of IndieUI's continuing open invitation continuing our conversation about working jointly. Allow me to invite you to the next Indie-UI teleconference as detailed below. Please feel free to join us on this call, or any following call. What:IndieUI Task Force Teleconference When:Wednesday 3 September 2:00 PMSan Francisco -- U.S. Pacific (Daylight) Time (PDT: UTC -7) 4:00 PMAustin -- U.S. Central (Daylight) Time (CDT: UTC -5) 5:00 PMBoston -- U.S. Eastern (Daylight) Time (EDT: UTC -4) 10:00 PMLondon -- British (Summer) Time (BST: UTC +1) 11:00 PMParis -- Central European Time (CET: UTC +2) 5:00 AMBeijing -- China Standard Time (Thursday, 4 September CST: UTC +8) 6:00 AMTokyo -- Japan Standard Time (Thursday, 4 September JST: UTC +9) 7:00 AMMelbourne -- Australian Eastern (Standard) Time (Thursday 4 September AEST: UTC +10) Where:W3C Teleconference--See Below * Time of day conversions Please verify the correct time of this meeting in your time zone using the Fixed Time Clock at: http://timeanddate.com/worldclock/fixedtime.html?msg=IndieUI+Teleconferenceiso=20140903T1700p1=43ah=1 ** Preliminary Agenda for IndieUI Task Force Teleconference 3 September 2014 Meeting: IndieUI Task Force Teleconference Chair:Michael_Cooper agenda+ preview agenda with items from two minutes agenda+ Editor's Report agenda+Checkin with Web Apps' Editing TF [See below] agenda+Testing Conversation; Polyfills agenda+Requirements Use Cases Progress agenda+ TPAC Planning http://www.w3.org/2014/11/TPAC/ agenda+ User Context Issues Actions https://www.w3.org/WAI/IndieUI/track/products/3 agenda+ Events Issues Actions https://www.w3.org/WAI/IndieUI/track/products/2 agenda+ Other Business agenda+Be Done Resource: IndieUI Minutes http://www.w3.org/2014/08/20-indie-ui-minutes.html Resource: Web Apps Editing TF Explainer: http://w3c.github.io/editing-explainer/commands-explainer.html Resource: For Reference Home Page:http://www.w3.org/WAI/IndieUI/ Email Archive: http://lists.w3.org/Archives/Public/public-indie-ui/ Resource: Teleconference Logistics Dial the Zakim bridge using either SIP or the PSTN. PSTN: +1.617.761.6200 (This is a U.S. number). SIP: za...@voip.w3.org You should be prompted for a pass code, This is 46343# (INDIE#) Alternatively, bypass the Zakim prompts and SIP directly into our teleconference. SIP: 0046...@voip.w3.org Instructions for connecting using SIP: http://www.w3.org/2006/tools/wiki/Zakim-SIP Place for users to contribute additional VoIP tips. http://www.w3.org/2006/tools/wiki/Zakim-SIP-tips IRC: server: irc.w3.org, channel: #indie-ui. During the conference you can manage your participation with Zakim commands as follows: 61# to mute yourself 60# to unMute yourself 41# to raise your hand (enter speaking queue) 40# to lower your hand (exit speaking queue) The system acknowledges these commands with a rapid, three-tone confirmation. Mobile phone users especially should use the mute function if they don't have a mute function in their phone. But the hand-raising function is a good idea for anyone not using IRC. * IRC access An IRC channel will be available. The server is irc.w3.org, The port number is 6665 (Note this is not the normal default) and The channel is #indie-ui. * Some helpful Scribing and Participation Tips http://www.w3.org/WAI/PF/wiki/Teleconference_cheat_sheet For more on the IRC setup and the robots we use for agenda and speaker queuing and for posting the log to the web, see: - For RRSAgent, that captures and posts the log with special attention to action items: http://www.w3.org/2002/03/RRSAgent - For Zakim, the IRC interface to the bridge manager, that will maintain speaker and agenda queues: http://www.w3.org/2001/12/zakim-irc-bot - For a Web gateway to IRC you can use if your network administrators forbid IRC, see: http://www.w3.org/2001/01/cgi-irc - For more on W3C use of IRC see: http://www.w3.org/Project/IRC/
Minutes IndieUI Teleconference 20 August 2014
http://www.w3.org/2014/08/20-indie-ui-minutes.html
PFWG request for abstract and introductions
The WAI Protocols and Formats Working Group has looked at a number of specifications published by the Web Applications Working Group recently. Our process is to note the publication of documents and take a quick look to determine if they need a closer review. However, many of the documents we have looked at recently have extremely brief abstracts, and no introductions. This makes it very difficult for us to figure out the nature of the specification, and in turn to determine what our interest in it might be. We request that you add more complete abstracts to the specifications, to provide a high-level but more complete idea of what the specification does. We also request that you add introduction sections to the specifications, to explain what problem the technology solves and how (in general terms) it addresses that. We think this will aid our own review and will also greatly help other reviewers to make useful comments. Michael Cooper PFWG staff contact
PFWG comments on View Mode Media Feature
This is a review of the Last Call draft of the View Mode Media Feature located at: http://www.w3.org/TR/2010/WD-view-mode-20100420/ This is a formal response form the Protocols and Formats Working Group. Approval to send this response is archived at http://www.w3.org/2010/05/19-pf-minutes.html#item06. Our thanks to Gregory Rosmaita and Gottfried Zimmerman for preparing this comment. The Last Call draft of the View Mode Media Feature states that it Applies to: visual and tactile media types http://www.w3.org/TR/2010/WD-view-mode-20100420/#the--view-mode--media-feature While these view modes make sense for visual media types, they don't seem appropriate for the two tactile media types braille and embossed, as defined in Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification. in Section 7.3 Recognized media types http://www.w3.org/TR/CSS2/media.html#media-types Please consider the following: 1. A user using a screen reader with a braille display. Should the user agent switch to the CSS rules defined for media type braille? This would be odd and unexpected behavior, since the primary interaction mode is visual. (Note: There are windows on a screen that the screen reader reads out and feeds the braille display). 2. In a pure tactile interaction environment which is not mediated through a visual screen, does the WIMP (Windows, Icons, Menus, Pointers) interaction model make sense at all? It could make sense in a 2D tactile pin matrix environment where raised dots are used to present letters (braille) and graphical strokes, and these dots can be used for interaction with the user. But it does not make sense for the current media type braille (which is meant to be a continuous stream of characters), and not for embossed (which is meant to be a static printout in braille). 3. 2D tactile interaction environments are not yet common. Should there be an additional tactile media type for 2D tactile interaction (such as pinmatrix or 2dtactile)? In research or for early adopters, is there already a commonly accepted interaction vocabulary for 2D tactile displays (such as the WIMP for visual displays)? Or does the Web Applications WG propose to go with the WIMP model for simple transfer between the visual and the tactile representation? In light of these points of ambiguity, Unless the Web Applications WG can define what the view modes -- windowed, floating, fullscreen, maximized and minimized -- mean for the media types braille and embossed, the PFWG advises that it would be better NOT to apply 'view-mode' to tactile media types at the current time. The PFWG welcomes the opportunity to discuss these issues with the Web Applications WG to ascertain what the view modes defined in the View Mode Media Feature means for the media types braille and embossed and would like to work in concert with the Web Apps WG and the CSS WG to refine and define what these concepts mean for the braille and embossed media types. -- Michael Cooper Web Accessibility Specialist World Wide Web Consortium, Web Accessibility Initiative E-mail coo...@w3.org mailto:coo...@w3.org Information Page http://www.w3.org/People/cooper/
Re: PFWG comments on Widgets 1.0: Packaging and Configuration Last Call (late, very late)
cases are still limited IMO. It need not be a requirement that the catalog list all files, only ones that need special information attached. Conformance checkers should check that the MIME type of every file can be determined reliably, either via the sniffing mechanisms already defined or via an entry in the catalog file. This would certainly be good. But outdated CC's, or differences between CC's and UAs, might cause problems: cc says can' detect type X, UA happily sniffs type X. However, it is certainly worthwhile considering the low hanging fruit (e.g., just checking file extensions, and magic numbers). There may well be other types of special information that the catalog might support, once introduced. So the benefits of providing this probably extend beyond improved MIME type detection. I'm sure there would be, but I can't think of any off the top of my head. However, for this reason, it might be worth while looking at systems that are already doing this (e.g., limitations/uses of appache .htaccess files). Can you think of other systems/uses? Understood and accepted with the explanations above. We didn't have specific additional uses for a catalog in mind when suggesting it, but generally observe the usefulness of them. We may be able to help come up with uses in a brainstorming session. Since a few of the responses include a suggestion to brainstorm together, perhaps there would be an opportunity to do so at the upcoming TPAC meeting? If you're too busy to do this in the near future I'm sure it can wait. PFWG is interested in engaging with you on this technology, as we see it being important down the road. Michael -- Michael Cooper Web Accessibility Specialist World Wide Web Consortium, Web Accessibility Initiative E-mail coo...@w3.org mailto:coo...@w3.org Information Page http://www.w3.org/People/cooper/
PFWG comments on Widgets 1.0: Packaging and Configuration Last Call (late, very late)
not be a requirement that the catalog list all files, only ones that need special information attached. Conformance checkers should check that the MIME type of every file can be determined reliably, either via the sniffing mechanisms already defined or via an entry in the catalog file. There may well be other types of special information that the catalog might support, once introduced. So the benefits of providing this probably extend beyond improved MIME type detection. -- Michael Cooper Web Accessibility Specialist World Wide Web Consortium, Web Accessibility Initiative E-mail coo...@w3.org mailto:coo...@w3.org Information Page http://www.w3.org/People/cooper/
