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

Square dpath with URI syntax #21

Open
nmushegian opened this issue Mar 7, 2022 · 1 comment
Open

Square dpath with URI syntax #21

nmushegian opened this issue Mar 7, 2022 · 1 comment

Comments

@nmushegian
Copy link
Member

nmushegian commented Mar 7, 2022

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!

sub-delims = "!" / "$" / "&" / "'" / "(" / ")"
/ "*" / "+" / "," / ";" / "="

BUT! That charset does not contain .

Pull quote

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.

@nmushegian
Copy link
Member Author

. is part of unreserved

  unreserved  = ALPHA / DIGIT / "-" / "." / "_" / "~"

that makes more sense

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

No branches or pull requests

1 participant