> Date: Fri, 27 Feb 2004 17:31:05 -0500
> From: "LeVan,Ralph" <[log in to unmask]>
> > I'd argue that including the leading slash is safer,
> > not least as most web servers and web browsers will
> > interpret
> > http://www.lib.ox.ac.uk:8080//test as equivalent to
> > http://www.lib.ox.ac.uk/test
> > i.e. it is more likely that omitting the slash will
> > break an unsuspecting client than vice versa.
> I think we need a rule here and I say it should be without the
> slash. The construction rule is that a slash will be inserted and
> clients should be aware of it. Your java test just tells me that
> the URL constructor is in error.
> This is another one that I won't obsess about. If you all decide
> that it's better with slashes, I won't complain. But please, let's
> document a rule one way on another and I'll test for compliance.
It _is_ documented:
fifth paragraph of the section:
The database element should contain the name of the
Z39.50 database which the record describes. For other
protocols such as SRW and SRU, this element may be
used to contain the remainder of the URL to the server
without any preceeding '/' character.
/o ) \/ Mike Taylor <[log in to unmask]> http://www.miketaylor.org.uk
)_v__/\ ``SAY IT WITH CHEESE'' -- sign outside Dimock, South Dakota.
Listen to my wife's new CD of kids' music, _Child's Play_, at