Subject: [scim] Design Team Status

From: Trey Drake <[email-masked]>
Date: Mon, 29 Oct 2012 10:43:37 -0500

The design team has identified and is actively working the following issues:

Schema:
- Object relationship (children objects?)
- Keep existing info model or adopt other.  vCard is in the running.  Key consideration is extensibility.
- Remove XML data model. Spec JSON only?
- Metadata on each attribute (possibly on each value). Provides the ability to set meta-data describing an attribute's: creation date , expiry date, source,  if verified, etc. 
- Attribute value case preservation (e.g. ExternalID). Must the service provider respect the consumer case sensitivity?  Problematic w.r.t. indexing, et al. 
- Entitlements – remove from spec and make it extension or define basic model

API:
- Re-visit the API.  Should we further elaborate the API/response so that it is more Graph like a la oData? For example, embed Group/user relationship/references?  
- Multi-Tenancy clarifications
- REST pattern (URL modeling, filter semantics, object naming rules)
- Patch improvements/cleanup
- Query/filter semantics improvements: return only values that match the query (not all values – ex. Search for groups with member foo, but only return member foo and not all members), negation
- Search query parameters via GET URL vs. post?  If POST there is a case to be made to introduce a search operation; e.g., X-SEARCH vs GET overloading
- Password management and policy – should this be spec'd now, later or simply handle as an extension?

Thanks,
Trey