OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xri message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [xri] Bracketing Refs [Authority Resolution]

	Could you talk to how this would work with:
A) Trusted resolution - how are the signatures linked in this new
B) Proxy resolution - if a proxy is returning a partial result that ends
with an XRD that contains a redirect, what is the form of the XRDS, for
example, and how does it get added to when further resolution happens
(e.g. if proxy a asks proxy b and proxy b is returning the partial
result, how does proxy a take that result and continue to build it for
proxy a's client).

	And where does the data about "redirects" live in this result...
The redirect data is published in an XRD, but I'm not sure where that
redirect data is in your example. Does XRD-E have the resolution data?
Or does XRD-A have it? 

      Instead of having a separated "RefRes" element, what about having
a way of embedding XRDs in XRDs next to (or as a child of) the
<Resolved>/<Query> element? (fraught with other issues, I'm sure). 


> -----Original Message-----
> From: Steven Churchill [mailto:steven.churchill@xdi.org] 
> Sent: Thursday, January 12, 2006 11:44 PM
> To: xri@lists.oasis-open.org
> Subject: [xri] Bracketing Refs [Authority Resolution]
> This proposes a bracketing scheme for outputting Refs during 
> the authority
> resolution phase. This provides a human and machine readable way to
> negotiate a nested Ref resolution hierarchy.
> <XRDS>
>     <XRD-A /> 
>     <RefRes>
>         <XRD-E />
> 	  <RefRes>
>             <XRD-H />
>     	  </RefRes>
>         <XRD-F />
>         <XRD-G />
>     </RefRes>
>     <XRD-B />    
>     <XRD-C />
>     <RefRes>
>         <XRD-I />
>     </RefRes>
>     <XRD-D />
> </XRDS>
> The <RefRes> element is used to bracket the XRDs necessary to 
> resolve a Ref.
> The <RefRes> element MUST appear between two <XRD> elements. 
> (It would never
> fall at the beginning or end, and two <RefRes> elements would 
> never appear
> together.)
> The final <XRD> in the <RefRes> is that used for the 
> subsegment resolution
> of the <XRD> that follows the <RefRes>. Therefore, in the 
> example above, the
> subsegment resolution XRD chain is:
>     G, B, I, D
> Note that, since the <RefRes> "replaces" the preceding <XRD> from a
> subsegment resolution standpoint, the number of (top-level) 
> XRDs in the
> <XRDS> is always equal to the number of authority subsegments.
> ~ Steve
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all 
> your TCs in OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgr

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]