By Independentid-Oracle on Feb 24, 2015
Last week, I had a question last week about SCIM's (System for Cross-domain Identity Management). How does the working group recommend handling message validation? Doesn't SCIM have a formal schema?
To be able to answer that question, I began to realize that the question was about a different style of schema than SCIM supports. The question was assuming that “schema” is defined how XML defines schema as a way to validate documents.
Rather than focus on validation, SCIM’s model for schema is closer to what one would describe as a database schema much like many other identity management directory systems of the past. Yet, SCIM isn't necessarily a new web protocol to access a directory. It is also for web applications to enable easy provisioning. The SCIM schema model is "behavioural" - it defines the attributes and associated attribute qualities a particular server supports. Do clients need to discover schema? Generally speaking they do not. Let’s take a closer look at schema in general and how SCIM’s approach supports cross-domain schema issues.