As JEP Editor, I hereby issue a Call for Experience on JEP-0030 (Service Discovery). As defined in JEP-0001, the Call for Experience is the last chance to provide feedback on a JEP before it advances from Draft to Final. To help the Jabber Council decide whether JEP-0030 is ready to advance to a status of Final, the JSF would like to gather the following information:
1. Who has implemented JEP-0030? I am aware of several client, server, and component implementations, including jabberd 1.4.3, jabberd 2.0, Exodus, and mu-conference. Further examples would be helpful. 2. Have implementers experienced any problems with the protocol as defined in JEP-0030? If so, please describe the problems and, if possible, suggested solutions. 3. Is the text of JEP-0030 clear and unambiguous? Are more examples necessary? Is the conformance language (MAY/SHOULD/MUST) appropriate? Have implementers found the text confusing at all? Please describe any suggestions you have for improving the text. If you have any comments on this JEP, please provide them within the next 2 weeks (i.e., by April 5), at which time the Call for Experience will end. After the Call for Experience, this JEP will if necessary undergo one more revision, after which it will be presented to the Jabber Council for voting to a status of Final. You may review the JEP here: http://www.jabber.org/jeps/jep-0030.html Please send all feedback to <[EMAIL PROTECTED]>. Thank you. Peter -- Peter Saint-Andre Jabber Software Foundation http://www.jabber.org/people/stpeter.php _______________________________________________ jdev mailing list [EMAIL PROTECTED] https://jabberstudio.org/mailman/listinfo/jdev
