Main Nav

A new version of the eduPerson spec is now in last call. See the attached document (apologies for cross-postings).

The changes from the previous version, eduPerson (200806), are found in the sections on eduPersonAffiliation, eduPersonPrimaryAffiliation and eduPersonTargetedID.  See the Change Log section of the document for details.

>>  Last call begins with this email on 12-March-2012 and will be open through 26-March-2012  <<

Please direct any and all comments, objections or suggestions to
 - if you are a subscriber to that mailing list
 - Or to if you are not.

For best results, open the attached .html file in your browser or your html editor of choice.

        --Keith Hazelton for MACE-Dir

eduPerson-201203-draft-01.html89.96 KB


Individual responses to detailed suggestions from Gabriel Sroka during the first round of last call  (Thank you, Gabriel, and others, for your input).

On Mar 12, 2012, at 17:35:18, Steve Olshansky wrote:


Begin forwarded message:

From: "Sroka, Gabriel" <>
Date: March 12, 2012 4:33:57 PM MDT
Subject: [i2mi-info] FW: [InC] Opening of Last Call on eduPerson (201203)

The link to "Home" at the beginning of the document returns a 404 (page not found). Perhaps that's intentional since it hasn't been published yet, but there are plenty of "draft" docs on


In "3.5 facsimileTelephoneNumber", "3.7 homePhone", "3.15 mobile", "3.18 pager", and "3.27 telephoneNumber", it's not specified whether national or international numbers (or both) should be used. They're both defined in [E.123, Section 2], e.g.:
National: (222) 555 1234
International: +1 222 555 1234
Previous versions of eduPerson (e.g. 200712) did specify "international". Was that loosened on purpose or on accident? And if we're using international here, then should "3.8 homePostalAddress" and "3.19 postalAddress" also have "$USA" like in [RFC 2252, 6.27]?:
1234 Main St.$Anytown, CA 12345$USA
Maybe a more basic way to answer both of these: is eduPerson designed for USA use? Home country use? International use? Any of the above?  "3.20 postalCode" mentions "other countries"…  Explicitly stating the answer to this question somewhere in eduPerson might add clarity.

Since the attributes in question are formally defined in other RFCs, the eduPerson specification carries over the definitions found there without change. 

However, the above questions might well be taken up by federations, or even an inter-federation initiative. It seems wiser to keep the eduPerson specification lean, and leave matters of best practice to the communities that have a direct stake in the matters at hand.

The most recent bullets in "4. Change Log" are numbered "1, 1, 2". It seems they should be "1, 2, 3". They're also single-spaced, whereas previous change log entries are double-spaced.


It'd be nice to provide links to RFCs and other publicly available standards, e.g.
either inline or together at the end of the document. If you don't want to "be responsible" for broken or changed links, you could always add a disclaimer that the links are added for convenience.

References section added

In "0 TOC", some of the anchors (<a href="#something">) are broken, e.g. links to 2, 2.1, 2.2, etc.


Subsections under 3 are separated by <hr>, but subsections under 2.2 are not. An <hr> or some extra space might be nice.

Done.       --Keith