*Action Items*
New
[AI] {Chris} will contact Mihn to discuss the technology managing the user experience within Signet.
[AI] {Minh} will contact Shibboleth developers to discuss UI technology management.

Carry Over
[AI] {Group} will via the list begin compiling scenarios to be used as potential use cases.
[AI] {Keith} will summarize naming discussion and make proposals to begin defining privilege, task, function, etc.

*Participants*
Lynn McRae, Stanford University (Chair)
Jennifer Vine, Stanford University
Minh Nguyen, Stanford University
Keith Hazelton, University of Wisconsin
Simon McLeish, London School of Economics
Chris Phillips, Queens University, Canada
Andy Cohen, Stanford University
Andrea Beesing, Cornell University
Tom Barton, University of Chicago
Blair Christensen, University of Chicago
David Walker, University of California Office of the President (UCOP)
Torbjörn Wiberg, Umeå University, Sweden
Terrie Clark, Internet2 (scribe)
Renee Frost, Internet2
Steve Olshansky, Internet2
Ann West, EDUCAUSE/Internet2

*Discussion*

User Interface Discussion
The group discussed the UI screen mock-ups and design changes to the screen mock-ups. In considering a unified look for Internet2 application developments, the group also discussed working with the UI developers from other Interent2 efforts, Grouper and Shibboleth, to ensure a more uniform usability experience for the three applications. The initial release of Signet will have an embedded logo and color scheme for the UI that, once installed by an institution, can be tailored to that institution’s logo and color scheme. For the initial release, the general layout and interaction style will remain constant throughout the application ensuring that all actions are presented in the same way across the application. The group will discuss other requirements for customization for future Signet releases. The group discussed the potential usability issues for page navigation, pop-up windows and wizards. For more information about the UI see http://www.stanford.edu/dept/itss/infrastructure/signet/project/ui/. For info about the Signet schema, please see http://www.stanford.edu/dept/itss/infrastructure/signet/project/doc/schema.html.

The group will seek early adopters for the Signet application in the near future. And, usability tests will be performed. The group will discuss scenarios, use cases and data to use in the screen mock-ups at the I2 Fall Member Meeting. The group discussed further definition of the application’s core terminology, which will be addressed in the next call.

Subjects Discussion
Similar to the requirements of Grouper, Signet will refer to items outside of the application. The word “subject” is used to refer to objects outside these systems. A consistent method to refer to subjects can be accomplished through common APIs. It would be attractive to have the same subject interface with Signet and Grouper. Other dimensions for consideration are that another purpose of the subject interface, beyond assigning membership, is to translate an authenticated user of a UI into a subject identifier. Further, if a query on more than one subject type occurs, then how will name resolution services be provided when resolving the identifiers if named differently. This could be specific to the data sources being used. Will this become a global reusable library? Probably not. It can be accomplished through a local data store provided for subject tables. Or, a Java class adapter provided by the application to accommodate the API and refer to an external data store to search for the subject. Subject identifier mapping should be known specifically in the interface.

There will be a Signet/Grouper working meeting on Monday, September 27, 2004 at the Internet2 Fall Member Meeting in Austin, Texas. For more information please see http://events.internet2.edu/2004/fall-mm/.

The next call is Friday, September 3, 2004 at 11:00AM ET.