Subject: [scim] Open Ticket Recommendations (Tickets 41 +)

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

Final open ticket recommendations:

Ticket: 41 Add IANA considerations
Recommendation: Defer
Comment: still a todo

Ticket: 42 Make server root searches optional
Recommendation: Apply to draft
Comment: This has been discussed on list and at IETF 87/88. Should proceed with proposed text

Ticket: 43 Consider dropping short-hand notation for complex multi-valued attributes
Recommendation: defer / merge with 36
Comment: Seems to be related to ticket 36?

Ticket: 44 Add JSON Schemas for Core Schema Resources
Recommendation: Apply to draft
Comment: Seems straight forward.  Note: seems related to Ticket 40 (JSON format for defining a set of scim schema extensions)

Ticket: 45 LDAP Mapping
Recommendation: Defer
Comment: LDAP is more of an endpoint (client) rather than SCIM SP capable item. Would an LDAP Profile of SCIM (e.g. no complex attributes Users) be more appropriate?

Ticket: 46 Clarify error responses and allow non-HTTP error codes
Recommendation: Defer
Comment: Need proposal text. Seems tied in with Ticket 37

Ticket: 47 Attribute Indexing
Recommendation: Apply to draft
Comment: Item proposal reviewed and discussed at IETF88

Ticket: 48 Operations with Extended Schema Attributes
Recommendation:  Apply to draft
Comment: Seems like a straight forward clarification

Ticket: 49 Ends With filter missing
Recommendation: Apply to draft
Comment: Apply missing filter to draft

Ticket: 50 Filter semantics do not allow filtering on complex plural attributes (aka inner join)
Recommendation: Apply to draft
Comment:  A reasonable set of proposals was given at IETF88 -- consensus was around adding [subattr clause] notation.

Ticket: 51 Formalize searching by schema
Recommendation: Apply to draft
Comment:  Seems like a reasonable clarification (?)

Ticket: 52 Minor textual changes
Recommendation: Apply to draft
Comment: editorial issues.

Ticket: 53 Consumer vs Client
Recommendation: Apply to draft
Comment: editorial issues.

Ticket: 54 Define core resource when referencing attributes
Recommendation: Apply to draft
Comment: editorial issue

Ticket: 55 Redirection
Recommendation: Apply to draft (for now)
Comment: some limited discussion on list. Is this an item that should be elevated to the WG working on REST?

Phil

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