XEP-0050 or XEP-0030 too restrictive?

[vArDo]

Here's query generated by Gajim to discover ad-hoc commands of given bot with response from it: http://gajim.pastebin.com/f2f311d43

Such answer in Gajim is ignored because it does not have node="http://jabber.org/protocol/commands" attribute in query node (as shown in example here: http://www.xmpp.org/extensions/xep-0050.html#retrieve ). Psi on the other hand accepts it.

In XEP-0030 it is said that: "If the request included a 'node' attribute, the response SHOULD mirror the specified 'node' attribute to ensure coherence between the request and the response." ( http://www.xmpp.org/extensions/xep-0030.html#info-nodes ).

So, there is no MUST for inclusion of node attribute in response - guys on Psi dev channel say, in such case, client should handle reponses without it as valid (as Psi does).

The question is: should Gajim accept such responses or ignore these (as it does now)?

All this discussion is because of SleekXMPP which does not include node attribute in XEP-0030 responses.

[asterix]

I would say that Gajim should handle it (it's only a should in the XEP) AND SleekXMPP should ad the node.

What about changing the XEP to use MUST?

[vArDo]

I've sent SleekXMPP patch to Kev (with these changes SleekBot? nicely interacts with Gajim, so there is no other hidden bug here, I suppose).

About changing XEP - Kev said that 'changes can be made but something like that could be hard work'. We could post this issue on XSF Standards mailing list. I've found discussion exactly about it (but from server-side): http://mail.jabber.org/pipermail/standards/2007-March/014675.html

Stpeter suggests adding 'MUST' to XEP. What's more important he agrees (but in server implementation) that queries without 'node' attribute should be ignored.