W3C

- DRAFT -

Independent User Interface Task Force Teleconference

16 Oct 2013

Agenda

See also: IRC log

Attendees

Present
Janina_Sajka, Katie_Haritos-Shea, Michael_Cooper, Rich_Schwerdtfeger, Andy_Heath, Jason_White, hober, jcraig
Regrets
Chair
Janina_Sajka
Scribe
Ryladog

Contents


<trackbot> Date: 16 October 2013

<janina> Meeting: IndieUI Task Force Teleconference

preview agenda with items from two minutes

<MichaelC> scribeNick: Ryladog

JW: I want to not Andy's contribution on Use Cases

JS: Michael should we delve in into the mechanical issues of Use Cases

MC: I had set upa seprerate wiki page...but we will need to merge those

AH: I can add them

MC: You can worry about formatting later
... There is a larfe section for Scenarion Use Cases, and a sperate for requirments

AH: I thought there was some kind of automated formatting of that

MC: I wish

AH: Tell me wherer to put it

<MichaelC> User Context Requirements

AH: OK I wil do it manually. I will look at whether that will work

MC: Wikis have constartints

JS: WElcome James

Calendar Review and Updates Through January 2014

JS: Timelines and Calendaring - I want to make some suggestions
... On the 30th Europe will have left - Andy you will be at a hour earlier
... It is 5pm EASTERN Standard time....
... Looking at Nov and Dec
... 30th , then for the 13th meeting - half of us will be in Shenzshen = - we will not want to meet on the 13th
... So then meet on the 20th, I suggest because we will have plenty to report on. And then go every two week from there. 5th of Dec and then the 12th
... Our afternoon calls will be reasonable enough for Andy
... I will have a schedule for our meeting by the 30th

TPAC2013 http://www.w3.org/WAI/IndieUI/wiki/Meetings/TPAC2013

<MichaelC> http://www.timeanddate.com/worldclock/meetingtime.html?iso=20131113&p1=136&p2=1232

JS: Several are palnning to be there and will talk about on User REquirements
... There will be buses from HongKong Shenzen

<MichaelC> TPAC travel scheduling wiki

MC: You should let W3C know that you are interested - they need enough folks before they will actually get the buses

JS: Jason does not want to travel from HongKong to Shenzshen alone, can you help with that Michael

JW: I will arrive on Sunday morning

JS: We have time still

JW: I am waiting for h visa application to go through

JS: Noting that there are quite few WebApps people will be there - shoudl we try to get wider participation at TPAC

JC: I think there will be a conference line for both - and they are meeting on different days
... Let us set up something for tTHursday then - I am planning on basically working from hoe to be available for as many conference times as possible

JW: On the Wed are there events ?

JS: Most of Wed is not pres-scheduled - mwe would want to do something
... We will be participating in Lightening Talks - we could suggest one for our group to interest the Web Apps and other folks

Editor's Report

JS: Beefing up examples to be a little less accessibility geto-ized - W3C WAI agrees with that - we will have planty to tweek - and correct before TPAC

JC: I have been on vacationand sick since we last met - so not lot was done
... Media Queies typr proposal - start off easy with proposing High Contrast type mode wotk with MS and OS 10 - for media query

LC: One is not specific to accessibili

JC: We will do one off proposals so groups dont get put off and will help seperate and control issues

AH: thi sis a good idea
... Micheal suggested we just keep a record of what is where in one list - that we see
... We will keep our stuff togther with pointers

JC: As a point of order do we - I think I sent the fornatted proposal to the IndieUi list sp I can send it to the CSS Working Group

JW: It does ring a bell

JC: I sent the Original so long ago - so I will repsond to the list with an update and then forward on to CCS WG

RS: What ever happened to black on white issues

JC: They proposed a vebdor prefoxed version
... we talked about an extended version - their vendor specific and one open
... I specifically included how MS High Contrast mode would fit into the synrax
... It looks like the Sept 27th I sent

thanks Rich

JC: having trouble finding IndieUI archive...

<jcraig> http://lists.w3.org/Archives/Public/public-indie-ui/2013Sep/0007.html

JC: that is the email that was an update to Cynthia covers both MS High Contrast modes and easy switchers

JS: while we wait for Rich to come back - we will look at your email

JC: I will send out a new one today that will be formatted for the W3C CSS Working Group

MC: What ypu are going to send is for starting the converrsation?

JC: My plan is to send just one of them for the display colors inverted - here is the first one
... So the second one would be the High Contrast Mode

<richardschwerdtfeger> calling back in

MC: So we want to record/record as they build up? Can we start the tracking now?

JC: whoever is managing medies queries can be applicable to CSS - whatever group ,manages the media querie for x

JS: we want to keep our requirments as our requirements

MC: I want to look our requirmenets when it goes off to these other entties and they keep it in their specs that wwe see is useful

JC: I cannot deternine if they actually have tracker

MC: They probably have one, but I am not sure what it is

JS: Well we will need to figure that out and that we will be monitoring (insert more PC language here) what is done with each requirment
... James I kope you feel better soon
... We will continue on the 30th

Events Requirements Walkthrough http://www.w3.org/WAI/IndieUI/wiki/Use_Cases_and_Requirements

MC: Events Requirments - two views

<MichaelC> Events Requirements

MC: What we have is Use Cases and SCenarios followed by Requirements
... So the first main question to ak is the list of Use Cases and Scenarios complete? Have we discribed thm all
... The seoncdd for each use case/scenaion are the requirments that it points to complete and documented?
... Then the reverse path -
... Look at the requirments and are they justifoed with an eixting Use Case
... those are the two veiws we need to take on these
... we only have 15 minutes
... A few months ago I combined these
... 1t Map
... 2nd Pop-up
... 3rd expand./coolaps
... 4th

5th is moving Focus around

MC: 6th Media Player Commands
... volumn
... Zoom seprate from Map
... Pan seperate from Map
... moving Point of Regard
... Continiuous and discontinuous
... Hiding and showing txt
... Neerness
... or gide additional text with out selection
... Summary details expanding

JC: So it is possible that it is going to be covered by expand /collapse

JW: It is a long list

MC: It is a long list
... towards the bottom there is not much descriptinf ro them

JS: We are not assuming that hese are all for 1.0 right

MC: Maybe we should agree hat that is what we are doing as well
... Almost all of them point to one requirements
... I cannot imagine that those are the only requirements couple of requirments

JW: I suppose one approach would be to ask people to review and have them suggest items are for 1.0 or a later version
... Collect Issues in other wrds

MC: Which of these might not be part of 1.0 just off hte top

JC: One that is outside the scope of 1 - is moving abojects /resizing object ona canvas as they are not that cpmmon

MC: Does tthat include th edrag and drop?

JC: No.
... Select something and perform some actipn on it - that is common enough i thinkw e should keep that
... We can already identify that we can split it into two diffeent different requirments
... Drag ad Drop - mark request - and then operate on marked item

MC: Ok you might find yourself needing to clarify the drag and drop scenarions and might need some clean up
... and there ther is a Move UI Object - mthose will need eith r combination or seperation
... Some were for pannoing and zooming

JC: that is on the fence - one is already in there for zooming on a map
... pan request and zoom request _ I wouldn't be broken up if we do have to move to 2.0
... Manipulation Request covers acombination or individual ones

MC: sound lie 1.0 scope
... Pop-up is that in 1.0mscope

JC: It depends on what people mean by Pop-Up MC:

<janina> ?

MC: Pop-up menu is a select expand ad collpase - but if it is contexual there is a secondary action

JC: Promary action it happens to shpw a dialog - these threee different scenarions

RS: the pop-up comes from the OS lie functions. I like James simplified version of it

MC: Maaybe the dialog component neeed to nbe moved to another

<richardschwerdtfeger> 2 minutes

JC: We need to clarify the vocabularies we use

MC: Open or collapse tree view

JC: that is covered by expand /collapse which is 1.0

MCL next ?? include links and buttons

JW: click events

JC: you want a UI independent activation event
... a general tap event would not unlock it
... AT would/could activate it

JW: Mac Os would be express event

JS; good stopping point

<jcraig> https://www.w3.org/WAI/IndieUI/track/products/2

MC: this discussion has helped me figure out some things we need to do - maybe we should continue

JC: we have an issue 3

<MichaelC> issue-3?

<trackbot> issue-3 -- SecondaryAction (aka "Context Menu") -- open

<trackbot> http://www.w3.org/WAI/IndieUI/track/issues/3

<MichaelC> action-53?

<trackbot> action-53 -- James Craig to Add ~"activate request" event to augment default action trigger when "click" handlers are inappropriate. -- due 2013-05-10 -- OPEN

<trackbot> http://www.w3.org/WAI/IndieUI/track/actions/53

JC: action 53

<jcraig> https://www.w3.org/WAI/IndieUI/track/actions/53

JC: there is anote that authors should use click inmost scenarios

<jcraig> ISSUE-3 and ACTION-53

JW: Is it possible to solve both with the same UI method

JC: No I think they are different

JW: if you had one for an action...
... you would solve then all
... is it a get

JC: this coul ccause a performance hot on the AT
... the browswer diesnt have to do anything

JS: I thnk we want tto protect the declarative approach for authors

RS: is this going to confuse authors

JS: lts think about this some

AH: We are going to have to do some radical surgery to the User Context Requirments
... Does anyone mind if I do that?

MC: yes we were bascially it is time to go to the next step

JW: I just could supply the use case as I didnt know them well enough yet

JS: this is a useful exersoze, I think this is helpful all around

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.138 (CVS log)
$Date: 2013/10/16 22:11:10 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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/Hogh/High/
Succeeded: s/exoand/expand/
Succeeded: s|MC: Our Reqquirments|topic: Events Requirements Walkthrough http://www.w3.org/WAI/IndieUI/wiki/Use_Cases_and_Requirements|
Found ScribeNick: Ryladog
Inferring Scribes: Ryladog
Default Present: Janina_Sajka, Katie_Haritos-Shea, Michael_Cooper, Rich_Schwerdtfeger, Andy_Heath, Jason_White, hober, jcraig
Present: Janina_Sajka Katie_Haritos-Shea Michael_Cooper Rich_Schwerdtfeger Andy_Heath Jason_White hober jcraig
Agenda: http://lists.w3.org/Archives/Public/public-indie-ui/2013Oct/0007.html
Found Date: 16 Oct 2013
Guessing minutes URL: http://www.w3.org/2013/10/16-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]