W3C home > Mailing lists > Public > public-indie-ui@w3.org > November 2012

Re: IndieUI Teleconference Agenda; 14 November 2012 at 18:00Z for 60 minutes

From: Andy Heath <andyheath@axelrod.plus.com>
Date: Wed, 14 Nov 2012 12:50:54 +0000
Message-ID: <50A393AE.5090404@axelrod.plus.com>
To: Janina Sajka <janina@rednote.net>
CC: public-indie-ui@w3.org
Digressing a little - can we table discussion of preferences and the 
User Context part at some point please.

I've looked at the current User Context draft and its a good start. As I 
read it right now its focussed around (potential) accessibility features 
of the device in question and whether it has them. This is obviously 
very important and required but may not be sufficient. One thing it may 
be useful to do is have preferences that are not responded to by the 
device but are passed up and on to the web app by the same mechanism as 
those that are. In fact we would imho in general want
to give the device the choice to respond or not (which seems pretty
suited to the events model - if not acted on by some level the 
preference gets passed on).  It may well be that even within one
vendor some devices may respond to a preference whilst others do
not respond to the same preference - it seems sensible then to me
to permit such to be settings of a device even if the device cannot 
respond to them - for example if the user requires enhanced contrast 
that might be handled directly by some devices that vendor produces and 
for others it might be passed to the web app to deliver alternative 
content.  What preferences a device can respond to directly (which may 
be faster than the web app responding) may be a selling point.
Similar arguments apply for example to a "I want a simple interface" 
preference and many others.  My view is we should focus mainly on those
preferences that devices *can* respond to directly but I don't think
we have a choice but to include other preferences unless we know we
have all the device manufacturers in the room.  Its a shame we didn't 
get to discuss this in Lyon.

Are editors drafts publicly visible ?  If so it would be useful I think
if we could address this soon so people know what the extent of the 
context is.  I'm not assuming there is agreement on this, just making 
the argument to look at it.

> What:    IndieUI Task Force Teleconference
> When:    Wednesday 14 November
>      10:00 AM        San Francisco -- U.S. Pacific (Standard) Time
> (UTC -8)
>       1:00 PM        Boston -- U.S. Eastern (Standard) Time
> (UTC -5)
>       6:00 PM        London -- British (Standard) Time
> (UTC +0)
> Where:    W3C Teleconference--See Below
> * Time of day conversions
> You can check for the correct time of this meeting in your time zone
> using the Fixed Time Clock at:
> http://timeanddate.com/worldclock/fixedtime.html?iso=20121114T13&p1=43
> ** Preliminary Agenda for IndieUI Task Force Telecon 14 November 2012
> Meeting: IndieUI Task Force telecon
> Chair: Janina_Sajka
> agenda+    Telecon Time Scheduling
> agenda+    Editor's Draft?
> https://www.w3.org/WAI/IndieUI/track/actions/open
> agenda+    Open Issues
> agenda+    Scribe for our Next Teleconference (on 28 November)
> agenda+    Be Done
> Resource: IndieUI F2F Minutes from TPAC2012
> Thursday:    http://www.w3.org/2012/11/01-indie-ui-minutes.html
> Friday:        http://www.w3.org/2012/11/02-indie-ui-minutes.html
> Resource: IndieUI Minutes
> http://www.w3.org/2012/10/17-indie-ui-minutes.html
> Resource: For Reference
> Home Page:    http://www.w3.org/WAI/IndieUI/
> Dial the Zakim bridge using either SIP or the PSTN.
> PSTN: +1.617.761.6200 (This is a U.S. number).
> SIP: zakim@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: 0046343@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/


Andy Heath
Received on Wednesday, 14 November 2012 12:51:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:13:18 UTC