[ticker-dev] Elvin presence specification draft 0.2 - separators

[Wanicki, Martin]

Ok,  I'm understanding the reason for enclosing the group in a delimiter
pair
it clearly makes the subscriptions easier.

It does seem tho, that the spec should not call them separators but should
instead enforce the wrapping of the group names in a delimiter pair.

This concept seems useful for other things like ( and I hate to bring it up
again)
distribution, and any attribute value containing a list of channels, groups,
usernames ..etc
To that end it may be good to spend a few minutes thinking about this
methods
application to other formats and incorperate it as a base spec for such
lists.

It would be handy not to have to develop more that one parsing routine for
each incarnation :-)

Just to be different - and probably annoying:-( what about
using some sort of bracketing characters instead ?

So a subs might look like
require(Presence-Info) && contains(Groups, "<dsto>","<foo.bar>","<bad
ideas>","<good ideas>")

or

require(Presence-Info) && contains(Groups, "{dsto}","{foo.bar}","{bad
ideas}","{good ideas}")

or

require(Presence-Info) && contains(Groups, "[dsto]","[foo.bar]","[bad
ideas]","[good ideas]")

or even

require(Presence-Info) && contains(Groups, "(dsto)","(foo.bar)","(bad
ideas)","(good ideas)")

personally I like the <value> or [value] versions :-)

cheers,


Martin 

eMails :
    Boeing      = martin.wanicki at boeing.com
    DSTC      = mwanicki at dstc.edu.au