Page: http://wiki.cocoondev.org/Wiki.jsp?page=SAX , version: 13 on Fri Feb 21 
13:13:53 2003 by SylvainWallez

- Some people thought "That's inconvenient! Why can't we handle the document in 
a sequential manner instead?". So they invented (particulary a guy named David 
Meggison invented) SAX, the __S__imple (or "Streaming") __A__pi (for) 
__X__mldocuments.
?                                                                               
                                                                                
                                                                          ^^

+ Some people thought "That's inconvenient! Why can't we handle the document in 
a sequential manner instead?". So they invented (particulary a guy named David 
Meggison invented) SAX, the __S__imple (or "Streaming") __A__pi (for) __X__ML 
documents.
?                                                                               
                                                                                
                                                                          ^^^

- The pipeline starts with a Generator that knows how to read __something__ 
(for example an XML document) and from that generate a stream of SAX events 
("document begins" etc). Then there might be a bunch of other components that 
modifies the stream of SAX events, for instance using XSLT or some other 
transforming algorithm.
+ The pipeline starts with a Generator that knows how to compute or read 
__something__ (for example parsing an XML document) and from that generate a 
stream of SAX events ("document begins" etc). Then there might be a bunch of 
other components that modifies the stream of SAX events, for instance using 
XSLT or some other transforming algorithm.
?                                                        +++++++++++            
                   ++++++++

- In the end there is the Serializer that listens to the SAXEvents and 
translates them to normal text.
+ In the end there is the Serializer that listens to the SAX events and 
translates them to a binary data stream. This transformation to binary data can 
be as simple as "translating" SAX events to text (the usual form of an XML 
document), or as complex as producing PDF from XSL:FO or a JPEG image from SVG.
- When the XMLGenerator looks at an XML file and sees "<doc>" it fires the 
SAXEvent "element 'doc' begins". 
?                                                                             ^

+ When the XMLGenerator looks at an XML file and sees "<doc>" it fires the SAX 
event "element 'doc' begins". 
?                                                                             ^^

- A Transformer might take it from here, perhaps instructed to transform every 
"<doc>" element into a "<document>" element. So when this Transformer recieves 
the "element 'doc' begins", it fires the SAXEvent "element 'document' begins".
?                                                                               
                                                                                
                                          ^

+ A Transformer might take it from here, perhaps instructed to transform every 
"<doc>" element into a "<document>" element. So when this Transformer recieves 
the "element 'doc' begins", it fires the SAX event "element 'document' begins".
?                                                                               
                                                                                
                                          ^^

- In the other end of the pipeline, when the serializer recieves the SAXEvent 
"element 'document' begins", it converts it to the text "<document>".
?                                                                       ^

+ In the other end of the pipeline, when the serializer recieves the SAX event 
"element 'document' begins", it converts it to the text "<document>".
?                                                                       ^^



Reply via email to