Versions Compared

Key

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

...

  1. Determine gaps between COmanage’s registry and the minimal, first iteration requirements for the TIER Entity Registry. Recommend to CAPE that development work be commissioned to fill those gaps.

Timeline

Iteration (Monday, February 1 to Friday, March 4, 2016)

 

  • Document Functional Requirements for System of Record (SoR) to the Entity Registry per the conscription pattern of enrollment.  

      • In the conscription pattern of enrollment, person resources are created/mastered in the Registry; an SoR sends the Registry a representation of a person resource that is new to them.

      • The Registry invokes a mock ID Match API operation that always returns ‘no match’

      • The Registry creates a new mock person resource and returns a unique id to the calling SoR.

...

      •  

  • Document operations on person resources to be exposed as APIs and as event messages for the above connections, SoR to Registry and Registry to IDMatch;  

...

  • Share drafts of these documents with TIER Data Structures and APIs WG for their comments and questions.

...

  • Define

...

  • a minimal first iteration Registry person schema/resource; Share with the API WG.

...

  • Draft a first iteration glossary of institutional processes around identity lifecycle management.

...

 

...

  •   

  • Draft fit

...

  • /gap analysis between current COmanage registry functionality and this WG’s minimal, first iteration requirements.

  • Provide CAPE with rough definition of work required to fill in gaps in COmanage functionality, recommend commissioning that work.

 

Iteration (Monday March 7 to Friday, April 1, 2016) 

  • Repeat

...

  • steps 1)

...

  •  to 4) above, expanding the scope of

...

  • functionality covered by API and event messaging operations.

 

Phase I Wrap-Up

 

After completion of the above tasks and deliverables, this Working  Working Group should help draft a charter for a follow-on Phase II Entity Registry Working Group charged Group charged with determining a richer set of functionality for the Entity Registry Component of TIER. Phase II work should also identify gaps, document resource needs and outline a roadmap for implementing expanded functionality in future releases of the TIER Entity Registry package.

 

Request for Internet2 Assistance:

...