Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

schema ids must be URIs #81

Merged
merged 1 commit into from
Oct 14, 2024
Merged

schema ids must be URIs #81

merged 1 commit into from
Oct 14, 2024

Conversation

azmeuk
Copy link
Contributor

@azmeuk azmeuk commented Oct 14, 2024

as defined by RFC763 §7

id
The unique URI of the schema. When applicable, service providers
MUST specify the URI, e.g.,
"urn:ietf:params:scim:schemas:core:2.0:User". Unlike most other
schemas, which use some sort of Globally Unique Identifier (GUID)
for the "id", the schema "id" is a URI so that it can be
registered and is portable between different service providers and
clients. REQUIRED.

fix #26

@azmeuk azmeuk force-pushed the issue-26-schema-id-uris branch 2 times, most recently from 97f8069 to 91858a0 Compare October 14, 2024 17:22
as defined by RFC763 §7

   id
      The unique URI of the schema.  When applicable, service providers
      MUST specify the URI, e.g.,
      "urn:ietf:params:scim:schemas:core:2.0:User".  Unlike most other
      schemas, which use some sort of Globally Unique Identifier (GUID)
      for the "id", the schema "id" is a URI so that it can be
      registered and is portable between different service providers and
      clients.  REQUIRED.
@azmeuk azmeuk force-pushed the issue-26-schema-id-uris branch from 91858a0 to 21b907b Compare October 14, 2024 17:24
@azmeuk azmeuk merged commit 5f41c7b into main Oct 14, 2024
16 of 20 checks passed
@azmeuk azmeuk deleted the issue-26-schema-id-uris branch October 14, 2024 19:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Check that the Schema ids are URIs
1 participant