XRI Resolution 2.0 status/errata/next steps

["Drummond Reed" <drummond.reed@cordance.net>]

XRI TC Members and XRI Resolution 2.0 Editors:

Several TC members have started sending me questions/notes about Working
Draft 10 Editor's Draft 05 (see link below). At this point in its
development, please do not hesistate to send ANY feedback/comment/question
directly to the list, as we are close enough to being complete that I'd
rather err on the side of having too much list traffic than having
discussions off-list.

Secondly, please note one erratum I realized after publishing ED 05. On
lines 933 to 935 of the PDF clean version (see link below), it currently
says:

2. If an xrd:Type, xrd:MediaType, or xrd:Path element is omitted, it MUST be
considered equivalent to including an instance of the respective element
with an @xrd:match attribute value of "any".

That is incorrect. The value should be "default". The following example
illustrates why.

<Service>
	<Type match="null" />
	<Path>bar</Path>
	<URI>http://one.example.com</URI>
</Service>
<Service>
	<Type match="null" />
	<URI>http://two.example.com</URI>
</Service>

If these two service endpoints were in the XRD for xri://@foo, and the
implied @xrd:match attribute value of a missing <Path> attribute was "any",
then BOTH service endpoints would match the XRI "xri://@foo/bar" because the
first would explicitly match the path but the second would match the path by
virtue of there being no <Path> element.

The desired behavior is that only the first service endpoint matches because
there is an explicit match whereas the second is only a default or
"catchall" match that is secondary to any explicit match. This is the
purpose of the "default" value of the @xrd:match attribute. 

With this correction, a missing Type/MediaType/Path element would be the
equivalent of including the respective element with the @xrd:match attribute
value of "default", i.e., the example above would be equivalent to the
following:

<Service>
	<Type match="null" />
	<Path>bar</Path>
	<URI>http://one.example.com</URI>
</Service>
<Service>
	<Type match="null" />
	<Path match="default" />
	<URI>http://two.example.com</URI>
</Service>

Lastly, the action item for all XRI Resolution 2.0 editors and implementers
is to review this draft as soon as you can and send any
feedback/questions/issues to the list. The goal is to work through any and
all remaining issues by the close of this week's XRI TC call (4PM Pacific
time on Thursday, Friday morning Asia) we we can publish the long-awaited
stable implementation draft of Working Draft 10 on Friday.

=Drummond 

-----Original Message-----
From: drummond.reed@cordance.net [mailto:drummond.reed@cordance.net] 
Sent: Sunday, February 19, 2006 12:57 AM
To: xri@lists.oasis-open.org
Subject: [xri] Groups - XRI Resolution 2.0 Working Draft 10 ED 05 (PDF
clean) (xri-resolution-v2.0-wd-10-ed-05-clean.pdf) uploaded

PDF of clean version.

 -- Mr Drummond Reed

The document named XRI Resolution 2.0 Working Draft 10 ED 05 (PDF clean)
(xri-resolution-v2.0-wd-10-ed-05-clean.pdf) has been submitted by Mr
Drummond Reed to the OASIS Extensible Resource Identifier (XRI) TC document
repository.

Document Description:
PDF version of XRI Resolution 2.0 Working Draft 10 Editor's Draft 05
(clean)

View Document Details:
http://www.oasis-open.org/apps/org/workgroup/xri/document.php?document_id=16
762

Download Document:  
http://www.oasis-open.org/apps/org/workgroup/xri/download.php/16762/xri-reso
lution-v2.0-wd-10-ed-05-clean.pdf


PLEASE NOTE:  If the above links do not work for you, your email application
may be breaking the link into two pieces.  You may be able to copy and paste
the entire link address into the address field of your web browser.

-OASIS Open Administration