- From: Jon Ferraiolo <jon.ferraiolo@adobe.com>
- Date: Tue, 18 Jan 2005 04:55:33 -0800
- To: Robin Berjon <robin.berjon@expway.fr>, Cameron McCormack <cam-www-svg@aka.mcc.id.au>
- Cc: www-svg@w3.org
Robin,
I'm not sure exactly what you mean relative to namespace defaulting. I have
been assuming that the default namespace for events would be the XML Events
namespace in order to have backwards-compatibility with what existed before
events were namespaced. For example, ev:event="click" would be equivalent
to ev:event="xevents:click", where 'xevents:' was defined to
"http://www.w3.org/2001/xml-events". Do you agree?
Jon
At 01:58 AM 1/18/2005, Robin Berjon wrote:
>Cameron McCormack wrote:
>>If I have a handler element and the event type is given by only a local
>>name, how is this resolved? Will it use the default namespace at that
>>point in the document, or the empty namespace (the one you specify with
>>xmlns="", whatever it is called) or the XML Events namespace?
>> <svg xmlns="http://www.w3.org/2000/svg" ...>
>> <handler ev:event="click">
>> // ...
>> </handler>
>> </svg>
>
>The content of ev:event is a QName that follows the namespace defaulting
>rules that apply to attributes. This would be in the spec except that the
>XML Events chapter has disappeared (sic), or it would be in the XML Events
>1.1 draft except I don't see that the Forms WG (or HTML WG, I can never
>remember) has published it (sic).
>
>Either way, the 'click' above is in no namespace, also denoted {}click for
>clarity.
>
>--
>Robin Berjon
> Research Scientist
> Expway, http://expway.com/
>
Received on Tuesday, 18 January 2005 13:01:45 UTC