On Tue Sep 29 15:28:26 2009, Nathan Fritz wrote:
On Sep 29, 2009, at 5:53 AM, Dave Cridland <[email protected]>
wrote:
On Tue Sep 29 12:31:39 2009, Mads Randstoft wrote:
After some talks at the jabber dev MUC, it seems there is a need
to be
able to add more data to a node and more data to an item than is
currently possible in a std. way.
I see priority as a valid addition to pubsub queuing. As far as
metadata is concerned, this seems to be contextual to the service
provider, and there is no way for a 3rd party pubsub service to
interpret your metadata, and so it is an implementation detail. Are
there values you need outside of the spec? Then add your own
namespace for your values to the publish call inside the pubsub
element. If you think these values would be helpful to others,
get them added to an appropriate xep or see if there is interest
in a new xep
What I think would be useful would be a framework for adding these -
hence a standardized, single, container element for the item's
metadata. Then some items can be opaque to the serverice, and only of
interest to subscribers, and others controlled exclusively by the
service.
Dave.
--
Dave Cridland - mailto:[email protected] - xmpp:[email protected]
- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
- http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
