Re: Namespaces

>       * The algorithm tries to find the longest NCName at the end
>       * of the uri, not immediately preceeded by the first colon
>       * in the string.

Thanks a lot!

Incidently, is there any good reason to not create resources such as
http://foo.com/bar/10 which can't be split? I happen to have a lot of
resources that already have numeric identifiers which people are
familiar with, so a natural solution would seem to be to specify an
http://foo.com/bar/ as xml:base and then describe resources using
rdf:about="10", for example. But if this is likely to cause problems
with tools, I'd consider using some prefix for the numbers. (Seems to
work fine with Jena, as far as I can tell.)