Versions Compared

Key

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

...

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)

Action Items

New

  1. Benn: Change URN to URI, discuss with Chris a reasonable maximum length based on typical group lengths (probably <= 255)
  2. Keith: To draft an example of an IDL representing

Old

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