See RFC 3986 (published in 2005) at
<
ftp://ftp.rfc-editor.org/in-notes/rfc3986.txt>. Scroll to near the
bottom of the very long page, to Appendix C. I quote part of that RFC:
> Using <> angle brackets around each URI is especially recommended as
> a delimiting style for a reference that contains embedded whitespace.
> For robustness, software that accepts user-typed URI should attempt
> to recognize and strip both delimiters and embedded whitespace.
The first paragraph of Appendix C gives the rationale:
> URIs are often transmitted through formats that do not provide a
> clear context for their interpretation. For example, there are many
> occasions when a URI is included in plain text; examples include text
> sent in email, USENET news, and on printed 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.
Any E-mail application is broken if it fails to comply with RFC 3986 by
recognizing that the <> brackets are external to and not part of a
bracketed URI. RFC 1738 (published in 1994) was the predecessor to RFC
3986 and contained the same specification for bracketing URIs. Thus,
developers have had 18 years to bring their applications into
compliance. Eudora Lite complied with the bracketing specification in
RFC 1738 at least 15 years ago.
By the way, RFC 1738 and RFC 3986 were broth written by Tim Berners-Lee,
recognized by many as "the father of the World Wide Web" and currently
the head of the W3C (the source of the authoritative specifications for
XML, HTML, CSS, etc).
--
David E. Ross
<
http://www.rossde.com/>
Anyone who thinks government owns a monopoly on inefficient, obstructive
bureaucracy has obviously never worked for a large corporation.
© 1997 by David E. Ross