RE: [xri-editors] Relative cross-references

["Dave McAlpin" <dave.mcalpin@epokinc.com>]

Here's one concern about allowing spaces in XRIs. IE provides an
extensibility mechanism for URIs it doesn't natively understand. You can
register a handler and IE will pass control to that handler when it needs to
resolve an identifier. If the user types @example into the navigation bar,
for example, your code can take over and resolve that as an XRI.
Unfortunately, if an identifier contains spaces IE (or at least many
versions of IE) assumes it can't possibly be a URI, skips the registered
handlers and sends the string directly to a search engine for processing.
Maybe this behavior will change when IRIs are more widely deployed, but for
now spaces aren't handled well by the most widely used URI processor.

Dave

> -----Original Message-----
> From: Sakimura, Nat [mailto:n-sakimura@nri.co.jp]
> Sent: Wednesday, November 05, 2003 10:30 PM
> To: Wachob, Gabe; Dave McAlpin; Drummond Reed; Lindelsee, Mike;
> xri-editors@lists.oasis-open.org
> Cc: Veizades, John; Marc LeMaitre; jerry.kindall@epok.net
> Subject: RE: [xri-editors] Relative cross-references
>
>
>
>
> > -----Original Message-----
> > From: Wachob, Gabe [mailto:gwachob@visa.com]
> > Sent: Thursday, November 06, 2003 2:41 PM
> >
> > Good point about CamelCase, Nat! Thats not a very i18n solution.
> >
> > Spaces are of course legal, but get encoded as %20.
>
> After normalization into URI form, right?
>
> >
> > But I think we have concluded that we don't even have to
> > address this issue normatively - its really an issue for the
> > names that get registered under = (for example). In other
> > words, its a namespace definition issue.
> >
>
> Indeed, and that was my understanding. However, in the current draft, in
> Section 2.2.5, Excluded characters are defined, and space is excluded
> normatively in ABNF. I am merely suggesting that perhaps we can drop SP
> from excluded list so that we really do not address to this issue
> normatively.
>
> Nat
>
>
> To unsubscribe from this mailing list (and be removed from the
> roster of the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/xri-editors/members/leave_workg
roup.php.