Re: [Standards] Service Discovery + dependent features

2015-03-17 Thread Christian Schudt
Ok, makes sense as well. I conclude from this discussion, that there are no extension protocols which MUST be coupled with another one in service discovery (i.e. if A then B), although for some they SHOULD (e.g. if urn:xmpp:jingle:transports:ibb:1 then urn:xmpp:jingle:1). Thanks. -Christian

Re: [Standards] Service Discovery + dependent features

2015-03-17 Thread Dave Cridland
On 16 March 2015 at 23:11, Lance Stout wrote: > This one may need to go to Peter for a philosophy question: what is to be > done when an implementation of feature Y MUST support X as a fallback, but > the user chooses to disable X. > MTI != MTD Mandatory To Implement does not mean Mandatory To

Re: [Standards] Service Discovery + dependent features

2015-03-17 Thread Florian Schmaus
On 16.03.2015 23:06, Christian Schudt wrote: > Thanks Florian, generally I agree, but please read my answers below. I was mostly having a modular XMPP client library in mind. Here, if you advertise support for 'carbons', the library code for forward will be loaded. And in Smack's case, it's the fu

Re: [Standards] Service Discovery + dependent features

2015-03-16 Thread Lance Stout
> True from a pure protocol point of view, but less true from a client's "UI > features" point of view. > http://xmpp.org/extensions/xep-0297.html#support says: > "Clients that implement this specification to display simple forwarded > messages (i.e. those not part of another extension)“ > > wh

Re: [Standards] Service Discovery + dependent features

2015-03-16 Thread Christian Schudt
Thanks Florian, generally I agree, but please read my answers below. >> urn:xmpp:carbons:2 ==> urn:xmpp:forward:0 >> http://jabber.org/protocol/si/profile/file-transfer ==> >> http://jabber.org/protocol/si >> http://jabber.org/protocol/caps ==> http://jabber.org/protocol/disco#info >> http://jab

Re: [Standards] Service Discovery + dependent features

2015-03-16 Thread Florian Schmaus
On 15.03.2015 22:25, Christian Schudt wrote: > there are several features/extension protocols, which are dependent on > others, e.g. > > urn:xmpp:carbons:2 ==> urn:xmpp:forward:0 > http://jabber.org/protocol/si/profile/file-transfer ==> > http://jabber.org/protocol/si > http://jabber.org/protoco

[Standards] Service Discovery + dependent features

2015-03-15 Thread Christian Schudt
Hi all, there are several features/extension protocols, which are dependent on others, e.g. urn:xmpp:carbons:2 ==> urn:xmpp:forward:0 http://jabber.org/protocol/si/profile/file-transfer ==> http://jabber.org/protocol/si http://jabber.org/protocol/caps ==> http://jabber.org/protocol/disco#info h