RE: [xri] XRI Resolution 2.0 Draft 10 comments

["Chasen, Les" <les.chasen@neustar.biz>]

Title: RE: [xri] XRI Resolution 2.0 Draft 10 comments

Raj, Thanks for submitting your questions to the TC.

One other thing we discussed, that may be a common confusion point, is the difference between the HTTP proxy resolver and the client resolver.  My answer is that a HTTP proxy resolver uses the client resolver.  The HTTP proxy resovler is a boot strap mechanism to allow non-XRI aware applications to use XRIs.  Its job is to get a SEP URI from the client resolver and perform a HTTP redirect.

Thanks

Les

 

I-Name:  =les.chasen 

 

_____________________________________________
From: Mohit Raj [mailto:mraj@amsoft.net]
Sent: Friday, January 20, 2006 8:02 AM
To: xri@lists.oasis-open.org
Subject: [xri] XRI Resolution 2.0 Draft 10 comments

Hi all,

My questions regarding the newly submitted draft are below:

1. Section 4.2.2 - Line 511 states that "Parameters specified in this manner SHOULD take precedence over the same parameters provided via any other interface". Of the 3 optional resolution parameters, if only 1 is provided in the HXRI, the values of the rest should be considered as null or other interfaces (such as HTTP header) should be considered?

2. Section 5.6 - Flowchart suggests that the value of xrd:XRD/xrd:Service/ xrd:Path should be equal to either Path OR "(" Path ")", in order for the service to be selected. Whereas the normative rules for the algorithm, pt. 4 says that the selection of a service should be *repeated* with the value of path = "(" Path ")". So, is there an EQUALITY or a PRIORITY relation between the path values distinguished by parenthesis?

Thanks

Mohit Raj << File: ATT968348.txt >>