[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Increased complexity in resolver.
(Please refer to increased-complexity-in-authority-graph.doc. This is the same one I sent earlier.) So the resolver is walking across the top-level subsegments. It encounters a global xref, so it duly invokes the authority resolution service (of the previous subsegment). It gets back an XRD. Now the resolver needs to evaluate the type of the next subsegment -- if it's another global xref then it can continue walking. Else it has to error out. I would sure hate to see that type of logic in the resolution spec. ~ Steve -----Original Message----- From: Steven Churchill [mailto:steven.churchill@xdi.org] Sent: Wednesday, April 25, 2007 3:33 PM To: 'xri@lists.oasis-open.org' Subject: FW: [xri] Flat structure for local delegation within global xrefs I think I've managed to confused everyone (again) by sending the wrong document. The attachment increased-complexity-in-authority-graph.doc summarizes my discussion with Drummond yesterday. For one thing, I fear that we've redefined the meaning of the term "XRI synonym". In the diagram you will note that when adding the localID "+west", @ootao*west is (still) a synonym for @ootao+west (they resolve to the same XRD), but @ootao*west*steve would no longer be a synonym for @ootao+west*steve. The other attachment (increased-complexity-in-authority-graph-flatness.doc) talks about the flat structure for local delegation within global xrefs. ~ Steve ________________________________________ From: Steven Churchill [mailto:steven.churchill@xdi.org] Sent: Wednesday, April 25, 2007 3:22 PM To: xri@lists.oasis-open.org Subject: [xri] Flat structure for local delegation within global xrefs (Blech.) Please see attached. ~ Steve
increased-complexiity-in-authority-graph.doc
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]