[scim] Question on the use of attributes from schema extensions

Keith Hazelton <keith.hazelton@wisc.edu> Tue, 11 August 2015 16:28 UTC

Return-Path: <keith.hazelton@wisc.edu>
X-Original-To: scim@ietfa.amsl.com
Delivered-To: scim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 179F91ACD15 for <scim@ietfa.amsl.com>; Tue, 11 Aug 2015 09:28:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.51
X-Spam-Level:
X-Spam-Status: No, score=-1.51 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YkwzIM4lLh9B for <scim@ietfa.amsl.com>; Tue, 11 Aug 2015 09:28:22 -0700 (PDT)
Received: from smtpauth3.wiscmail.wisc.edu (wmauth3.doit.wisc.edu [144.92.197.226]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D29321ACD14 for <scim@ietf.org>; Tue, 11 Aug 2015 09:28:22 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_D0NgYZYGElDlQFyboXCz7w)"
Received: from avs-daemon.smtpauth3.wiscmail.wisc.edu by smtpauth3.wiscmail.wisc.edu (Oracle Communications Messaging Server 7.0.5.33.0 64bit (built Aug 27 2014)) id <0NSX00900E5VB000@smtpauth3.wiscmail.wisc.edu> for scim@ietf.org; Tue, 11 Aug 2015 11:28:21 -0500 (CDT)
X-Spam-PmxInfo: Server=avs-3, Version=6.1.1.2430161, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.8.11.161816, SenderIP=0.0.0.0
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0187.outbound.protection.outlook.com [207.46.163.187]) by smtpauth3.wiscmail.wisc.edu (Oracle Communications Messaging Server 7.0.5.33.0 64bit (built Aug 27 2014)) with ESMTPS id <0NSX00I6KF358SD0@smtpauth3.wiscmail.wisc.edu> for scim@ietf.org; Tue, 11 Aug 2015 11:28:18 -0500 (CDT)
Received: from DM2PR0601MB1231.namprd06.prod.outlook.com (10.160.220.21) by DM2PR0601MB1232.namprd06.prod.outlook.com (10.160.220.22) with Microsoft SMTP Server (TLS) id 15.1.225.19; Tue, 11 Aug 2015 16:28:16 +0000
Received: from DM2PR0601MB1231.namprd06.prod.outlook.com ([10.160.220.21]) by DM2PR0601MB1231.namprd06.prod.outlook.com ([10.160.220.21]) with mapi id 15.01.0225.018; Tue, 11 Aug 2015 16:28:16 +0000
Received-SPF: None (protection.outlook.com: wisc.edu does not designate permitted sender hosts)
Date: Tue, 11 Aug 2015 16:28:16 +0000
From: Keith Hazelton <keith.hazelton@wisc.edu>
X-Originating-IP: [128.104.18.177]
To: SCIM WG <scim@ietf.org>
Message-id: <3FBCDECF-424B-4C8D-AE4F-7C2BADEC91F2@wisc.edu>
Content-language: en-US
Accept-Language: en-US
Thread-topic: Question on the use of attributes from schema extensions
Thread-index: AQHQ1FK56KvsUaCh00CJq2Szj2pZpg==
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-microsoft-exchange-diagnostics: 1; DM2PR0601MB1232; 5:f9eHRWLUUaLGkK057r4IWaYTfDMCvQpwouTVt3yG8ZbsCO+yZgvDLmImLu/onDLTqGwhIbRX2gKfcEDTcYi4dyJc1iD/mZyzqwMHxcO9Dx8VjAuPVlD0sQOMz1PAdeS1m/SP102rT9vDu6routak9w==; 24:Qq3+iDlFI1adK8DZXIAEtmm8mxX1V1j86UeKYkJbySfO5wNiqWcO+GZzJc6/nFVNYwCuyxQ+Dfs9IQ2eiHs4DmLzc6sazOKy8OpLYKfG88k=; 20:Elz7BIBYK/HZpc4ttb1F0vVLF/P3JAD9fXgri+GbeypdRvycrrUliAmlo7OkCpfnNqkZw4kwQGqTn+DGCOTatQ==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0601MB1232;
x-microsoft-antispam-prvs: <DM2PR0601MB1232FD77E9609056256ABEB6F47F0@DM2PR0601MB1232.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(3002001); SRVR:DM2PR0601MB1232; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0601MB1232;
x-forefront-prvs: 066517B35B
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(189002)(199003)(229853001)(46102003)(105586002)(77096005)(5002640100001)(62966003)(66066001)(33656002)(2656002)(86362001)(64706001)(87936001)(5001860100001)(19580405001)(450100001)(5001960100002)(189998001)(110136002)(2900100001)(15975445007)(92566002)(107886002)(77156002)(10400500002)(88552001)(16236675004)(89122001)(4001540100001)(19617315012)(68736005)(122556002)(106356001)(82746002)(81156007)(106116001)(5001830100001)(101416001)(97736004)(19580395003)(54356999)(75432002)(36756003)(50986999)(90282001)(102836002)(40100003)(83716003)(99286002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR0601MB1232; H:DM2PR0601MB1231.namprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
X-OriginatorOrg: wisc.edu
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Aug 2015 16:28:16.5342 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2ca68321-0eda-4908-88b2-424a8cb4b0f9
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0601MB1232
Authentication-results: spf=none (sender IP is ) smtp.mailfrom=keith.hazelton@wisc.edu;
Archived-At: <http://mailarchive.ietf.org/arch/msg/scim/za9c9DRadKQ733bXHhNH-GS4sng>
Subject: [scim] Question on the use of attributes from schema extensions
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Simple Cloud Identity Management BOF <scim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/scim>, <mailto:scim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/scim/>
List-Post: <mailto:scim@ietf.org>
List-Help: <mailto:scim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/scim>, <mailto:scim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Aug 2015 16:28:25 -0000

Prior to draft-ietf-scim-core-schema-10, this language was found in Section 3: “Except for the base object schema, the schema extension URI SHALL be used as a JSON container to distinguish attributes belonging to the extension namespace from base schema attributes.”

In later drafts, e.g. draft-ietf-scim-core-schema-22, the corresponding language is: "Unlike core attributes, extended attributes are kept in their own sub-attribute namespace identified by the schema extension URI."

Is it the intent of the current language that in the JSON representations of a resource it is permissible to interleave namespace-qualified attributes from schema extensions with attributes from the core schema? E.g., is something like this allowed:

{
  "schemas":
    [ "urn:ietf:params:scim:schemas:core:2.0:User",
      "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"],
  "id": "2819c223-7f76-453a-919d-413861904646",
  "externalId": "701984",
  "userName": "bjensen@example.com",
  "name": {
    "formatted": "Ms. Barbara J Jensen III",
    "familyName": "Jensen",
    "givenName": "Barbara",
    "middleName": "Jane",
    "honorificPrefix": "Ms.",
    "honorificSuffix": "III"
  },
  "displayName": "Babs Jensen",
  "nickName": "Babs",

  "enterprise:2.0:User:employeeNumber": "701984",
  "enterprise:2.0:User:costCenter": "4130",
  "enterprise:2.0:User:organization": "Universal Studios",
  "enterprise:2.0:User:division": "Theme Park",
  "enterprise:2.0:User:department": "Tour Operations",
  "enterprise:2.0:User:manager": {
      "value": "26118915-6090-4610-87e4-49d8ca9f808d",
      "$ref": "../Users/26118915-6090-4610-87e4-49d8ca9f808d",
      "displayName": "John Smith"
    }
...
}

Such a layout would make it easier to visually scan such a resource, thus encouraging the freer use of schema extensions where appropriate.

      Regards,  --Keith Hazelton
--
email & jabber: keith.hazelton@wisc.edu<mailto:keith.hazelton@wisc.edu>
calendar: http://go.wisc.edu/i6zxx0