On Tue Jul 19 21:31:13 2011, XMPP Extensions Editor wrote:
1. Is this specification needed to fill gaps in the XMPP protocol
stack or to clarify an existing protocol?
Yes.
2. Does the specification solve the problem stated in the
introduction and requirements?
No. No problem is defined; see below.
3. Do you plan to implement this specification in your code? If
not, why not?
[N/A, I don't really do clients]
4. Do you have any security concerns related to this specification?
No.
5. Is the specification accurate and clearly written?
Not entirely.
I'm concerned by the final rule in ยง2.3, which suggests that *any*
presence update from the contact SHOULD break the lock. I think this
rule is fine; however I think a short discussion of when to ignore
this rule would be useful.
Also, it would be useful to have a paragraph somewhere explaining
what the user experince the specification keeps talking about
actually is - that is, what the goal of the specification is.
Dave.
--
Dave Cridland - mailto:[email protected] - xmpp:[email protected]
- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
- http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
