Pubsub event message with SHIM information holding multiple subscriptions should have the name='SubID'.

Yes, there are many more than these 3 changes. These are just a few that popped up either from the forums or when I was doing some other coding. All of them logged many years (and a couple of versions of the spec) ago.

As for whether it is acceptable, that is why I said Guus should be consulted, ultimately it is his decision.

This will probably break the Smack code as well, as it adheres to the same version of the spec.

Sorry, didn't knew that. I only browsed Jira for issues, I could fix.
On the other hand suggests that there are only 3 sub tasks to fix and you are done. In reality though, there a far more changes (like 30?) between 1.8 and 1.13. Implementing either all of them or none of them, seems like a hard task.
I don't see it that critical, if only parts of a newer specification are implemented.

This should only be fixed as part of the parent task. On it's own it makes for inconsistent version adherence. By changing this without updating the rest of pubsub to the latest version, it will not be consistent with any specific version of the spec.

I haven't been keeping tabs, but unless someone has updated the code to a later version, pubsub is currently compliant with version 1.8.

Guus should be consulted to see if this is acceptable.

Note: That is why it wasn't fixed a long time ago. The fix is trivial, but the spec update is not.

Yes, it was. Now fixed.

Hi Robin, Is this still valid?