Re: Lobbies

Jason McIntosh writes:
 > Any client that can use service discovery (which is to say, any 
 > self-respecting client) can easily discover a lobby's JabberID. It need 
 > only send a disco items request to the bookkeeper, with a node 
 > comprising the ruleset's URI followed by the string |lobby. (That's a 
 > "pipe" character, then the word "lobby".)

I still don't like this pipe convention...  Why not have the disco
info for the ruleset URI include a "lobby" field?  Same goes for
"servers", although we'd have to have a convention for putting
multiple JIDs into a single string (whitespace-separated would be my
preference, but perhaps comma-separated is more conventional).

I've also been thinking about RDF, which is a mechanism (and concrete
XML syntax) for representing arbitrary directed graphs whose nodes and
edges are labeled with URIs.  This might be a more natural fit for
this Resource Description task, but it's also Yet Another Technology.

--dougo <at> place.org

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/