[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xdi] XDI collection as attribute
On Sep 15, 2014, at 10:13 PM, =Drummond Reed <drummond.reed@xdi.org> wrote:
Anything surrounded by < > is an attribute; the same thing without the < > will be an entity; anything not surrounded by < > is not an attribute. XDI syntax puts < > around all path elements which are attributes so you can recognize them immediately, even though once you encounter an attribute in a path everything following is an attribute (or value) and no more entities are allowed, so any < > after the first are in fact redundant information, and are there just so parsing doesn’t have to backtrack. The fact that we use [< >] instead of <[ ]> is actually a bit of an inconsistency that adds at least one rule to the ABNF, but the consensus at the time was that [< >] was already in use and may look better visually. As the ABNF keeper, I’m always arguing in favor of syntactic consistency to simplify the rules.
One thing I’m not clear on here is, if you take the collection of personal authorities then index a single member from it, isn’t that the same as just specifying that personal authority? i.e. [=]!drummond vs. =drummond
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]