Skip Menu |
 

This queue is for tickets about the XML-LibXML CPAN distribution.

Report information
The Basics
Id: 31001
Status: resolved
Priority: 0/
Queue: XML-LibXML

People
Owner: Nobody in particular
Requestors: fergus [...] twig.demon.co.uk
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: (no value)
Fixed in: (no value)



Subject: explaination for createElementNS XML/LibXML/Document.pod is wrong
Download (untitled) / with headers
text/plain 564b
Show quoted text
>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.
Subject: Re: [rt.cpan.org #31001] explaination for createElementNS XML/LibXML/Document.pod is wrong
Date: Wed, 28 Nov 2007 00:42:40 +0100
To: bug-XML-LibXML [...] rt.cpan.org
From: Christian Glahn <christian.glahn [...] lo-f.at>
Download (untitled) / with headers
text/plain 1.6k
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.
Download (untitled) / with headers
text/plain 124b
I just did what Christian suggested. Since there are no further comments by the original reporter, I'm closing this ticket.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.