W3C home > Mailing lists > Public > www-svg@w3.org > May 2005

RE: [SVGMobile12] namespace events are not qualified?

From: MAHE Vincent RD-TECH-REN <v.mahe@francetelecom.com>
Date: Thu, 26 May 2005 12:15:34 +0200
Message-ID: <B30D6148F304A743A53B9B44751CDB9A02EAB18A@FTRDMEL2.rd.francetelecom.fr>
To: "Mark Birbeck" <mark.birbeck@x-port.net>, "Jon Ferraiolo" <jon.ferraiolo@adobe.com>, "Ola Andersson" <Ola.Andersson@ikivo.com>
Cc: "KONO Masahiko" <kono.masahiko@canon.co.jp>, <www-svg@w3.org>


Yes, these discussions should happen on other forums.
Personnally, my only goal is to have SVG Tiny be as precise as possible to avoid issues and interoperability problems even if sometimes some Issues come from other format connex to SVG.
We have the same issue concerning urlRequest or SVGTimer APIs which should rather be defined in a more global "Web Application" WG.

We seriously lack time concerning SVGT and if you want to give it a chance to be adopted by the mobile industry, we can not wait too long that W3C solves this internal issues.

If I understand well what you say, it means an e-mail should be sent to the DOM WG about this issue.

Regards,

Vincent

-----Message d'origine-----
De : Mark Birbeck [mailto:mark.birbeck@x-port.net] 
Envoyé : jeudi 26 mai 2005 11:59
À : MAHE Vincent RD-TECH-REN; 'Jon Ferraiolo'; 'Ola Andersson'
Cc : 'KONO Masahiko'; www-svg@w3.org
Objet : RE: [SVGMobile12] namespace events are not qualified?

Hi Vincent,

> Since everybody seems to agree on this, has Ola been given an action 
> to
update the
> Tiny spec. accordingly so that it becomes clearer for every developer 
> &
implementer
> which reads the spec. ?

I know we now agree on the problem, but I don't agree that the solution is some sort of 'clarification' in SVG Tiny. If the problem really is there, then DOM 3 Events needs to be corrected.

I say "if", because it may be that there is an aspect of the implementation that the authors haven't explained that makes this problem go away. But my experience of trying to implement this last year was that it was not possible to make DOM 3 Events and DOM 2 Events co-exist.

There are a couple of ways that this might be solved, but I assume that discussion should take place on a different forum.

Regards,

Mark
 

Mark Birbeck
CEO
x-port.net Ltd.

e: Mark.Birbeck@x-port.net
t: +44 (0) 20 7689 9232
w: http://www.formsPlayer.com/
b: http://internet-apps.blogspot.com/

Download our XForms processor from
http://www.formsPlayer.com/ 
Received on Thursday, 26 May 2005 10:15:49 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:30 GMT