...
- The SCIM extension mechanism means all attributes defined in an extension are collected into a complex schema element below all the SCIM-defined base schema attributes. If there are two extensions, there will be two collections of additional attributes. See the example of a SCIM User resource supplemented with a SCIM Enterprise User.
- Precludes modification of any attribute defined in a given SCIM 2,0 Resource Type. SCIM Resource Type identifiers (Users, Groups, etc.) are reserved names in TIER, and all attributes defined in a given SCIM Resource Type must share the same syntax and semantics when used in TIER.
Proposal 2)
...
Don't reuse User and Group SCIM Resource Types, but define and use new Resource Types TierGroup and TierUser. Stick with "TIER is a superset of SCIM"
Pros:
- Freedom to define our own schema without having to prefix attribute names
- Avoids use of the clunky SCIM schema extension mechanism for Users and Grouips
Cons:
- TIER User and Group Resource Types would have "Tier" at the front while other resource type name would not (or would they?)