:subject versa :message. Aaron, Dilyan in favor of adding :subject.
Michael wants to keep using :message.
I need to poll people on this, as I don't hear a clear consensus on
this. Please pick one of the following:
3). I don't care whether we have :message or :subject, but we should
have only one of them.
Option 3, or better still, make it a positional argument, ie the last argument.
:o)
Issue #4:
Dilyan suggested to add "expiration" parameter/option to the notify
action. While I see some utility in this option, I am reluctant to
extend the document so late in the game, unless there is strong
support from the WG. I would recommend to add this option in a
separate document. Opinions?
I've heard a couple of voices for this feature, but no rough consensus yet.
Hint for people who want this functionality: please provide some text
for inclusion into the document. This will improve your chances of
winning the argument ;-).
I'm not interested in this, it sounds like an unnecessary layer of complexity
based on the premise that the transport is frequently unreliable. It sounds to
me like a feature more useful on the client that receives the notifications to
filter (perhaps using sieve) out the "old" notifications and bin them.
Issue #5:
Ken (in a private message) has suggested to extend "body" test
instead of introducing a new "extract_text" test. Opinions?
I agree.
Issue #6:
Arnt wants to be able to do "send notification over XMPP, if can be
delivered immediately. Otherwise send it over SMS".
This issue needs further discussion.
Aaron replied that he likes the idea. Anybody else?
Other alternative are:
1). Add a test to check if a notification method (specified as an URI)
can deliver the notification immediately.
Opinions?
I have a hesitant preference for a test to check the capabilites of a
notification method. Perhaps a set of variables in a namespace.
=======
+ A new issues (# 8): the Sieve notify document needs to describe what
should happen if a parameter specified in two ways in the same notify
call: as a notify action parameter and as an URI parameter to the method
parameter, for example:
notify :method
"xmpp:tim(_at_)example(_dot_)com?message;subject=SIEVE"
:message "You got mail";
(assume for a moment that the content of the :message gets translated
into the subject of the resulting notification)
Options suggested so far:
4). specify both the notify and the URI parameters is an error.
Option 4. Preferably parse time error.
Nigel