This touches probably all namespace related DOM functions.
I dealt with the problem at the beginning of developing for XML::LibXML.
The problem is, how much of the DOM specification should be repeated in
the documentation of XML::LibXML.
Maybe the specification should be mentioned at the beginning of each
sections. Somewhat in the style of "Many functions listed here are
extensively documented in the DOM Level 3 specification. Please refer to
the specification for extensive documentation."
And then indicate the DOM functions like in "appears in DOM Level X".
Would that be sufficient?
Christian
On Tue, 2007-11-27 at 07:15 -0500, fergus mcmenemie via RT wrote:
Show quoted text> Tue Nov 27 07:15:04 2007: Request 31001 was acted upon.
> Transaction: Ticket created by fergus
> Queue: XML-LibXML
> Subject: explaination for createElementNS XML/LibXML/Document.pod is wrong
> Broken in: (no value)
> Severity: Normal
> Owner: Nobody
> Requestors: fergus@twig.demon.co.uk
> Status: new
> Ticket <URL:
http://rt.cpan.org/Ticket/Display.html?id=31001 >
>
>
> >createElementNS
> >
> > $element = $dom->createElementNS( $namespaceURI, $qname );
> >
> >This function creates a new Element Node bound to the DOM with
> >the name $nodename and placed in the given namespace.
>
> The explanation does not describe the $qname argument. This combined
> with the lack of any user-level overview of how namespaces are dealt
> with by libxml makes it extremely difficult for ME to figure out
> how to use this stuff properly.
>
> Desperately need some decent examples or guides on how to create, modify
> and parse XML documents containing namespaces.
