Carry-over *Action Items*
[AI] Keith will email the list with a summary of recent developments in the eduPersonEntitlement space.
[AI] {Keith} will work on simplifying the URN MACE and OID registry page. (27-Mar-06)
[AI] {Keith} will contact (Walter Cohen and Jon} about contributing towards requirements. (27-Mar-06)
[AI] {Bob} will email the list with an informative sentence regarding an additional spec. (13-Mar-06)
[AI] {Steven Carmody} will write up use cases on requirements for provisioning systems, and send to {Walter}. (9-Jan-05)
Future *Agenda Topic*
– M ACE -Dir & EDUCAUSE – how might/should they work together on IdM issues?
*Discussion*
{Keith} lead the call by reviewing a list of potential work items for the MACE-Dir Group during the remainder of 2006. See: <http://arch.doit.wisc.edu/keith/mace-dir/draft-mace-dir-workItems-2006-00.html/> or <http://arch.doit.wisc.edu/keith/mace-dir/draft-mace-dir-workItems-2006-00.static.html/>.
-AuthN: Characterizing authentication events: Use cases, information models, attributes and bindings-
{Keith} suggested that there ought to be a Level of Assurance for testing – might the AuthN attribute work in this sense? Would this work have value, and if so, would it be for internal MACE-Dir use, or would it have a larger scope? [AI] {Keith} will draft a solicitation to the MACE-Dir WG requesting use cases on Levels of Assurance at respective campuses.
Some of the work is either dynamic or static, while some is session bound. [AI] {Group} will draft a proposal for InCommon to clarify MACE-Dir efforts. [AI] {Keith] will raise discussion on the next InCommon Technical Advisory Committee call about the role of MACE-Dir efforts in the Information Model.
-Trusted email addresses-
The Group discussed issues that define a trusted email address, including validation and verification. {Brendan} discussed how USC permits a user to have their campus mail forwarded to an external mail provider, at which point, the user assumes responsibility for receiving mail as though it were the official campus email address. The directory itself does not do forwarding. [AI] {Keith} will revisit the mailing list archives to mine for possible uses cases.
-Deprecating new urn:mace:dir:attribute-def assignments-
The Group discussed how to tolerate, but not encourage, the use of URLs in officially sanctioned materials. What should happen when there is an obvious violation of specifications? It will be more efficient to guide practices of a federation than to try to control individual instances of these violations. InCommon is the proper venue to address the federation work, such as providing examples and documentation.
-eduPerson (2007??): Refactored document suite: Use cases, information models, attributes & bindings-
The eduPerson (2007??) is overdue and much needed. [AI] {Keith} will begin work on eduPerson (2007??). [AI] Group will review the work on eduCourse and give feedback on how to proceed similarly or otherwise.
-eduPersonEntitlement best practices
The Group discussed simplifying work within the Middleware space by reaching consensus on terminology. Where should labor be divided between group memberships and entitlements. Are there use cases in this area? {Tom} suggested holding off until there was more experience and feedback with Signet and Grouper, before a white paper or best practices could be established.
The next MACE-Dir WG conference call will be held on Monday, August 14, 2006.