xml::dom::parser(1) [redhat man page]

PARSER(1)						User Contributed Perl Documentation						 PARSER(1)

NAME

       XML::DOM::Parser - An XML::Parser that builds XML::DOM document structures

SYNOPSIS

	use XML::DOM;

	my $parser = new XML::DOM::Parser;
	my $doc = $parser->parsefile ("file.xml");

DESCRIPTION

       XML::DOM::Parser extends XML::Parser

       The XML::Parser module was written by Clark Cooper and is built on top of XML::Parser::Expat, which is a lower level interface to James
       Clark's expat library.

       XML::DOM::Parser parses XML strings or files and builds a data structure that conforms to the API of the Document Object Model as described
       at <http://www.w3.org/TR/REC-DOM-Level-1>.  See the XML::Parser manpage for other additional properties of the XML::DOM::Parser class.
       Note that the 'Style' property should not be used (it is set internally.)

       The XML::Parser NoExpand option is more or less supported, in that it will generate EntityReference objects whenever an entity reference is
       encountered in character data. I'm not sure how useful this is. Any comments are welcome.

       As described in the synopsis, when you create an XML::DOM::Parser object, the parse and parsefile methods create an XML::DOM::Document
       object from the specified input. This Document object can then be examined, modified and written back out to a file or converted to a
       string.

       When using XML::DOM with XML::Parser version 2.19 and up, setting the XML::DOM::Parser option KeepCDATA to 1 will store CDATASections in
       CDATASection nodes, instead of converting them to Text nodes.  Subsequent CDATASection nodes will be merged into one. Let me know if this
       is a problem.

Using LWP to parse URLs
       The parsefile() method now also supports URLs, e.g. http://www.erols.com/enno/xsa.xml.  It uses LWP to download the file and then calls
       parse() on the resulting string.  By default it will use a LWP::UserAgent that is created as follows:

	use LWP::UserAgent;
	$LWP_USER_AGENT = LWP::UserAgent->new;
	$LWP_USER_AGENT->env_proxy;

       Note that env_proxy reads proxy settings from environment variables, which is what I need to do to get thru our firewall. If you want to
       use a different LWP::UserAgent, you can either set it globally with:

	XML::DOM::Parser::set_LWP_UserAgent ($my_agent);

       or, you can specify it for a specific XML::DOM::Parser by passing it to the constructor:

	my $parser = new XML::DOM::Parser (LWP_UserAgent => $my_agent);

       Currently, LWP is used when the filename (passed to parsefile) starts with one of the following URL schemes: http, https, ftp, wais,
       gopher, or file (followed by a colon.)  If I missed one, please let me know.

       The LWP modules are part of libwww-perl which is available at CPAN.

perl v5.8.0							    2000-01-31								 PARSER(1)

XML::DOM::Attr(3)					User Contributed Perl Documentation					 XML::DOM::Attr(3)

NAME

       XML::DOM::Attr - An XML attribute in XML::DOM

DESCRIPTION

       XML::DOM::Attr extends XML::DOM::Node.

       The Attr nodes built by the XML::DOM::Parser always have one child node which is a Text node containing the expanded string value (i.e.
       EntityReferences are always expanded.) EntityReferences may be added when modifying or creating a new Document.

       The Attr interface represents an attribute in an Element object.  Typically the allowable values for the attribute are defined in a
       document type definition.

       Attr objects inherit the Node interface, but since they are not actually child nodes of the element they describe, the DOM does not
       consider them part of the document tree. Thus, the Node attributes parentNode, previousSibling, and nextSibling have a undef value for Attr
       objects. The DOM takes the view that attributes are properties of elements rather than having a separate identity from the elements they
       are associated with; this should make it more efficient to implement such features as default attributes associated with all elements of a
       given type. Furthermore, Attr nodes may not be immediate children of a DocumentFragment. However, they can be associated with Element nodes
       contained within a DocumentFragment. In short, users and implementors of the DOM need to be aware that Attr nodes have some things in
       common with other objects inheriting the Node interface, but they also are quite distinct.

       The attribute's effective value is determined as follows: if this attribute has been explicitly assigned any value, that value is the
       attribute's effective value; otherwise, if there is a declaration for this attribute, and that declaration includes a default value, then
       that default value is the attribute's effective value; otherwise, the attribute does not exist on this element in the structure model until
       it has been explicitly added. Note that the nodeValue attribute on the Attr instance can also be used to retrieve the string version of the
       attribute's value(s).

       In XML, where the value of an attribute can contain entity references, the child nodes of the Attr node provide a representation in which
       entity references are not expanded. These child nodes may be either Text or EntityReference nodes. Because the attribute type may be
       unknown, there are no tokenized attribute values.

   METHODS
       getValue
	   On retrieval, the value of the attribute is returned as a string.  Character and general entity references are replaced with their
	   values.

       setValue (str)
	   DOM Spec: On setting, this creates a Text node with the unparsed contents of the string.

       getName
	   Returns the name of this attribute.

perl v5.16.3							    2000-01-31							 XML::DOM::Attr(3)