[standards-jig] NEW: Message Delivery Semantics (JEP-0079)

Casey Crabb crabbkw at nafai.dyndns.org
Thu Apr 17 03:44:29 UTC 2003


Some nit-picks:
Section 2.3, last sentence before example 6 reads
"To disable any defined semantics for a thread, the user sends an
empty <semantics/> scoped to that thread:"

I believe it would be more clear to say
"To disable all defined semantics for a thread, the user sends an
empty <semantics/> scoped to that thread:"

Any sounds like you can selectively disable semantics.


Echoing other comments:
 Section 7.1.1 "expire-in" condition":
   It needs to be made clear which receiving entity is the starting
   point for the countdown.

 Section 7.1.2 "expire-on" condition:
   Either provide a link to the documentation of ISO-8601 or provide
   it inline with samples.

 Section 7.1.3 "match-resource" condition:
   The examples need to be more explicit: 'Sending to
   "user at host/home/laptop" would match logins "user at host/home" or
   "user at host/h" or "user at host/home/laptop", but not the login
   "user at host/work/desktop"'  etc.

 Section 7.2:
  in the table, I would make the description of "fail" be something
  like 'Reply to the "from" with an <error/>, and only the <rule/>(s)
  that triggered this action.



Other thoughts:
It seems like this would be a good place to add guaranteed delivery
rules as well.

You might want a use cases section that describes some of the common
use cases: ie, "don't store this message until user logs in", "store
this for a very specific resource until it logs in or time limit is
hit", etc.


Thoughts?
--
Casey
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/standards/attachments/20030416/7ede8bb5/attachment.sig>


More information about the Standards mailing list