• From: Stefan Haustein <stefan.haustein@t...>
• To: XML-Dev Mailing list <xml-dev@i...>
• Date: Fri, 07 Jan 2000 00:03:39 +0100

Hello,

can anybody explain to me why in DOM2 both

    public Attr setAttributeNodeNS(Attr newAttr);
and 
    public Attr setAttributeNode(Attr newAttr);

exist, but only one remove method

    public Attr removeAttributeNode(Attr oldAttr);

Also, the current DOM2 spec says that mixing 
simple and namespace-aware methods should be 
avoided and will result in unpredictable behavior.

There are five methods in DOM2.Element that I 
would normally expect to default to the element 
namespace if available:  

 public String getAttribute(String name);
 public void setAttribute(String name, String value);
 public void removeAttribute(String name);
 public Attr getAttributeNode(String name);
 public NodeList getElementsByTagName(String name);

What is the reason for leaving the semantics open to the
implementation instead of reusing them as convenience
methods?

Best regards

Stefan

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo@i... the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Follow-Ups:
  • Re: two little DOM2 questions...
    • From: Ray Whitmer <ray@x...>

• References:
  • Re: Wish lists for the Holidays
    • From: "Lauren Wood" <lauren@s...>

• Prev by Date: Requirement for attributes with schema scope
• Next by Date: Re: Namespace question: Do attributes inherit the element's namespace?
• Previous by thread: Re: Wish lists for the Holidays
• Next by thread: Re: two little DOM2 questions...
• Index(es):
  • Date
  • Thread