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
This specification does not mandate a particular registered name
lookup technology and therefore does not restrict the syntax of reg-
name beyond what is necessary for interoperability. Instead, it
delegates the issue of registered name syntax conformance to the
operating system of each application performing URI resolution, and
that operating system decides what it will allow for the purpose of
host identification. A URI resolution implementation might use DNS,
host tables, yellow pages, NetInfo, WINS, or any other system for
lookup of registered names. However, a globally scoped naming
system, such as DNS fully qualified domain names, is necessary for
URIs intended to have global scope. URI producers should use names
that conform to the DNS syntax, even when use of DNS is not
immediately apparent, and should limit these names to no more than
255 characters in length.
The text was updated successfully, but these errors were encountered:
https://datatracker.ietf.org/doc/html/rfc3986/#section-3
Current dpath is valid “host” in URI
dmap://<dpath>
This is actually correct despite the fact that the user-defined hierarchies will live in this area
This is pretty nice, we get the whole “subreg” charset for runes which is pretty big!
BUT! That charset does not contain
.
Pull quote
The text was updated successfully, but these errors were encountered: