TIER Entity Registry Working Group Home
Future Calls: Chose the one (Wed. or Fri.) that works best for your schedule and time zone):
Subgroup 2: Friday, 26 February, 2016 at 10 am Eastern, 7 am Pacific, 3 pm UTC
Subgroup 1: Wednesday, 2 March, 2016 at 3 pm Eastern, Noon Pacific, 8 pm UTC
Agenda for upcoming WG meetings plus meeting notes for the past ones are here: http://j.mp/1PWMCp5
Attendees are encouraged to participate in live-scribing the meetings on the above Google doc.
Email List: tier-entreg@internet2.edu
– To subscribe, browse to https://lists.internet2.edu/sympa/admin/tier-entreg
Working Group Chair: Warren Curry, University of Florida
Charter for the TIER Entity Registry Working Group (wiki page)
Key Deliverables for TIER R1
By March 4 (from Charter)
- 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;
- Define a minimal first iteration Registry person schema/resource
- 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 COmanage WG with rough definition of work required to fill in gaps in COmanage functionality
By April 2016 (from Charter)
Iterate on above, expanding scope of functionality covered by API and event messaging operations.
Requirements on an Entity Registry
- From CIFER Registry Team
- From CIFER Enrollment (Registration) Requirements
- From TIER campus surveys
- From U Florida (courtesy of Warren Curry)
Functional Model for Entity Registry and Allied Services
- Identity Registry Functional Model (Sept. 2011, CIFER)
Schema for core IAM resources
Prior work: CIFER SOR-Registry Core Schema Specification
Gabor’s overview: https://gist.github.com/geszes/3d4b9ff49441058db434
Draft Based on Schema.org: https://gist.github.com/geszes/6bfd8926bded03786a63
Clemson Authology schema: http://authology.org/doc/VaultServiceReference/vaultServiceReference.html
Penn State Person Bio Record
COmanage Registry Data Model
Person Schema Comparisons:
Member-contributed Resources
- University of Wisconsin - UDS Person Schema
- Comparison of UW-Madison UDS Person API and CIFER API
- Rob Carter thoughts on fine-grained authZ on APIs for data access
See Also:
TIER Data Structures and APIs Working Group
Background information on TIER, Internet2 initiative on Trust and Identity in Education and Research