Versions Compared

Old Version 5

changes.mady.by.user Jon Miner

Saved on

compared with

New Version Current

changes.mady.by.user Keith Hazelton (wisc.edu)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

For purposes of this document, the term SCIM stands is a shorthand for RFC's 7642, 7643 and 7644

...

  1. TIER API specifications follow SCIM conventions on syntax and semantics unless specific and documented alternatives are called out
  2. Some TIER APIs may be defined as profiles of SCIM-defined APIs
  3. TIER Resource Type specifications follow SCIM conventions on schema definition and extension processes, syntax and semantics
  4. Some TIER resource types may be defined as profiles of SCIM resource types
  5. In the case of messages that carry a representation of a resource, they should share the data structure and schema of its API counterpart.

Benefits of following these principles:

...

  1. For each TIER-defined resource type, ensure that all required SCIM meta attributes have a direct counterpart in the TIER meta element
  2. To add Institution-level schema elements to TIER-defined resource types, follow the SCIM-defined schema extension methods
  3. Define Internet2 Trust and Identity processes for self-registration of resource types and their schema: :everage Open API 2.0 and some API Manager, Developer Portal