From 7681f739297eac622516c49942fc34070ac779be Mon Sep 17 00:00:00 2001 From: Christian Hammond Date: Thu, 2 Sep 2004 08:05:12 +0000 Subject: [PATCH] Wrote about urgency levels. --- docs/ChangeLog | 5 ++++ docs/notification-spec.xml | 49 +++++++++++++++++++++++++++++++++++++- 2 files changed, 53 insertions(+), 1 deletion(-) diff --git a/docs/ChangeLog b/docs/ChangeLog index f233708..62ffc10 100644 --- a/docs/ChangeLog +++ b/docs/ChangeLog @@ -1,3 +1,8 @@ +Thu Sep 02 01:05:01 PDT 2004 Christian Hammond + + * notification-spec.xml: + - Wrote about urgency levels. + Thu Sep 02 00:53:17 PDT 2004 Christian Hammond * notification-spec.xml: diff --git a/docs/notification-spec.xml b/docs/notification-spec.xml index 1a890e1..cb15eeb 100644 --- a/docs/notification-spec.xml +++ b/docs/notification-spec.xml @@ -391,7 +391,54 @@ Urgency Levels - Write me! + + Notifications have an urgency level associated with them. This defines + the importance of the notification. For example, "Your computer is on + fire" would be a critical urgency. "Joe Bob signed on" would be a low + urgency. + + Urgency levels are defined as follows: + + Urgency Levels + + + + Level + Name + + + + + 0 + Low + + + 1 + Medium (Normal) + + + 2 + High + + + 3 + Critical + + + +
+ + Developers must use their own judgement when deciding the urgency of a + notification. Typically, if the majority of programs are using the same + level for a specific type of urgency, other applications should follow + them. + + + Server implementations may use urgency information how they see fit. + Possible implementations may keep critical notifications on the screen + until the user manually closes them, which is our recommendation. However, + there are no user interface guidelines in this area. +