See also: IRC log
<trackbot> Date: 24 July 2013
<janina> trackbot, start meeting
<trackbot> Meeting: Independent User Interface Task Force Teleconference
<trackbot> Date: 24 July 2013
<janina> Meeting: IndieUI Task Force Teleconference
<janina> mc: We have a request from the wg
<janina> mc: To telecon with them and describe our work, and engage in a coordination conversation
<MichaelC> MBUI WG
<janina> scribe: janina
<MichaelC> scribe: jasonjgw
TPAC meeting: letters of recommendation recommended for visa purposes and hotel reservations need to be made (with limited availability). The agenda will appear closer to the meeting. Visa applications can be time-consuming.
<MichaelC> http://lists.w3.org/Archives/Public/public-indie-ui/2013Jul/0011.html
<MichaelC> https://dvcs.w3.org/hg/IndieUI/raw-file/e1d36dc3cfba/src/indie-ui-events.html
Janina issues a call for comments and objections regarding publication of the Events module at the above URI.
Consensus: the working group resolves to publish the document.
RESOLUTION: Publish the document at https://dvcs.w3.org/hg/IndieUI/raw-file/e1d36dc3cfba/src/indie-ui-events.html as a updated Public Working Draft
The Web Applications working group is about to publish UI Events. Janina notes that Michael has reviewed the document and there are no conflicts with our work.
Janina clarifies that it's a first public working draft.
The URI is expected to be available soon and will be forwarded to the IndieUI list then.
Rich notes issues of particular interest - activate/click and mutation events.
<MichaelC> action-42?
<trackbot> ACTION-42 -- Michael Cooper to consolidate use cases -- due 2013-03-13 -- OPEN
<trackbot> http://www.w3.org/WAI/IndieUI/track/actions/42
<MichaelC> IndieUI (Events) Use Cases and Requirements
Janina notes interest in developing a formal use cases and requirements document for IndieUI Events.
Michael notes that some of the use cases could be combined and clarified; he has consolidated scenarios in the wiki now, while avoiding other substantive changes to the material.
Michael's next step is to separate use cases from requirements structurally in the document and to consolidate requirements, linking them to scenarios.
The requirements should then be reviewed and prioritized. He proposes to carry out this work.
The working group will need to review it, to do the prioritization and prepare the document for publication prior to CR.
Two working drafts, at least, can be expected before the Events Last Call.
<MichaelC> IndieUI (User Context) Requirements
Michael notes in reply to Andy that the requirements for User Contexts are now separate from those for Events (see their respective URIs).
Michael also suggests a parallel format for the User Contexts and Events requirements documents.
Andy undertakes, per his action item, to follow a similar format to the Events use cases in drafting User Contexts use cases/scenarios.
<MichaelC> action-61?
<trackbot> ACTION-61 -- Andy Heath to heath to provide Use Cases -- due 2013-07-17 -- OPEN
<trackbot> http://www.w3.org/WAI/IndieUI/track/actions/61
<MichaelC> action-61: User Context requirements being developed at http://www.w3.org/WAI/IndieUI/wiki/User_Context/Requirements
<trackbot> Notes added to ACTION-61 Heath to provide Use Cases.
No objections to Michael's proposal to move requirements into a separate section, separate from scenarios, in the Events requirements document.
<janina> jw: No developments since our last discussion of this.
<janina> jw: We're waiting on implementation news to understand how we will build our testing
<janina> jw: Hopefully, we will be able to automate testing
<janina> mProcess question: What do we want next
<janina> jw: If we know what implementations ae doing, we can move forward, so how to get that?
<janina> mc: Understand there's webkit, maybe safari implementation? When James is back we can ask.
<janina> mc: Ask about webkit, not safari.
<janina> hober: It's an open source project, so easy to check into
There is discussion of implementations.
<janina> janina: We believe Googls is working on it, but unsure how close it is to Apple's webkit.
<janina> janina: We best discover that soon
Michael suggests determining a precise question to raise with implementors.
<janina> mc: Suggests Jason liaz with Domenic
<janina> jw: good
Jason and Michael agree to prepare this and to liaise appropriately.
This was partially covered in the earlier item on requriements.
<janina> jw: I've had an informal read through ISO 24751
<janina> jw: A large number of assertions in ISO not currently in our requirements
<janina> jw: Some should probably not migrate to our reqs, i.e. parts that sys app doesn't have control over
<janina> jw: How to add? Separate, incorporated, there are quite a few, including some very interesting ones
<janina> ah: The ISO has lots that's not used
<janina> ah: We determined to start us with a smaller model
<janina> ah: The GPII people are planning a registry that will be seeded with 24751
<janina> ah: Suggest we put them at the end of ours
<janina> jw: I can prepare a separate doc that includes 24751 that isn't current in our doc
<janina> ah: Suggest we try to coordinate our vocabularies if we can
<janina> jw: Will do my best to create a list in a separate doc for us to consider alongside the items already proposed here
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/72451/24751/g Found Scribe: janina Inferring ScribeNick: janina Found Scribe: jasonjgw Inferring ScribeNick: jasonjgw Scribes: janina, jasonjgw ScribeNicks: janina, jasonjgw Default Present: jasonjgw, janina, Michael_Cooper, Andy, hober, Rich Present: jasonjgw janina Michael_Cooper Andy hober Rich Found Date: 24 Jul 2013 Guessing minutes URL: http://www.w3.org/2013/07/24-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]