Jay Garcia wrote:
> Phillip M. Jones, C.E.T. wrote:
>
>
>><snews://secnews.netscape.com/netscape/netscape6/windows>
>><snews://secnews.netscape.com/netscape/netscape6/macintosh>
>><snews://secnews.netscape.com/netscape/netscape6/unix>
>>
>
>
> Curious ...
>
>
> Dave posted the same URL's basically but didn't include them in < > like
> you did. Why do you do that? I've asked this same question many times
> with no satisfactory responses. I also note that you do not enclose the
> URL's in your sig with < > ... ???
>
> I notice no ill effects in any posts with or without the < > ....
>
>
Well, in fact there is a recommendation from The Internet Society,
dating back to ancient 1998, to do exactly this. Below is the Appendix E
of RFC 2396, quoted in full.
Berners-Lee, et. al. Standards Track [Page 33]
RFC 2396 URI Generic Syntax August 1998
E. Recommendations for Delimiting URI in Context
URI are often transmitted through formats that do not provide a clear
context for their interpretation. For example, there are many
occasions when URI are included in plain text; examples include text
sent in electronic mail, USENET news messages, and, most importantly,
printed on paper. In such cases, it is important to be able to
delimit the URI from the rest of the text, and in particular from
punctuation marks that might be mistaken for part of the URI.
In practice, URI are delimited in a variety of ways, but usually
within double-quotes "http://test.com/";, angle brackets
<http://test.com/>, or just using whitespace
http://test.com/
These wrappers do not form part of the URI.
In the case where a fragment identifier is associated with a URI
reference, the fragment would be placed within the brackets as well
(separated from the URI with a "#" character).
In some cases, extra whitespace (spaces, linebreaks, tabs, etc.) may
need to be added to break long URI across lines. The whitespace
should be ignored when extracting the URI.
No whitespace should be introduced after a hyphen ("-") character.
Because some typesetters and printers may (erroneously) introduce a
hyphen at the end of line when breaking a line, the interpreter of a
URI containing a line break immediately after a hyphen should ignore
all unescaped whitespace around the line break, and should be aware
that the hyphen may or may not actually be part of the URI.
Using <> angle brackets around each URI is especially recommended as
a delimiting style for URI that contain whitespace.
The prefix "URL:" (with or without a trailing space) was recommended
as a way to used to help distinguish a URL from other bracketed
designators, although this is not common in practice.
For robustness, software that accepts user-typed URI should attempt
to recognize and strip both delimiters and embedded whitespace.
For example, the text:
Yes, Jim, I found it under "http://www.w3.org/Addressing/";,
but you can probably pick it up from <ftp://ds.internic.
net/rfc/>. Note the warning in <http://www.ics.uci.edu/pub/
ietf/uri/historical.html#WARNING>.
contains the URI references
http://www.w3.org/Addressing/
ftp://ds.internic.net/rfc/
http://www.ics.uci.edu/pub/ietf/uri/historical.html#WARNING
--
/M.v.h. Lars A. >>>*P*M*<<<
Check the site at <http://members01.chello.se/peemm>
