On 03.11.2015 19:00, Mark Rejhon wrote: > On Mon, Oct 26, 2015 at 12:49 PM, Florian Schmaus <[email protected] > <mailto:[email protected]>> wrote: > > > XEP-0115 is Entity Capabilities > > http://xmpp.org/extensions/xep-0115.html > > It's a rather important standard that's still DRAFT. > > Entity Capabilities are important to avoid lookups. But they are only an > optimization on top of XEP-30. Most XEPs have no hard dependency on > Entity Capabilities, i.e. the protocols also work using ordinary XEP-30 > lookups, and therefore don't require to mention it as normative > reference. > > > That said, XEP-0203 (FINAL) references XEP-0045 (DRAFT) in a rather > important way, even to the point of including it in Examples > (type='groupchat'). But one is not required to implement xep45 when implementing xep203. Delayed delivery meta-data is just a good match for some xep45 cases (amongst others).
> Upon a reading XEP-0301 does not require implementation of any of the > DRAFT standards with the sole exception of XEP-0115 (as mentioned) which > is common anyway. Correct me if I'm wrong, but nothing in xep301 *requires* xep115. That is, you could implement xep301 on top of a software stack which only supports xep30 and it would work just fine. The only reference to xep115 in xep301 I could find is in § 5: """ In order for an application to determine whether an entity supports this protocol, where possible it SHOULD use the dynamic, presence-based profile of service discovery defined in Entity Capabilities (XEP-0115) [17]. However, if an application has not received entity capabilities information from an entity, it SHOULD use explicit service discovery instead. """ This is a common standard statement one finds in most XEPs requiring feature discovery. It comes down to "If you can use xep115 to determine the features, then use it, if not, use xep30". I'm not sure if I like every XEP repeating this mantra wise again and again. As far as I can tell, the dependencies section in xep301 """ Dependencies: XMPP Core, XMPP IM, XEP-0030 """ is correct. - Florian
signature.asc
Description: OpenPGP digital signature
