...
+1-734-615-7474 (Please use if you do not pay for Long Distance)
+1-866-411-0013 (toll free US/Canada Only)
0167481# 0123809# (Participant Code)
Attendees
...
- Scott C
- Chris H
- Jeremy R
- Tom Z
- Keith H
- Benn O
Agenda
- Review old action items
- Group API Data Structures and Operations
- Permissions API Data Structures and Operations
- findGroups/search filter
- Open questions
- Comments from COmanage Int'l Call
enum immediacy
may be too complicated for the default/simple case- COIP is using AFS style permissions on groups (code at github)
- IDLs
- Does wire protocol matter? REST?
- What else before prototyping?
- Review Group API TODO
Notes
...
- Subject type was dropped from I2 subject API because subject ID and source ID will uniquely identify a subject
- Subject type is basically a namespace qualifier
- Review of Permissions, Groups (see AIs for changes)
- Is findGroups() search syntax too complicated?
- Is enum immediacy too complicated?
- Reasonable default, and some stuff may need it (inc potentially COmanage) to determine unassignability or how a membership came to be
- (CORBA) IDL vs WSDL vs Thrift vs REST API
- Do we want to specify the wire protocol or use an RPC like model?
- REST API might be more useful for javascript queries
Action Items
New
...
- Chris: Revise Permissions API Data Structures and Operations
- permissionLookup -> resource, make terminology consistent with paccman
- Enumerate "common" permissions
- Benn: Update Group API Data Structures and Operations
- Drop privilege stuffÂ
- All: Contemplate alternate proposals for findGroups() search syntax
- Keith: Proof of Concept Thrift spec
- Chris: Draft REST or POX API
Old
- Keith: Look into IDLs
- Benn: Revise current draft based on 2/22 call
- Chris: Draft initial search filter object
- Benn: Change URN to URI, update draft with renaming (and possibly other things that the GMS may want to tell the client)
- Benn and Tom Z: Figure out where to start with Provisioning API
- Chris: Find out why subject type was dropped from I2 subject API
- All: Identify use cases for renaming