[Standards] geoloc: PEP=user, <iq>=resource
stpeter at jabber.org
Mon Jun 4 15:33:41 UTC 2007
Stephen Pendleton wrote:
> -----Original Message-----
> From: standards-bounces at xmpp.org [mailto:standards-bounces at xmpp.org] On
> Behalf Of Peter Saint-Andre
> Sent: Friday, June 01, 2007 5:19 PM
> To: XMPP Extension Discussion List
> Subject: Re: [Standards] geoloc: PEP=user, <iq>=resource
>> See XEP-0060, it's pretty straightforward. We're encouraging use of PEP
>> for this stuff, as discussed here:
>>From the discussion you pointed to:
>>> Actually, once PEP starts to be more deployed (hopefully later this
>>> year), I'd like to remove/deprecate the non-PEP parts of XEP-80.
>> Yes. In fact maybe that should be done now - to avoid (new)
>> implementations of the non-PEP parts?
> So I guess I am confused. When you talk about removing/deprecating the
> "non-PEP" parts in the discussion, do you mean the pubsub method, and/or the
> message and/or presence methods?
> The XEP says that the pubsub way OR the PEP way is the "SHOULD" way to do
> it. I dont think that there should be two SHOULD ways of doing things,
> otherwise interoperability suffers. This is one spec that should definitely
> be as interoperable as possible in order to encourage its use.
I can't speak for Ian, but "non-pubsub" seems right (where PEP is a
flavor of pubsub and therefore included -- if you're an end user and you
have a PEP service available at your "home" server, use that; if not,
use a non-PEP pubsub service available on the 'net).
XMPP Standards Foundation
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
More information about the Standards