[Standards-JIG] JEP-0060 Publisher Model - nodehirarchy

Peter Saint-Andre stpeter at jabber.org
Tue May 30 20:00:27 UTC 2006


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

Jean-Louis Seguineau wrote:
> Bernhard, building the hierarchy is a matter of server implementation. You
> can implement a node to be a child of another node without exposing the fact
> in the node ID. You could for example implement an indirect index based
> reference instead of using building the semantic in the ID.
> 
> Having provision for semantic in the IDs is IMHO a major shortcoming of this
> JEP. It is opening the Pandora box for all sorts of interpretations of the
> standard, and above all reduces XMPP to 'yet another hierarchical pubsub'.
> But this is only my strong opinion...

A NodeID SHOULD be opaque. A NodeID MAY have semantic meaning in a
particular implementation or deployment, but assigning semantic meaning
to NodeIDs is NOT RECOMMENDED.

Peter

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEfKRaNF1RSzyt3NURAvKVAKCDY1r/iIqu/M+M2xXB3oZKFSipIgCgxOGg
V9MEkBPiPa+QMeAS50n9x0Q=
=1tl6
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060530/687d6f52/attachment.bin>


More information about the Standards mailing list