- From: Doug Schepers <schepers@w3.org>
- Date: Mon, 01 Mar 2010 14:31:09 -0500
- To: Domenico Strazzullo <nst@dotuscomus.com>
- CC: www-svg@w3.org
Hi, Nico- Domenico Strazzullo wrote (on 2/26/10 11:44 AM): > > I am totally pleased that this issue is being resolved and I approve the > resolutions. Good to hear. Your extensive authoring experience makes your feedback especially valuable. > - One red object in the spatial region of one clipped green object in an > upper layer. > - The two objects appear then one next to the other. > - They both have events; the red says "I'm red" while the green says > "I'm green". > > Question: what do you expect the end user to expect when she clicks on > the red object? Unless we all want to reconvert to prestidigitation > games developers, we would like our user to see the "I'm red" message. Yes, that was our reasoning, too. > This is not an errata, it's a clarification at best. Just as a clarification, a clarification is an erratum. :) Nico surely knows this, but for those who don't know what the errata are... Think of a errata document as a FAQ: when we get a question about an unclear part of the spec (from either developers or implementers), we publish the clarification so other implementers can find it easily, to help interoperability. >The point is, a > spec, however exhaustive it may be, cannot possibly cover all of its > subjects in a binary like manner, as it is not addressing AI enabled > machines after all, or is it? Agreed. There will always be things that fall through the cracks. >And my question to the implementors is > this: in doubt, why not simply ask, communicate, so that possible doubts > on interpretation are dissipated? Who pays cash when dealing with > oddities that are so reminiscent of the old html-css demons? The > developers. Please, think also of the time and energy that go into these > discussions to solve incertitudes that should be solved beforehand. As a developer, I have to agree. We are actually in a pretty good position now, with a mature, experienced community, and with most of the major browser implementers active in the SVG WG and asking these questions. Since the SVG WG operates in public now, that also helps close the feedback loop between code authors and implementers. We will continue to air these issues in public to solicit feedback. Regards- -Doug Schepers W3C Team Contact, SVG and WebApps WGs
Received on Monday, 1 March 2010 19:31:12 UTC