On 14 March 2018 at 18:28, Jonas Wielicki <jo...@wielicki.name> wrote:
> The XEP Editor would like to Call for Experience with XEP-0092 before > presenting it to the Council for advancing it to Final status. > > > During the Call for Experience, please answer the following questions: > > 1. What software has XEP-0092 implemented? Please note that the > protocol must be implemented in at least two separate codebases (at > least one of which must be free or open-source software) in order to > advance from Draft to Final. > MongooseIM (open source) also implements this XEP. > > 2. Have developers experienced any problems with the protocol as > defined in XEP-0092? If so, please describe the problems and, if > possible, suggested solutions. > No. > > 3. Is the text of XEP-0092 clear and unambiguous? Are more examples > needed? Is the conformance language (MAY/SHOULD/MUST) appropriate? > Have developers found the text confusing at all? Please describe any > suggestions you have for improving the text. > Yes, it's clear. > > If you have any comments about advancing XEP-0092 from Draft to Final, > please provide them by the close of business on 2018-03-28. After the > Call for Experience, this XEP might undergo revisions to address > feedback received, after which it will be presented to the XMPP > Council for voting to a status of Final. > > > You can review the specification here: > > https://xmpp.org/extensions/xep-0092.html > > Please send all feedback to the standards@xmpp.org discussion list. > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > _______________________________________________ >
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
