W3C home > Mailing lists > Public > uri@w3.org > February 2004

Re: RFC2396bis - implementation results using revised syntax

From: Mike Brown <mike@skew.org>
Date: Thu, 5 Feb 2004 15:48:12 -0700 (MST)
Message-Id: <200402052248.i15MmCX5052174@chilled.skew.org>
To: uri@w3.org
Cc: gk@ninebynine.org

Graham Klyne wrote:
> Test case:  "http://example.123./aaa/bbb#ccc"
> I'd like to confirm that this is now regarded as a valid URI.  In previous 
> versions of this specification, it was not (according to my interpretation 
> and implementation).

The discussion and resolution can be found in the issues doc:
http://cvs.apache.org/viewcvs.cgi/*checkout*/ietf-uri/rev-2002/issues.html?rev=1.55#038-qualified

You can see there that the productions were changed at your request, so it's
probably safe to assume that the elimination of toplabel was deliberate, in
order to fully accomodate unqualified hostnames. Issue 016 also touches on
this.

If you have any more test cases to share (aside from the ones in the spec),
I'd like to see them, just so I can further verify my own implementation. My
implementation in Python with regular expressions has presented no problems so
far. If anyone wants to see, it's open source:

implementation:
http://cvs.4suite.org/cgi-bin/viewcvs.cgi/~checkout~/4Suite/Ft/Lib/Uri.py?rev=HEAD&content-type=text/plain
(in particular, have a look at the Absolutize, _eliminateDotSegments,
 and _initUriValidationRegex functions)

test suite:
http://cvs.4suite.org/cgi-bin/viewcvs.cgi/~checkout~/4Suite/test/Lib/test_uri.py?rev=HEAD&content-type=text/plain
(this module expects to be imported and run in a custom testing framework,
 but the source and comments should be clear enough for inspection)

-Mike
Received on Thursday, 5 February 2004 17:48:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:07 UTC