Re: [Standards] [Council] component-s2s

On 4 February 2015 at 21:29, Kevin Smith kevin.sm...@isode.com wrote: I’m -1 on the component-s2s spec. I’ve been backwards and forwards a number of times on whether to use the veto or not, and I’m using it in the lightest sense. I'll elide the flame war if that's OK? I appreciate it's

[Standards] component-s2s

Hi folks, I’m -1 on the component-s2s spec. I’ve been backwards and forwards a number of times on whether to use the veto or not, and I’m using it in the lightest sense. I think we should have a wider discussion before we publish an experiment to replace the existing historical and ST

[Standards] XMPP APIs and duplicate extension elements

If I'm not mistaken, no XMPP specification forbids duplicate extension elements, i.e. same element name and namespace, as direct child of the stanza element. For example message … foo xmlns=http://example.org; data='42' / foo xmlns=http://example.org; data='1337' / /message is perfectly

Re: [Standards] XMPP APIs and duplicate extension elements

On 4 Feb 2015, at 11:37, Florian Schmaus f...@geekplace.eu wrote: If I'm not mistaken, no XMPP specification forbids duplicate extension elements, i.e. same element name and namespace, as direct child of the stanza element. For example message … foo xmlns=http://example.org; data='42' /