The release of eduPerson 1.0 is a milestone on the road to a common middleware infrastructure for educational institutions. We have reached consensus on core attributes and the mechanisms by which they should be populated.
Institutions waiting for stability in the specification can now proceed with implementation.
With more implementations comes higher visibility, and with higher visibility comes the participation of other stakeholders and interested parties. We anticipate many suggestions from these new participants and we plan to produce versions 1.1, 1.2, and 2.0 as the standards and practices evolve. We are especially interested in hearing about new applications that might benefit from enhancements to the 1.0 specification. Implementers of eduPerson should be aware of its planned evolution and exercise prudence. A likely area of change will be to the list of allowed values for the eduPersonAffiliation and eduPersonPrimaryAffliliation attributes.