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

[www-svg] <none>

From: Dean Jackson <dino@w3.org>
Date: Fri, 9 Jun 2006 07:56:42 +1000
Message-Id: <A64D2202-2815-4244-8051-FB847AA03C3A@w3.org>
Cc: Robin Berjon <robin.berjon@expway.fr>, www-svg@w3.org
To: Bjoern Hoehrmann <derhoermi@gmx.net>

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

 >The current draft is more confused in this regard than the previous  
one.
 >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.

Thanks,

Dean
Received on Thursday, 8 June 2006 21:56:54 GMT

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