[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xri] GCS Characters
I continue to struggle with why we need two ways to put a global xri in the context of another xri. =drummond@microsoft.com and =drummond*(@microsoft.com) seem to do the same thing. If the later is less than desirable let's drop ()'s in xri. From: Drummond Reed <drummond.reed@cordance.net> To: 'OASIS XRI TC' Cc: 'John Bradley' Sent: Mon Nov 24 14:07:53 2008 Subject: RE: [xri] GCS Characters First, just to address some clarification
questions in this thread, the proposal under discussion, called GCS Delimiter,
is posted at: http://wiki.oasis-open.org/xri/XriThree/GcsDelimiter The accompanying ABNF that implements this
proposal is at: http://wiki.oasis-open.org/xri/XriThree/SyntaxAbnf
As described there in more detail, the
proposal is that in XRI 3.0, all GCS characters (=, @, +, $) are treated in XRI
syntax as delimiters just like * and ! are in XRI 2.0. Per the ABNF, both =drummond@microsoft.com
and @microsoft.com=drummond would parse into two subsegments. =drummond@microsoft.com
would parse into: 1) =drummond 2) @microsoft.com @microsoft.com=drummond would parse into: 1) @microsoft.com 2) =drummond =drummond+phone+home would parse into: 1) =drummond 2) +phone 3) +home In XRI resolution, each of these would
produce its own XRD. I don’t know why John thinks this is strange –
an XRD can describe any resource, and certainly my phone collection is a
resource, and my home phone is a resource. =Drummond From: John Bradley
[mailto:jbradley@mac.com] Well thats a can of worms:) I think in Drummonds proposal + and $ also get to have XRD. In the first segment the only place those
symbols formerly known as GCS would have
there conventional meaning is if they are attached to the
first sub segment. If they are the leading character of any other subsegment they would be
treated as * and the =, +, $ are only inferences to the global
concept. Remember I am the one opposed to the change unless there is a good
reason. So take any pro things I say with a grain of salt. The thing is that under that they will be treated as sub segments by
the authority server, so what gets passed? For =drummond@microsoft.com
the first subsegment is =drummond what is the second that get passed to
=drummonds's authority service? @microsoft.com *(@microsoft.com) microsoft.com So would =drummond*microsoft.com produce the same XRD as =drummond@microsoft.com? Could go ether way depending on how we define resolution. Yes having =drummond+phone have its own XRD seems sort of funky to me
as well. John B. On 24-Nov-08, at 10:23 AM, Victor Grey wrote:
The confusion with email
addresses, social, technical or otherwise, is not the only problematic aspect
of the @ GCS character. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]