[Top] [All Lists]

Re: values of notify ":priority" tag

2005-12-06 02:07:40

On Mon, Dec 05, 2005 at 01:31:58PM -0000, Nigel Swinson wrote:
"This makes it sound like there are hard and fast rules between
user status notifications and the setting of the priority parameter,
yet the discussion is very brief and doesn't elaborate to rigorously
define all those rules.  I also feel uneasy about adding syntax that
permits only 3 levels of priority.   I think we should either drop the
parameter, or extend it to allow an almost arbitrary number and style
of priority statuses, even if we only define 3 for now.  I'm thinking
of the Priority/X-Priority/X-MSMail-Priority mess in mail headers.
I'd suggest a string which could be used with the relational draft to
do numeric comparisons if desired."

Personally, I wonder why priorities are considered so useful and the
option is not just dropped, but that's me.

Assuming the majority likes :priority, I agree to the above and suggest
to allow arbitrary values, like :from does, because each method might
use different data formats as sender.  For SMTP, it is certainly a
mail address, for SMS a phone number or an alphanumeric sender tag.
Saying :priority must be defined as in RFCs relevant to e-mail makes
sense for SMTP, but not neccessarily for SMS.

I think the notify extension should focus on being a framework to be
filled with methods that interface different media, inside and outside
the internet.