Minutes: COmanage-TAC call of 10-June- 2011
Attending
Ken Klingenstein, Internet2 (stand-in chair)
Keith Hazelton, University of Wisconsin-Madison
Michael Gettes, CMU
Benn Oshrin, Internet2
Steve Olshansky, Internet2
Emily Eisbruch, Internet2 (scribe)
New Action Items
[AI] (Benn and Heater) revise the current COmanage glossary definition for "COmanage platform." https://spaces.at.internet2.edu/display/COmanage/Glossary
[AI] (Everyone) review the COmanage glossary and express questions/concerns to Heather and Benn prior to 14-June-2011 if possible. https://spaces.at.internet2.edu/display/COmanage/Glossary
[AI] (Benn) during upcoming trip to SURFnet, inquire about progress in domesticating FileSender
Carry Over Action Items
[AI] (Keith) will check with Project Bamboo concerning IRODS connection.
[AI] (RL "Bob") will initiate a GSS / SAML / LDAP discussion with Scott Cantor.
[AI] (Keith) will send a pointer to OpenSearch information
[AI] (Ken) will provide a link to the French listing regarding applications and sets/bundles of attributes.
[AI] (Ken) will contact David Groep about VOMS GUMS.
[AI] (Steven) will develop a one-page write-up on attribute aggregation.
COmanage Project Org.
The COmanage lists have been restructured as described here: https://spaces.at.internet2.edu/display/COmanage/Project+Org+Structure
This is the first call of the COmanage-TAC group.
Heather plans to schedule a monthly COmanage community call which will include topics such as: Invitation and enrollment flow, Latest in domesticated apps, Connecting with researchers, VO-specific attributes (CMP as IdP)
Keith wondered if the Project Org Structure wiki page should state that TAC members might share opinions about the direction for the COmanage project, which elements of other CMPs are best to build on, etc.
Terminology, especially the terms "COmanage Platform" and "CO"
• Ken asked for clarification about the use of the term COmanage Platform in the sentence: "The COmanage Technical Advisory Committee will advise on the technical questions and issues that relate to the COmanage platform...."
• Benn explained that broadly speaking the COmanage platform is what you get when you combine the COmanage registry with Grouper and a set of applications. That collective ecosystem of things is the COmanage platform. We are leaving this vague to see how it evolves.
• COmanage platform will look different depending on the user's configuration
• Ken stated that he is OK with the definition of COmanage platform evolving over time. Perhaps every 3 months we should revisit what we mean
• Benn stated that the current glossary definition (COmanage platform = A CMP based on the COmanage data model and the COmanage REST COnnector API but otherwise independent in its design and implementation) is probably too narrow/too specific.
[AI] (Benn and Heater) revise the current COmanage glossary definition for "COmanage platform." https://spaces.at.internet2.edu/display/COmanage/Glossary
• Michael raised concern about the glossary definition of CO as "A Virtual Organization, but with additional capabilities allowing for collaborators to use their institutional identities and services. A CO provides the essential IT infrastructure supporting collaborations between people among separate institutions overcoming the traditional boundaries of Internet applications."
• Michael stated that a CO is not necessarily a VO.
• Ken agreed, and also suggested that perhaps there should be a concept in the glossary about a group that is "to the left or soft side of a CO"
• Benn and Heather will review these terms on Tuesday 14-June-2011, and they welcome appreciate input. Ken is not available to join Heather and Benn's Tuesday discussion, but Ken would like to have a call with Heather and Benn later in the week.
[AI] (Everyone) review the COmanage glossary and express questions/concerns to Heather and Benn prior to 14-June-2011 if possible. https://spaces.at.internet2.edu/display/COmanage/Glossary
File Sender Services
• Ken reported that Internet2 is moving forward with a file sender type of service, offered to members at an attractive cost.
• Randy Frank is spearheading this.
• Most likely this will not be a federated service, partly due to complications around attribute release.
• File sender software will be discussed at the CSG meeting next week. Internationally, projects include:https://wiki.surfnetlabs.nl/display/domestication/FileSenderhttp://www.bigfilesender.com.au/faq.html
[AI] (Benn) during upcoming trip to SURFnet, inquire about progress in domesticating FileSender
• There has been conversation on several lists about box.net , which is a file sharing platform for smaller files
• There is some interest in bringing box.net into InCommon.
• Shel is on the technical advisory group for box.net
• There is a SAML version of box.net, configured for one login. See http://support.onelogin.com/entries/388391-configuring-saml-for-box-net
Service Instance of COmanage / Mutual Sharing with the Dutch CMP
• Eventually there will most likely be a service instance of COmanage, but timeframe is not clear.
• Sharing of pieces of the CMP work between Internet2 and the Dutch is seen as a positive
• Michael: The Dutch CMP work makes heavy use of OpenSocial. Is COmanage open to doing that also? https://wiki.surfnetlabs.nl/display/OpenConext/Features
• Benn: OpenSocial is part of the UI conversation. Possibly uPortal or other options could fill this same function.
• We should be guided by what our users need, and this can adapt over time
• Keith: as part of Project Bamboo role, I want to get the OpenConext stack running to kick it around
• Keith noted that OpenConext is using JANUS ( http://code.google.com/p/janus-ssp/as ) metadata management tool
• JANUS may or may not work in the COmanage (non-European) environment. Centralized mechanisms make sense in Europe.
Next COmanage-TAC call: Friday, 24-June-2011, 2pm ET