Hi, Folks-
We should put together a use case and requirements document (or section
of the spec) to scope out this work. I know it seems like makework, but
it can help resolve many issues later on, and serve as a measure of the
maturity and success of the spec in meeting its goals.
I've started a simple wiki page to kick this off:
http://www.w3.org/2008/webapps/wiki/Web_Notifications
Regards-
-Doug Schepers
W3C Team Contact, SVG and WebApps WGs
Drew Wilson wrote (on 2/23/10 5:26 PM):
2010/2/23 Jonas Sicking <jo...@sicking.cc>
The same is not true for the suggest notification API. Several
proposals have been put forward that do not rely on fallback.
One of the reasons I stepped back from this discussion is because it
seemed clear that we weren't going to make progress on solutions until
we had agreement on requirements (specifically, the amount of
interaction that we want to enable in these notifications). The
non-fallback proposals that have been put forward aren't acceptable to
me for the same reasons that Jonas is opposed to the fallback proposals
- we both have a different vision for what the requirements should be.
I'd like to see us focus on gaining some consensus around requirements,
because I think the rest of these disagreements will mostly resolve
themselves once we do that.
-atw
