[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xri] Question regarding XRI 3.0 resolution where a redirect isdesired
Part of the problem is I don't get what you think you are achieving by having an intermediate ref to =Bill.Barnhill@communitivity. If the authority =Bill.Barnhill wants to use the CID and services that are pointed to by @communitivity=Bill.Barnhill then you ref it directly. If you want to use the CID from =Bill.Barnhill with the services described in @communitivity=Bill.Barnhill you do a redirect. The concept is the same between XRI 2 and 3 but the syntax of the XRD is different. You can also ref individual services to different XRDs if you like. John B. On 3-Jul-09, at 12:38 PM, Barnhill, William [USA] wrote: > > Hmm. Ok, that helps but still some questinos..inline if I can.. > ________________________________________ > From: John Bradley [jbradley@mac.com] > Sent: Friday, July 03, 2009 12:22 PM > To: Barnhill, William [USA] > Cc: xri@lists.oasis-open.org > Subject: Re: [xri] Question regarding XRI 3.0 resolution where a > redirect is desired > > I think you are confusing some XDI ideas that don't exist in XRI. > > XRI resolution returns a XRD or a subset of the XRD if you are doing > service selection. > > =Bill.Barnhill@communitivity is a community root authority > administered by =Bill.Barnhill and is only an unverified inference > that it somehow relates to @communitivity. > > That is what some people object to about XRI 3.0 syntax. > > *bill*; Yeah I remember that whole discussion now from the face to > face on. > > if there is a @communitivity authority it needs to create an authority > service that can serve the XRD for its child nodes like =Bill.Barnhill > Again that node has no direct relation to the root =Bill.Barnhill. > Anyone can create a entry in there a community directory for > =Bill.Barnhill > > You can ref or redirect in the authority segment but not in the path. > The Path is part of service selection. > > *bill*:That's ok, I had expected to be doing that in the authority > segment only anyway > > So yes you could have a ref from =Bill.Barnhill to > =Bill.Barnhill@communitivity to @communitivity=Bill.Barnhill and > perform the service selection for +blog on the final XRD. > > Refs change the subject and redirects don't in XRI 2.0 so they are not > the same. > > *bill*: What about in XRI 2.0, or is that from XRI 2.0 on, incl 3.0? > > *bill*: Also, could I not do a redirect from =Bill.Barnhill to > =Bill.Barnhill@communitivity and then to > @communitivity=Bill.Barnhill? I realize that in XRI there is no > implied relationship but there's no exclusion of a relationship > either (AFAIK), so a layer on top of XRI could add meaning there but > would have to understand that only another such layer on top of XRI > would understand it, correct? > > *bill*: Also, is it explicitly required that resolution from one > side of a redirect be the same URI scheme and associated resolution > binding as the URI scheme and binding on the other side of the > redirect? > > Remember in XRI you are resolving the XRD or a service in the XRI not > a data value as you might in XDI. > > John B. > > On 3-Jul-09, at 9:32 AM, Barnhill, William [USA] wrote: > >> >> Thanks John, that does help but I still have a few questions. >> Though I know about the left to right my thought is that some >> individual, say =Bill.Barnhill, is delegating their data to >> @communitivity so =Bill.Barnhill/+blog resolves to what >> =Bill.Barnhill@communitivity/+blog resolves to. This will only work >> for my use if XRI resolution redirects are referer aware. Is there >> any mechanism to pass the source a a redirect in resolution? If >> not, was that considered and rejected or didn't come up until now? >> Either way I'd like to know thoughts on it. The idea of being able >> to tell the previously resolved subsegment during resolution and >> having resolution be able to resolve differently depending on that >> info seems like a powerful ability not just limited to my use case. >> >> I could have it redirect to directly to >> @Communitivity=Bill.Barnhill/+blog but I'd really like to be able to >> redirect first to =Bill.Barnhill@communitivity/+blog and then if >> desired redirect to @Communitivity=Bill.Barnhill/+blog. >> >> Thanks, >> =Bill.Barnhill >> >> >> ________________________________________ >> From: John Bradley [jbradley@mac.com] >> Sent: Thursday, July 02, 2009 7:49 PM >> To: Barnhill, William [USA] >> Cc: xri@lists.oasis-open.org >> Subject: Re: [xri] Question regarding XRI 3.0 resolution where a >> redirect is desired >> >> Bill XRI are left to right so I think you mean redirect to >> @communitivity=Bill.Barnhill/+blog >> >> The / indicates the start of the path and is used for service >> selection not authority resolution. >> >> So from an XRI resolution point of view. >> =Bill.Barnhill/+blog is a one subsegment XRI with a path of >> +blog it is the SEP of your blog in the =Bill.Barnhill XRD >> =Bill.Barnhill+blog is a two subsegment XRI with no path It >> is >> the XRD of your blog >> @communitivity=Bill.Barnhill/+blog s a two subsegment XRI with a >> path of +blog, @communitivity has an authority service that >> resolves >> =Bill.Barnhill that XRD is searched for a +blog service. >> >> Don't know if that helps. >> >> John B. >> On 2-Jul-09, at 7:25 PM, Barnhill, William [USA] wrote: >> >>> >>> Apologies to the list, am resending due to incorrect subject. >>> >>> I have a question on XRD that I'd appreciate any help on. I was >>> trying to figure out the resolution steps with XRI 3.0 for the use >>> case where say I have an XRI =Bill.Barnhill/+blog that redirects to >>> where data actually is =Bill.Barnhill@communitivity/+blog? >>> >>> Also would this be typically represented as =Bill.Barnhill+blog >>> rather than =Bill.Barnhill/+blog? >>> >>> Thanks, >>> Bill >>> ________________________________________ >>> From: Barnhill, William [USA] [barnhill_william@bah.com] >>> Sent: Thursday, July 02, 2009 4:54 PM >>> To: Mary McRae; xri@lists.oasis-open.org >>> Subject: RE: [xri] Fwd: Mary: SVN for XRI TC? >>> >>> Hi Mary, I just checked and we don't have an XDI SVN repo yet..could >>> we get that as well? >>> >>> Thanks, >>> Bill >>> ________________________________________ >>> From: Mary McRae [mary.mcrae@oasis-open.org] >>> Sent: Tuesday, May 12, 2009 1:52 PM >>> To: xri@lists.oasis-open.org >>> Subject: [xri] Fwd: Mary: SVN for XRI TC? >>> >>> An SVN area has been created for the XRI TC. It is tied into Kavi >>> authentication, meaning anyone who is a TC member has write access; >>> the rest of the world (incuding TC observers) are read-only. >>> http://tools.oasis-open.org/version-control/browse/wsvn/xri/?sc=0 >>> >>> There are some rules regarding its use posted here: >>> http://tools.oasis-open.org/ >>> >>> most importantly, please remember the following: >>> >>> * At least once a month (unless no work has been done), and prior >>> to each TC meeting at which one or more documents will be discussed, >>> a Working Draft of any/all documents must be uploaded to the TC >>> document repository, properly identified according to the Naming >>> Guidelines (links to the non-Kavi system are insufficient) >>> * All TC member reviews and ballots must be based on a Working >>> Draft as posted to the TC document repository (links to the non-Kavi >>> system are insufficient) >>> >>> Caveat: I am not an SVN expert; I hardly remember what SVN stands >>> for. We are not providing 'help'. You can ask me questions but I >>> won't be able to answer them. >>> >>> Regards, >>> >>> Mary >>> >>> >>> Mary P McRae >>> Director, Standards Development >>> Technical Committee Administrator >>> OASIS: Advancing open standards for the information society >>> email: mary.mcrae@oasis-open.org<mailto:mary.mcrae@oasis-open.org> >>> web: www.oasis-open.org<http://www.oasis-open.org> >>> twitter: fiberartisan #oasisopen >>> phone: 1.603.232.9090 >>> >>> Standards are like parachutes: they work best when they're open. >>> >>> >>> >>> >>> >>> >>> >>> >>> Begin forwarded message: >>> >>> From: Neil Joseph Schelly <neil.schelly@oasis-open.org<mailto:neil.schelly@oasis-open.org >>>>> >>> Date: May 12, 2009 1:32:30 PM EDT >>> To: Mary McRae <mary.mcrae@oasis-open.org<mailto:mary.mcrae@oasis-open.org >>>>> >>> Subject: Re: Fwd: Mary: SVN for XRI TC? >>> >>> Done. >>> -N >>> >>> On Tuesday 12 May 2009 12:04:14 pm you wrote: >>> Hi Neil, >>> >>> Please set up SVN for XRI. >>> >>> Thanks! >>> >>> Mary >>> >>> Begin forwarded message: >>> From: "Drummond Reed" <drummond.reed@cordance.net<mailto:drummond.reed@cordance.net >>>>> >>> Date: May 12, 2009 2:25:19 AM EDT >>> To: <mary.mcrae@oasis-open.org<mailto:mary.mcrae@oasis-open.org>> >>> Cc: "'Will Norris'" >>> <will@willnorris.com<mailto:will@willnorris.com>>, "'Eran Hammer- >>> Lahav'" >>> <eran@hueniverse.com<mailto:eran@hueniverse.com> >>> >>> , "'John Bradley'" <jbradley@mac.com<mailto:jbradley@mac.com>> >>> >>> Subject: Mary: SVN for XRI TC? >>> >>> Mary, >>> >>> The XRD 1.0 editor team at the XRI TC is going to be using DocBook, >>> and >>> they'd really like an SVN repository so they can check in changes to >>> different parts of the doc as they go. >>> >>> Can you set us up with access to the OASIS SVN? And if so, how long >>> will it >>> take (right now I think we'd only need 2-3 TC members needing >>> accounts). >>> >>> Thanks, >>> >>> =Drummond >>> >>> >>> >>> -- >>> Neil Schelly, Senior Systems Administrator >>> OASIS: Advancing open standards for the information society >>> http://www.oasis-open.org/ >>> W: +1.978.667.5115 x213 >>> M: +1.508.410.4776 >>> >>> New to OASIS? Take a Tour >>> http://www.oasis-open.org/home/tour.php >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this mail list, you must leave the OASIS TC that >>> generates this mail. Follow this link to all your TCs in OASIS at: >>> https://www.oasis-open.org/apps/org/workgroup/portal/ >>> my_workgroups.php >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this mail list, you must leave the OASIS TC that >>> generates this mail. Follow this link to all your TCs in OASIS at: >>> https://www.oasis-open.org/apps/org/workgroup/portal/ >>> my_workgroups.php >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this mail list, you must leave the OASIS TC that >> generates this mail. Follow this link to all your TCs in OASIS at: >> https://www.oasis-open.org/apps/org/workgroup/portal/ >> my_workgroups.php >> >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]