[Standards] Move CSI to Last Call ("Proposed")

Dave Cridland dave at cridland.net
Tue Jul 28 08:20:23 UTC 2015


On 28 July 2015 at 08:22, Florian Schmaus <flo at geekplace.eu> wrote:

> On 27.07.2015 23:29, Sam Whited wrote:
> > Hi all,
> >
> > I'd like to propose that the Council vote to move XEP-0452: Client
> > State Indication into last call (the "Proposed State"), and then
> > hopefully into draft afterwards.
> >
> > The XEP has been sitting dormant since it was last updated almost a
> > year ago (2014-08-28).
>
> I've talked to Matt at the Summit this year about a message notification
> send by the server to the client indicating a successful CSI state
> change. We agreed on the change and I sent a patch to Matt a while ago.
> But the patch was not applied since then. I've created a PR now:
> https://github.com/xsf/xeps/pull/34
>
>
What? Why? What can a client do in response to the information? What would
it not do without it?

Also, why wrap the server notification in a message, and do I assume that
the use of two namespace versions is in error?


> That said: I don't think that CSI has sufficient adoption at the moment
> to move to draft.
>
> - Florian
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20150728/9d29fe66/attachment.html>


More information about the Standards mailing list