* Sam Ruby wrote:
>I'm a bit concerned about precedence rules (what happens if there is an
>href attribute *AND* an atom:href attribute?). What makes most sense
>here is for a prohibition disallowing such in any exension. I would
>support such a rule.
Allowing either atom:href or href is not a good idea either, you have to
check for both attributes each time you access it and if having both at
the same time is not allowed or causes undefined behavior, you need to
avoid that, turning
x.setAttributeNS(null, 'foo', 'bar');
into
if (x.hasAttributeNS(null, 'foo') &&
x.hasAttributeNS(atom, 'foo'))
{
throw "...";
}
else
{
x.removeAttributeNS(atom, 'atom');
x.setAttributeNS(null, 'foo', 'bar');
}
This might not be too relevant for some Atom implementations, but if you
implement Atom through SVG 1.2 + sXBL + ECMAScript, the result would not
be pretty.
--
Bj�rn H�hrmann � mailto:[EMAIL PROTECTED] � 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/
