On 11.02.20 16:21, Jonas Schäfer (XSF Editor) wrote:
The XEP Editor would like to Call for Experience with XEP-0198 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-0198 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.
Converse.js (MPLv2) supports XEP-0198 over websocket connections.
2. Have developers experienced any problems with the protocol as
defined in XEP-0198? If so, please describe the problems and, if
possible, suggested solutions.
Like others, I've encountered counter bugs. Unsure whether anything can
be done in the XEP about this.
3. Is the text of XEP-0198 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.
AFAICT yes.
If you have any comments about advancing XEP-0198 from Draft to Final,
please provide them by the close of business on 2020-02-25. 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.
No.
You can review the specification here:
https://xmpp.org/extensions/xep-0198.html
Please send all feedback to the [email protected] discussion list.
_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________
_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________
