Re: SGV-sgv, ...not svg? sure?

["James K. Lowden" <jklowden speakeasy org>]

James Henstridge wrote:

> As for whether case should matter for xml namespace URIs, the current code
> for loading shape files uses the standard libxml function to get a handle
> for the namespace.  As libxml doesn't perform case folding here, I doubt
> that URIs are supposed to be case insensitive.  If you think I am wrong
> about this, you should tell Daniel Veillard about it as it would be a bug
> in libxml.

James,

Making me work, eh?  :-)

The URI spec is governed by RFC 2396, quoted below, which I found at
http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc2396.html.  Sad to say, it says
only "should".

Setting aside the question of how you could be "wrong" without making an
assertion, I followed your suggestion, thank you, and raised the topic with
Daniel Veillard.  Bug 57156 posted.

--jkl

>From RFC 2396:

3.1 Scheme Component

      Just as there are many different methods of access to resources, there
are a variety of schemes for identifying such resources. The URI syntax
consists of a sequence of components separated by reserved characters, with
the first component defining the semantics for the remainder of the URI
string.

      Scheme names consist of a sequence of characters beginning with a lower
case letter and followed by any combination of lower case letters, digits,
plus ("+"), period ("."), or hyphen ("-"). For resiliency, programs
interpreting URI should treat upper case letters as equivalent to lower case
in scheme names (e.g., allow "HTTP" as well as "http").

[...]

6 URI Normalization and Equivalence

      In many cases, different URI strings may actually identify the
identical resource. For example, the host names used in URL are actually case
insensitive, and the URL <http://www.XEROX.com> is equivalent to
<http://www.xerox.com>. In general, the rules for equivalence and definition
of a normal form, if any, are scheme dependent. When a scheme uses elements
of the common syntax, it will also use the common syntax equivalence rules,
namely that the scheme and hostname are case insensitive and a URL with an
explicit ":port", where the port is the default for the scheme, is equivalent
to one where the port is elided.