6 Jun
2024
6 Jun
'24
2:56 p.m.
Hi Nicolas,
Le jeudi 6 juin 2024, 09:47:17 UTC+2 Nicolas Cedilnik a écrit :
What do you say if we allow context =
'mobile', 'desktop' or 'advanced',
with 'advanced' meaning that rules are defined as children of the
element, eg <always context='advanced'>
<when day="monday" xmlns='custom:namespace-0:0'>
<start>9:00</start>
<end>17:00</end>
</when>
<something-very-advanced xmlns='custom:namespace-1:0'
type='super-subtle' />
</always>
We could make that similar to bookmarks extensions in the sense that
clients MUST preserve what's in there, especially if they don't
understand the content?
That could do it. My main concern is to let the door open for extensions, and
describing that clients MUST preserve as you suggest seems OK to me.
You should also specify what to do with unknown "<context>" (do we
"ignore"
the notification rule? Do we just ignore the context?).
Also with your system, we can't specify at the same time "desktop/mobile"
and
advanced. And I would like to say something like "notify me for my office chats
on my mobile during working hours, otherwise silence them".
I would actually put "mobile" and "desktop" in child elements of
<context> (or
whatever name used for filtering.
Also, if several rules are allowed, we have to manage conflict: what if I have
something which tell me to notify me for a room on mobile, and just after
something telling me the opposite? I suppose that the latter one must be used,
but it should be specified.
Best,
Goffi