See JEP 119 for more details: http://www.jabber.org/jeps/jep-0119.html
On Sat, 8 Jan 2005 14:03:35 -0500, Stephen Pendleton <[EMAIL PROTECTED]> wrote: > I am currently implementing the GEOLOC JEP-0080 with the pubsub mechanism, > and I have run into an issue that may be caused by a misunderstanding on my > part. > > The issue is that JEP-0080 doesn't have an explicit use-case for how an > Entity would subscribe to a particular users location information in Section > 4. I understand that the subscription syntax can be determined using the > pubsub JEP-0060. From what I can determine, the correct syntax for a > subscription request should be similar to: > > <iq type="set" > from="[EMAIL PROTECTED]/home" > to="pubsub.jabber.org" > id="sub1"> > <pubsub xmlns="http://jabber.org/protocol/pubsub";> > <subscribe > node="geoloc:[EMAIL PROTECTED]" > jid="[EMAIL PROTECTED]"/> > </pubsub> > </iq> > > Given this syntax, how can I make my implementation interoperable with other > JEP-0080 implementations? In order to do this, I would need to know what the > value for the "node" attribute in the <subscribe> stanza is supposed it be. > Are we supposed to use disco to discover this? If so, how? I think it would > be helpful to spell this out more precisely in JEP-0080. > > Thanks! > > _______________________________________________ > jdev mailing list > [email protected] > http://mail.jabber.org/mailman/listinfo/jdev > -- Joe Hildebrand _______________________________________________ jdev mailing list [email protected] http://mail.jabber.org/mailman/listinfo/jdev
