2011 02 08 Conference Call

Bridge Info

2/8/2010 4:00 PM, US/Eastern

+1-734-615-7474 (Please use if you do not pay for Long Distance)
+1-866-411-0013 (toll free US/Canada Only)

0167481# (Participant Code)

Attendees

• Jen B
• Keith H
• Scott C
• Eric W
• Tom Z
• Chris H
• Benn O

Agenda

1. Group API Data Structures and Operations
   1. Identifiers and overall structure
   2. Open questions
   3. Next steps
2. Provisioning API?

Notes

1. URN vs URI/URL
   1. What's a good max length for URI/URL?
2. Is there a good (eg: DOM/IDL) way to represent APIs in wide use these days?
3. How to deal with renaming? Or do we need to?
   1. One identifier with an HTTP-301 like response code (we may want to embed this anyway)
   2. Allow multiple URI identifiers, some of which may be persistent (eg: UUID)
   3. Prohibit reassignment of renamed groups (plausible if the VIP-wants-the-name case is invalid)
   4. API: should rather than must identify when a group has been renamed
   5. Perhaps this is really a phase 2 kind of thing
4. Search Filters?
   1. Problematic for federated groups (where the group itself is federated)
   2. This is probably just for UIs – therefore probably just need substring on name or member

Action Items

New

1. Benn: Change URN to URI, discuss with Chris a reasonable maximum length based on typical group lengths (probably <= 255), update draft with renaming (and possibly other things that the GMS may want to tell the client), first draft of on search filters
2. Keith: To draft an example of an IDL representing
3. Benn: Review various open questions with Chris, perhaps start on some of the TODO items
4. Benn and Tom Z: Figure out where to start with Provisioning API

Old

1. Chris: Find out why subject type was dropped from I2 subject API
2. Benn: To put together new identifier proposal
3. Benn: Clean up Group API Data Structures and Operations for wider distribution
4. All: Identify use cases for renaming