May I introduce you to eduPerson?

1
May I introduce you to eduPerson?
Keith Hazelton Sr. IT Architect,
UW-Madison http//axle.doit.wisc.edu/haz TNC
2001, Antalya, Turkey, 15-May-2001
2
Topics

• EduPerson in context
• Selected facets of the specification
• Next steps
• Communities of interest in higher education
  schema work
• Questions and discussion

3
eduPerson in Context

• Wave of higher education directory
  implementation
• Internet2 Middleware Architecture Committee for
  Education (MACE) directory working group formed
• Planning and implementation advice LDAP
  Recipe
• http//www.georgetown.edu/giia/internet2/
  ldap-recipe/

4
eduPerson in Context

• Community of interest beyond the single campus
• Institution-to-institution sharing
• Institution-to-vendor access to resources
• eduPerson auxiliary object class
• Surfing the wave (a modest top-down initiative)
• Scope person entries in our directories
• http//www.educause.edu/eduperson/

5
eduPerson 1.0, Jan-2001

• Six attributes introduced by eduPerson
• eduPersonAffiliation (more on this in a minute)
• eduPersonPrimaryAffiliation
• eduPersonNickname
• eduPersonOrgDN
• eduPersonOrgUnitDN
• eduPersonPrincipalName
• The rest of the 1.0 spec. offers guidance on
  attributes from person, orgPerson and
  inetOrgPerson

6
eduPerson 1.0, Jan-2001

• eduPersonAffiliation attribute
• Controlled vocabulary specified
• Involves radical simplification
• Faculty, staff, student, alum, member, affiliate,
  employee
• Member is any one or more of fac/staff/student/e
  mployee
• Member is the most generic service class
  (parallels UW-Madison eligible for ID card)

7
eduPerson 1.0, Jan-2001

• Is there any value in a gross-grained attribute
  like eduPersonAffiliation?
• Large volume licensed resource providers will
  likely be its biggest fans
• This attribute promises a single, standards-based
  attribute that would reliably identify the
  licensors major intended service class (faculty,
  staff, student, alum, member)
• MACE-Shibboleth will demo _at_ I2 fall meeting

8
eduPerson 1.0, Jan-2001

• eduPerson object class future
• Of course eduPersonAffiliation controlled
  vocabulary will grow
• In general eduPerson will evolve by a community
  process
• Please participate by sending comments to
  eduperson-comments_at_internet2.edu

9
MACE-Dir Priorities

• MACE-Dir current priorities
• Broader stakeholder involvement in future of
  eduPerson 1.0
• Getting groups and roles into (and out of) the
  directory
• Affiliated directories

10
MACE-Dir Priorities

• Affiliated directories
• Some of us have affiliations with multiple
  institutions
• Imagine a white pages application that showed all
  those affiliations
• Imagine sharing the load by carrying pieces of
  info in the directory closest to theiir home

11
MACE-Dir Priorities

• MACE-Dir current priorities
• Getting the directory to handle non-person
  entries (org. units, services, hardware devices)
• CIM, Grid, ...
• Coordinate with international directory
  initiatives and projects and outgrow the
  US-centrism of version 1.0

12
Growing the Higher Ed. Directory Community of
Interest

• Grid needs
• International interest in resource sharing
• How?
• Participation in joint projects
• ?

13
Questions and Discussion

• Your turn...