Subject: [scim] Open Ticket Recommendations (Tickets 21 - 40 )

From: Phil Hunt <[email-masked]>
Date: Mon, 30 Dec 2013 13:07:54 -0800

Continuing the open ticket review….

Ticket:  21Add "application" or "system" resource schema
Recommendation: Defer
Comment: This is of interest.  OAuth is defining client registration and this could be the basis for a new schema. This could easily be done in the oAuth client registration draft or a separate SCIM WG draft.  Defer for now.

Ticket:  22 Add metadata to attributes
Recommendation:  Defer
Comment: This would be difficult in some cases to implement at the attribute level in a general way. More discussion needed

Ticket:  23 Clarify requirements for preserving case in attribute values
Recommendation: Defer
Comment: More discussion needed.

Ticket:  24 Add negation operator for filters
Recommendation: Apply to draft
Comment: I think Kelly made a proposal that was accepted at IETF 88?  Note: ticket is not up-to-date

Ticket:  26 Allow search for groups with member foo, but only return member foo and not all members
Recommendation: Won't fix
Comment: This can be avoided by constructing a filter that confirms membership and then requesting only the group id and/or name to be returned.

Ticket:  30
Recommendation: Defer
Comment: No significant work done

Ticket:  31 Support for Consistent Paged Results
Recommendation: Won't Fix
Comment: While the ticket is not up-to-date, there has been a lot of discussion that there is not a strong desire for this feature compared with the possible costs.  At present, current implementers feel retaining search state necessary for consistent results could become a drain on resources and a possible DoS problem.

Ticket:  32 Async / Workflow Support
Recommendation: Defer
Comment: I think we need some practical implementation exploration before commenting on this issue. There is a general async REST issue here.

Ticket:  35 Define Mutability
Recommendation: Add to draft
Comment: This was discussed at IETF88 with recommendations put forward and agreed by the audience.

Ticket:  36  Address is a complex multi-valued attribute or list of sub-attributes
Recommendation: Defer
Comment: this item still needs some discussion

Ticket:  37 Error response when server is unwilling to perform query
Recommendation: Defer
Comment: Could be quickly resolved, however no specific proposal entered on ticket

Ticket: 39  Clarification for response body on DELETE
Recommendation: Defer
Comment: This could be resolved quickly.  Should follow common REST practices IMHO.

Ticket: 40 JSON format for defining a set of SCIM schema extensions
Recommendation: Defer
Comment:  More discussion needed. Could be done as a separate draft

Tickets 41 to 55 to follow…

Phil

@independentid
www.independentid.com
[email-masked]