Patent Publication Number: US-2020285607-A1

Title: Processing structured data

Description:
CROSS REFERENCE TO RELATED APPLICATIONS 
     This application is a continuation of U.S. patent application Ser. No. 15/393,481, filed Dec. 29, 2016, entitled “PROCESSING STRUCTURED DATA,” which is a continuation of U.S. patent application Ser. No. 13/894,118, filed May 14, 2013, entitled “PROCESSING STRUCTURED DATA,” which is a continuation of U.S. patent application Ser. No. 11/777,110, filed Jul. 12, 2007, entitled “PROCESSING STRUCTURED DATA,” which is a continuation-in-part of U.S. patent application Ser. No. 11/581,211 filed Oct. 13, 2006, now U.S. Pat. No. 7,761,459, which is a continuation-in-part of U.S. patent application Ser. No. 10/272,077, filed Oct. 15, 2002, now U.S. Pat. No. 7,133,857, issued Nov. 7, 2006, all of which are herein incorporated by reference. 
    
    
     FIELD OF THE INVENTION 
     The present invention relates to the field of structured data files in computer systems. More specifically, the present invention relates to the processing of structured data in an efficient manner. 
     BACKGROUND OF THE INVENTION 
     Structured data represents a large portion of the information accessed on the Internet and other computer networks. There are several reasons why structured data is so popular. American Standard Code for Information Interchange (ASCII) and its extensions, such as Unicode Transformation Formats UTF-8 and UTF-16 are among the most common standard encoding formats. Text encoding puts information into a format that is easily readable by a human, thus it is easy for programmers to develop and debug applications. Lastly, textual encoding is extensible and adding new information may be as simple as adding a new key-value pair. 
     Recently, Extensible Markup Language (XML) has been growing in popularity. XML is a markup language for documents containing structured information. Unlike its predecessor, Hypertext Markup Language (HTML), where tags are used to instruct a web browser how to render data, in XML the tags are designed to describe the data fields themselves. XML, therefore, provides a facility to define tags and the structural relationships between them. This allows a great deal of flexibility in defining markup languages to using information. Because XML is not designed to do anything other than describe what the data is, it serves as the perfect data interchange format. 
     XML, however, is not without its drawbacks. Compared with other data formats, XML can be very verbose. Processing an XML file can be very CPU and memory intensive, severely degrading overall application performance. Additionally, XML suffers many of the same problems that other software-based text-based processing methods have. Modern processors prefer binary data representations, particularly ones that fit the width of the registers, over text-based representations. Furthermore, the architecture of many general-purpose processors trades performance for programmability, thus making them ill-suited for text processing. Lastly, the efficient parsing of structured text, no matter the format, can present a challenge because of the added steps required to handle the structural elements. 
     Most current XML parsers are software-based solutions that follow either the Document Object Model (DOM) or Simple API for XML (SAX) technologies. DOM parsers convert an XML document into an in-memory hierarchical representation (known as a DOM tree), which can later be accessed and manipulated by programmers through a standard interface. SAX parsers, on the other hand, treat an XML document as a stream of characters. SAX is event-driven, meaning that the programmer specifies an event that may happen, and if that event occurs, SAX gets control and handles the situation. 
     In general, DOM and SAX are complementary, not competing, XML processing models, each with its own benefits and drawbacks. DOM programming is programmer-friendly, as the processing phase is separate from application logic. Additionally, because the data resides in the memory, repetitive access is fast and flexible. However, DOM requires that the entire document data structure, usually occupying 7-10 times the size of the original XML document, be loaded into the memory, thus making it impractical for large XML documents. SAX, on the other hand, can be efficient in parsing large XML documents (at least when only small amounts of information need to be processed at once), but it maintains little of the structural information of the XML data, putting more of a burden on programmers and resulting in code that is hardwired, bulky, and difficult to maintain. 
     What is needed is an application program interface (API) that combines the best attributes of both DOM and SAX parsing. 
     BRIEF DESCRIPTION OF THE INVENTION 
     The present invention provides a fast and efficient way of processing structured data by utilizing an intermediate file to store the structural information. The structured data may be processed into a Binary mask Format (BMF) file which may serve as a starting point for post-processing. A tree structure built on top of the BMF file may be constructed very quickly, and also takes up less space than a DOM tree. Additionally, BMF records may reside entirely in the memory and contain structural information, allowing SAX-like sequential data access. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate one or more embodiments of the present invention and, together with the detailed description, serve to explain the principles and implementations of the invention. 
       In the drawings; 
         FIG. 1  is a block diagram illustrating a layer view of an apparatus for efficiently processing structured data in accordance with an embodiment of the present invention. 
         FIG. 2  is a block diagram illustrating an apparatus for efficiently processing structured data in accordance with an embodiment of the present invention. 
         FIG. 3  is a timing diagram illustrating the operation of the hardware in accordance with an embodiment of the present invention. 
         FIG. 4  is a flow diagram illustrating a method for modifying the content of a target string in a BMF file from an old string to a new string in accordance with an embodiment of the present invention. 
         FIG. 5  is a diagram illustrating a BMF record format in accordance with an embodiment of the present invention. 
         FIG. 6  is a flow diagram illustrating a method for efficiently processing a structured data file, the structured data file including one or more pieces of content, in accordance with an embodiment of the present invention. 
     
    
    
     DETAILED DESCRIPTION 
     Embodiments of the present invention are described herein in the context of a system of computers, servers, and software. Those of ordinary skill in the art will realize that the following detailed description of the present invention is illustrative only and is not intended to be in any way limiting. Other embodiments of the present invention will readily suggest themselves to such skilled persons having the benefit of this disclosure. Reference will now be made in detail to implementations of the present invention as illustrated in the accompanying drawings. The same reference indicators will be used throughout the drawings and the following detailed description to refer to the same or like parts. 
     In the interest of clarity, not all of the routine features of the implementations described herein are shown and described. It will, of course, be appreciated that in the development of any such actual implementation, numerous implementation-specific decisions must be made in order to achieve the developer&#39;s specific goals, such as compliance with application- and business-related constraints, and that these specific goals will vary from one implementation to another and from one developer to another. Moreover, it will be appreciated that such a development effort might be complex and time-consuming, but would nevertheless be a routine undertaking of engineering for those of ordinary skill in the art having the benefit of this disclosure. 
     In accordance with the present invention, the components, process steps, and/or data structures may be implemented using various types of operating systems, computing platforms, computer programs, and/or general purpose machines. In addition, those of ordinary skill in the art will recognize that devices of a less general purpose nature, such as hardwired devices, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), or the like, may also be used without departing from the scope and spirit of the inventive concepts disclosed herein. 
     For purposes of this disclosure, a structured data file is any file containing content as well as some information regarding the structural organization of the content. The present invention provides a fast and efficient way of processing structured data by utilizing an intermediate file to store the structural information. The structured data may be processed into a Binary mask Format (BMF) file which may serve as a starting point for post-processing. A tree structure built on top of the BMF file may be constructed very quickly, and also takes up less space than a DOM tree. Additionally, BMF records may reside entirely in the memory and contain structural information, allowing SAX-like sequential data access. However, while this document will describe advantages that the present invention provides over DOM or SAX, one of ordinary skill in the art will recognize that the present invention need not be limited to replacing DOM or SAX, and can be expanded to non-XML type processing. 
       FIG. 1  is a block diagram illustrating a layer view of an apparatus for efficiently processing structured data in accordance with an embodiment of the present invention. The apparatus may comprise three layers. A hardware text processing accelerator  100 , occupying the lowest layer, may offer the horsepower necessary to relieve the central processing unit (CPU) from the most processor intensive part of the task. On top of the hardware text processing accelerator  100  may lie a device driver layer  102  that is responsible for the communication between the hardware text processing accelerator  100  and a software layer  104 . The software layer  104  may be designed to offer maximum flexibility and further improve the performance. It may export APIs that are standard-compliant. 
     The hardware may be designed such that it may quickly match multiple patterns against an incoming data stream.  FIG. 2  is a block diagram illustrating an apparatus for efficiently processing structured data in accordance with an embodiment of the present invention. A text processor  200  may be the core of the accelerator. It may be composed of multiple Finite State Machines (FSMs) that process an incoming document in parallel. The output may be the BMF file. It also may set several result registers (not pictured). A PCI interface  202  may handle all handshaking between the hardware and a server PCI bus  204 . A memory controller  206  may receive commands from the PCI interface  202  and convert the PCI address to on-board memory address space. It also may access the board memory accordingly. Configuration registers  208  may determine the configuration of the text processing pipeline and the organization of the memory controller  206 . It may load default values from configuration ROM  210 . Some of the values may be modified by software through the PCI interface  202 . The Configuration ROM  210  may store the default setting of the text processor configuration. It also may store the configuration map of FPGAs. 
     A document buffer  212  may store the incoming document. This may be a Synchronous Dynamic Random Access Memory (SDRAM). Paging may be utilized if the incoming document is larger than the total buffer size. A BMF buffer  214  may store the output BMF files, together with several other text processor result register values. This may be a separate SDRAM, although in one embodiment of the present invention it may share a single SDRAM with the document buffer. A string cache  216  may buffer the incoming data to smooth out and speed up SDRAM access. A DMA engine  218  may grab the frame data from server main memory and send it back the BMF file. 
       FIG. 3  is a timing diagram illustrating the operation of the hardware in accordance with an embodiment of the present invention. A reset  300  may be sent out by the host computer system, or by a specific application. While reset is asserted, the configuration may be loaded from ROM to the configuration registers. The text processor then may be set to a default state according to the configuration registers. When software calls the device driver, a start signal  302  may be sent through the PCI to indicate the beginning of a document processing cycle. Then the PCI master may assert a frame number  304  to indicate the beginning of a write transaction. The PCI master may then drive the address/data  306  to the PCI bus. The PCI target interface may respond, causing the DMA to read the document into the SDRAM document buffer  308 . There may also be certain PCI commands reserved to update the configuration registers. The memory controller may be activated by PCI command. It may start processing data in the string buffer  310 . It also may send sync signals to the memory controller. The transferring and processing may be repeated. 
     The PCI target may sense a valid window to send data. Then the PCI master may assert the frame number to indicate the beginning of a read transaction  312 . The PCI target holds the bus. The DMA engine may then transfer the BMF and result register data to main memory  314 . When all the data is transferred, the PCI target interface may send an end signal to the device driver  316 . The next document processing cycle may start again with a start signal from the device driver  318 . 
     The output of the hardware is a BMF. In one embodiment of the present invention, the BMF defines a binary record format that is used to describe various fields in a structured data file. It can be viewed as a two-dimensional field of bits. Each piece of useful information in the structured data file may correspond to a record in the BMF file. A record may comprise a starting offset and length of a target string in the structured data file. It may also comprise the depth value, node type, and bit-wide flags. These will be discussed in more detail below. The total length of a record may be an integer multiple of a 32-bit word—the width of the memory bus in most commercial architectures. Two record types may be defined: a full version of 12 bytes in length, and a compressed version of 8 bytes in length. The full version may be based on the assumption that both the string length and the starting offset are 32-bits wide, whereas the compressed version may assume a 16-bit field, which translates to a maximum length of 65536 bytes. 
       FIG. 4  is a flow diagram illustrating a method for modifying the content of a target string in a BMF file from an old string to a new string in accordance with an embodiment of the present invention. At  400 , a piece of memory of the length of the new string may be allocated. At  402 , the new string may be filled into the memory. At  404 , a record in the BMF file corresponding to the old string may be located. At  406 , a corresponding bit flag for the record may be changed from relative offset to absolute offset. The first time a file is converted to BMF form, relative offsets may be used. However, as soon as a modification is made to a specific string, it can often be difficult if not impossible to continue to track the relative offset for that string. Therefore, absolute offsets may be utilized for all modified strings. At  408 , an offset value in the BMF record for the old string may be replaced with a pointer value of the new string in memory. At  410 , a length field in the BMF record for the old string may be replaced with the length of the new string. 
     There are at least three types of possible BMF file modes: read-only mode, read-modify mode, and read-modify-add mode. In read-only mode, records representing various types of nodes may be placed sequentially into a BMF file, leaving no empty records. For example, a leaf-level element may be represented as a record for the starting tag, 2n records (one of r property name and one property value) for in properties, and one record for the text for the element, and finally one record for an ending tag name. The presence of the ending tag record may be used for document validation. 
     The read-modify mode may be identical to read-only mode except each record allows for limited write-access, meaning content can be altered, but not added. 
     The read-modify-add mode allows complete write-access, which is done by embedding empty records into the file. 
     The record format may be picked to efficiently represent the necessary information of the original data structure. It may also be made less efficient on purpose to speed up downstream processing. 
       FIG. 5  is a diagram illustrating a BMF record format in accordance with an embodiment of the present invention. A control word  500  may be thirty-two bits in total in this embodiment. This may include a depth value  502  of sixteen bits. The depth value may indicate the depth of a tag in the hierarchy of tags in the structured data file. Thus, the first tag in a file will have a depth of zero, whereas if another starting tag appears before an ending tag for the first tag, that second starting tag will have a depth of one. A content type  504  may be provided, which indicates what type of information the content is. In an embodiment of the present invention, the following value/content type pairs may be used in this field: 
     
       
         
           
               
             
               
                 TABLE 1 
               
             
            
               
                   
               
               
                 Content Types and Corresponding Values 
               
            
           
           
               
               
               
            
               
                 Content 
                   
                   
               
               
                 Type Value 
                 Content name 
                 Example 
               
               
                   
               
            
           
           
               
               
               
            
               
                 0 
                 Starting Tag 
                 &lt;   example   &gt; 
               
               
                 1 
                 Ending Tag 
                 &lt;/   example   &gt; 
               
               
                 2 
                 Property Name 
                 &lt;example    property1   =”this”&gt; 
               
               
                 3 
                 Property Value 
                 &lt;example property2 =”   that   ”&gt; 
               
               
                 4 
                 Text 
                 &lt;example&gt;    tasty       fruit     
               
               
                   
                   
                 &lt;/example&gt; 
               
               
                 5 
                 Comment 
                 &lt;!- -    this       is       a       comment    - -&gt; 
               
               
                 6 
                 Processing Instruction 
                 &lt;?    ......    ?&gt; 
               
               
                 7 
                 Markup declaration I 
                 &lt;![   CDATA   [...&lt;&lt;&lt;&gt;&gt;&gt;...]]&gt; 
               
               
                   
                 name 
                   
               
               
                 8 
                 Markup declaration I 
                 &lt;![CDATA[   ...&lt;&lt;&lt;&gt;&gt;&gt;...   ]]&gt; 
               
               
                   
                 value 
                   
               
               
                 9 
                 Markup declaration II 
                 &lt;!   ENTITY    ...&gt; 
               
               
                   
                 name 
                   
               
               
                 10 
                 Markup declaration II 
                 &lt;!ENTITY    ...   &gt; 
               
               
                   
                 value 
                   
               
               
                 11 
                 Entity reference 
                 &amp;example.bib; 
               
               
                 12 
                 Property Name Value 
                 &lt;example    property1=”this”   &gt; 
               
               
                   
                 Pair 
                   
               
               
                 13 
                 Starting tag for empty 
                 &lt;   example   /&gt; 
               
               
                   
                 element 
               
               
                   
               
            
           
         
       
     
     A modification indicator  506  may also be provided, which indicates whether or not the record has been modified. This is important because, as described above, if the record has been modified, then the offset field will contain the real pointer value, not a relative offset. An insertion indicator  508  may indicate that data was inserted in between two existing records. Once again, this is important in determining how to utilize the offset field. If the insertion indicator is set to 1, it indicates that the offset field contains a pointer to an external piece of memory, one that can be used to add child nodes to the current node. An end of document indicator  510  may indicate whether the tag is the last one in the document. This can be important because in some embodiments, ending tags may be ignored when encoding the BMF file in order to save space. Therefore, the last tag in the BMF file may not correspond to the last tag in the structured data file. 
     A current record in use field  512  may be used to indicate that a record has been deleted. If the field is set to 0, the record may be safely ignored because it has been deleted. A name space indicator  514  may indicate whether or not there is a name space within the token (which may be represented by an “=” sign). A reference bit  516  may indicate when there is an external reference, such as an “&amp;” in a text string. 
     There may be one or more reserved bits  518 , which are set aside for future uses. Lastly, a length field  520  may indicate the length of the content. 
     The BMF file, together with the original data in memory, completely describes the original data and its inherent data structure. Traversing the data structure may be easily accomplished using the BMF records. Higher level applications and processing are therefore facilitated by using the BMF. To make it easily accessible and readily integrated to higher level application and processing, device drivers and an application programming interface (API) may be built on top of the BMF. 
       FIG. 6  is a flow diagram illustrating a method for efficiently processing a structured data file, the structured data file including one or more pieces of content, in accordance with an embodiment of the present invention. The structured data file may be an extensible markup language file. The process loops through each piece of content. In another embodiment of the present invention, the process loops through each relevant piece of content. Relevancy can be determined by the programmer and may be chosen so as to minimize the amount of space used for a BMF file. At  600 , a BMF record is created in a BMF file, the BMF record corresponding to the piece of content. At  602 , an off set may be stored in the BMF record indicating a starting position for the piece of content relative to the beginning of the structured data file. At  604 , a depth of the piece of content may be stored in the BMF record, the depth indicating a level in a hierarchy of tags in the structured data file. At  606 , a content type of the piece of content may be stored in the BMF record, the content type indicating a type of information for the piece of content. The content type may take many forms, such as a starting tag, ending tag, property name, property value, text, comment, processing instruction, markup declaration name, markup declaration value, external reference, property name pair, etc. At  608 , a length may be stored for the piece of content in the BMF record. 
     At  610 , a modification indicator for the piece of content may be stored in the BMF record, the modification indicator indicating if the BMF record has been modified and the modification indicator initially set to indicate that no modification has been made. At  612 , an insertion indicator for the piece of content may be stored in the BMF record, the insertion indicator indicating if the BMF record has been inserted between two existing BMF records and the insertion indicator initially set to indicate that the BMF record has not been inserted between two existing BMF records. At  614 , an end of document indicator for the piece of content may be stored in the BMF record, the end of document indicator indicating if the BMF record corresponds to a last piece of content in the structured data file. At  616 , a current record in use field may be stored for the piece of content in the BMF record, the current record in use field indicating whether the piece of content has been deleted. 
     The following example may be used to illustrate an embodiment of the present invention. One of ordinary skill in the art will recognize that this is merely an example and should not be read to be limiting in any way. Suppose an XML file as follows: 
     
       
         
           
               
             
               
                   
               
             
            
               
                 &lt;?xml version=″1.0″ encoding=″US-ASC  ″?&gt; 
               
               
                 &lt;benchmark:database xmlns:benchmark=″http://example.com/xml/ 
               
               
                 benchmark″&gt; 
               
               
                 &lt;benchmark:person id=″012345″&gt; 
               
               
                 &lt;benchmark:email name=″Name012345″ /&gt; 
               
               
                 &lt;!--Edited with XML spy v4.2 --&gt; 
               
               
                 &lt;benchmark:line1&gt;L i n e 1 012345 012345&lt;/benchmark:line1&gt; 
               
               
                 &lt;/benchmark:person&gt; 
               
               
                 &lt;/benchmark:database&gt; 
               
               
                   
               
               
                     indicates data missing or illegible when filed 
               
            
           
         
       
     
     An embodiment of the present invention may ignore ending tags and produce the following BMF file: 
                                                                     Starting                   End of   Current   Name                    offset       Token   Modify   Insertion   Document   Record    space                   32    Depth   type   Indicator   Indicator   Indicator   in use   indicator   Reference   un-   Length       bit   5 bit   4 bit   1 bit   1 bit   1 bit   1 bit   1 bit   Indicator   used   16 bit                                                                            2   0   6   0   0   0   1   0   0   0   38       42   0   0   0   0   0   1   1   0   0   18       61   0   2   0   0   0   1   1   0   0   14       78   0   3   0   0   0   1   0   0   0   35       116   1   0   0   0   0   1   1   0   0   16       133   1   2   0   0   0   1   0   0   0   2       137   1   3   0   0   0   1   0   0   0   4       147   2   0   0   0   0   1   1   0   0   15       163   2   2   0   0   0   1   0   0   0   4       169   2   3   0   0   0   1   0   0   0   10       185   1   5   0   0   0   1   0   0   0   25       218   2   0   0   0   0   1   1   0   0   15       234   2   4   0   0   0   1   0   0   0   23       0   0   0   0   0   1   1   0   0   0   0                    
The packet BMF records are:
 
     
       
         
           
               
               
               
               
               
               
               
               
               
               
               
             
               
                   
               
             
            
               
                 00000000000000000000000000000010 
                 00000 
                 0110 
                 0 
                 0 
                 0 
                 1 
                 0 
                 0 
                 0 
                 00100110 
               
               
                 00000000000000000000000000101010 
                 00000 
                 0000 
                 0 
                 0 
                 0 
                 1 
                 1 
                 0 
                 0 
                 00010010 
               
               
                 00000000000000000000000000111101 
                 00000 
                 0010 
                 0 
                 0 
                 0 
                 1 
                 1 
                 0 
                 0 
                 00001110 
               
               
                 00000000000000000000000001001110 
                 00001 
                 0011 
                 0 
                 0 
                 0 
                 1 
                 0 
                 0 
                 0 
                 00100011 
               
               
                 00000000000000000000000001110100 
                 00001 
                 0000 
                 0 
                 0 
                 0 
                 1 
                 1 
                 0 
                 0 
                 00010000 
               
               
                 00000000000000000000000010000101 
                 00001 
                 0010 
                 0 
                 0 
                 0 
                 1 
                 0 
                 0 
                 0 
                 00000010 
               
               
                 00000000000000000000000010001001 
                 00010 
                 0011 
                 0 
                 0 
                 0 
                 1 
                 0 
                 0 
                 0 
                 00000110 
               
               
                 00000000000000000000000010010011 
                 00010 
                 0000 
                 0 
                 0 
                 0 
                 1 
                 1 
                 0 
                 0 
                 00001111 
               
               
                 00000000000000000000000010100011 
                 00010 
                 0010 
                 0 
                 0 
                 0 
                 1 
                 0 
                 0 
                 0 
                 00000100 
               
               
                 00000000000000000000000010101001 
                 00001 
                 0011 
                 0 
                 0 
                 0 
                 1 
                 0 
                 0 
                 0 
                 00001010 
               
               
                 00000000000000000000000010111001 
                 00010 
                 0101 
                 0 
                 0 
                 0 
                 1 
                 0 
                 0 
                 0 
                 00011001 
               
               
                 00000000000000000000000011011010 
                 00010 
                 0000 
                 0 
                 0 
                 0 
                 1 
                 1 
                 0 
                 0 
                 00001111 
               
               
                 00000000000000000000000011101010 
                 00010 
                 0100 
                 0 
                 0 
                 0 
                 1 
                 0 
                 0 
                 0 
                 00010111 
               
               
                 00000000000000000000000000000000 
                 00000 
                 0000 
                 0 
                 1 
                 1 
                 1 
                 0 
                 0 
                 0 
                 00000000 
               
               
                   
               
            
           
         
       
     
     Currently, DOM (a W3C standard) is well-defined and the most widely used representation of XML&#39;s inherent hierarchy. DOM represents an XML document as a tree structure, with the elements, attributes, and text defined as nodes. A node may have a single parent node, sibling nodes and child nodes. For example, consider the following XML snippet: 
     
       
         
           
               
               
             
               
                   
               
             
            
               
                   
                 &lt;A&gt;text0 &lt;B1 attrName=″val″&gt;&lt;C1&gt;text1&lt;/C1&gt;&lt;C2&gt;text2 
               
               
                   
                 &lt;/C2&gt;&lt;/B1&gt;&lt;B2&gt;&lt;B3&gt;&lt;/B3&gt;&lt;/A&gt; 
               
               
                   
               
            
           
         
       
     
     The node named “B1” has a parent node named “A.” It also has two child nodes, respectively named “C1” and “C2.” The “C1” node is the first child node as it appears before the “C2” node in the XML text. The “B1” node also has sibling nodes named “text0”, “B2” and “B3” respectively. The text node named “Text 0” is the previous sibling of the node “B1.” The “B2” is the next sibling for “B1” node as it appears before “B3” node. By the same token, the “B3” node is the next sibling node for “B2” node. Also the first and only child of the “C1” node is a text node named “text.” 
     DOM treats attribute nodes differently. In the XML snippet shown above, the “B1” node doesn&#39;t treat its attribute named “attrName” as its child. 
     Many DOM node types have their equivalent BMF types. For example, an element type in DOM corresponds to the starting tag. DOM, however, does not have a node type corresponding to BMF&#39;s ending tag type. 
     Since a BMF file completely describes the inherent structure in the data file as one can navigate the document by scanning across of BMF records and keeping track of their token types. And they don&#39;t need any additional descriptors to identify its siblings, children, or parent. The inclusion of ending tag as a type is important. DOM resorts to various pointers and complex data structures to maintain the hierarchical information of XML, and does not have a node type corresponding to ending tag. SAX returns ending tags of XML, but discards them by default. In contrast, a BMF file maintains the ending tag in memory as a record so the structure information of an XML file is unambiguous. Consider the following examples: 
     Example 1 
     &lt;a&gt;&lt;b1&gt;&lt;/b1&gt;&lt;b2&gt;&lt;/b2&gt;&lt;a&gt; 
     Example 2 
     &lt;a&gt;&lt;b1&gt;&lt;b2&gt;&lt;/b2&gt;&lt;b1&gt;&lt;/a&gt; 
     If the ending tags are missing, the corresponding BMF have identical record types 
     Starting tag for a 
     Starting tag for b1 
     Starting tag for b2 
     Without ending tags, it will be difficult to determine whether b2 is the sibling, or child, of b2. With ending tags, one can clearly tell the relationship between b1 and b2 in the above examples. 
     In Example 1, the token types are: 
     Starting tag for a 
     Starting tag for b1 
     Ending tag for b1 
     Starting tag for b2 
     Ending tag for b2 
     Ending tag for a 
     In Example 2, the token types are: 
     Starting tag for a 
     Starting tag for b1 
     Starting tag for b2 
     Ending tag for b2 
     Ending tag for b1 
     Ending tag for a 
     To tell whether b1 is a sibling, or child, of b2, one can calculate the depth value of each tags. In example 1, b1 and b2 both have the same depth value so they are siblings. In example 2, b1 and b2 have depth value of 1 and 2 respectively, so b2 is the child of b1. 
     When the depth value is included in the BMF records, ending tags can be ignored to save space. 
     For BMF records to maintain structural information of XML documents containing empty elements (elements having no content, denoted by a specially defined starting tag that indicates an empty element), there are at least two options. 
     The first option is to assign the starting tag of an empty element a content type that is different from a starting tag of a non-empty element. Consider the following XML: &lt;root&gt;&lt;element/&gt;&lt;/root&gt;. Its corresponding BMF file may contain three BMF records: the first one for “root” as a non-empty starting tag, the second for “element” as an empty starting tag, and the third for the ending tag for “&lt;/root&gt;.” When the BMF records choose to include a depth value, the ending tag&#39;s BMF record may be ignored. 
     The second option is to use the same content type for both empty and non-empty starting tag, and to insert a BMF record of a “dummy” ending tag for an empty starting tag. The dummy tag can take various forms, all aiming to preserve the structural integrity of the BMF file. For example, one can insert a BMF record corresponding to a zero-length ending tag at the end of an empty element. Or alternatively, he can add a BMF record for “&gt;” or “/&gt;” to emulate the ending tag. It is called a “dummy” because it doesn&#39;t represent a real ending tag. 
     In some cases, it would be beneficial to have some additional way to speed up the traversal of document structure. For example, a BMF record can contain a 32-bit descriptor which contains the reference in various forms, such as the relative index value, absolute index value or memory address, of the next sibling or first child, but not both, as there is additional storage overhead for having such descriptors. 
     The reference to the next sibling makes it possible to jump to the next sibling without scanning the BMF records between the current record and its next sibling. The reference to the first child record makes it possible to jump to the first child without scanning the BMF records between the current record and first child record. Some of the other possible references a BMF record can have are parent, root, previous sibling, last child. It should be noted that the reference to a child node is actually a reference to a record corresponding to the child node, as the nodes are represented in the intermediate file as records. Likewise the reference to a next sibling node is actually a reference to a record corresponding to the next sibling node. 
     When a record does not have a sibling, it is convenient to use some constant value to denote the absence of the sibling. That constant value can be thought of as a special reference value. For example, a constant value of zero at the descriptor field could be interpreted as there is not sibling or child, depending on the actual usage of the descriptor. 
     The concept outlined in this specification can also be applied to processing JSON (JavaScript Object Notion). JSON is invented to allow web browsers to exchange data structure easily as a JSON string has browser&#39;s default support, such as Javascript&#39;s eval( ). 
     XML and JSON are similar as both represent tree-structure and are human readable. The basic textual content types in JSON are keys and values. Consider the following XML file: 
     
       
         
           
               
             
               
                   
               
             
            
               
                 &lt;menu id=″file″ value=″File″&gt; 
               
               
                  &lt;popup&gt; 
               
               
                   &lt;menuite  &gt;&lt;value&gt;New&lt;/value&gt;&lt;onclick&gt;CreateNewDoc( ) &lt;/onclick&gt; 
               
               
                 &lt;/menuitem&gt; 
               
               
                   &lt;menuitem&gt;&lt;value&gt;Open&lt;/value&gt;&lt;onclick&gt;OpenDoc( ) &lt;/onclick&gt;  
               
               
                 &lt;/menuitem&gt; 
               
               
                   &lt;menuitem&gt;&lt;value&gt;Close&lt;/value&gt;&lt;onclick&gt;CloseDoc( ) &lt;/onclick&gt;  
               
               
                 &lt;/menuitem&gt; 
               
               
                  &lt;/popup&gt; 
               
               
                 &lt;/menu&gt; 
               
               
                 The equivalent JSON representation is shown below 
               
               
                 (″menu″    
               
               
                  ″id″: ″file″, 
               
               
                  ″value″: ″File″, 
               
               
                  ″popup″: { 
               
               
                   ″menuitem″ :    
               
               
                    (″value″: ″New″, ″onclick″: ″CreateNewDoc( )″), 
               
               
                    (″value″: ″Open″, ″onclick″: ″OpenDoc ( )″), 
               
               
                    (″value″: ″Close″, ″onclick″: ″CloseDoc ( )″), 
               
               
                   } 
               
               
                  } 
               
               
                 }} 
               
               
                   
               
               
                     indicates data missing or illegible when filed 
               
            
           
         
       
     
     The ‘{’ and ‘}’ in JSON delimit a new level of nesting. For example, in the JSON example above, the key “popup” has a value following “:” and because there is a ‘{,’ it just indicates that there is a next level of nesting, potentially consisting of a new key value pair. To extend BMF for JSON processing, there needs to be content types “left brace” and “right brace” respectively corresponding to ‘{’ and ‘}.’ Consider the JSON file below:
         {“menu”: {“id”: “file”}}       

     To create its corresponding BMF file, one inserts a BMF record for ‘{’ whose content type is left brace, a BMF record for the “menu” whose content type is “key,” a BMF record for “{” whose content type is “left brace,” a BMF record for “id” whose content type is “key,” a BMF record for “file” whose content type is “value,” a BMF record for “}” whose content type is “right brace,” and a BMF record for “}” whose content type is “light brace.” 
     Table 2 summarize the content types for the above example. 
     
       
         
           
               
             
               
                 TABLE 2 
               
             
            
               
                   
               
               
                 Content types and values for the JSON files 
               
            
           
           
               
               
               
            
               
                 JSON Content Value 
                 JSON Content Name 
                 Example 
               
               
                   
               
               
                 0 
                 Left brace 
                     {   “id”: “file”} 
               
               
                 1 
                 Right brace 
                 {“id”: “file”   }     
               
               
                 2 
                 Key 
                 {“   id   ”: “file”} 
               
               
                 3 
                 Value 
                 {“id”: “   file   ”} 
               
               
                   
               
            
           
         
       
     
     While embodiments and applications of this invention have been shown and described, it would be apparent to those skilled in the art having the benefit of this disclosure that many more modifications than mentioned above are possible without departing from the inventive concepts herein. The invention, therefore, is not to be restricted except in the spirit of the appended claims.