[Standards-JIG] Re: LAST CALL: JEP-0172 (User Nickname)

Peter Saint-Andre stpeter at jabber.org
Mon May 1 19:41:00 UTC 2006

Hash: SHA1

Good point, I will add examples for both PEP and generic pubsub.


Daniel Henninger wrote:
> May I ask that someone specify pubsub/pep use within this JEP?  Section
> 4.5 mentions that pubsub/pep ought to be used, BUT it doesn't provide
> any examples or real information regarding it's use.  I basically "made
> something up" for the moment which may or may not be good.  =)  (I'm
> trying to implement all of this with PyICQ/PyAIM)  Anyway, basically I
> stored this:
> <items node="http://jabber.org/protocol/nick">
>       <item id="current">
>         <nick xmlns="http://jabber.org/protocol/nick">Jadestorm</nick>
>       </item>
> </items>
> Seemed reasonable enough.  Might be stupid, might not.  =D  Either way,
> if pubsub/pep is going to be suggested in the JEP, I'd love to see an
> example of storing it in pubsub/pep listed.  (or is this implied
> somewhere that I'm not seeing?)
> Daniel
> On May 1, 2006, at 1:43 PM, Remko Troncon wrote:
>> On 01 May 2006, at 19:26, Peter Saint-Andre wrote:
>>> Yes, at some point we need to "bite the bullet" and tell people to use
>>> pubsub/PEP. I'm just not sure exactly when that point is...
>> Well, that statement can be turned around: for years, every feature
>> that could be done through PubSub (even if it was far fetched) and
>> that didn't was shot down without further discussion. Is it a good
>> time to stop doing it now, now that a usable version of pubsub is
>> finally emerging ? ;-)
>> Anyway, i agree: as long as PEP isn't draft, you can't enforce it.
>> cheers,
>> Remko
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060501/b63e7ec7/attachment.bin>

More information about the Standards mailing list