...
- How are subjects namespaced?
- How is a subject represented? What attributes are built in? (e.g. Grouper has built in name, description, id, source, and can be searched by identifier or id or either). Or does the group service communicate with an id, and subject information is retrieved from another system.
- Can you get netId's back from the service or just opaque id's?
Protocol
- Initial assumption is web service based with pluggable authentication
- Do we need a messaging design (xmpp)?
- REST? (if REST, then XML, JSON, and/or XHTML)?
- SOAP?
- Simple calls?
- Batched calls (e.g. replace all members of a group with the attached list)? (if batched, can you pass a TX type)?
- Simple responses or complex responses (e.g. for groups a subject is in, return just the ID (KIM) or return group information(Grouper))?
- How are results communicated back? Result code, description, warnings, errors, success_TF, etc?
- If you add a member to a group who is already a member, is that a success, and is there a result code that represents that? (same with delete)
- Paging and sorting for results?
- Is the client and server version transmitted in the request/response?
...