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


Help: OASIS Mailing Lists Help | MarkMail Help

xdi message

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

Subject: Re: [xdi] colon for values only?

Yes, I thought about that. But I personally was comfortable with it for one reason: unlike the other context symbols, colon is the only one that only appears alone, and only at the end of a literal statement. So even though it does have this very special role as a context symbol, to me it seemed okay for it to be allowed in the specialized ! and * syntax (where it is NOT a context symbol, just part of the identifier syntax).

However, if you feel strongly that we should use another character, since we can't change the character used in either IPv6 identifiers or for URI schemes, we should pick another character for the terminal literal. Not sure what would work best -- just not dot since it's a legal XDI identifier character. We could go back to the empty chevrons...

=Drummond (really going to bed now ;-)

On Tue, Apr 16, 2013 at 12:49 AM, Markus Sabadello <markus.sabadello@xdi.org> wrote:
Hmm I'll play with it a bit, but in all the discussions we have ever had about syntax, we never had a case where a certain symbol would only sometimes (at the end) have XDI semantics associated with it, and sometimes (in the middle) not.

Or we leave colon as a valid identifier in arcs (e.g. UUIDs) and use something else for value.


On Tue, Apr 16, 2013 at 9:42 AM, Drummond Reed <drummond.reed@xdi.org> wrote:
Markus, I thought about this and started working on it in the ABNF. The key challenge with not using colons is: a) they are the standard delimiter in IPv6 addresses, and b) they align nicely with URI scheme syntax.

Since they are not allowed as the first character in any subsegment EXCEPT the terminating literal subsegment, it shouldn't be hard to exclude them in parsing, no?


On Tue, Apr 16, 2013 at 12:33 AM, Markus Sabadello <markus.sabadello@xdi.org> wrote:
While doing some implementation work I ran into a parsing challenge around colons

We have been using them to indicate a value, but we're also using them in UUIDs.
To me this creates ambiguity in the parsing process.

So I propose to use colons ONLY for values.
One idea would then be to use dots . instead in UUIDs, since dots have no syntactical meaning in XDI anyway.

This is completely orthogonal to the current discussions around paired vs. leading vs. trailing symbols.

Example with dots in UUIDs according to "Second Strawman":
Joseph would your version look like this? Please correct

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