Re: Boeing XRI Use Cases

On 7/15/08, David Orchard <orchard@pacificspirit.com> wrote:
> Mark,
>
> I believe that you do not need a new URI scheme to extract information from
> URIs.  HTML would have needed to create HTMLFORMSURI: or somesuch to do
> forms in URIs using your example.  I will again bring up URI templates and
> the metadata in URI TAG finding.  I believe that a scheme whereby xris are
> denoted by http:// + some authority that can do XRI resolution (such as
> David Booth's purl.org suggestion) + a specific format for such URIs is
> completely within Web arch.  There's no division of the information space
> and web browsers can do GETs on the URIs without special software.  I'm
> certainly not prepared to lobby the XRI folks any further than this.  If
> they do provide URIs using http:// schemes, I cannae ask them more laddie.

Using hypermedia to enable a publisher to expose a URI's structure is
perfectly Web friendly of course.  And I admit to not reading the
entire resolution spec, but it was this paragraph of 11.2 that set off
alarm bells for me because it doesn't prescribe using any
authoritative information in determining whether an http URI is an
HXRI or not.

"URI processors that recognize XRIs SHOULD interpret the local part of
an HTTP or HTTPS URI (the path segment(s) and optional query segment)
as an XRI provided that: a) it conforms to this ABNF, and b) the first
segment of the path conforms to the xri-authority or iauthority
productions in [XRISyntax]."

If that paragraph is incorrect/incomplete, then I stand corrected.

Mark.
-- 
Mark Baker.  Ottawa, Ontario, CANADA.         http://www.markbaker.ca
Coactus; Web-inspired integration strategies  http://www.coactus.com

Received on Tuesday, 15 July 2008 05:37:59 UTC