[Standards] geoloc: PEP=user, <iq>=resource
Peter Saint-Andre
stpeter at jabber.org
Fri Jun 1 16:19:06 CDT 2007
Stephen Pendleton wrote:
> Ah, I was confused because it looked like the examples were for pubsub
> (XEP-0060), not PEP, because the section header says "4.1 Entity publishes
> location via pubsub". Even though PEP is a specific form on pubsub I was
> thinking of XEP-0060. I just reread it and saw where in parenthesis there is
> a reference to the examples being based on PEP (XEP-0163). My mistake.
Right I edited those fast, will fix.
> There are no examples then on how this can be used with pubsub (XEP-0060) in
> the XEP.
See XEP-0060, it's pretty straightforward. We're encouraging use of PEP
for this stuff, as discussed here:
http://mail.jabber.org/pipermail/standards/2007-May/015421.html
> In the pubsub case the <addresses> info is needed, unless you gave
> some semantic meaning to the pubsub node name. I hear people talking about
> pubsub being deprecated in this case in favor of PEP.
No no no. PEP is a step on the road to full pubsub, or a flavor of
pubsub if you will. It's fine to geoloc in a full pubsub implementation
if you have one, especially for non-human entities (tracking packages
via XMPP anyone?). But for human users, PEP is the friendly flavor of
pubsub that we're encouraging people to use.
/psa
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.jabber.org/pipermail/standards/attachments/20070601/def8d6cc/smime-0001.bin
More information about the Standards
mailing list