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

Re: SVG12: ev:event vs namespaces

From: Jon Ferraiolo <jonf@adobe.com>
Date: Wed, 2 Nov 2005 06:02:17 -0800
Message-ID: <6ECA24BE410D994496A2AE995367C5C8301C18@namail3.corp.adobe.com>
To: "Bjoern Hoehrmann" <derhoermi@gmx.net>
Cc: <www-svg@w3.org>

This is the SVG WG response to you're the thread that begins with:
And where your last response (copied below) was:

Thanks for your follow-on comments on this issue. We agree that unqualified event names belong in the XML Events namespace. We have reviewed the specification to make sure that it is clear that this is true. The latest draft now says the 'event' attribute can only accept a particular discrete set of event names (with a hyperlink to a section which provides the list of values), and then the referenced section now says that all of the events that are allowed are in the XML Events namespace. 

Please reply to this mail within two weeks if these changes do not
address your concerns.




From: Bjoern Hoehrmann <derhoermi@gmx.net> 
Date: Sun, 29 May 2005 14:38:43 +0200
To: Robin Berjon <robin.berjon@expway.fr> 
Cc: www-svg@w3.org 
Message-ID: <429bb65e.66345171@smtp.bjoern.hoehrmann.de> 

* Robin Berjon wrote:
>Bjoern Hoehrmann wrote:
>> This does not make much sense considering that NMTOKEN is a superset of
>> QName. Please change the schema such that it does not include such re-
>> dundant choices. Further, please change the prose such that it is clear
>> how events are to be referred to; if that involves QNames, this would
>> require to define the resolution algorithm, and if it involves names
>> without prefixes, it would likely require to define the default name-
>> space for such values.
>Yes, of course we meant NCName here. This has been fixed in the schema 
>and we are adding the prose explaining that the resolution algorithm 
>matches that of XSLT QNames, and not that of XML Schema.

This does not satisfy me. Now that ev:listener has been added to SVG
Tiny 1.2, you would also need to say the algorithm for ev:listener's
event attribute. Looking at the draft I also note that it does not
discuss the event name in case of invalid and absent values for the
attribute, and I strongly object to ev:event="x" matching "x" events
in any namespace, it's guranteed that authors will use the simple
unprefixed forms and hence cause a lot of trouble using new and
custom events. Please define the things mentioned above and change
the algorithm to default to the XML Events namespace.
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Wednesday, 2 November 2005 14:02:44 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:05 UTC