Hi XMPP community,
 
I have read and implemented some XEP which are in Draft status and now I have some suggestions to improve them.
 
In particular I suggest the following:
 
XEP-0107: User Mood:
The sample and the XML Schema tell me differen things. The sample suggests:
<happy>
    <ecstatic xmlns='http://ik.nu/ralphm'/>
</happy>

but the XML Schema says, moods are an empty element. Furthermore, what's the benefit to include sub-elements like this one? I mean, if it can just be any element, nobody will understand it, except both users have the same client.
 
I suggest to either remove the ability to included "sub-moods" or to change the XML Schema.
It would also be easier to implement if a mood is defined as attribute and using an enumeration like:
<xs:restriction base="xs:string">
                    <xs:enumeration value="happy" />
                    <xs:enumeration value="afraid" />
</xs:restriction>
 
 
XEP-0115: Entity Capabilities
The node attribute confuses me!
node='http://code.google.com/p/exodus#QgayPKawpkPSDYmwT/WM94uAlu0='
Shouldn't the result of a Service Discovery request with *no* node attribute be exactly the same as if a node attribute is included, at least in the case of Entity Capabilities (namely it should list all features and identities of the "root" node)? So is it just there for backwards-compatibility (as the spec says), but has no other meaning?
If I include Entity Capabilities in my presence I sent, should I just set the node attribute to the name of the software I am using? I still don't understand why this is important because actually only the verfication string is important, no?
 
 
XEP-0172: User Nickname:
4. Use Cases should not list Multi-User Chat and Waiting List as use cases, since they have been removed/deprecated, no!?
 
 
XEP-0184: Message Delivery Receipts:
It should be more clear about the Message type, which should be used for receipts. I assume it is always type="normal" even if I send a receipt to a chat message.
 
 
XEP-0308: Last Message Correction
Why does it discourage "to correct messages older than the most recent"? Technically it should not matter, which message you correct. And if a client has lost track of an older message... well it just won't be corrected then. Afaik in Skype you can also correct messages, other than the most recent one. (not quite sure though).
Maybe it should be expanded on "messages which belong to the same chat session, i.e. have the same thread id".
 
 
That's it for now. Let know, what you think!
Kind regards
Christian
 

Reply via email to