RFC 7643, "System for Cross-domain Identity Management: Core Schema", September 2015

Note: This RFC has been updated by RFC 9865

Errata ID: 8362
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Matthias Winter
Date Reported: 2025-03-31
Rejected by: Deb Cooley
Date Rejected: 2025-10-28

Section 6 says:

   id
      The resource type's server unique id.  This is often the same
      value as the "name" attribute.  OPTIONAL.

   name
      The resource type name.  When applicable, service providers MUST
      specify the name, e.g., "User" or "Group".  This name is
      referenced by the "meta.resourceType" attribute in all resources.
      REQUIRED.

It should say:

   id
      The resource type's server unique id.  This is often the same
      value as the "name" attribute.  OPTIONAL.

   name
      The resource type name.  When applicable, service providers MUST
      specify the name, e.g., "User" or "Group".  This name is
      referenced by the "meta.resourceType" attribute in all resources.
      REQUIRED. The resource type name must be unique within the server.

Notes:

ResourceTypes are not referenced by their "id" in the meta.resourceType attribute, but by their "name".
Section 3.3 states:
In order to determine which URI value in the "schemas" attribute is
the base schema and which is an extended schema for any given
resource, the resource's "resourceType" attribute value MAY be used
to retrieve the resource's "ResourceType" schema (see Section 6).

This would not work if there were numerous ResourceType resources with the same name. The name must therefore be unique within the server.

This also applies to the schema definition in section 8.7.2 where it should be defined with "uniqueness": "server" instead of "none".
--VERIFIER NOTES--
Resource types are referenced by their ID. ALWAYS.

It often occurs that name and id are the same. The scenario you describe would not occur because it would point by ID.

Report New Errata