Minutes:Joint XRI & XDI TC Telecon 10AM PT Thursday 2007-04-05

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

Following are the minutes for a joint unofficial telecon of the XRI and XDI
TCs at:

Date:  Thursday, 05 April 2007 USA
Time:  10:00AM - 12:00PM Pacific Time

ATTENDING

Wil Tan
Marty Schlieff
Steve Churchill
Drummond Reed


AGENDA

1) REMINDER TO REGISTER FOR THE OASIS SYMPOSIUM AND XRI/XDI F2F MEETING

If you are planning on coming and have not registered, please do. See

	http://www.oasis-open.org/events/symposium/2007/index.php 

# DRUMMOND and LAURIE to set up a schedule for telecon times with TC members
who want to dial in. For the time being, please pencil:

 - 1-5PM Wednesday April 18
 - 1-5PM Thursday, April 19 <== This is the most important of the two

# STEVE to review CanonicalID page on wiki and note any outstanding issues
or topics.


2) XRI RESOLUTION 2.O WD 11 ISSUE #37 - SERVICE REFS

We discussed the page at:

	http://wiki.oasis-open.org/xri/XriCd02/ServiceRefs 

It was a very productive discussion that reached the following conclusions:

* The XRDs that result from service refs are essentially the same as any
other XRD in the $auth*res chain. The only difference is that they represent
a step "sideways" to a "substitute" or "replacement" XRD rather than down to
the XRD representing the next authority subsegment. So they conform to all
the rules for HTTPS and SAML trusted resolution.

* Each XRD resulting from a service ref will have an empty query element
relecting the fact that this is not a new query, but a "redirect" from the
last query.

* Based on Steve's and Wil's input, the preferred mechanism for indicating a
service ref is reusing the XRD/Ref element at the service level, i.e.,
XRD/Service/Ref.

* To follow the service ref chain, the target XRD resulting from following
an XRD/Service/Ref element MUST have a ref attribute whose value MUST be the
fully constructed URI from the source XRD/Service/Ref element.

# DRUMMOND to write this up on the wiki page.

We will do a final close on this issue this week so it can be included in
WD11 for review at the f2f meeting.
	

3) XRI SYNTAX 2.1

Steve, Wil, and Drummond continued a discussion of the parse tree examples
at:

	http://wiki.oasis-open.org/xri/XriCd02/ParseTreeExamples

Their general consensus is that the tree is clear and regular, and differs
from the 2.0 tree only with respect to the increased number of types for
literals and xrefs. The key remaining issue is any proposed normalization
rules.

# STEVE and WIL to continue to analyze the tree to see if they discover any
other issues.