startPrefixMapping(self,
prefix,
uri)

Begin the scope of a prefix-URI Namespace mapping.

The information from this event is not necessary for normal Namespace
processing: the SAX XML reader will automatically replace prefixes for
element and attribute names when the
http://xml.org/sax/features/namespaces feature is true (the default).

There are cases, however, when applications need to use prefixes in
character data or in attribute values, where they cannot safely be
expanded automatically; the start/endPrefixMapping event supplies the
information to the application to expand prefixes in those contexts
itself, if necessary.

Note that start/endPrefixMapping events are not guaranteed to be
properly nested relative to each-other: all startPrefixMapping events
will occur before the corresponding startElement event, and all
endPrefixMapping events will occur after the corresponding endElement
event, but their order is not guaranteed.

startElementNS(self,
name,
qname,
attrs)

Signals the start of an element in namespace mode.

The name parameter contains the name of the element type as a (uri,
localname) tuple, the qname parameter the raw XML 1.0 name used in the
source document, and the attrs parameter holds an instance of the
Attributes class containing the attributes of the element.

The uri part of the name tuple is None for elements which have no
namespace.

characters(self,
content)

Receive notification of character data.

The Parser will call this method to report each chunk of character
data. SAX parsers may return all contiguous character data in a single
chunk, or they may split it into several chunks; however, all of the
characters in any single event must come from the same external entity so
that the Locator provides useful information.

ignorableWhitespace(self,
content)

Receive notification of ignorable whitespace in element content.

Validating Parsers must use this method to report each chunk of
ignorable whitespace (see the W3C XML 1.0 recommendation, section 2.10):
non-validating parsers may also use this method if they are capable of
parsing and using content models.

SAX parsers may return all contiguous whitespace in a single chunk, or
they may split it into several chunks; however, all of the characters in
any single event must come from the same external entity, so that the
Locator provides useful information.