1. when the relative uri is empty > an exception is thrown (i think it
is a good idea to avoid empty uris)
We should probably handle this one. Looks like parseUriReference()
will need to be changed to handle an empty URI.
2. when there are more relative path ".." segments than hierarchical
levels in the base uri's path (the ".." expression must not change the
authority component of a uri). There are two options here:
base: http://a/b/c/d;p?q
relative: ../../../g
option1: http://a/../g
option2: http://a/g (compensating author errors)
Option 2 sounds good here.
Mike
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
