See also: IRC log
<trackbot> Date: 12 June 2013
<janina> Meeting: IndieUI Task Force Teleconference
<janina> trackbot, start meeting
<trackbot> Meeting: Independent User Interface Task Force Teleconference
<trackbot> Date: 12 June 2013
<janina> Meeting: IndieUI Task Force Teleconference
<janina> Chair: Janina_Sajka
<andy> p5=andy I think
<MichaelC> scribe: rich
No news on TPAC2013. Should be news by next meeting.
No discussion on editor's email
<andy> http://www.w3.org/WAI/RD/2013/user-modeling/
<andy> http://www.w3.org/WAI/RD/wiki/User_modeling
Research WAI group document about user requirements
What kind of view should we be taking towards their work (re: user context module)
<andy> [1] http://lists.w3.org/Archives/Public/w3c-wai-ig/2013AprJun/0230
<andy> [2] http://www.w3.org/WAI/#x20130515a
<andy> [3] http://www.w3.org/News/2013#entry-9823
<andy> [4] http://www.w3.org/WAI/RD/wiki/Distribution_Table_for_UM4A
Andy: They have a symposium on
user adaptation but failed to contact us
... Should we get on their distribution list?
Janina: List is open, you're welcome to join it
Andy: Will attend symposium, but they should know about what we're doing
Janina: They are aware via WAI coordination group
Andy: Bigger issue is other groups beyond Research WAI who will be involved in symposium
Janina: Two issues - 1. They need
to cast a wider net for participation; 2. What impact does
their work have on what we're doing?
... They do research, not specifications, so there is limited
overlap with current standardization work
Michael: We could add to their wiki of things to work on.
<MichaelC> http://www.w3.org/WAI/RD/wiki/Research_Topics
Andy: We want to avoid fragmented/competing solutions
Michael: You can listen in to symposium even if you're not presenting
Jason: updated revisions to
requirements document. we're in the collecting phase, we're not
excluding anything right now
... document needs to find a home (probably a wiki). what's the
next step? wait for more comments? discuss at future meeting to
establish exclusion criteria?
Consensus is we need input beyond our group on some things (e.g., privacy) before we start cutting things
Michael and Jason will work on mechanics of wiki
Jason: number of people are concerned about disclosing AT being used, even with privacy controls. wants to see use cases for that information. it's not clear what the legitimate use cases, benefits and drawbacks would be for that information.
<Zakim> MichaelC, you wanted to suggest pros / cons of various engineering proposals and to say and then take to stakeholders including the Privacy IG, will mean describing the full issue
Andy: wants clarification on what kinds of devices are in our scope (mobile, desktop...)
Michael: scope is deliberately not restricted. initial focus is mobile devices but that's not our limit.
<Zakim> janina, you wanted to ask whetehr we should agree on the approach we want before we ask the wider community?
<andy> janina - if we can agree on
Janina: we should hash out an engineering approach internally before going to wider community. that would get us better feedback than a more amorphous proposal
<Zakim> MichaelC, you wanted to say if we think privacy is controversial, we might want to provide a couple well-formed alternate options for stakeholders to consider
<MichaelC> scribe: jasonjgw
Rich elucidates his comments to the list regarding an immediate need for IndieUI Events in mobile environments and there should be a strategy of completing Events first, potentially with smaller releases with incremental updates.
<Zakim> MichaelC, you wanted to say I would like to see a FPWD of user context, then go back to events
Michael acknowledges the desire for the faster timeline but maintains the need for a first public working draft of User Contexts.
Janina clarifies that we need to establish what work remains to be done regarding Events.
There is discussion of possibly releasing a further working draft based on the current editor's draft.
Rich highlights the pragmatic needs arising in mobile environments and the importance of making progress on this (while still working on User Contexts).
Janina echos this and acknowledges the unexpected difficulties of User Contexts, which affected the time-line (first draft of User Contexts was originally scheduled for early in the year, shortly after Events).
Michael notes that the Events requirements need to be further elucidated.
Janina proposes we look at remaining actions to see how far we are from Last Call.
Michael notes the necessity of a further public working draft prior to any discussion of Last Call.
Rich notes difficulties in mobile environments (a lack of key events for instance), as the motivation for accelerating progress on the Events module.
<Zakim> MichaelC, you wanted to talk about testing
Michael highlights the importance of testing and the need to carry it out prior to Last Call, as Aria experience demonstrates. We need to develop a test plan expeditiously.
This is scribe.perl Revision: 1.138 of Date: 2013-04-25 13:59:11 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/Michael:/Jason:/ Succeeded: s/I need to hop off the call soon// Found Scribe: rich Inferring ScribeNick: rich Found Scribe: jasonjgw Inferring ScribeNick: jasonjgw Scribes: rich, jasonjgw ScribeNicks: rich, jasonjgw Default Present: Janina_Sajka, Rich, Michael_Cooper, +1.412.624.aaaa, Rich_Simpson, Jason_White, Andy_Heath Present: Janina_Sajka Rich Michael_Cooper +1.412.624.aaaa Rich_Simpson Jason_White Andy_Heath Regrets: James_Craig Ted_O´Connor Found Date: 12 Jun 2013 Guessing minutes URL: http://www.w3.org/2013/06/12-indie-ui-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]