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

Nominally reference the IRI specification in documentation #2467

Merged
merged 1 commit into from
Oct 2, 2023

Conversation

nvmkuruc
Copy link
Collaborator

@nvmkuruc nvmkuruc commented Jun 1, 2023

Description of Change(s)

The URI specification nominally referenced throughout the Ar documentation restricts the character set to ASCII characters. This update to documentation clarifies that--

  • Resolvers registered via uriSchemes may also accept UTF-8 encoded IRIs (a unicode supporting resource identifier specification)
  • Resolvers working with protocols that only accept URIs may (but are not required to) support IRIs encoded in layers and handle percent encoding idempotently at the resolver level
  • USD does not validate URI or IRI paths beyond what's needed to dispatch via a resource identifier's scheme component. Resolvers handle their own parsing, validation, and normalization of asset paths.

This change also converts the invalid my_scheme URI/IRI scheme to my-scheme.

Fixes Issue(s)

  • I have verified that all unit tests pass with the proposed changes
  • I have submitted a signed Contributor License Agreement

@sunyab
Copy link
Contributor

sunyab commented Jun 2, 2023

Filed as internal issue #USD-8385

@pixar-oss pixar-oss merged commit ea5d442 into PixarAnimationStudios:dev Oct 2, 2023
@nvmkuruc nvmkuruc deleted the aririreference branch December 29, 2023 03:15
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.

3 participants