Hi Peter,

Many thanks for your swift action. We will be contributing an XEP-0009
implementation to SleekXMPP (Python) , so being compliant with the standard,
and therefore having an implementation that is interoperable, is very
valuable for us.

With kind regards,

Gerard Maas.


On Fri, Oct 7, 2011 at 12:08 AM, Peter Saint-Andre <stpe...@stpeter.im>wrote:

> On 10/5/11 10:24 AM, Peter Saint-Andre wrote:
> > On 10/5/11 9:07 AM, Peter Saint-Andre wrote:
> >> On 10/5/11 1:20 AM, Gerard Maas wrote:
> >>> Hi Peter,
> >>>
> >>> Thanks for the follow-up.
> >>>
> >>> Could you give me an idea about the timeline of such a revision? Are we
> >>> talking days/weeks/months?
> >>
> >> Hours? :)
> >>
> >> The XMPP Council will discuss the matter in its meeting today, which
> >> just started.
> >
> > See here:
> >
> > http://xmpp.org:5290/muc_log/muc.xmpp.org/council/111005/#15:32:53
> >
> > and here:
> >
> > http://xmpp.org:5290/muc_log/muc.xmpp.org/council/111005/#15:46:16
> >
> > SleekXMPP appears to have <Base64> but in the chatroom Lance Stout said
> > he could fix that.
> >
> > I am inclined to view <Base64> as a typo in the (unofficial) schema that
> > we borrowed from Elliotte Rusty Harold's book, and inclined to correct
> > the schema with a prominent note in the text about earlier versions of
> > the spec showing <Base64> instead of <base64>.
>
> I've provisionally updated the spec:
>
> http://xmpp.org/extensions/tmp/xep-0009-2.2.html
>
> http://xmpp.org/extensions/diff/api/xep/0009/diff/2.1/vs/2.2rc1
>
> I expect that the XMPP Council will consider these changes at its next
> meeting.
>
> Peter
>
> --
> Peter Saint-Andre
> https://stpeter.im/
>
>
>

Reply via email to