[Adium-devl] JEP 0117 & Smack

[Colin Barrett]

On May 3, 2006, at 9:53 PM, Evan Schoenberg wrote:

> What of JEP-0117 does Smack not already implement?  In other words,  
> is "making Adium support JEP-0117" and "integrating Smack as an  
> Adium protocol library" in a sense the same project with a  
> different stated endpoint?
>

David & I have been investigating exactly what is needed for JEP-0117  
compliance.

The question we need to answer is: are some of these implemented but  
not listed. The way to answer this is to check the dependency list  
for each implemented one, and determine if it includes the  
unimplemented ones.

Items with stars are implemented, and numbers in parenthesis  
represent the JEP that compliance comes from.

* 1. JEP-0073: Basic IM Protocol Suite <http://www.jabber.org/jeps/ 
jep-0073.html>.
* 2. JEP-0001: Jabber Enhancement Proposals <http://www.jabber.org/ 
jeps/jep-0001.html>.
* 3. JEP-0045: Multi-User Chat <http://www.jabber.org/jeps/ 
jep-0045.html>.
* 4. JEP-0071: XHTML-IM <http://www.jabber.org/jeps/jep-0071.html>.
* 5. JEP-0096: File Transfer <http://www.jabber.org/jeps/jep-0096.html>.
6. JEP-0115: Entity Capabilities <http://www.jabber.org/jeps/ 
jep-0115.html>.
* 7. JEP-0004: Data Forms <http://www.jabber.org/jeps/jep-0004.html>.
8. JEP-0020: Feature Negotiation <http://www.jabber.org/jeps/ 
jep-0020.html>.
* (96) 9. JEP-0047: In-Band Bytestreams <http://www.jabber.org/jeps/ 
jep-0047.html>.
* (96) 10. JEP-0065: SOCKS5 Bytestreams <http://www.jabber.org/jeps/ 
jep-0065.html>.
* (45) 11. JEP-0068: Field Data Standardization for Data Forms  
<http://www.jabber.org/jeps/jep-0068.html>.
* (45)12. JEP-0082: Jabber Date and Time Profiles <http:// 
www.jabber.org/jeps/jep-0082.html>.
* (96) 13. JEP-0095: Stream Initiation <http://www.jabber.org/jeps/ 
jep-0095.html>.

So the list of missing JEPs is:
1. JEP-0115: Entity Capabilities <http://www.jabber.org/jeps/ 
jep-0115.html>.
2. JEP-0020: Feature Negotiation <http://www.jabber.org/jeps/ 
jep-0020.html>.

Here is a jive forum thread about jep-0020 David found:
http://www.jivesoftware.org/community/ 
thread.jspa;jsessionid=a5D5ukXgxM-aPDXp9R?messageID=103760&#103760

An interesting line from JEP-0020:
A discovery protocol such as Service Discovery [1] enables Jabber  
entities to query other entities regarding the features they support,  
but does not provide a means for the two entities to negotiate  
specific options related to the advertised features (e.g., specific  
methods of file transfer such as In-Band Bytestreams [2] or SOCKS5  
Bytestreams [3]).

This sounds to me like JEP 0020 is required for file transfer. If  
not, I'd like some clarification, especially combined with the forum  
thread.

On IRC, David, Geoff and another interested party, Brian Chu, were  
discussing the issue and we came up with the following recommendations:

- For now, let the issue of how we want to divy things up sit until  
all applications are in.
- As acceptable applications come in for Jabber, inform people of the  
situation (so they can possibly apply elsewhere), and try to set up a  
meeting on or around May 9th (via IRC).

One final note: We should probably change "0117 compliance" to  
"improving smack in useful ways," since 0117 is almost done. There  
are tons of JEP to implement, we can go hog wild with this.

-Colin (& David, via SEE)