Patent Application
20140258851
Flow format documents and fixed format documents are widely used and have different purposes. Flow format documents organize a document using complex logical formatting objects such as sections, paragraphs, columns, and tables. As a result, flow format documents offer flexibility and easy modification making them suitable for tasks involving documents that are frequently updated or subject to significant editing. In contrast, fixed format documents organize a document using basic physical layout elements such as text runs, paths, and images to preserve the appearance of the original. Fixed format documents offer consistent and precise format layout making them suitable for tasks involving documents that are not frequently or extensively changed or where uniformity is desired. Examples of such tasks include document archival, high-quality reproduction, and source files for commercial publishing and printing. Fixed format documents are often created from flow format source documents. Fixed format documents also include digital reproductions (e.g., scans and photos) of physical (i.e., paper) documents.
In situations where editing of a fixed format document is desired but the flow format source document is not available, the fixed format document may be converted into a flow format document. Conversion involves parsing the fixed format document and transforming the basic physical layout elements from the fixed format document into the more complex logical elements used in a flow format document.
Table of contents pages, sections or areas and associated headings are common elements in many documents. For example, in a large business or educational document, text may be organized under a number of headings and subheadings distributed through the body of the document. At or near the beginning of the document, a table of contents page may be included that lists each of the headings and subheadings and typically provides a page number on which each heading or subheading and associated text or other content is located. In some cases, a table of contents page or area may also be located in other areas of a document, for example, at the end of a document, or in various places inside a document. In addition, headings that may be associated with table of contents items may be located in various places throughout a document including above and below a table of contents page or area. In addition, some documents may have multiple tables of contents pages where a small table of contents page may list only a high level subset of headings and/or subheadings and where a larger table of contents page may list a full set of all headings and subheadings contained in the document.
Currently, when converting a fixed format document that contains a table of contents into a flow format document, the table of contents page, section or area and the items comprising the table of contents are not recognized, and thus, when the fixed format document is converted, page numbers associated with table of contents items will not be correct in the converted document. That is, the page numbers in the table of contents (typically at the end of each table of content item) will not be correct after conversion (owing to reflow of the converted document), and thus, it will be difficult to update the converted document. In addition, during document conversion, table of contents items sometimes will be sometimes into single paragraphs (owing to erroneous paragraph detection), and thus, the reconstructed table of contents page, section or area in the flow format document will not look the same as the pre-converted fixed format document.
It is with respect to these and other considerations that the present invention has been made.
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended as an aid in determining the scope of the claimed subject matter.
Embodiments of the present invention solve the above and other problems by providing detection of table of contents entries in a fixed format document and reconstructing detected table of contents entries in a flow format document. After detection of table of contents entries in a table of contents page, section or area of a fixed format document, the detected entries are used to improve detection of headings in the fixed format document, for example, by finding headings on pages in the fixed format document corresponding to page numbers associated with detected table of contents entries. During reconstruction of the fixed format document into a flow format document, the detected table of contents page, section or area may be replaced with a single “smart field” which may, in turn, be populated with headings collected from the fixed format document to create a reconstructed table of contents page, section or area.
Embodiments provide for searching for lines in a fixed format document that have attributes of table of contents entries, for example, headings, space separators and page numbers. Table of contents entry candidates are generated by collecting such possible table of contents entry lines along with lines occurring before and after the possible table of contents entry lines into table of contents candidate groupings. Each grouping is then compared to text in the fixed format document to find matches of table of contents candidates with headings or subheadings in the fixed format document.
After non-matching and/or false positive table of contents candidates are discarded, those table of contents candidates detected to be correct table of contents entries are used for reconstruction a table of contents page, area, or section in a flow format document.
The details of one or more embodiments are set forth in the accompanying drawings and description below. Other features and advantages will be apparent from a reading of the following detailed description and a review of the associated drawings. It is to be understood that the following detailed description is explanatory only and is not restrictive of the invention as claimed.
The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate various embodiments of the present invention. In the drawings:
As briefly described above, embodiments of the present invention are directed to providing detection of table of contents entries in a fixed format document and reconstructing detected table of contents entries in a flow format document. After detection of table of contents (sometimes referred to as TOC) entries in a table of contents page, section or area of a fixed format document, the detected entries are used to improve detection of headings in the fixed format document, for example, by finding headings on pages in the fixed format document corresponding to page numbers associated with detected table of contents entries. During reconstruction of the fixed format document into a flow format document, the detected table of contents page, section or area may be replaced with a single “smart field” which may, in turn, be populated with headings collected from the fixed format document to create a reconstructed table of contents page, section or area.
According to embodiments, one or more table of contents entries are detected in a fixed format document, and table of contents entry candidates are generated by grouping one or more lines containing suspected table of contents entries. Each grouping is compared to text contained in the fixed format document for locating matching headings, subheadings, and associated text in the fixed format document. After non-matching or false positive matches are discarded, table of contents entry candidates detected to be correct table of contents entries are used detect headings contained in the fixed format document. Detected headings are collected, and then during reconstruction of the flow format document, the detected TOC page, section or area is replaced with a single TOC smart field. The TOC smart field may then be populated with the detected headings to create a TOC page, section or area in the reconstructed flow format document.
The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers are used in the drawing and the following description to refer to the same or similar elements. While embodiments of the invention may be described, modifications, adaptations, and other implementations are possible. For example, substitutions, additions, or modifications may be made to the elements illustrated in the drawings, and the methods described herein may be modified by substituting, reordering, or adding stages to the disclosed methods. Accordingly, the following detailed description does not limit the invention, but instead, the proper scope of the invention is defined by the appended claims.
Referring now to the drawings, in which like numerals represent like elements, various embodiments will be described.
In the illustrated embodiment, the fixed format detection and flow format reconstruction engine 120 and the table of contents detection and reconstruction engine 122 may operate as part of a document converter 102 executed on a computing device 104. The document converter 102 converts a fixed format document 106 into a flow format document 108 using a parser 110, a document processor 112, and a serializer 114. The parser 110 reads and extracts data from the fixed format document 106. The data extracted from the fixed format document is written to a data store 116 accessible by the document processor 112 and the serializer 114. The document processor 112 analyzes and transforms the data into flowable elements using one or more detection and/or reconstruction engines. Finally, the serializer 114 writes the flowable elements into a flowable document format (e.g., a word processing format).
Where processing begins depends on the type of fixed format document 106 being parsed. A native fixed format document 106A may be created directly from a flow format source document and may contain some or all of the basic physical layout elements. Alternatively, a native fixed format document 106A may be created directly with an appropriate application that allows for creation of a fixed format document as an original document. The embedded data objects are extracted by the parser and are available for immediate use by the document converter; although, in some instances, minor reformatting or other minor processing is applied to organize or standardize the data. In contrast, all information in an image-based fixed format document 106B created by digitally imaging a physical document (e.g., scanning or photographing) is stored as a series of page images with no additional data (i.e., no text-runs or paths). In this case, the optional optical character recognition engine 202 analyzes each page image and creates corresponding physical layout objects. Once the physical layout objects 208 are available, the layout analysis engine 204 analyzes the layout of the fixed format document. After layout analysis is complete, the semantic analysis engine 206 enriches the logical layout objects with semantic information obtained from analysis of the physical layout objects and/or logical layout objects.
As illustrated in
Referring still to
Referring to the table of contents entry 315, a heading 316 of “Quick Brown Fox” is illustrated, followed by one or more space separators 320, followed by a page number 325. The illustrated table of contents entry 315 is typical of one or more table of contents entries that may be included in a table of contents page, section, or area of a given document. As should be appreciated, in some instances a table of contents entry may include a table of contents heading 316 followed by different types of space separators 320, for example, the dots illustrated in
As should be appreciated, the example table of contents entries illustrated in
The page number 325 displayed for the table of contents entry indicates a page number in the associated document on which the heading 316 and/or associated text may be located. That is, following the example illustrated in
Referring still to
Referring now to
As briefly described above, in some instances, table of contents entries may be “smart fields” wherein table of contents entries 315, 330, 335, 340 in a table of contents page, section or area may be linked to associated headings 350, 360, 370, 380 in the associated document. Thus, if the associated document is edited such that information in the document linked to associated table of contents entries changes, those changes may be reflected in the table of contents entries displayed in the table of contents page, section or area. For example, if the example document illustrated in
Referring then to
At operation 408, line and paragraph detection are performed by the fixed format detection and reconstruction engine 120 for separating the received fixed format document into one or more individual lines and paragraphs that may be further analyzed for detecting table of contents entries, as described herein. At operation 410, lines containing table of contents entry attributes are detected by the table of contents detection engine 122. According to an embodiment, the table of contents detection engine 122 parses each detected line and analyzes each detected line for attributes of table of contents entries, as illustrated and described above with reference to
For the alphanumeric page indicator, the table of contents detection engine 122 may look for any number of numeric page indicators, for example, “1, 2, 3, etc.”, or the table of contents detection engine may look for one or more alphabetical page indicators, for example, “a, b, c, etc.”, or the table of contents detection engine 122 may look for page indicators of other types, for example, roman numerals, or other types of alphanumeric indicators that may be used for indicating a page on which associated headings and/or text may be located. That is, the TOC detection engine 122 may look for page indicators as any of a variety of alphanumeric indicators used according to different languages and text types.
As should be appreciated, in some cases a given table of contents entry may include a table of contents heading, but may not include space separators and page indicators. For example, a given document may include multiple tables of contents pages, sections, or areas. For example, a summary table of contents may include a listing of a subset of the headings contained in a document without listing associated page numbers on which the headings may be found in the associated document. A secondary table of contents may include a listing of all headings and subheadings along with page numbers on which the headings and/or subheadings and associated text may be found.
According to an embodiment, during the process of finding lines that may be table of contents entry candidates, the table of contents detection engine 122 may perform the search based on the text orientation of the received text. For example, if it is known that the received document was written in a left-to-right orientation, for example, as written in English, then the table of contents detection engine may look for table of contents entry candidates according to a left-to-right text rendering orientation. On the other hand, if it is known that the document was rendered according to a right-to-left orientation, then the table of contents detection engine 122 may analyze the text according to a right-to-left orientation. According to one embodiment, a given fixed format document may contain a mixture of left-to-right and right-to-left oriented text. Because of this possibility, the table of contents detection engine 122 may search for TOC entry candidates on a line-by-line basis where the text orientation of each line is considered as opposed to the orientation of the document. If the origin of the document and associated text rendering orientation is not known, then the table of contents detection engine 122 may analyze the text according to both orientations.
At operation 412, the table of contents detection engine 122 attempts to identify a table of contents page, section or area 300 in the received fixed format document. As described above, a table of contents page, section or area 300 often includes a heading or title, for example “Table of Contents,” or “Contents,” or “Table of Headings,” or “Headings,” or the like. The table of contents detection engine 122 may look for such text for determining whether a given page or pages includes table of contents entries associated with a table of contents page, section or area. As should be appreciated, this heuristic analysis may be important when multiple TOC candidates (e.g., from multiple TOC pages, sections or areas) are found, and thus, this heuristic may be used for determining which TOC entry is the best or right entry, as discussed further below.
Determining whether a particular page or pages is/are associated with a table of contents for the received document will assist the table of contents detection engine in determining whether entries contained therein are in fact table of contents entries. As should be appreciated, if no such table of contents title or heading is available, the table of contents detection engine 122 may continue with the process of affirmatively detecting table of contents entries, but a detection of a particular page or pages as a table of contents page, section or area will assist in and improve the confidence associated with the detection of table of contents entries.
At operation 414, the table of contents detection engine generates one or more table of contents entry candidates for detection and potential use in reconstruction of a table of contents page, section or area in a reconstructed flow format document. At operation 416, the table of contents detection engine 122 groups together one or more lines of potential table of contents entry lines as potential table of contents candidates. According to an embodiment, lines that end with successive page numbers in the same numbering schemes may be grouped together. For example, consider the following lines found in a TOC page, section or area:
Heading 1 . . . i
Heading 2 . . . iii
Heading 3 . . . iv
Heading 4 . . . 1
Heading 5 . . . 5
Heading 6 . . . 6
Heading 7 . . . 3
Heading 8 . . . 7
According to this example, the table of contents detection engine 122 may find three TOC candidates: (1) first three lines as a first TOC candidate; (2) the second three lines as a second TOC candidate; and (3) the remaining two lines as a third candidate. Continuing with this example, later the TOC detection engine 122 may put together the first and second TOC candidates or other combinations which may be the case in a given document to use one scheme at the beginning of a document and another scheme in the rest of the document.
Referring back to
Next, the table of contents detection engine 122 may generate a number of table of contents entry candidates from the table of contents entry 335 illustrated in
Referring still to the example TOC items in
Referring now to operation 418, the table of contents detection engine 122 retrieves a first table of contents entry candidate for analysis against the received fixed format document. At operation 420, the table of contents detection engine 122 retrieves the page number, if available, from the end of one of the lines of the retrieved table of contents entry candidate as illustrated and described above with reference to
In order to locate a page that may contain matching text, the table of contents detection engine 122 may use one or more of a variety of different methods. According to one embodiment, the TOC engine 122 may use pattern matching for detecting page numbers on pages of the fixed format document and for detecting headings that may be compared against each table of contents candidate. That is, if the TOC engine 122 needs to check page 3 of a fixed format document to determine whether a given heading is located on that page, then the TOC engine 122 may use pattern matching for locating the page and for subsequently attempting to locate a heading matching a given TOC entry candidate. For example, referring to
At operation 421, a determination is made by the detection engine 122 as to whether text matching the first table of contents entry candidate is found on a page in the received fixed format document. If no text matching the first table of contents entry candidate is found in the fixed format document, the method proceeds to operation 422, and the candidate is discarded at operation 422. If the first analyzed table of contents entry candidate is discarded at operation 422, the method proceeds back to operation 418, and the next table of contents entry candidate is retrieved for analysis.
Referring back to operation 421, if text is found in the received fixed format document matching the retrieved table of contents entry candidate, the method proceeds to operation 423, and a determination is made as to whether the text found in the fixed format document matching text in the first table of contents entry candidate is in heading text located on the page associated with the first analyzed table of contents entry candidate. For example, referring to
As illustrated in
Referring still to operation 423, if the analyzed table of contents entry candidate text does match exactly the heading text found in the received fixed format document, the method proceeds to operation 424, and a determination is made as to whether the table of contents entry candidate is found in more than one table of contents page, section or area. As described above, in some cases, a given document may include more than one table of contents page, section or area, and likewise, a given heading may be listed in multiple locations in a given document. If at operation 424 a determination is made that the analyzed table of contents entry candidate is found in only one table of contents page, section or area, then the method proceeds to operation 425, and the candidate is saved and the heading found in the fixed format document matching a heading contained in the TOC candidate is designated for eventual reconstruction in the desired flow format document.
If at operation 424, the table of contents entry candidate is found in more than one table of contents page, section or area, the method proceeds to operation 426, and a determination is made as to whether the table of contents entry candidate is found in multiple pages, sections or areas identified as table of contents pages, sections or areas, for example, where a table of contents title 310 is found on each of the multiple pages, sections or areas. If so, the method proceeds to operation 432, and a determination is made as to which of the table of contents pages, sections or areas is the largest. At operation 434, the table of contents entry candidate associated with the largest of the table of contents pages, sections or areas is saved and the heading found in the fixed format document matching a heading contained in the TOC candidate is designated for eventual use in reconstructing the desired flow format document.
Referring back to operation 426, if the analyzed table of contents entry candidate is not found on a page, area or section readily identifiable as a table of contents page, section or area (as identified by a table of contents title 310), the method proceeds to operation 440, and a determination is made as to the largest of the table of content item sets (containing table of contents entry candidates) containing the matching table of contents entry candidate. The method proceeds to operation 442, and the matching table of contents entry candidate contained in the largest of the table of content item sets is saved and the heading found in the fixed format document matching a heading contained in the TOC candidate is designated for eventual reconstruction in the desired flow format document.
At operation 450, any heading found in the fixed format document matching a heading contained in the table of content entry candidate designated and saved for inclusion in a reconstructed flow format document, is utilized by the table of contents detection engine 122 for reconstructing a table of contents page, section or area, containing one or more reconstructed table of contents entries in a reconstructed flow format document. According to an embodiment, reconstruction of the table of contents page, section or area includes locating a position of the detected table of contents page, section or area and replacing all the lines and/or paragraphs in that TOC page, section or area with a single “smart field.” Then, all the collected headings that matched TOC candidates are populated into the smart field to create a TOC page, section or area in the resulting flow format document. The method 400 ends at operation 490.
While the invention has been described in the general context of program modules that execute in conjunction with an application program that runs on an operating system on a computer, those skilled in the art will recognize that the invention may also be implemented in combination with other program modules. Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.
The embodiments and functionalities described herein may operate via a multitude of computing systems including, without limitation, desktop computer systems, wired and wireless computing systems, mobile computing systems (e.g., mobile telephones, netbooks, tablet or slate type computers, notebook computers, and laptop computers), hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, and mainframe computers.
In addition, the embodiments and functionalities described herein may operate over distributed systems (e.g., cloud-based computing systems), where application functionality, memory, data storage and retrieval and various processing functions may be operated remotely from each other over a distributed computing network, such as the Internet or an intranet. User interfaces and information of various types may be displayed via on-board computing device displays or via remote display units associated with one or more computing devices. For example user interfaces and information of various types may be displayed and interacted with on a wall surface onto which user interfaces and information of various types are projected. Interaction with the multitude of computing systems with which embodiments of the invention may be practiced include, keystroke entry, touch screen entry, voice or other audio entry, gesture entry where an associated computing device is equipped with detection (e.g., camera) functionality for capturing and interpreting user gestures for controlling the functionality of the computing device, and the like.
As stated above, a number of program modules and data files may be stored in the system memory 504. While executing on the processing unit 502, the program modules 506 (e.g., the fixed format detection and flow format reconstruction engine 120, the table of contents detection and reconstruction engine 122, the parser 110, the document processor 112, and the serializer 114) may perform processes including, but not limited to, one or more of the stages of the method 400 illustrated in
Furthermore, embodiments of the invention may be practiced in an electrical circuit comprising discrete electronic elements, packaged or integrated electronic chips containing logic gates, a circuit utilizing a microprocessor, or on a single chip containing electronic elements or microprocessors. For example, embodiments of the invention may be practiced via a system-on-a-chip (SOC) where each or many of the components illustrated in
The computing device 500 may also have one or more input device(s) 512 such as a keyboard, a mouse, a pen, a sound input device, a touch input device, etc. The output device(s) 514 such as a display, speakers, a printer, etc. may also be included. The aforementioned devices are examples and others may be used. The computing device 500 may include one or more communication connections 516 allowing communications with other computing devices 518. Examples of suitable communication connections 516 include, but are not limited to, RF transmitter, receiver, and/or transceiver circuitry; universal serial bus (USB), parallel, or serial ports, and other connections appropriate for use with the applicable computer readable media.
Embodiments of the invention, for example, may be implemented as a computer process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media. The computer program product may be a computer storage media readable by a computer system and encoding a computer program of instructions for executing a computer process.
The term computer readable media as used herein may include computer storage media and communication media. Computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. The system memory 504, the removable storage device 509, and the non-removable storage device 510 are all computer storage media examples (i.e., memory storage.) Computer storage media may include, but is not limited to, RAM, ROM, electrically erasable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store information and which can be accessed by the computing device 500. Any such computer storage media may be part of the computing device 500.
Communication media may be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media. The term “modulated data signal” may describe a signal that has one or more characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), infrared, and other wireless media.
One or more application programs 667 may be loaded into the memory 662 and run on or in association with the operating system 664. Examples of the application programs include phone dialer programs, e-mail programs, personal information management (PIM) programs, word processing programs, spreadsheet programs, Internet browser programs, messaging programs, and so forth. The system 602 also includes a non-volatile storage area 668 within the memory 662. The non-volatile storage area 668 may be used to store persistent information that should not be lost if the system 602 is powered down. The application programs 667 may use and store information in the non-volatile storage area 668, such as e-mail or other messages used by an e-mail application, and the like. A synchronization application (not shown) also resides on the system 602 and is programmed to interact with a corresponding synchronization application resident on a host computer to keep the information stored in the non-volatile storage area 668 synchronized with corresponding information stored at the host computer. As should be appreciated, other applications may be loaded into the memory 662 and run on the mobile computing device 600, including the fixed format detection and flow format reconstruction engine 120, the table of contents detection and reconstruction engine 122, the parser 110, the document processor 112, and the serializer 114 described herein.
The system 602 has a power supply 670, which may be implemented as one or more batteries. The power supply 670 might further include an external power source, such as an AC adapter or a powered docking cradle that supplements or recharges the batteries.
The system 602 may also include a radio 672 that performs the function of transmitting and receiving radio frequency communications. The radio 672 facilitates wireless connectivity between the system 602 and the “outside world,” via a communications carrier or service provider. Transmissions to and from the radio 672 are conducted under control of the operating system 664. In other words, communications received by the radio 672 may be disseminated to the application programs 667 via the operating system 664, and vice versa.
The radio 672 allows the system 602 to communicate with other computing devices, such as over a network. The radio 672 is one example of communication media. Communication media may typically be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. The term computer readable media as used herein includes both storage media and communication media.
This embodiment of the system 602 provides notifications using the visual indicator 620 that can be used to provide visual notifications and/or an audio interface 674 producing audible notifications via the audio transducer 625. In the illustrated embodiment, the visual indicator 620 is a light emitting diode (LED) and the audio transducer 625 is a speaker. These devices may be directly coupled to the power supply 670 so that when activated, they remain on for a duration dictated by the notification mechanism even though the processor 660 and other components might shut down for conserving battery power. The LED may be programmed to remain on indefinitely until the user takes action to indicate the powered-on status of the device. The audio interface 674 is used to provide audible signals to and receive audible signals from the user. For example, in addition to being coupled to the audio transducer 625, the audio interface 674 may also be coupled to a microphone to receive audible input, such as to facilitate a telephone conversation. In accordance with embodiments of the present invention, the microphone may also serve as an audio sensor to facilitate control of notifications, as will be described below. The system 602 may further include a video interface 676 that enables an operation of an on-board camera 630 to record still images, video stream, and the like.
A mobile computing device 600 implementing the system 602 may have additional features or functionality. For example, the mobile computing device 600 may also include additional data storage devices (removable and/or non-removable) such as, magnetic disks, optical disks, or tape. Such additional storage is illustrated in
Data/information generated or captured by the mobile computing device 600 and stored via the system 602 may be stored locally on the mobile computing device 600, as described above, or the data may be stored on any number of storage media that may be accessed by the device via the radio 672 or via a wired connection between the mobile computing device 600 and a separate computing device associated with the mobile computing device 600, for example, a server computer in a distributed computing network, such as the Internet. As should be appreciated such data/information may be accessed via the mobile computing device 600 via the radio 672 or via a distributed computing network. Similarly, such data/information may be readily transferred between computing devices for storage and use according to well-known data/information transfer and storage means, including electronic mail and collaborative data/information sharing systems.
Embodiments of the present invention, for example, are described above with reference to block diagrams and/or operational illustrations of methods, systems, and computer program products according to embodiments of the invention. The functions/acts noted in the blocks may occur out of the order as shown in any flowchart. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
The description and illustration of one or more embodiments provided in this application are not intended to limit or restrict the scope of the invention as claimed in any way. The embodiments, examples, and details provided in this application are considered sufficient to convey possession and enable others to make and use the best mode of claimed invention. The claimed invention should not be construed as being limited to any embodiment, example, or detail provided in this application. Regardless of whether shown and described in combination or separately, the various features (both structural and methodological) are intended to be selectively included or omitted to produce an embodiment with a particular set of features. Having been provided with the description and illustration of the present application, one skilled in the art may envision variations, modifications, and alternate embodiments falling within the spirit of the broader aspects of the general inventive concept embodied in this application that do not depart from the broader scope of the claimed invention.
