Attendees:

Arnie Miles, Georgetown/PESC

Jeff Alderson, ConnectEDU

Michael Gettes, CMU

Michael Morris, ACT

Ann West, InCommon (scribe for this call)

Nate Klingenstein, InCommon

Bob Morgan, UWashington

Steve Olshanksy, I2

Mark Cohen, Parchment

Jim Leous, Penn State

Nirmal Rahi, College Board

Agenda:

1. Ann will discuss note-taking
2. Action items from last call
3. Implementation strategies - status to date and when do we start
wire-frames?
4. Scheduling webinar
5. Open discussion

Discussion:

Action from last call:

Schedule a webinar to finish the discussions on the flows and begin the wire frames. Waiting on names of volunteers to do wireframes, because these people need to be on wire frame webinar.

Ask Michael Morris to provide help with wireframes. That person needs to attend webinar. - Spoke with Michael this morning, working on a name. Michael will be on this call.

Action Items from Last Call

- Who will develop user experience wireframes based on implementation strategies that we've posted?

  [AI] ACT -  mike.simpson@act.org

  - What tools will we be using? Could use balsamiq (free) for clickable/functional interface. Not as pretty, but useable.

  [AI] Mike Morris will check it out. 

  [AI] Jeff will help out if standardize on tools

- Schedule a webinar to discuss wireframes

 Q: Should we have an example to show what one would look like?

 A: Yes. Could be an example of what's already done as an example of a wireframe.

Implementation Strategies

- Email from participants on list from the past week

 Implementations are trying to work in all the permutations that the user might take. 

 Q: Should we simplify the diagram to represent specific flows?

 A: College Board is using flows like this. It's better to have the building blocks described and then use them to address your goals.  

Change Flows to be:

1) login with Commit collab and use that exclusively: capture identifier for local use

2) link commit collab to existing local account

3) link local account to existing commit collab

4) login with local account exclusively after integration with commit credential 

Wireframes are trying to capture initial and subsequent visits in one flow. Not always clear how flows are going to look. Using the wireframes, it will be easier to convey where the gaps are.

[AI] Nirmal/Nate to finish up sequence diagrams before Thursday webinar - Need the local account login (#4) to be added 

Discussion of outstanding questions at the bottom of integration strategy #2:

 1. Can one "CommIT collaborative" account be mapped to multiple accounts from a given service organization? 

A: It depends on the service org policy and application. For most integration strategies, one to one mapping is best. 

 2. Can one account from a service organization be mapped to multiple "CommIT collaborative" accounts? 

A: One to one mapping is usually best.

3. Failed login at "CommIT collaborative" sends you back to "CommIT collaborative"; is that right, or should you go back to the referring service organization? 

A: Users need a way back to the Service Org. Explore this in the wireframes. 

4. Is an active session at "CommIT collaborative" necessary for data transmission between organizations? 

A; Don't need an active session.  Service providers could act as proxy for users, given user consent. Consent based flow could be built on top of the authn scenarios we're talking about now. 

Q: Do we really want user consent? We need it, if we're using a single identifier across all service providers. Could be interpreted as a huge privacy issue if there are no ways that user can control aggregation of their data. 

Minutes

Arnie can't take minutes and lead the calls at the same time. Ann asked if each organization would be willing to volunteer to take turns doing the notes for the calls. Completed notes will be sent to Arnie for posting on the wiki. The group agreed. 

At the end of each call, Arnie will ask for 

- action item recap from the scribe

- a volunteering organization to scribe the next call. 

[AI] Jeff/ConnectEDU responsible for minutes for the next call on the wireframes. 

Action items:

ACT and ConnectEDU will develop wire frames for next call and coordinate on what tool to use

Jim and Jeff to provide examples of wire frame for web conference

Arnie to publich doodle poll to determine when the wire frame meeting will be scheduled

Nate/Ann/InC to provide Adobe connect

Nirmal/Nate to finish up sequence diagrams before wire frame discussion

Jeff/ConnectEDU responsible for minutes for the next call on the wireframes

[AI] ACT and Connect EDU will develop wireframes for next call and 
  coordinate on what tool to use
  [AI] Jim and Jeff to provide example of wire frames
  [AI] Arnie to publish a doodle poll to determine when the wire frame meeting will be 
  scheduled
  [AI] Nate/Ann/InCommon to provide Adobe connect
  [AI] Nirmal/Nate to finish up sequence diagrams before wire frame discussion
  [AI] Jeff/ConnectEDU responsible for minutes for the next call on the wireframes[AI] ACT and Connect EDU will develop wireframes for next call and 
  coordinate on what tool to use
  [AI] Jim and Jeff to provide example of wire frames
  [AI] Arnie to publish a doodle poll to determine when the wire frame meeting will be 
  scheduled
  [AI] Nate/Ann/InCommon to provide Adobe connect
  [AI] Nirmal/Nate to finish up sequence diagrams before wire frame discussion
  [AI] Jeff/ConnectEDU responsible for minutes for the next call on the wireframes