Subject: [scim] Querying and Attr list expected formats and results with extended schema

From: Phil Hunt <[email-masked]>
Date: Mon, 9 Sep 2013 10:25:30 -0700

In the case where extended schema is being used, I'd like to clarify attribute use in filters, attributes, results.

Let's say I am using urn:scim:schemas:extension:enterprise:2.0:User and I want to query employeeNumber that is part of that schema.  

For both filters and attributes would the following apply:
a. The plain attribute name can be used if no conflicts
b. In case of conflicts, a fully qualified name may be used in attributes and filters, eg:
urn:scim:schemas:extension:enterprise:2.0:User:employeeNumber

Note above, I have used ':' between the schema qualifier and the attribute name.

Likewise, a filter for a complex attribute:
urn:myOfficeExtension:addresses.type="main"

Where this hypothetical addresses might be a similarly defined User addresses but contains a set of work locations.

GET /Users?attributes=userName,employeeNumber
   Host: example.com
   Accept: application/json
   Authorization: Bearer h480djs93hd8

   HTTP/1.1 200 OK
   Content-Type: application/json

   {
     "schemas":["urn:scim:schemas:core:2.0:ListResponse"],
     "totalResults":2,
     "Resources":[
       {
         "id":"5bd1b1f6-b337-452e-942a-786dd50e66f2",
         "userName":"bjensen",
         "urn:scim:schemas:extension:enterprise:2.0:User": {
             "employeeNumber": "11250"
             }
           }

       },
       {
	 "id":"9168eea2-4f76-4997-bf7e-d9c90277b31a".
         "userName":"jsmith"
       }
     ]
   }

Is this what the group feels should be occurring?

Phil

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