I don't think this is correct. Any url can make use of the # directive.
It just tells a browser to go to a specific part of a document instead of
to the beginning. I don't know of any browsers that actually 'generate'
these internally.
>The question mark would seem better suited to search the list of contents,
>e.g. http://www/foo/bar.tar.Z?*.c
>would return
>
>blech.c erk.c glug.c
>
>A related question is whether I can have slashes in the test following
>the # or ?. e.g. for a tar file with relative filenames
>
>http://www/foo/bar.tar.Z#./blech.c
>
>would be common. Since slashes are meaningful to an http: URL, and the
>browser can interpret them, would this cause confusion?
The only problem with using ./ in the path would be that the browser
is likely to interpret it as a relative pathname. For example,
http://www/foo/bar.tar.Z#./blech.c would more than likely be translated
into http://www/foo/bar.tar.Z#/foo/blech.c by a browser.
It would be fairly easy to tell the replacing function not to replace
any . or .. after a # sign though. (I haven't tried this with mosaic or
lynx yet, but I know that my emacs browser would replace the ./ with nothing
so the url above would be http://www/foo/bar.tar.Z#blech.c)
-Bill Perry