Attendees

Agenda

1. Introductions/Roll Call
2. Updates
3. Project Proposal - Eric/Jessica/Renee/Matt
   1. Requirements Chunking Exercise - Matt
   2. Draft Proposal - Eric/Jessica
   3. Timeline and Estimates Work - Renee/Matt
4. Strategy Group Updates - Bob

Action Items

1. Review Identity Match proposal on a future call?
2. Rehash group's goals and workplan for near future

Notes

back to the existential question:  what does this subteam think it is doing, or supposed to be doing?

• continued discussion about finding the balance between code and interfaces
• code fills gaps, interfaces define the gaps to be filled
• the "suite" wants code, and decisions about this code vs that code
• the "ecosystem" wants interfaces, and architecture

consensus regarding id-match as the first example component to define interfaces and component functionality

• is id-match component "inside" the Person Registry?
  where "inside" could mean:  inseparable from PR, or only called by PR
  one UC campus has a model where id-match is called by source systems, so need to support that
  OpenRegistry has Java interface, but id-match is "inside" today

how do we do interface specification? 

• language-specific is to be avoided
• Kuali has used SOA (XML/SOAP) service contracts
• RESTful is popular these days.  yes, everyone likes RESTful, so let's do that

the HR interface

• UC overall is driven by common Oracle HR across campuses
  Rutgers has Oracle HR too, interested in common interface
    but at Rutgers person data flows via Data Warehouse

F2F

• in Phoenix Jan 5-6 2012
• please indicate interest in attendance (if you haven't been tapped already)

public communication

• some concern about whether we have enough to say, but on reflection maybe we do
• add bullets to wiki page, maybe wind up next week