Re: [Uri-review] Request for review

[Timothy Mcsweeney <[e-mail]>]

Hi Dan, 

For the browser example, it is going to leave the client as 'drop#fg234' but come back to the client as 'fg234.dropexample.com'. 

Looking at the second sentence of section 2.2 of rfc3986 it give three choices for defining delimiters:

by using general syntax

by each scheme-specific syntax

by the implementation-specific syntax of a URI's derefrencing algorithm.

The 'drop' scheme uses the last one.  I was thinking of a way to show this being done with http but didn't thing anyone really wanted to see that.

Tim

On May 23, 2020 at 7:31 PM "Daniel R. Tobias" < [e-mail]> wrote:

On 22 May 2020 at 17:29, Timothy Mcsweeney wrote:

The second draft of the 'drop' URI scheme is available and can be

found here < 

https://datatracker.ietf.org/doc/draft-mcsweeney-drop-scheme/" rel="nofollow">" rel="noopener" target="_blank" data-mce-href="https://datatracker.ietf.org/doc/draft-mcsweeney-drop-scheme/>">https://datatracker.ietf.org/doc/draft-mcsweeney-drop-scheme/>.  Thank

you. 

This doesn't seem to resolve any of the issues people have raised; it

still omits the mandatory colon after the scheme, and puts its main

content, used for resource resolution and retrieval, in a fragment

identifier, which is intended for client-specific post-processing

after a document is retrieved.

--

== Dan ==

Dan's Mail Format Site: http://mailformat.dan.info/" rel="noopener nofollow" target="_blank">http://mailformat.dan.info/

Dan's Web Tips: http://webtips.dan.info/" rel="noopener nofollow" target="_blank">http://webtips.dan.info/

Dan's Domain Site: http://domains.dan.info/" rel="noopener nofollow" target="_blank">http://domains.dan.info/

_______________________________________________

Uri-review mailing list

[e-mail]

https://www.ietf.org/mailman/listinfo/uri-review" rel="noopener nofollow" target="_blank">https://www.ietf.org/mailman/listinfo/uri-review