I was reading XEP-0237 just now, and noticed the <optional/> in the
stream feature.
I'm wondering whether we're getting a bit enthusiastic about these.
Some thoughts:
1) Does this imply we might want to have mandatory XEP-0237, by
including a <required/>? I mean, really?
2) Is it right that all these <required/> and <optional/> elements
are in different namespaces to each other? (ie, the <optional/> I
noticed is, in fact, <optional
xmlns='urn:xmpp:features:rosterver:0'/> in full, and therefore
different to, say, TLS's <optional/> element)
3) For many cases, <required/> is superfluous, or misleading. It
appears that TLS being "required" really indicates that an ecnrypted
channel is required, and requiring SASL or dialback is surely just
requiring "authentication", which seems like a given.
I admit I'm playing devil's advocate a bit here, but how far off the
mark am I being?
Dave.
--
Dave Cridland - mailto:[email protected] - xmpp:[email protected]
- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
- http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
