1 / 13

Exploring EduPerson in Higher Education Directories

Dive into the EduPerson specification, its implementation, and the community's future direction in higher education directories. Discover key attributes like EduPersonAffiliation and how it simplifies service class identification. Join the discussion on evolving EduPerson object classes and stakeholder involvement in shaping the directory landscape.

sagira
Download Presentation

Exploring EduPerson in Higher Education Directories

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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 TNC 2001, Antalya, Turkey

  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/ TNC 2001, Antalya, Turkey

  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/ TNC 2001, Antalya, Turkey

  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 TNC 2001, Antalya, Turkey

  6. eduPerson 1.0, Jan-2001 • eduPersonAffiliation attribute • Controlled vocabularyspecified • Involves radical simplification • Faculty, staff, student, alum, member, affiliate, employee • “Member” is any one or more of fac/staff/student/employee • “Member” is the most generic service class (parallels UW-Madison “eligible for ID card”) TNC 2001, Antalya, Turkey

  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 licensor’s major intended service class (faculty, staff, student, alum, member) • MACE-Shibboleth will demo @ I2 fall meeting TNC 2001, Antalya, Turkey

  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@internet2.edu TNC 2001, Antalya, Turkey

  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… TNC 2001, Antalya, Turkey

  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 TNC 2001, Antalya, Turkey

  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 TNC 2001, Antalya, Turkey

  12. Growing the Higher Ed. Directory Community of Interest • Grid needs • International interest in resource sharing • How? • Participation in joint projects • …? TNC 2001, Antalya, Turkey

  13. Questions and Discussion • Your turn... TNC 2001, Antalya, Turkey

More Related