MACE-Dir call
January 9, 2005

*Participants*

Keith Hazelton, U. Wisconsin - Madison (chair)
Tom Barton, U. Chicago
Todd Piket, MTU
Steven Carmody, Brown U.
Scott Cantor, Ohio State U.
Walter Hoehn, U. Memphis
Brendan Bellina, USC
RL "Bob" Morgan, U. Washington
Ann West, EDUCAUSE/Internet2
Steve Olshansky, Internet2
Jessica Bibbee, Internet2 (scribe)

New *Action Items*

[AI] {Keith} will work on finalizing scoped attributes before sending out a last call on the eduPerson rev, and will then submit to the MACE Group for comments/approval.
[AI] {Walter and Tom} will collaborate on the development of a domain model.
[AI] {Steven} will write-up use cases on requirements for provisioning systems, and send to {Walter}.

Carry-over *Action Items*

[AI] {Volunteers} should contact {Roland} if they are would like to review the documentation and look at the code for the software. (5-Dec-05)
[AI] {Walter} will work on developing a domain model for Nexus. (5-Dec-05)
[AI] {Group} will contribute their own requirements for provisioning systems, and should contact {Walter}. (5-Dec-05)
[AI] {Group} will send feedback to {Brendan} for incorporation into the HEP revision 6. (21-Nov-05)

*Discussion*

{Keith} posted a revised draft of the eduPerson to the mailing list, available at: <http://www.nmi-edit.org/eduPerson/draft-internet2-mace-dir-eduperson-latest.html>. All comments and edit suggestions are to be sent to Keith. [AI] {Keith} will work on finalizing scoped attributes before sending out a last call on the eduPerson rev, and will then submit to the MACE Group for comments/approval.

The Group discussed attributes of the InCommon Federation. How does an entitlement differ from affiliation? The library community uses InCommon to allow access rights for certain pages. The usage of each defines it within that particular context. The value of allowing multiple documents to say the same thing lies in that it supports the flexibility of one to change, without forcing the others to follow. Still, efforts should be made wherever possible to minimize the overlapping of terms with the same definitions. Beyond InCommon, enforcement of definitions is not possible. Also discussed were the possibility of and how a multiple federation would operate. How does the European federation handle these issues? InCommon needs to ensure that things are defined as needed, and that the technical documentation is revised accordingly.

{Walter} has received some feedback regarding the requirements for provisioning systems, and will respond to the WG mailing list as a whole. He is still interested in receiving additional suggestions for requirements. The Group was pleased to hear that U. Memphis management has approved the release of the Nexus code under the Apache 2 license. [AI] {Walter and Tom} will collaborate on the development of a domain model.

[AI] {Steven} will write-up use cases on requirements for provisioning systems, and send to {Walter} (cf. Keith’s email on 9-Jan.)

Please note that the calls will be returning to the original bi-weekly schedule; due to the Martin Luther King holiday, the 16-January call will be cancelled. Therefore, the next MACE-Dir call will be held on Monday, January 30, 2006 at 4:30pm ET.