It depends on what we want to standardize: 1. data form fields (as in field names and/or multi-stage registration workflow?) 2. new top level elements (much like username and password <-- there should be kept for backwards compatibility of course, but adding new ones... I don't know)
I have to say multi-stage registration is very unpredictable (e.g. registration through SMS, OTP device, public key, and who knows what else), so it would be hard to write a standard flexible enough IMO. What do you suggest? On Wed, Feb 3, 2016 at 4:53 PM, Stephen Paul Weber <[email protected]> wrote: >> https://github.com/kontalk/specs/blob/master/register.md > > > This appears to be identical to my proposal, which gives me hope. (Data > forms are certainly supported by XEP-0077 already, and would of course be > used more likely than the old fields on moders clients. I think both should > be supported by servers for compatability, but this is not really relevant > to the particular issue of multi-stage support.) > > So it seems there is more need in the world than just mine, and two > independently-developed but identical solutions. Should we write up a > "real" XEP? > > > -- > Stephen Paul Weber, @singpolyma > See <http://singpolyma.net> for how I prefer to be contacted > edition right joseph -- Daniele _______________________________________________ Standards mailing list Info: http://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
