The <inline/> stream feature wrapper is just a neat wrapper for all stream features that can be inlined into SASL to announce themselves. Yes ISR works without inline but that's not the point.
Imagine we want to make compression inline-able. Simply by looking at the <compression/> stream feature a client doesn’t know if compression can be inlined into SASL. So if we want to make compression inlinable the new XEP (or an amendment to the existing XEP) would have to either announce a new stream feature called <compression-inline/> (This is kind of - but not really - what ISR is doing) or place itself in the <inline> wrapper like this: <inline><compression/></inline> It's just a syntax modification that some people find more pleasent; not a new addition to the XEP to achieve something that wasn’t possible before. _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
