Hi, I would like to submit an enhancement to XEP-0060 specification to provide a mechanism for the node owner to subscribe a client with subscription options. As per section 8.2.2 (Modify Subscriptions) of the specification, the node owner can change the subscription state of a client to 'subscribed' using the below stanza.
<iq type='set' from='[email protected]/elsinore' to='pubsub.shakespeare.lit' id='subman2'> <pubsub xmlns='http://jabber.org/protocol/pubsub#owner'> <subscriptions node='princely_musings'> <subscription jid='[email protected]' subscription='subscribed'/> </subscriptions> </pubsub> </iq> Support for the below stanza will enable the node owner to subscribe a client along with subscription options. This will allow full control to the node owner in managing the subscriptions centrally. <iq type='set' from='[email protected]/elsinore' to='pubsub.shakespeare.lit' id='subman3'> <pubsub xmlns='http://jabber.org/protocol/pubsub#owner'> <subscriptions node='princely_musings'> <subscription jid='[email protected]' subscription='subscribed'> <options> <x xmlns='jabber:x:data' subscription='subscribed'> <field var='FORM_TYPE' type='hidden'> <value>http://jabber.org/protocol/pubsub#subscribe_options</value> </field> <field var='http://www.cisco.com/xpath#xpath_filter'> <value>/session[location='IN']</value> <field> </x> </options> </subscription> </subscriptions> </pubsub> </iq> Please let me know your thoughts. Regards, Krishna Chaitanya.
