-
See https://trustoverip.github.io/tswg-did-x509-method-specification/#percent-encoding.
Can we rewrite this in terms of RFC 3986?
-
```
based on RFC 3986
http://www.ietf.org/rfc/rfc3986.txt
```
Original issue reported on code.google.com by `zwetan` on 22 Jan 2009 at 1:53
-
```
based on RFC 3986
http://www.ietf.org/rfc/rfc3986.txt
```
Original issue reported on code.google.com by `zwetan` on 22 Jan 2009 at 1:53
-
```
based on RFC 3986
http://www.ietf.org/rfc/rfc3986.txt
```
Original issue reported on code.google.com by `zwetan` on 22 Jan 2009 at 1:53
-
The spec references RFC-3986 for how to determine the base URI for relative reference resolution. It also has a concept of an "initial Base URI". This concept unnecessarily complicates the model and s…
-
To achieve strict RFC 3986 conformance (specifically, '+' in query strings is a LITERAL '+' and not a placeholder for ' ' as per the W3C's URL recommendations, the following is necessary:
qs.pa…
-
ZnUrl seems to go against RFC 3986, in that it replaces percent-encoded octets for some reserved characters by those characters. Take the following block:
```
[ :url | (ZnUrl fromString: url) asSt…
-
Edited by @hsivonen to put resolution options at the top for folks who come here:
This compilation error is due to a combination of:
1. SQLx unnecessarily turning off the default features of `url`…
-
```
based on RFC 3986
http://www.ietf.org/rfc/rfc3986.txt
```
Original issue reported on code.google.com by `zwetan` on 22 Jan 2009 at 1:53
-
```
based on RFC 3986
http://www.ietf.org/rfc/rfc3986.txt
```
Original issue reported on code.google.com by `zwetan` on 22 Jan 2009 at 1:53