Versions Compared

Old Version 6

changes.mady.by.user rlmorgan@washington.edu

Saved on

compared with

New Version 7

changes.mady.by.user rlmorgan@washington.edu

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

Note
titleRequirement

A general Registry solution must be able to support multiple types of SORs, which may not provide the same attributes.

Wiki MarkupTypically, an SOR is only authoritative for role-level data about a specific population (eg: students or employees). _\[OSIdM4HEteam:Not trying to start a terminology battle here... role just means, eg, attributes associated with being a student.\]_ The Registry is authoritative for person-level data. The line between these two may vary according to a given organization's needs or policies, but typically person-level data includes attributes such as name (which may be selected from an SOR's name for an individual) or netid, while role-level data includes attributes such as title or physical address.

Note
titleRequirement

A general Registry solution must be flexible enough to handle variations across organizational data models.

...