-
According to the glTF [URIs](https://github.com/KhronosGroup/glTF/blob/main/specification/2.0/Specification.adoc#28-uris) section:
> Paths with non-ASCII characters MAY be written as-is, with JSON …
-
**This is a tracker issue.** Only discuss things here if they are i18n group internal meta-discussions about the issue. **Contribute to the actual discussion at the following link:**
§ https://gith…
-
> if a DOI URI is used in a context where
an IRI is expected (such as in an RDF file), should any non-ASCII Unicode
graphic characters in the DOI Name be %-encoded? My default reading of the
draft…
-
https://w3c.github.io/miniapp-addressing/
The specification refers to RFC 3986 as a basis for the MiniApp URI Scheme. This reference should be changed to RFC 3987, to allow for using IRIs.
---
…
-
### Current Behavior
With the new BOM Validation, the HTTP 400 response could be improved to more easily pin-point the failing component
For example, this is an API response we have recently rec…
-
Perhaps each of these should be separate issues, but for now:
There are three main things talked about in RFC 3987 which are not currently in the URL standard.
Addressing these should be in the proble…
-
Although this is straight out of the RFC, it is not good enough for proper use.
HEXDIG should include "a"-"f"
ipchar, iunreserved and ucschar should have a "-" before the rule.
The grammar is ambig…
-
The heavy use of "IRI" as terminology in the spec, referencing RFC 3987, raises a number of thorny issues and actually makes JSON-LD out-of-sync with the latest developments at W3C. See https://www.w3…
-
Section 2.8 URIs is unclear.
It does not appear to be possible for an implementation to determine whether a URI has been percent-encoded or written as-is.
> Reserved characters (as defined by [RFC…
-
The [Addressable](https://github.com/sporkmonger/addressable) gem features its own URI parser. There are two main benefits of using Addressable:
– its behaviour is consistent among Ruby implementat…