Re: [Standards] various rfc3920bis feedback

2009-04-16 Thread Philipp Hancke
Dave Cridland schrieb: That's an assertion not necessarily backed up by evidence. I am not convinced that TLS + EXTERNAL is a non-starter on the public XMPP network, but then again I help to run a CA that issues free domain certificates for that network (visit http://xmpp.org/ca/ to get yours

[Standards] Small typos in ad-hoc commands (XEP-0050)

2009-04-16 Thread Nicolas Vérité
Hi, There are small typos in XEP-0050: Ad-Hoc Commands: http://xmpp.org/extensions/xep-0050.html :%s/X-Windows/X-Window/g http://en.wikipedia.org/wiki/X_Window_System ;-) -- Nicolas Vérité (Nÿco) mailto:nicolas.ver...@gmail.com Jabber ID : xmpp:n...@jabber.fr http://linuxfr.org/ -

Re: [Standards] Small typos in ad-hoc commands (XEP-0050)

2009-04-16 Thread Peter Saint-Andre
On 4/16/09 8:03 AM, Nicolas Vérité wrote: Hi, There are small typos in XEP-0050: Ad-Hoc Commands: http://xmpp.org/extensions/xep-0050.html :%s/X-Windows/X-Window/g http://en.wikipedia.org/wiki/X_Window_System ;-) Fixed, thanks. :) Peter -- Peter Saint-Andre https://stpeter.im/

Re: [Standards] Meta-data in Pubsub XEP-0060

2009-04-16 Thread Peter Saint-Andre
On 12/19/08 5:38 AM, Brett Zamir wrote: Might the meta-data query result (section 5.4 in XEP-0060) recommend the @type attribute on the x's field/ children so that a client could, for example, know to display a boolean type as the more readable true and false as opposed to the potential values

Re: [Standards] Pubsub extension idea

2009-04-16 Thread Peter Saint-Andre
On 12/25/08 10:35 PM, Brett Zamir wrote: Hi, Along the lines of how Data Forms types and Data Forms Validation can influence display of forms, I'd like to see some standard way in which Pubsub payloads could be similarly extensible, not only by allowing different namespaces (as is now

Re: [Standards] [Fwd: Re: LAST CALL: XEP-0237 (Roster Versioning)]

2009-04-16 Thread Peter Saint-Andre
On 4/14/09 12:44 PM, Jiří Zárevúcký wrote: You are raising the scenario of the stream dying right after the server sends 303. I'm saying that client 1 MUST NOT consider itself to be up to date when it receives 303, because the server has already told it that the latest version is 305.

Re: [Standards] [Fwd: Re: LAST CALL: XEP-0237 (Roster Versioning)]

2009-04-16 Thread Jiří Zárevúcký
2009/4/17 Peter Saint-Andre stpe...@stpeter.im: I think you're making it too complicated for the typical usage. Peter Yeah. You are probably right. These are just nuances that would affect very little people throughout the whole existence of the protocol, but given they don't make anything

Re: [Standards] [Fwd: Re: LAST CALL: XEP-0237 (Roster Versioning)]

2009-04-16 Thread Peter Saint-Andre
Ahoj Jirka, On 4/16/09 8:39 PM, Jiří Zárevúcký wrote: 2009/4/17 Peter Saint-Andre stpe...@stpeter.im: I think you're making it too complicated for the typical usage. Peter Yeah. You are probably right. These are just nuances that would affect very little people throughout the whole

Re: [Standards] [Fwd: Re: LAST CALL: XEP-0237 (Roster Versioning)]

2009-04-16 Thread Jiří Zárevúcký
2009/4/17 Peter Saint-Andre stpe...@stpeter.im: Ahoj Jirka, On 4/16/09 8:39 PM, Jiří Zárevúcký wrote: 2009/4/17 Peter Saint-Andre stpe...@stpeter.im: I think you're making it too complicated for the typical usage. Peter Yeah. You are probably right. These are just nuances that would