Subject: [scim] Two draft search proposals: X-Search and Token-Search

From: Phil Hunt <[email-masked]>
Date: Sun, 23 Dec 2012 15:02:42 -0800

The design team has developed to strawman proposals (draft-hunt-scim-tokensearch & draft-hunt-scim-xsearch) to solve 3 outstanding ticket items.  Both solutions are equivalent and are expressed as if they were independent specifications. The 3 items covered are:

1 Ticket 25 - Ability to search for objects of multiple resource types
2.Ticket 29 - Ability to search without leaking confidential filter terms in the URL (POST search).
3.Ticket 31 - Ability to page through results without the result set changing between page requests.

The major difference between these specifications are that one creates a RESTful resource representation of the search operation and the other uses token parameters to represent a search result.  Depending on your point of view, one may seem simpler than the other. To give you a quick summary of the differences, a PDF is attached comparing the APIs.

For now, let's not get into the details right away. Let's keep this simple. Which draft is closer to what you would like to see?   X-/Search or Token-Search

With the agreement of the chairs, we can then seek to refine one of the candidate proposals and then discuss what parts to include (if at all) in the main specification and what parts ot keep separate.

Links to the draft are:
http://datatracker.ietf.org/doc/draft-hunt-scim-xsearch
http://datatracker.ietf.org/doc/draft-hunt-scim-tokensearch

Thanks to everyone for your contributions and comments on this.

Happy holidays!

Phil

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