W3C home > Mailing lists > Public > www-svg@w3.org > June 2006

Re: SVG12: ev:event vs namespaces

From: Dean Jackson <dean@w3.org>
Date: Fri, 9 Jun 2006 08:00:10 +1000
Message-Id: <61B85801-D507-4104-8CD8-98350699FF88@w3.org>
Cc: www-svg@w3.org, Robin Berjon <robin.berjon@expway.fr>
To: Bjoern Hoehrmann <derhoermi@gmx.net>

[doh! forgot the subject again. anyone got a nice bookmarklet for
generating an email response to a message in the w3c archives?]

 >>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

 >The current draft is more confused in this regard than the previous
 >To mention just one problem, the definition is
 >  ev:event = "<string>"
 >    The name of the event to handle. This attribute is in the XML
 >    Events namespace. See event list for a list of all supported
 >    events and [XML-Events] for the definition of the ev:event
 >    attribute.
 > And the draft uses syntax like ev:event="ev:click" in examples. How
 > would one go from "<string>" and "as defined in XML Events" to "some
 > sort of qualified name, as defined in SVG Tiny 1.2"?

This was an error. We've now removed all the instances of namespace
qualified event attribute values in examples.

As the previous response said, the ev:event attribute references the
definition from XML Events, with a limited set of allowed values. All
events are in the XML Events namespace.


Received on Thursday, 8 June 2006 22:00:19 UTC

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