From W3C Wiki

Various developers have created implementations and test suites for the URL, URI and IRI specifications, and have discussed them on the uri and [htp://lists.w3.org/Archives/Public/public-iri/ public-iri] and related MailingLists:

URI tests

IRI tests

These tests were explicitly oriented toward "IRI" testing, although the line between URI and IRI testing can be vague (some of the URI tests were URL tests)SSS:

Moving tests to W3C testing infrastructure

LarryMasinter Through "Test the Web Forward" and other initiatives, I would like to get URL/URI/IRI testing integrated into the overall browser test infrastructure. See W3C Testing Interest Group

Systems to test

Of course, it is important to test how browsers behave to make sure the browsers "match reality". However, in addition, URIs and IRIs are also supported by important elements of the infrastructure: proxies and web servers. So testing should extend to those elements. Other systems that use URIs that are not browsers include Atom (for news feeds), and XMPP (for instant messaging). Testing those elements will be problematic without a broader test infrastructure.

Do we need to find other systems, e.g., those that use 'snmp' scheme?

Do we need to test IRI handling through registerProtocolHandler.

Testing Fragment Identifier usage

For a variety of MIME types, browsers need to pass through fragment identifiers, e.g., page numbers for PDF to the PDF reader.

Additional (older) information

swap/uripath.py and Uri.py also contain functions for deriving a relative URI reference from an origin URI and target URI.

Note also Error handling in URIs discussion and URL encoding tests by Ian Hickson for HTML 5.

(LinkMe: notes from python conference where DanConnolly talked with Guido about urlparse.py in the python std lib...)

Nearby... UriSchemes, W3C URI Interest Group.

earlier: URI spec review: URI specification (RFC 2396 revision), some review notes 29May