Package spade :: Module RDF0Parser :: Class RDF0Parser
[hide private]
[frames] | no frames]

Class RDF0Parser

source code


FIPA RDF Content Language Parser

Instance Methods [hide private]
 
__init__(self) source code
 
encodeTag(self, tag, content) source code
 
encodeInitTag(self, tag) source code
 
encodeEndTag(self, tag) source code
 
encodeInitTagAttr(self, tag, attr, value) source code
 
encodeOneLineTag(self, tag1, tag2, value) source code
 
encode(self, content)
Content Encoding
source code
 
startDocument(self)
Receive notification of the beginning of a document.
source code
 
startPrefixMapping(self, prefix, uri)
Begin the scope of a prefix-URI Namespace mapping.
source code
 
startElementNS(self, name, qname, attributes)
Signals the start of an element in namespace mode.
source code
 
endElementNS(self, name, qname)
Signals the end of an element in namespace mode.
source code
 
characters(self, buff)
Receive notification of character data.
source code
 
parse(self, s) source code

Inherited from xml.sax.handler.ContentHandler: endDocument, endElement, endPrefixMapping, ignorableWhitespace, processingInstruction, setDocumentLocator, skippedEntity, startElement

Method Details [hide private]

__init__(self)
(Constructor)

source code 
Overrides: xml.sax.handler.ContentHandler.__init__

startDocument(self)

source code 

Receive notification of the beginning of a document.

The SAX parser will invoke this method only once, before any other methods in this interface or in DTDHandler (except for setDocumentLocator).

Overrides: xml.sax.handler.ContentHandler.startDocument
(inherited documentation)

startPrefixMapping(self, prefix, uri)

source code 

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.

Overrides: xml.sax.handler.ContentHandler.startPrefixMapping
(inherited documentation)

startElementNS(self, name, qname, attributes)

source code 

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.

Overrides: xml.sax.handler.ContentHandler.startElementNS
(inherited documentation)

endElementNS(self, name, qname)

source code 

Signals the end of an element in namespace mode.

The name parameter contains the name of the element type, just as with the startElementNS event.

Overrides: xml.sax.handler.ContentHandler.endElementNS
(inherited documentation)

characters(self, buff)

source code 

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.

Overrides: xml.sax.handler.ContentHandler.characters
(inherited documentation)