Re: [scim] Clarification on Groups Schema membership attribute

[Brian Demers <[e-mail]>]

To follow up, a colleague reached out directly to me and mentioned section
2.4 of the Core RFC https://www.rfc-editor.org/rfc/rfc7643#section-2.4

This mentions that _all_ multivalued attributes have the sub-attributes:
type, primary, value, display, $ref

Is this something that should be added to section 8.7.1?
Is there someplace where we could host official reference copies of the
schema defined in the RFCs? Something like simplecloud.info (I don't know
who owns this site)

On Fri, Jan 6, 2023 at 2:09 PM Brian Demers <[e-mail]> wrote:

> TL;DR - What are the official sub-attributes of "membership" items in the
> Groups schema?
>
> The Groups schema listed in section 8.7.1 lists the possible
> sub-attributes for `members` to be: `value`, `$ref`, and `type`.
> The example in 8.4, contains `value`, `$ref`, and `display`
>
> Section 4.2,  "Group" Resource Schema, only makes reference to `id`,
> `$ref`, and _hints_ at `type`
>
> members
>       A list of members of the Group.  While values MAY be added or
>       removed, sub-attributes of members are "immutable".  The "value"
>       sub-attribute contains the value of an "id" attribute of a SCIM
>       resource, and the "$ref" sub-attribute must be the URI of a SCIM
>       resource such as a "User", or a "Group".  The intention of the
>       "Group" type is to allow the service provider to support nested
>       groups.  Service providers MAY require clients to provide a
>       non-empty value by setting the "required" attribute characteristic
>       of a sub-attribute of the "members" attribute in the "Group"
>       resource schema.
>
>
> NOTE: Section 8.7.1 does state the following:
> > Where permitted, individual values and schema MAY change
>
> If this schema is not complete, is there an _official_ schema in JSON
> that is?
>
>
>