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

Why iota: and not iota://? #8

Open
joakim opened this issue Jun 2, 2018 · 0 comments
Open

Why iota: and not iota://? #8

joakim opened this issue Jun 2, 2018 · 0 comments

Comments

@joakim
Copy link
Owner

joakim commented Jun 2, 2018

Just to clarify why I believe iota: is the correct choice for this URI scheme.

From RFC 7595 (URI Scheme Guidelines), section 3.2:

   Schemes SHOULD avoid improper use of "//".  The use of double slashes
   in the first part of a URI is not a stylistic indicator that what
   follows is a URI: double slashes are intended for use ONLY when the
   syntax of the <scheme-specific-part> contains a hierarchical
   structure.  In URIs from such schemes, the use of double slashes
   indicates that what follows is the top hierarchical element for a
   naming authority (Section 3.2 of RFC 3986 has more details).  Schemes
   that do not contain a conformant hierarchical structure in their
   <scheme-specific-part> SHOULD NOT use double slashes following the
   "<scheme>:" string.

See also the discussion in #5 and discussions in the #trinity channel on Discord.

@joakim joakim changed the title Why iota: without double-slash? Why iota: and not iota://? Jun 2, 2018
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