I've just been reading through the current version of
http://xmpp.org/extensions/xep-0280.html and have a couple of
comments:
In example 14, we have:
<message xmlns='jabber:client'
from='[email protected]'
to='[email protected]/home'
type='chat'>
<forwarded xmlns='urn:xmpp:forward:0'>
<received xmlns='urn:xmpp:carbons:1'/>
<message>... </message>
</forwarded>
</message>
I think it makes more sense to have the forwarded payload inside the
received payload, instead of the reverse. I think this because the
forwarded message is a feature of the carbon, rather than the reverse
(Carbons depends on Forwarding, Forwarding doesn't depend on Carbons).
Second is regarding
"Upon receiving an inbound or outbound gone chat state (as a carbon
copy) for a given conversation, that conversation SHOULD be removed
from user display"
I think we should be avoiding mandating (at least non-security
critical) UI features - I think this is a simple tweak from normative
'SHOULD' to 'is suggested' or similar.
/K
