Ignore:
Timestamp:
Jan 30, 2013, 6:03:41 PM (7 years ago)
Author:
nmedfort
Message:

edits

File:
1 edited

Legend:

Unmodified
Added
Removed
  • docs/Working/icXML/background-fundemental-differences.tex

    r2866 r2872  
    11\subsection {Sequential vs. Parallel Paradigm}
    22
    3 % Sequential: bytes through layers
    43Xerces---like all traditional XML parsers---processes XML documents sequentially.
    54Each character is examined to distinguish between the
     
    98validation and content processing modes.
    109
    11 
    1210In other words, Xerces belongs to an equivalent class applications termed FSM applications\footnote{
    13   Herein FSM applications are software systems whose behavior is defined by the inputs,
     11  Herein FSM applications are considered software systems whose behaviour is defined by the inputs,
    1412  current state and the events associated with transitions of states.}.
    1513Each state transition indicates the processing context of subsequent characters.
    1614Unfortunately, textual data tends to be unpredictable and any character could induce a state transition.
    1715
    18 % Unfortunately, textual data tends to consist of variable-length strings sequenced in
    19 % unpredictable patterns.
    20 % Each character must be examined in sequence because any character could be a state transition until deemed otherwise.
    21 
    22 
    23 
    24 
    25 % Parallel: blocks/segments/buffers through layers
    2616Parabix-style XML parsers utilize a concept of layered processing.
    27 A block of source text is transformed into a set of lexical bit streams,
     17A block of source text is transformed into a set of lexical \bitstream{}s,
    2818which undergo a series of operations that can be grouped into logical layers,
    2919e.g., transposition, character classification, and lexical analysis.
    3020Each layer is pipeline parallel and require neither speculation nor pre-parsing stages\cite{HPCA2012}.
    31 % In adapting to the requirements of the Xerces sequential parsing API,
    32 % however, the resultant parallel bit streams may out-of-order \wrt{} the source document.
    33 % Hence they must be amalgamated and iterated through to produce sequential output.
    3421To meet the API requirements of the document-ordered Xerces output,
    35 the results of the Parabix processing layers must be interleaved to produce the equivalent behavior.
     22the results of the Parabix processing layers must be interleaved to produce the equivalent behaviour.
Note: See TracChangeset for help on using the changeset viewer.