[Standards-JIG] Re: Ad-hoc Commands and nesting

Nolan Eakins sneakin at semanticgap.com
Sat Jan 22 18:08:57 UTC 2005


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Peter Saint-Andre wrote:
| In article <200501191820.31891.trejkaz at trypticon.org>,
|  Trejkaz <trejkaz at trypticon.org> wrote:
|
|
|>On Wednesday 19 January 2005 10:55, Joe Hildebrand wrote:
|>Taking branches into account, what is the difference between this:
|>
|>    <identity category="hierarchy" type="branch"/>
|>
|>and this:
|>
|>    <identity category="automation" type="command-list"/>
|
| Well, a disco node can have two identities, so it's not necessary to
| choose between these. :-)

I know this thread has become slightly stale, but I had an idea related
to it and had to find it so...

Standards wise I would say a decision should be made on which to use for
branches. I know if I was implementing this I would NOT want to support
both. Personally I would favor the identity that is already used for
branches in other JEPs, which I'm guessing is the "hierarchy/branch"
identity.

The idea that sent me back to this thread is about Service disco in
general. I don't know if this is possible, but I don't see why it should
not be: can a disco#items query return a list of items that are a mix of
~ say Pubsub nodes, adhoc commands, branches, clients, and any other
service disco#item? This may require an additional attribute or two be
added to the <item/> elements or a child element. Would this be desirable?

- - Nolan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB8pa4huPszQVSPEARAq3dAJ0R47oS8vus++Ua/C2rHB3u5SrynQCfftWJ
FghrmjKs5Sp0j8UNfaS4mnY=
=YN+U
-----END PGP SIGNATURE-----




More information about the Standards mailing list