On 17 Jun 2004, at 17:48, Justin Karneges wrote:
In addition, many of the features you mention just plain aren't ready in
specification form. Avatars? XHTML-IM? Voice chat? These are all
Experimental. Maybe we should start certifying Jabber Council members, to
motivate them to approve some JEPs? (and speaking of which, my "jep-secure"
has beat the record of the longest time from submission to publication, and
is still counting.)
Protocols do not move forward by sheer will of the council. The /reason/ those JEPs are /still/ experimental is because of lack of implementation attempts. If we had a compliance board, and the board said "ok, we're going to try to have Avatars as part of the 2005 compliance spec", then client authors would start working on implementing avatars, and the JEP would start changing and moving forward. Obviously if the JEP is not finalized in time for the 2005 compliance tests it can only be "recommended" at best and not an actual requirement, but it will have pushed the client authors to attempt to implement a JEP, and by extension, pushed the JEP forward.
JEPs do not move forward by sheer will of Council or JEP authors. Client-based JEPs need client implementations to test them and work out bugs... and then the Council can start moving things forward based on real experience.
How many test implementations of jep-secure are there?
Julian
_______________________________________________ jdev mailing list [EMAIL PROTECTED] https://jabberstudio.org/mailman/listinfo/jdev
