See also: IRC log
<trackbot> Date: 08 January 2014
<janina> Meeting: IndieUI Task Force Teleconference
<janina> http://www.w3.org/WAI/PF/meetings/2014-01-ftf
<scribe> scribe: Ryladog
<scribe> ScribeNick: Ryladog
<scribe> Scribe: Katie Haritos-Shea
JS: Conflict on the Jan 22 folks traveling for PF F2F
<scribe> Chair: Janina
JS: We can move it to the 29th if you like
<andy> +Andy_Heath
JS: Not meeting on the 22nd but will be meeting on the 29th
rrs agent, make minutes
JS: the UAAG 2.0 Last Call
... There are 2 email from Jeanne Spellman (W3C staff contact
for UAAG) sent for us to reivew
<janina> http://lists.w3.org/Archives/Public/public-indie-ui/2014Jan/0001.html
<janina> http://lists.w3.org/Archives/Public/public-indie-ui/2014Jan/0002.html
JS: These are the two email URLs
for the review
... You can give us a report on the 29th and others can
comment
JW: I will do that and post something to the list
JS: Not usually our job in IndieUI
JC: Mainly editorial stuff responding to folks who have sent feedback. Mostly the high contrast issue - mostly informative changes
JS: We have talked about
publishing a stablization draft of Events
... Micheal need to get all of our testing for a report to the
Director - this is a good deal of work, with the PF F2F - so we
are pushing that stabilization draft of Events probably out to
February
... You thought the draft was more ready than I thought
JC: Yes all of the commnets and feedback especially for the TPAC, but most of them are closed. Maybe we can do that in February also. I did not promise the CG that we would do that - but itis possible to have a first public working draft
JS: If we do not get it done by February thenit will prbably be un April bc of CSUN
<MichaelC> https://dvcs.w3.org/hg/IndieUI/raw-file/default/src/indie-ui-requirements.html
MC: I have the document up - the
editors draft is hear as a reminder. This verson has the Use
Cases and events - the User Context section is currently empty.
We have this for organizational purposes, but this is not
set
... It is useful to orgnaize by document. The document has
pointers to where the requirments are addressed. You will see
that there are some without pointers
... There is a cross reference between use cases and event
requirments. There are cases that there are requirments that
are not tied to a scenario. And there are senarios that are not
mapped to a requirment. So we need to revisit and clean all of
that up
... We cold probably publish this as is, but we can also wait
until it is more mature
JS: Good way to get comments to release as is...:-)
JW: I think the scenarios were written before the requirments
JS: Would anyone object to publishing this for review in this state?
MC: The intro might need to be copied for UI Events into the this Introduction and we can put the Status of this Document point there as well
JS: This makes sense to me. Any other thoughts?
JW: Just is there any obvious fixes that would not be too controversial to do?
MC: Yes the mapping - but I myself do not have much time this January
RS: You want to just publish the Requirements?
MC: I think we need at least one
cycle of review before the First Public draft
... Having a vetted requirements document helps us onthe
documentation track
RS: I do not see any issues, just that we review
MC: We are targeting mid-February
because the ARIA stuff for Jan 30th which is ambitous - but
when we get that done I will be aleto move to IndieUI
... Mid to late February.
JS: I think we are hoping to get Events 1.0 to CR this year in 2014
RS: Yes but we need to implementations. The Chrome guy is out having a new baby
JS: In terms of next steps it
looks possible that a stablization events draft - and a first
public working draft for late February
... and a first Requirements public working draft for late
February
... We and JUDY want to make the ARIA before CSUN if
possible
RS: I am see if I can help Judy. We really need to get ARIA out this year
JS: Issaccson is doing something
for Firefox OS to use IndieUI
... It has been 4 or 5 months ago
JC: He did say they would be interetsed but he did not commit to an implementation
RS: If we do not think there are going to be a changing much we need to focus on the second implementation
MC: InARIA testing became a big
bottleneck and we want o avoid that with IndieUI. I do not have
to be respobsible for the testing and hold things up
... One of our problems has been that the potential implementor
have not joined the IndieUI working group. We want to try to
work with Mozilla more closely.
JS: Lets see who we can get in Torornto to join the meeting when in Toronto
MC: We want to see if anybody has
any test files or we can try to provide test files to
implemntors
... We can set up a smaller caucus for implemntors
JS: Testing is a concern and
identifying our other implementors
... We have already had discussions that the Mozilla code base
may be still e too Close bewtween MOzlla and Apple. Blink and
WebKit
JC: Somethings are completely diverged - there are cases that the same patch can e applied to both - if that is true it is too close
RS: You could look at each others code base
MC: We have to convince the Director that the implementations are seperate
RS: I will contact Mike from Mozilla then
SJ: Chrome might indeed be
RS: Should we approach Microsoft?
MC: Microsoft never said why they
are not part of the Working Group
... If we could get Mozilla and Opera that will probably pull
Microsoft in
RS: Well let me send an email to Champion at Microsoft
zaakim, next item
JS: We are acknowledging that this is important
JC: Can you remind me of thename of the W3C
MC: Toby
JC: Hemight be a good person to ask about this. Unlike ARIA - this will not be tied to specific Accessibility APIs
MC: Tody will refer us to Test
the Web Forward and ??
... It is worth talking to, he will be ale to help get us some
pointers
... What we lack in the harness is a runner
... I do not think that it addreses the UAs that we will
initially be running IndieU on. They are having a metting in
San Fran in April the Browser Testing Group
JC: What does the Test the Web Forward is doing what?
MC hey get folks in a room to test specs that are needing testing in W3C specs - it is like a test file creation event. It does not clarify how to make these tests
MC: I am not sure that it will help us or not
JC: That does sound very useful to me for our needs
MC: I amnot sure if the test harness has the ability to ttest the functioality at the layer of IndieUI events
JC: But I think there is a way
MC: Maybe with a combination of
Web Driver and Test the Web Forward test harness may work for
our needs
... I think he (??) is still onstaff ad available
JS: it is worth asking him
MC: How should i phrase the
question to him?
... I will ask Toby about testharness.js and web driver is
something that he can help us with and join us for a call
JC: Is there something that is programmatically determinble like the acid test. It would be good for Toby to explain what TestHarness.js actually does
<MichaelC> TTWF documentation on testharness.js
MC: Test the Web Forward actually
hasbetter documentation
... We should understnd this info at this url before we speak
with him - as well as Web Driver (which is a W3C spec)
<MichaelC> WebDriver
JW: I think that wold be helpful
MC: This version of Web Driver may be out of date - but understanding what it does may be importnat
Takashi: I am not sure about this
JS: We are trying to find out where you expertiseis
JC: Jus looking at the Test Harness I think I could write a few tests. It is very similar to how WebKit tests are set up. The asynchronous testing may be an issue
AH: Nothing
JW: Paper presentation in Paris - I will be corrdinating with Andy on this..
JS: This has been a good
restart
... We will meet agian in three weeks onJanuary 29th
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) Found Scribe: Ryladog Inferring ScribeNick: Ryladog Found ScribeNick: Ryladog Found Scribe: Katie Haritos-Shea Scribes: Ryladog, Katie Haritos-Shea WARNING: No "Present: ... " found! Possibly Present: AH Apple JC JS JW Janina_Sajka Katie_Haritos-Shea Kurosawa MC MichaelC Michael_Cooper P0 P1 P2 P5 P7 RS Rich_Schwerdtfeger SJ ScribeNick Takashi andy https inserted janina jasonjgw jcraig renoirb richardschwerdtfeger trackbot You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy Found Date: 08 Jan 2014 Guessing minutes URL: http://www.w3.org/2014/01/08-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]