[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xri] RE: [xdi] XDI/XRI Question
By the way, having a client application guess what I intended (which I think is the idea with xri: epok =Dave +email and may have been the idea with xri:@epok.pin/=Dave/+email) is a different matter. I don't have a problem with an intelligent client making guesses, but that doesn't affect equivalence. If I type epok.net into my browser, it may guess that I really meant http://www.epok.net. That doesn't make epok.net and http://www.epok.net equivalent, however, in any context except the context of that particular client application. Dave > -----Original Message----- > From: Dave McAlpin [mailto:dave.mcalpin@epok.net] > Sent: Sunday, February 29, 2004 4:12 PM > To: 'Fen Labalme'; 'Dave McAlpin'; drummond.reed@cordance.net > Cc: xdi@lists.oasis-open.org; xri@lists.oasis-open.org > Subject: [xri] RE: [xdi] XDI/XRI Question > > First, I'll acknowledge that xri:@epok.pin/=Dave/+email is syntactically > legal. Second, because =Dave/+email is part of local access and is > therefore > outside of the define resolution protocol, it's conceivable that it could > be > considered equivalent to (=Dave)/(+email). Having said that, I think it's > reflects a very bad practice. I much prefer > xri:@epok.pin/(=Dave)/(+email). > The reason a subsegment is allowed to start with =, + or @ is because it's > not ambiguous with a fully qualified XRI. In other words, =Dave is allowed > because = couldn't possibly be a global context symbol - if it were, it > would be inside a cross-reference. Equating the two is wrong, in my > opinion. > Drummond may disagree. > > Dave > > > > -----Original Message----- > > From: Fen Labalme [mailto:fen@idcommons.org] > > Sent: Sunday, February 29, 2004 12:57 AM > > To: Dave McAlpin; drummond.reed@cordance.net > > Cc: xdi@lists.oasis-open.org; xri@lists.oasis-open.org > > Subject: Re: [xdi] XDI/XRI Question > > > > "Dave McAlpin" <dave.mcalpin@epok.net> writes: > > > > > This is an edited version of an email thread from Bill. I haven't had > > > time to respond, but I'll try to put something together this weekend > > > unless someone else chimes in first. > > > > ... > > > > > I'm thinking the resolution would go like this? > > > > > > Original XRI: xri:@epok.email.(@epok.pin.(=Dave)) > > > > I think the original XRI could look like this: > > > > xri:@epok.pin/=Dave/+email > > > > If I understand the gist of recent discussions with Drummond, this could > > be equivalent (if real world resolver best practices so dictate) to: > > > > xri:@(epok.pin)/(=Dave)/(+email) > > > > This would look up =Dave according to the epok.pin authority, and then > > look up the +email element within that object. > > > > > A few other questions: > > > > > > 1) The xri form I'm looking for was something that could be put on a > > > biz card and the email would be good even if you transferred jobs, > > > assuming you updated a registry. Is there a form for that? I saw > > > electronic business cards as one example use case, but has the syntax > > > for that use been developed? > > > > A shorthand that might be useful for business cards might be something > > like this: > > > > xri: epok =Dave +email > > > > where the resolver inserts slashes between the segments. > > > > While this XRI is totally local to Epok, and therefore would not follow > a > > person as they changed jobs, simply removing the company name would find > > Dave (assuming he had a global e-name). Note that when =Dave is > > resolved with respect to a company's authority, +email may resolve to a > > different value than when looked up via the global name. Also, link > > contracts prevent =Dave from being directly spammed. > > > > I'm not sure if any of this is correct, but I'm trying to learn this > > stuff and figure I'd try to get my thoughts out there. > > > > Best, > > Fen > > > > PS: Email problems: > > > > I replied to Bill Thursday night, but my email to the list went into a > > black hole and never appeared on the XDI list. I've sent an email to > > Scott McGrath about this, and hopefully this one will be distributed. > > > > My original note (already out-of-date) is attached. > > > > > > > To unsubscribe from this mailing list (and be removed from the roster of > the OASIS TC), go to http://www.oasis- > open.org/apps/org/workgroup/xri/members/leave_workgroup.php. >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]