...
- URN vs URI/URL
- What's a good max length for URI/URL?
- Is there a good (eg: DOM/IDL) way to represent APIs in wide use these days?
- How to deal with renaming? Or do we need to?
- One identifier with an HTTP-301 like response code (we may want to embed this anyway)
- Allow multiple URI identifiers, some of which may be persistent (eg: UUID)
- Prohibit reassignment of renamed groups (plausible if the VIP-wants-the-name case is invalid)
- API: should rather than must identify when a group has been renamed
- Perhaps this is really a phase 2 kind of thing
- Search Filters?
- Problematic for federated groups (where the group itself is federated)
- This is probably just for UIs – therefore probably just need substring on name or member
Action Items
New
- 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
- Keith: To draft an example of an IDL representing
- Benn: Review various open questions with Chris, perhaps start on some of the TODO items
- Benn and Tom Z: Figure out where to start with Provisioning API
Old
- Chris: Find out why subject type was dropped from I2 subject API
- Benn: To put together new identifier proposal
- Benn: Clean up Group API Data Structures and Operations for wider distribution
- All: Identify use cases for renaming