You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's 2023, and unicode in general and utf-8 in particular are now well-supported. Is there any reason not accept an unencoded IRI(-reference) anywhere a URI(-reference) is currently allowed? While all IRIs can be encoded to URIs, they are not readable in such forms, making for poor UX. Note that JSON Schema already expanded to support IRIs for their next version.
A quick search for "IRI" in open issues and discussions did not turn up anything one way or another.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
It's 2023, and unicode in general and utf-8 in particular are now well-supported. Is there any reason not accept an unencoded IRI(-reference) anywhere a URI(-reference) is currently allowed? While all IRIs can be encoded to URIs, they are not readable in such forms, making for poor UX. Note that JSON Schema already expanded to support IRIs for their next version.
A quick search for "IRI" in open issues and discussions did not turn up anything one way or another.
Beta Was this translation helpful? Give feedback.
All reactions