IETF Logo Mail Archive

[scim] how to describe SCIM extensions in the modern world

Eliot Lear <lear@lear.ch> Wed, 25 January 2023 14:36 UTC

Return-Path: <lear@lear.ch>
X-Original-To: scim@ietfa.amsl.com
Delivered-To: scim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AA43C14CF0C for <scim@ietfa.amsl.com>; Wed, 25 Jan 2023 06:36:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=lear.ch
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aYS456-CyBeC for <scim@ietfa.amsl.com>; Wed, 25 Jan 2023 06:36:07 -0800 (PST)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [IPv6:2a00:bd80:aa::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4099EC14CF15 for <scim@ietf.org>; Wed, 25 Jan 2023 06:36:06 -0800 (PST)
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1674657363; bh=FYVHV9FgmPc0S+/P+9yA97SZWKT784smzZP7i+4JuEs=; h=Date:To:Cc:From:Subject:From; b=TkPEIxIzEs8GZi3ITHzxajF3i6XXxQORobY53bgnY4vN4J7KTEITksrZaSoQj/jpE 8doHOX7qI+ovfmTlN1EEtHU/5FLSoKrr1E7HlZVDDqgQsaTd8Pi2kOtDTXjEsLLdmG Fh7XQ4bFzijD7uW4D8Apl/0hQV4ayOeikgFIQIhk=
Received: from [IPV6:2001:420:c0c0:1011::1] ([IPv6:2001:420:c0c0:1011:0:0:0:1]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-22ubuntu3) with ESMTPSA id 30PEa2kN518811 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Wed, 25 Jan 2023 15:36:03 +0100
Content-Type: multipart/alternative; boundary="------------V0pudnwr4Rrvg1JEE0d3A9YE"
Message-ID: <46c19fb4-9c71-c1aa-1a77-6bf2f2b65a6a@lear.ch>
Date: Wed, 25 Jan 2023 15:36:01 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.6.1
Content-Language: en-US
To: "scim@ietf.org" <scim@ietf.org>
Cc: Carsten Bormann <cabo@tzi.org>
From: Eliot Lear <lear@lear.ch>
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/XtanIMeEWen4umd8KeHlu4Ha8Lw>
Subject: [scim] how to describe SCIM extensions in the modern world
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 25 Jan 2023 14:36:12 -0000

Hi everyone,

Last year I said that we were looking for the best way to describe SCIM 
extensions.  Realistically the world is going in one of three directions:

  * JSON Schema;
  * OpenAPI; and
  * AsyncAPI

JSON Schema presents some challenges for Internet-Drafts in that it 
doesn't fold well.  Not that this should be the key design decision, but 
it is annoying.

OpenAPI and AsyncAPI each borrow from JSON Schema.  OpenAPI directly 
maps to a RESTful interface while AsyncAPI can map to Other Things like 
MQTT.  But it too seems to be able to map to RESTful.

Do people have thoughts about this?

Eliot

v2.23.0 | Report a Bug | By Email