Patent Publication Number: US-10783192-B1

Title: System, method, and user interface for a search engine based on multi-document summarization

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     The present continuation-in-part patent application claims priority benefit of the U.S. patent application Ser. No. 13/539,098 filed on 29 Jun. 2012 and U.S. patent application Ser. No. 12/023,014 filed on 30 Jan. 2008 under 35 USC 111(a), both of which are entitled “System, Method, and User Interface for a Search Engine Based on Multi-Document Summarization”; which in turn claims priority benefit of the U.S. provisional application for patent serial number 60/888,515 filed on Feb. 6, 2007 under 35 U.S.C. 119(e); all of which are hereby incorporated by reference for all purposes to the extent that such subject matter is not inconsistent herewith or limiting hereof. 
    
    
     FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT 
     Not applicable. 
     REFERENCE TO SEQUENCE LISTING, A TABLE, OR A COMPUTER LISTING APPENDIX 
     Not applicable. 
     COPYRIGHT NOTICE 
     A portion of the disclosure of this patent document contains material that is subject to copyright protection by the author thereof. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or patent disclosure for the purposes of referencing as patent prior art, as it appears in the Patent and Trademark Office, patent file or records, but otherwise reserves all copyright rights whatsoever. 
     FIELD OF THE INVENTION 
     One or more embodiments of the invention generally relate to search summaries. More particularly, the invention relates to metadata-based search summary creation. 
     BACKGROUND OF THE INVENTION 
     The following background information may present examples of specific aspects of the prior art (e.g., without limitation, approaches, facts, or common wisdom) that, while expected to be helpful to further educate the reader as to additional aspects of the prior art, is not to be construed as limiting the present invention, or any embodiments thereof, to anything stated or implied therein or inferred thereupon. 
     Search summaries are typically used to quickly summarize one or more search results from a search engine. Often times a user may wish for search summaries to be created according to a set of user requirements and/or metadata associated with the users. Search summaries and/or results that may be biased by user metadata may provide more accurate search summaries and/or results for the user. 
     The following is an example of a specific aspect in the prior art that, while expected to be helpful to further educate the reader as to additional aspects of the prior art, is not to be construed as limiting the present invention, or any embodiments thereof, to anything stated or implied therein or inferred thereupon. By way of educational background, another aspect of the prior art generally useful to be aware of is that some existing search engines may allow for search results and/or summaries to be filtered according to a set list of options. 
     In view of the foregoing, it is clear that these traditional techniques are not perfect and leave room for more optimal approaches. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       The present invention is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which: 
         FIG. 1  illustrates an exemplary search results&#39; page from an Internet search engine with an addition of a summary request button, in accordance with an embodiment of the present invention; 
         FIG. 2  illustrates an exemplary summary on a user&#39;s query, produced by a search system, in accordance with an embodiment of the present invention; 
         FIG. 3  illustrates an exemplary summary on a user&#39;s query, where each sentence or text fragment in the summary is followed by a reference to its source, in accordance with an embodiment of the present invention; 
         FIG. 4  is a flowchart illustrating an exemplary process for the interaction between a search engine and a summarization engine, in accordance with an embodiment of the present invention; 
         FIG. 5  is a flowchart illustrating an exemplary process for the interaction between a question answering system and a summarization engine, in accordance with an embodiment of the present invention; 
         FIG. 6  illustrates a typical computer system that, when appropriately configured or designed, can serve as a computer system in which the invention may be embodied; 
         FIG. 7  illustrates the architecture of an exemplary system for metadata-based search summary creation, in accordance with an embodiment of the present invention; 
         FIG. 8  is a flow chart illustrating an exemplary process for metadata-based search summary creation, in accordance with an embodiment of the present invention; 
         FIG. 9  is a flow chart illustrating an exemplary process for creating search queries on a query module, in accordance with an embodiment of the present invention; 
         FIG. 10  is a flow chart illustrating an exemplary process for finding search results on a search module, in accordance with an embodiment of the present invention; 
         FIG. 11  is a flow chart illustrating an exemplary process for creating search summaries on a summary module, in accordance with an embodiment of the present invention; 
         FIG. 12  is a flow chart illustrating an exemplary process for displaying results on a display module, in accordance with an embodiment of the present invention; 
         FIG. 13  is a block diagram depicting an exemplary client/server system which may be used by an exemplary web-enabled/networked embodiment of the present invention; and 
         FIG. 14  illustrates a block diagram depicting a conventional client/server communication system. 
     
    
    
     Unless otherwise indicated illustrations in the figures are not necessarily drawn to scale. 
     DETAILED DESCRIPTION OF SOME EMBODIMENTS 
     The present invention is best understood by reference to the detailed figures and description set forth herein. 
     Embodiments of the invention are discussed below with reference to the Figures. However, those skilled in the art will readily appreciate that the detailed description given herein with respect to these figures is for explanatory purposes as the invention extends beyond these limited embodiments. For example, it should be appreciated that those skilled in the art will, in light of the teachings of the present invention, recognize a multiplicity of alternate and suitable approaches, depending upon the needs of the particular application, to implement the functionality of any given detail described herein, beyond the particular implementation choices in the following embodiments described and shown. That is, there are modifications and variations of the invention that are too numerous to be listed but that all fit within the scope of the invention. Also, singular words should be read as plural and vice versa and masculine as feminine and vice versa, where appropriate, and alternative embodiments do not necessarily imply that the two are mutually exclusive. 
     It is to be further understood that the present invention is not limited to the particular methodology, compounds, materials, manufacturing techniques, uses, and applications, described herein, as these may vary. It is also to be understood that the terminology used herein is used for the purpose of describing particular embodiments only, and is not intended to limit the scope of the present invention. It must be noted that as used herein and in the appended claims, the singular forms “a,” “an,” and “the” include the plural reference unless the context clearly dictates otherwise. Thus, for example, a reference to “an element” is a reference to one or more elements and includes equivalents thereof known to those skilled in the art. Similarly, for another example, a reference to “a step” or “a means” is a reference to one or more steps or means and may include sub-steps and subservient means. All conjunctions used are to be understood in the most inclusive sense possible. Thus, the word “or” should be understood as having the definition of a logical “or” rather than that of a logical “exclusive or” unless the context clearly necessitates otherwise. Structures described herein are to be understood also to refer to functional equivalents of such structures. Language that may be construed to express approximation should be so understood unless the context clearly dictates otherwise. 
     All words of approximation as used in the present disclosure and claims should be construed to mean “approximate,” rather than “perfect,” and may accordingly be employed as a meaningful modifier to any other word, specified parameter, quantity, quality, or concept. Words of approximation, include, yet are not limited to terms such as “substantial”, “nearly”, “almost”, “about”, “generally”, “largely”, “essentially”, “closely approximate”, etc. 
     As will be established in some detail below, it is well settle law, as early as 1939, that words of approximation are not indefinite in the claims even when such limits are not defined or specified in the specification. 
     For example, see Ex parte Mallory, 52 USPQ 297, 297 (Pat. Off. Bd. App. 1941) where the court said “The examiner has held that most of the claims are inaccurate because apparently the laminar film will not be entirely eliminated. The claims specify that the film is “substantially” eliminated and for the intended purpose, it is believed that the slight portion of the film which may remain is negligible. We are of the view, therefore, that the claims may be regarded as sufficiently accurate.” 
     Note that claims need only “reasonably apprise those skilled in the art” as to their scope to satisfy the definiteness requirement. See Energy Absorption Sys., Inc. v. Roadway Safety Servs., Inc., Civ. App. 96-1264, slip op. at 10 (Fed. Cir. Jul. 3, 1997) (unpublished) Hybridtech v. Monoclonal Antibodies, Inc., 802 F.2d 1367, 1385, 231 USPQ 81, 94 (Fed. Cir. 1986), cert. denied, 480 U.S. 947 (1987). In addition, the use of modifiers in the claim, like “generally” and “substantial,” does not by itself render the claims indefinite. See Seattle Box Co. v. Industrial Crating &amp; Packing, Inc., 731 F.2d 818, 828-29, 221 USPQ 568, 575-76 (Fed. Cir. 1984). 
     Moreover, the ordinary and customary meaning of terms like “substantially” includes “reasonably close to: nearly, almost, about”, connoting a term of approximation. See In re Frye, Appeal No. 2009-006013, 94 USPQ2d 1072, 1077, 2010 WL 889747 (B.P.A.I. 2010) Depending on its usage, the word “substantially” can denote either language of approximation or language of magnitude. Deering Precision Instruments, L.L.C. v. Vector Distribution Sys., Inc., 347 F.3d 1314, 1323 (Fed. Cir. 2003) (recognizing the “dual ordinary meaning of the term “substantially” as connoting a term of approximation or a term of magnitude”). Here, when referring to the “substantially halfway” limitation, the Specification uses the word “approximately” as a substitute for the word “substantially” (Fact 4). (Fact 4). The ordinary meaning of “substantially halfway” is thus reasonably close to or nearly at the midpoint between the forwardmost point of the upper or outsole and the rearwardmost point of the upper or outsole. 
     Similarly, the term ‘substantially’ is well recognize in case law to have the dual ordinary meaning of connoting a term of approximation or a term of magnitude. See Dana Corp. v. American Axle &amp; Manufacturing, Inc., Civ. App. 04-1116, 2004 U.S. App. LEXIS 18265, *13-14 (Fed. Cir. Aug. 27, 2004) (unpublished). The term “substantially” is commonly used by claim drafters to indicate approximation. See Cordis Corp. v. Medtronic AVE Inc., 339 F.3d 1352, 1360 (Fed. Cir. 2003) (“The patents do not set out any numerical standard by which to determine whether the thickness of the wall surface is ‘substantially uniform.’ The term ‘substantially,’ as used in this context, denotes approximation. Thus, the walls must be of largely or approximately uniform thickness.”); see also Deering Precision Instruments, LLC v. Vector Distribution Sys., Inc., 347 F.3d 1314, 1322 (Fed. Cir. 2003); Epcon Gas Sys., Inc. v. Bauer Compressors, Inc., 279 F.3d 1022, 1031 (Fed. Cir. 2002). We find that the term “substantially” was used in just such a manner in the claims of the patents-in-suit: “substantially uniform wall thickness” denotes a wall thickness with approximate uniformity. 
     It should also be noted that such words of approximation as contemplated in the foregoing clearly limits the scope of claims such as saying ‘generally parallel’ such that the adverb ‘generally’ does not broaden the meaning of parallel. Accordingly, it is well settled that such words of approximation as contemplated in the foregoing (e.g., like the phrase ‘generally parallel’) envisions some amount of deviation from perfection (e.g., not exactly parallel), and that such words of approximation as contemplated in the foregoing are descriptive terms commonly used in patent claims to avoid a strict numerical boundary to the specified parameter. To the extent that the plain language of the claims relying on such words of approximation as contemplated in the foregoing are clear and uncontradicted by anything in the written description herein or the figures thereof, it is improper to rely upon the present written description, the figures, or the prosecution history to add limitations to any of the claim of the present invention with respect to such words of approximation as contemplated in the foregoing. That is, under such circumstances, relying on the written description and prosecution history to reject the ordinary and customary meanings of the words themselves is impermissible. See, for example, Liquid Dynamics Corp. v. Vaughan Co., 355 F.3d 1361, 69 USPQ2d 1595, 1600-01 (Fed. Cir. 2004). The plain language of phrase 2 requires a “substantial helical flow.” The term “substantial” is a meaningful modifier implying “approximate,” rather than “perfect.” In Cordis Corp. v. Medtronic AVE, Inc., 339 F.3d 1352, 1361 (Fed. Cir. 2003), the district court imposed a precise numeric constraint on the term “substantially uniform thickness.” We noted that the proper interpretation of this term was “of largely or approximately uniform thickness” unless something in the prosecution history imposed the “clear and unmistakable disclaimer” needed for narrowing beyond this simple-language interpretation. Id. In Anchor Wall Systems v. Rockwood Retaining Walls, Inc., 340 F.3d 1298, 1311 (Fed. Cir. 2003)” Id. at 1311. Similarly, the plain language of claim  1  requires neither a perfectly helical flow nor a flow that returns precisely to the center after one rotation (a limitation that arises only as a logical consequence of requiring a perfectly helical flow). 
     The reader should appreciate that case law generally recognizes a dual ordinary meaning of such words of approximation, as contemplated in the foregoing, as connoting a term of approximation or a term of magnitude; e.g., see Deering Precision Instruments, L.L.C. v. Vector Distrib. Sys., Inc., 347 F.3d 1314, 68 USPQ2d 1716, 1721 (Fed. Cir. 2003), cert. denied, 124 S. Ct. 1426 (2004) where the court was asked to construe the meaning of the term “substantially” in a patent claim. Also see Epcon, 279 F.3d at 1031 (“The phrase ‘substantially constant’ denotes language of approximation, while the phrase ‘substantially below’ signifies language of magnitude, i.e., not insubstantial.”). Also, see, e.g., Epcon Gas Sys., Inc. v. Bauer Compressors, Inc., 279 F.3d 1022 (Fed. Cir. 2002) (construing the terms “substantially constant” and “substantially below”); Zodiac Pool Care, Inc. v. Hoffinger Indus., Inc., 206 F.3d 1408 (Fed. Cir. 2000) (construing the term “substantially inward”); York Prods., Inc. v. Cent. Tractor Farm &amp; Family Ctr., 99 F.3d 1568 (Fed. Cir. 1996) (construing the term “substantially the entire height thereof”); Tex. Instruments Inc. v. Cypress Semiconductor Corp., 90 F.3d 1558 (Fed. Cir. 1996) (construing the term “substantially in the common plane”). In conducting their analysis, the court instructed to begin with the ordinary meaning of the claim terms to one of ordinary skill in the art. Prima Tek, 318 F.3d at 1148. Reference to dictionaries and our cases indicates that the term “substantially” has numerous ordinary meanings. As the district court stated, “substantially” can mean “significantly” or “considerably.” The term “substantially” can also mean “largely” or “essentially.” Webster&#39;s New 20th Century Dictionary 1817 (1983). 
     Words of approximation, as contemplated in the foregoing, may also be used in phrases establishing approximate ranges or limits, where the end points are inclusive and approximate, not perfect; e.g., see AK Steel Corp. v. Sollac, 344 F.3d 1234, 68 USPQ2d 1280, 1285 (Fed. Cir. 2003) where it where the court said We conclude that the ordinary meaning of the phrase “up to about 10%” includes the “about 10%” endpoint. As pointed out by AK Steel, when an object of the preposition “up to” is nonnumeric, the most natural meaning is to exclude the object (e.g., painting the wall up to the door). On the other hand, as pointed out by Sollac, when the object is a numerical limit, the normal meaning is to include that upper numerical limit (e.g., counting up to ten, seating capacity for up to seven passengers). Because we have here a numerical limit—“about 10%”—the ordinary meaning is that that endpoint is included. 
     In the present specification and claims, a goal of employment of such words of approximation, as contemplated in the foregoing, is to avoid a strict numerical boundary to the modified specified parameter, as sanctioned by Pall Corp. v. Micron Separations, Inc., 66 F.3d 1211, 1217, 36 USPQ2d 1225, 1229 (Fed. Cir. 1995) where it states “It is well established that when the term “substantially” serves reasonably to describe the subject matter so that its scope would be understood by persons in the field of the invention, and to distinguish the claimed subject matter from the prior art, it is not indefinite.” Likewise see Verve LLC v. Crane Cams Inc., 311 F.3d 1116, 65 USPQ2d 1051, 1054 (Fed. Cir. 2002). Expressions such as “substantially” are used in patent documents when warranted by the nature of the invention, in order to accommodate the minor variations that may be appropriate to secure the invention. Such usage may well satisfy the charge to “particularly point out and distinctly claim” the invention, 35 U.S.C. § 112, and indeed may be necessary in order to provide the inventor with the benefit of his invention. In Andrew Corp. v. Gabriel Elecs. Inc., 847 F.2d 819, 821-22, 6 USPQ2d 2010, 2013 (Fed. Cir. 1988) the court explained that usages such as “substantially equal” and “closely approximate” may serve to describe the invention with precision appropriate to the technology and without intruding on the prior art. The court again explained in Ecolab Inc. v. Envirochem, Inc., 264 F.3d 1358, 1367, 60 USPQ2d 1173, 1179 (Fed. Cir. 2001) that “like the term ‘about,’ the term ‘substantially’ is a descriptive term commonly used in patent claims to ‘avoid a strict numerical boundary to the specified parameter, see Ecolab Inc. v. Envirochem Inc., 264 F.3d 1358, 60 USPQ2d 1173, 1179 (Fed. Cir. 2001) where the court found that the use of the term “substantially” to modify the term “uniform” does not render this phrase so unclear such that there is no means by which to ascertain the claim scope. 
     Similarly, other courts have noted that like the term “about,” the term “substantially” is a descriptive term commonly used in patent claims to “avoid a strict numerical boundary to the specified parameter.”; e.g., see Pall Corp. v. Micron Seps., 66 F.3d 1211, 1217, 36 USPQ2d 1225, 1229 (Fed. Cir. 1995); see, e.g., Andrew Corp. v. Gabriel Elecs. Inc., 847 F.2d 819, 821-22, 6 USPQ2d 2010, 2013 (Fed. Cir. 1988) (noting that terms such as “approach each other,” “close to,” “substantially equal,” and “closely approximate” are ubiquitously used in patent claims and that such usages, when serving reasonably to describe the claimed subject matter to those of skill in the field of the invention, and to distinguish the claimed subject matter from the prior art, have been accepted in patent examination and upheld by the courts). In this case, “substantially” avoids the strict 100% nonuniformity boundary. 
     Indeed, the foregoing sanctioning of such words of approximation, as contemplated in the foregoing, has been established as early as 1939, see Ex parte Mallory, 52 USPQ 297, 297 (Pat. Off. Bd. App. 1941) where, for example, the court said “the claims specify that the film is “substantially” eliminated and for the intended purpose, it is believed that the slight portion of the film which may remain is negligible. We are of the view, therefore, that the claims may be regarded as sufficiently accurate.” Similarly, In re Hutchison, 104 F.2d 829, 42 USPQ 90, 93 (C.C.P.A. 1939) the court said “It is realized that “substantial distance” is a relative and somewhat indefinite term, or phrase, but terms and phrases of this character are not uncommon in patents in cases where, according to the art involved, the meaning can be determined with reasonable clearness.” 
     Hence, for at least the forgoing reason, Applicants submit that it is improper for any examiner to hold as indefinite any claims of the present patent that employ any words of approximation. 
     Unless defined otherwise, all technical and scientific terms used herein have the same meanings as commonly understood by one of ordinary skill in the art to which this invention belongs. Preferred methods, techniques, devices, and materials are described, although any methods, techniques, devices, or materials similar or equivalent to those described herein may be used in the practice or testing of the present invention. Structures described herein are to be understood also to refer to functional equivalents of such structures. The present invention will now be described in detail with reference to embodiments thereof as illustrated in the accompanying drawings. 
     From reading the present disclosure, other variations and modifications will be apparent to persons skilled in the art. Such variations and modifications may involve equivalent and other features which are already known in the art, and which may be used instead of or in addition to features already described herein. 
     Although Claims have been formulated in this Application to particular combinations of features, it should be understood that the scope of the disclosure of the present invention also includes any novel feature or any novel combination of features disclosed herein either explicitly or implicitly or any generalization thereof, whether or not it relates to the same invention as presently claimed in any Claim and whether or not it mitigates any or all of the same technical problems as does the present invention. 
     Features which are described in the context of separate embodiments may also be provided in combination in a single embodiment. Conversely, various features which are, for brevity, described in the context of a single embodiment, may also be provided separately or in any suitable subcombination. The Applicants hereby give notice that new Claims may be formulated to such features and/or combinations of such features during the prosecution of the present Application or of any further Application derived therefrom. 
     References to “one embodiment,” “an embodiment,” “example embodiment,” “various embodiments,” “some embodiments,” “embodiments of the invention,” etc., may indicate that the embodiment(s) of the invention so described may include a particular feature, structure, or characteristic, but not every possible embodiment of the invention necessarily includes the particular feature, structure, or characteristic. Further, repeated use of the phrase “in one embodiment,” or “in an exemplary embodiment,” “an embodiment,” do not necessarily refer to the same embodiment, although they may. Moreover, any use of phrases like “embodiments” in connection with “the invention” are never meant to characterize that all embodiments of the invention must include the particular feature, structure, or characteristic, and should instead be understood to mean “at least some embodiments of the invention” includes the stated particular feature, structure, or characteristic. 
     References to “user”, or any similar term, as used herein, may mean a human or non-human user thereof. Moreover, “user”, or any similar term, as used herein, unless expressly stipulated otherwise, is contemplated to mean users at any stage of the usage process, to include, without limitation, direct user(s), intermediate user(s), indirect user(s), and end user(s). The meaning of “user”, or any similar term, as used herein, should not be otherwise inferred or induced by any pattern(s) of description, embodiments, examples, or referenced prior-art that may (or may not) be provided in the present patent. 
     References to “end user”, or any similar term, as used herein, is generally intended to mean late stage user(s) as opposed to early stage user(s). Hence, it is contemplated that there may be a multiplicity of different types of “end user” near the end stage of the usage process. Where applicable, especially with respect to distribution channels of embodiments of the invention comprising consumed retail products/services thereof (as opposed to sellers/vendors or Original Equipment Manufacturers), examples of an “end user” may include, without limitation, a “consumer”, “buyer”, “customer”, “purchaser”, “shopper”, “enjoyer”, “viewer”, or individual person or non-human thing benefiting in any way, directly or indirectly, from use of. or interaction, with some aspect of the present invention. 
     In some situations, some embodiments of the present invention may provide beneficial usage to more than one stage or type of usage in the foregoing usage process. In such cases where multiple embodiments targeting various stages of the usage process are described, references to “end user”, or any similar term, as used therein, are generally intended to not include the user that is the furthest removed, in the foregoing usage process, from the final user therein of an embodiment of the present invention. 
     Where applicable, especially with respect to retail distribution channels of embodiments of the invention, intermediate user(s) may include, without limitation, any individual person or non-human thing benefiting in any way, directly or indirectly, from use of, or interaction with, some aspect of the present invention with respect to selling, vending, Original Equipment Manufacturing, marketing, merchandising, distributing, service providing, and the like thereof. 
     References to “person”, “individual”, “human”, “a party”, “animal”, “creature”, or any similar term, as used herein, even if the context or particular embodiment implies living user, maker, or participant, it should be understood that such characterizations are sole by way of example, and not limitation, in that it is contemplated that any such usage, making, or participation by a living entity in connection with making, using, and/or participating, in any way, with embodiments of the present invention may be substituted by such similar performed by a suitably configured non-living entity, to include, without limitation, automated machines, robots, humanoids, computational systems, information processing systems, artificially intelligent systems, and the like. It is further contemplated that those skilled in the art will readily recognize the practical situations where such living makers, users, and/or participants with embodiments of the present invention may be in whole, or in part, replaced with such non-living makers, users, and/or participants with embodiments of the present invention. Likewise, when those skilled in the art identify such practical situations where such living makers, users, and/or participants with embodiments of the present invention may be in whole, or in part, replaced with such non-living makers, it will be readily apparent in light of the teachings of the present invention how to adapt the described embodiments to be suitable for such non-living makers, users, and/or participants with embodiments of the present invention. Thus, the invention is thus to also cover all such modifications, equivalents, and alternatives falling within the spirit and scope of such adaptations and modifications, at least in part, for such non-living entities. 
     Headings provided herein are for convenience and are not to be taken as limiting the disclosure in any way. 
     The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. 
     It is understood that the use of specific component, device and/or parameter names are for example only and not meant to imply any limitations on the invention. The invention may thus be implemented with different nomenclature/terminology utilized to describe the mechanisms/units/structures/components/devices/parameters herein, without limitation. Each term utilized herein is to be given its broadest interpretation given the context in which that term is utilized. 
     Terminology. The following paragraphs provide definitions and/or context for terms found in this disclosure (including the appended claims): 
     “Comprising.” This term is open-ended. As used in the appended claims, this term does not foreclose additional structure or steps. Consider a claim that recites: “A memory controller comprising a system cache . . . .” Such a claim does not foreclose the memory controller from including additional components (e.g., a memory channel unit, a switch). 
     “Configured To.” Various units, circuits, or other components may be described or claimed as “configured to” perform a task or tasks. In such contexts, “configured to” or “operable for” is used to connote structure by indicating that the mechanisms/units/circuits/components include structure (e.g., circuitry and/or mechanisms) that performs the task or tasks during operation. As such, the mechanisms/unit/circuit/component can be said to be configured to (or be operable) for perform(ing) the task even when the specified mechanisms/unit/circuit/component is not currently operational (e.g., is not on). The mechanisms/units/circuits/components used with the “configured to” or “operable for” language include hardware—for example, mechanisms, structures, electronics, circuits, memory storing program instructions executable to implement the operation, etc. Reciting that a mechanism/unit/circuit/component is “configured to” or “operable for” perform(ing) one or more tasks is expressly intended not to invoke 35 U.S.C. .sctn.112, sixth paragraph, for that mechanism/unit/circuit/component. “Configured to” may also include adapting a manufacturing process to fabricate devices or components that are adapted to implement or perform one or more tasks. 
     “Based On.” As used herein, this term is used to describe one or more factors that affect a determination. This term does not foreclose additional factors that may affect a determination. That is, a determination may be solely based on those factors or based, at least in part, on those factors. Consider the phrase “determine A based on B.” While B may be a factor that affects the determination of A, such a phrase does not foreclose the determination of A from also being based on C. In other instances, A may be determined based solely on B. 
     The terms “a”, “an” and “the” mean “one or more”, unless expressly specified otherwise. 
     Unless otherwise indicated, all numbers expressing conditions, concentrations, dimensions, and so forth used in the specification and claims are to be understood as being modified in all instances by the term “about.” Accordingly, unless indicated to the contrary, the numerical parameters set forth in the following specification and attached claims are approximations that may vary depending at least upon a specific analytical technique. 
     The term “comprising,” which is synonymous with “including,” “containing,” or “characterized by” is inclusive or open-ended and does not exclude additional, unrecited elements or method steps. “Comprising” is a term of art used in claim language which means that the named claim elements are essential, but other claim elements may be added and still form a construct within the scope of the claim. 
     As used herein, the phase “consisting of” excludes any element, step, or ingredient not specified in the claim. When the phrase “consists of” (or variations thereof) appears in a clause of the body of a claim, rather than immediately following the preamble, it limits only the element set forth in that clause; other elements are not excluded from the claim as a whole. As used herein, the phase “consisting essentially of” limits the scope of a claim to the specified elements or method steps, plus those that do not materially affect the basis and novel characteristic(s) of the claimed subject matter. Moreover, for any claim of the present invention which claims an embodiment “consisting essentially of” a certain set of elements of any herein described embodiment it shall be understood as obvious by those skilled in the art that the present invention also covers all possible varying scope variants of any described embodiment(s) that are each exclusively (i.e., “consisting essentially of”) functional subsets or functional combination thereof such that each of these plurality of exclusive varying scope variants each consists essentially of any functional subset(s) and/or functional combination(s) of any set of elements of any described embodiment(s) to the exclusion of any others not set forth therein. That is, it is contemplated that it will be obvious to those skilled how to create a multiplicity of alternate embodiments of the present invention that simply consisting essentially of a certain functional combination of elements of any described embodiment(s) to the exclusion of any others not set forth therein, and the invention thus covers all such exclusive embodiments as if they were each described herein. 
     With respect to the terms “comprising,” “consisting of” and “consisting essentially of” where one of these three terms is used herein, the presently disclosed and claimed subject matter may include the use of either of the other two terms. Thus in some embodiments not otherwise explicitly recited, any instance of “comprising” may be replaced by “consisting of” or, alternatively, by “consisting essentially of”, and thus, for the purposes of claim support and construction for “consisting of” format claims, such replacements operate to create yet other alternative embodiments “consisting essentially of” only the elements recited in the original “comprising” embodiment to the exclusion of all other elements. 
     Devices or system modules that are in at least general communication with each other need not be in continuous communication with each other, unless expressly specified otherwise. In addition, devices or system modules that are in at least general communication with each other may communicate directly or indirectly through one or more intermediaries. 
     A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary a variety of optional components are described to illustrate the wide variety of possible embodiments of the present invention. 
     As is well known to those skilled in the art many careful considerations and compromises typically must be made when designing for the optimal manufacture of a commercial implementation any system, and in particular, the embodiments of the present invention. A commercial implementation in accordance with the spirit and teachings of the present invention may configured according to the needs of the particular application, whereby any aspect(s), feature(s), function(s), result(s), component(s), approach(es), or step(s) of the teachings related to any described embodiment of the present invention may be suitably omitted, included, adapted, mixed and matched, or improved and/or optimized by those skilled in the art, using their average skills and known techniques, to achieve the desired implementation that addresses the needs of the particular application. 
     A “computer” may refer to one or more apparatus and/or one or more systems that are capable of accepting a structured input, processing the structured input according to prescribed rules, and producing results of the processing as output. Examples of a computer may include: a computer; a stationary and/or portable computer; a computer having a single processor, multiple processors, or multi-core processors, which may operate in parallel and/or not in parallel; a general purpose computer; a supercomputer; a mainframe; a super mini-computer; a mini-computer; a workstation; a micro-computer; a server; a client; an interactive television; a web appliance; a telecommunications device with internet access; a hybrid combination of a computer and an interactive television; a portable computer; a tablet personal computer (PC); a personal digital assistant (PDA); a portable telephone; a mobile telephone; a smartphone; a tablet; a wearable computing system including, but not limited to, an eyeglass, a watch, a bracelet, an earpiece, a headband; application-specific hardware to emulate a computer and/or software, such as, for example, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application specific integrated circuit (ASIC), an application specific instruction-set processor (ASIP), a chip, chips, a system on a chip, or a chip set; a data acquisition device; an optical computer; a quantum computer; a biological computer; and generally, an apparatus that may accept data, process data according to one or more stored software programs, generate results, and typically include input, output, storage, arithmetic, logic, and control units. 
     Those of skill in the art will appreciate that where appropriate, some embodiments of the disclosure may be practiced in network computing environments with many types of computer system configurations, including personal computers, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. Where appropriate, embodiments may also be practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or by a combination thereof) through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices. 
     “Software” may refer to prescribed rules to operate a computer. Examples of software may include: code segments in one or more computer-readable languages; graphical and or/textual instructions; speech to text and/or text to speech applications; speech recognition applications; applets; pre-compiled code; interpreted code; compiled code; and computer programs. 
     The example embodiments described herein can be implemented in an operating environment comprising computer-executable instructions (e.g., software) installed on a computer, in hardware, or in a combination of software and hardware. The computer-executable instructions can be written in a computer programming language or can be embodied in firmware logic. If written in a programming language conforming to a recognized standard, such instructions can be executed on a variety of hardware platforms and for interfaces to a variety of operating systems. Although not limited thereto, computer software program code for carrying out operations for aspects of the present invention can be written in any combination of one or more suitable programming languages, including an object oriented programming languages and/or conventional procedural programming languages, and/or programming languages such as, for example, Hyper text Markup Language (HTML), Dynamic HTML, Extensible Markup Language (XML), Extensible Stylesheet Language (XSL), Document Style Semantics and Specification Language (DSSSL), Cascading Style Sheets (CSS), Synchronized Multimedia Integration Language (SMIL), Wireless Markup Language (WML), Java™, Jini™, C, C++, Smalltalk, Perl, UNIX Shell, Visual Basic or Visual Basic Script, Virtual Reality Markup Language (VRML), ColdFusion™ or other compilers, assemblers, interpreters or other computer languages or platforms. 
     Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user&#39;s computer, partly on the user&#39;s computer, as a stand-alone software package, partly on the user&#39;s computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user&#39;s computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). 
     A network is a collection of links and nodes (e.g., multiple computers and/or other devices connected together) arranged so that information may be passed from one part of the network to another over multiple links and through various nodes. Examples of networks include the Internet, the public switched telephone network, the global Telex network, computer networks (e.g., an intranet, an extranet, a local-area network, or a wide-area network), wired networks, and wireless networks. 
     The Internet is a worldwide network of computers and computer networks arranged to allow the easy and robust exchange of information between computer users. Hundreds of millions of people around the world have access to computers connected to the Internet via Internet Service Providers (ISPs). Content providers (e.g., website owners or operators) place multimedia information (e.g., text, graphics, audio, video, animation, and other forms of data) at specific locations on the Internet referred to as webpages. Websites comprise a collection of connected, or otherwise related, webpages. The combination of all the websites and their corresponding webpages on the Internet is generally known as the World Wide Web (WWW) or simply the Web. 
     Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. 
     The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. 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 involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. 
     These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks. 
     Further, although process steps, method steps, algorithms or the like may be described in a sequential order, such processes, methods and algorithms may be configured to work in alternate orders. In other words, any sequence or order of steps that may be described does not necessarily indicate a requirement that the steps be performed in that order. The steps of processes described herein may be performed in any order practical. Further, some steps may be performed simultaneously. 
     It will be readily apparent that the various methods and algorithms described herein may be implemented by, e.g., appropriately programmed general purpose computers and computing devices. Typically a processor (e.g., a microprocessor) will receive instructions from a memory or like device, and execute those instructions, thereby performing a process defined by those instructions. Further, programs that implement such methods and algorithms may be stored and transmitted using a variety of known media. 
     When a single device or article is described herein, it will be readily apparent that more than one device/article (whether or not they cooperate) may be used in place of a single device/article. Similarly, where more than one device or article is described herein (whether or not they cooperate), it will be readily apparent that a single device/article may be used in place of the more than one device or article. 
     The functionality and/or the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality/features. Thus, other embodiments of the present invention need not include the device itself. 
     The term “computer-readable medium” as used herein refers to any medium that participates in providing data (e.g., instructions) which may be read by a computer, a processor or a like device. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media include, for example, optical or magnetic disks and other persistent memory. Volatile media include dynamic random access memory (DRAM), which typically constitutes the main memory. Transmission media include coaxial cables, copper wire and fiber optics, including the wires that comprise a system bus coupled to the processor. Transmission media may include or convey acoustic waves, light waves and electromagnetic emissions, such as those generated during radio frequency (RF) and infrared (IR) data communications. Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, DVD, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, an EPROM, a FLASH-EEPROM, removable media, flash memory, a “memory stick”, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read. 
     Various forms of computer readable media may be involved in carrying sequences of instructions to a processor. For example, sequences of instruction (i) may be delivered from RAM to a processor, (ii) may be carried over a wireless transmission medium, and/or (iii) may be formatted according to numerous formats, standards or protocols, such as Bluetooth, TDMA, CDMA, 3G. 
     Where databases are described, it will be understood by one of ordinary skill in the art that (i) alternative database structures to those described may be readily employed, (ii) other memory structures besides databases may be readily employed. Any schematic illustrations and accompanying descriptions of any sample databases presented herein are exemplary arrangements for stored representations of information. Any number of other arrangements may be employed besides those suggested by the tables shown. Similarly, any illustrated entries of the databases represent exemplary information only; those skilled in the art will understand that the number and content of the entries can be different from those illustrated herein. Further, despite any depiction of the databases as tables, an object-based model could be used to store and manipulate the data types of the present invention and likewise, object methods or behaviors can be used to implement the processes of the present invention. 
     A “computer system” may refer to a system having one or more computers, where each computer may include a computer-readable medium embodying software to operate the computer or one or more of its components. Examples of a computer system may include: a distributed computer system for processing information via computer systems linked by a network; two or more computer systems connected together via a network for transmitting and/or receiving information between the computer systems; a computer system including two or more processors within a single computer; and one or more apparatuses and/or one or more systems that may accept data, may process data in accordance with one or more stored software programs, may generate results, and typically may include input, output, storage, arithmetic, logic, and control units. 
     A “network” may refer to a number of computers and associated devices that may be connected by communication facilities. A network may involve permanent connections such as cables or temporary connections such as those made through telephone or other communication links. A network may further include hard-wired connections (e.g., coaxial cable, twisted pair, optical fiber, waveguides, etc.) and/or wireless connections (e.g., radio frequency waveforms, free-space optical waveforms, acoustic waveforms, etc.). Examples of a network may include: an internet, such as the Internet; an intranet; a local area network (LAN); a wide area network (WAN); and a combination of networks, such as an internet and an intranet. 
     As used herein, the “client-side” application should be broadly construed to refer to an application, a page associated with that application, or some other resource or function invoked by a client-side request to the application. A “browser” as used herein is not intended to refer to any specific browser (e.g., Internet Explorer, Safari, FireFox, or the like), but should be broadly construed to refer to any client-side rendering engine that can access and display Internet-accessible resources. A “rich” client typically refers to a non-HTTP based client-side application, such as an SSH or CFIS client. Further, while typically the client-server interactions occur using HTTP, this is not a limitation either. The client server interaction may be formatted to conform to the Simple Object Access Protocol (SOAP) and travel over HTTP (over the public Internet), FTP, or any other reliable transport mechanism (such as IBM® MQSeries® technologies and CORBA, for transport over an enterprise intranet) may be used. Any application or functionality described herein may be implemented as native code, by providing hooks into another application, by facilitating use of the mechanism as a plug-in, by linking to the mechanism, and the like. 
     Exemplary networks may operate with any of a number of protocols, such as Internet protocol (IP), asynchronous transfer mode (ATM), and/or synchronous optical network (SONET), user datagram protocol (UDP), IEEE 802.x, etc. 
     Embodiments of the present invention may include apparatuses for performing the operations disclosed herein. An apparatus may be specially constructed for the desired purposes, or it may comprise a general-purpose device selectively activated or reconfigured by a program stored in the device. 
     Embodiments of the invention may also be implemented in one or a combination of hardware, firmware, and software. They may be implemented as instructions stored on a machine-readable medium, which may be read and executed by a computing platform to perform the operations described herein. 
     More specifically, as will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon. 
     In the following description and claims, the terms “computer program medium” and “computer readable medium” may be used to generally refer to media such as, but not limited to, removable storage drives, a hard disk installed in hard disk drive, and the like. These computer program products may provide software to a computer system. Embodiments of the invention may be directed to such computer program products. 
     An algorithm is here, and generally, considered to be a self-consistent sequence of acts or operations leading to a desired result. These include physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers or the like. It should be understood, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. 
     Unless specifically stated otherwise, and as may be apparent from the following description and claims, it should be appreciated that throughout the specification descriptions utilizing terms such as “processing,” “computing,” “calculating,” “determining,” or the like, refer to the action and/or processes of a computer or computing system, or similar electronic computing device, that manipulate and/or transform data represented as physical, such as electronic, quantities within the computing system&#39;s registers and/or memories into other data similarly represented as physical quantities within the computing system&#39;s memories, registers or other such information storage, transmission or display devices. 
     Additionally, the phrase “configured to” or “operable for” can include generic structure (e.g., generic circuitry) that is manipulated by software and/or firmware (e.g., an FPGA or a general-purpose processor executing software) to operate in a manner that is capable of performing the task(s) at issue. “Configured to” may also include adapting a manufacturing process (e.g., a semiconductor fabrication facility) to fabricate devices (e.g., integrated circuits) that are adapted to implement or perform one or more tasks. 
     In a similar manner, the term “processor” may refer to any device or portion of a device that processes electronic data from registers and/or memory to transform that electronic data into other electronic data that may be stored in registers and/or memory. A “computing platform” may comprise one or more processors. 
     Embodiments within the scope of the present disclosure may also include tangible and/or non-transitory computer-readable storage media for carrying or having computer-executable instructions or data structures stored thereon. Such non-transitory computer-readable storage media can be any available media that can be accessed by a general purpose or special purpose computer, including the functional design of any special purpose processor as discussed above. By way of example, and not limitation, such non-transitory computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code means in the form of computer-executable instructions, data structures, or processor chip design. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or combination thereof) to a computer, the computer properly views the connection as a computer-readable medium. Thus, any such connection is properly termed a computer-readable medium. Combinations of the above should also be included within the scope of the computer-readable media. 
     While a non-transitory computer readable medium includes, but is not limited to, a hard drive, compact disc, flash memory, volatile memory, random access memory, magnetic memory, optical memory, semiconductor based memory, phase change memory, optical memory, periodically refreshed memory, and the like; the non-transitory computer readable medium, however, does not include a pure transitory signal per se; i.e., where the medium itself is transitory. 
     Some embodiments of the present invention may provide means and/or methods for metadata-based search summary creation. Some of these embodiments may comprise computer software. In some of these embodiments, software may be integrated into hardware, including, without limitation, uniquely-designed hardware for running embodiment software. 
     Preferred embodiments of the present invention provide a new type of search result, in the form of an automatically generated text summary of substantially relevant search results. Within the summary, each sentence or text fragment has one or more references such as, but not limited to, a bibliographical reference or web address to the Web page(s) from which the text fragment was extracted. In some embodiments, the summary constitutes a digest on the topic specified by the user&#39;s query, extracting and blending together significant and relevant aspects of the results. Ideally, the user&#39;s query is satisfied, and the user does not need to navigate individual sources; however, in some embodiments the user is able to navigate these individual sources if desired. Preferred embodiments are implemented for Internet searches; however, some embodiments may be implemented to address search issues in other locations such as, but not limited to, the Intranet, an enterprise network, a standalone computer, when searching from a mobile communication device, etc. In preferred embodiments, the graphical user interface (GUI) is in the form of a button on the main search engine page and/or on the search engine results page with a command to display a text summary of results. Once the user clicks this button, the summary is produced and displayed for the user. 
     Preferred embodiments of the present invention comprise the following components: search means, a multi-document summarization engine and a software program. A system implementing these components may have a human interface or an application programming interface (API). The search means may be a search engine, meta-search engine, vertical search engine, or other means of searching that accepts the user&#39;s query, matches the query against a set of documents in a search engine index, and returns a list of matching search results. A query may be entered by, without limitations, voice input and/or touch input such as, typing, clicking, etc. The search engine may be proprietary or commercially available. Depending on the particular embodiment, the search engine may be on the Internet, the Intranet, an enterprise network, a local area network (LAN), a mobile communication device, or a standalone computer or server. In preferred embodiments, the multi-document summarization engine analyzes the search results returned by the search engine, and produces a text summary of the results. Those skilled in the art will recognize, in accordance with the present teachings, that there are a variety of algorithms of multi-document summarization that may be used in embodiments of the present invention. The software program in preferred embodiments integrates the search engine, the summarization engine, and user interface actions such as, but not limited to, buttons to request the summary and to display the summary, save buttons, etc. This software program is herein referred to as the system core. Those skilled in the art will recognize, in accordance with the present teachings, that the exact mechanism for the implementation of the system core can vary, as long as the components are integrated in accordance with embodiments of the present invention. 
     The summary of results may satisfy the user&#39;s query fully or partially depending on the particular embodiment or system settings. The summary obtained from preferred embodiments may contain answers that the user was looking for, or at least give the user a good overview of the information contained in the document set. From the summary, the user can see which of the documents are better suited to his query, and may navigate to those documents directly from the summary. 
     Multi-document summarization systems are known to those skilled in the art. There is a great variety of algorithms used by different systems, targeting various domains of content and producing different quality of summaries. In general, a multi-document summarization system reads each document in the set of documents to summarize, analyzes the syntax and semantics of the documents, extracts key semantic concepts from the document, matches sentences or text fragments to the concepts being extracted, and constructs a summary comprising sentences or text fragments taken out of different documents in the set of documents to summarize. Those skilled in the art will recognize, in accordance with the present teachings that the exact algorithm for summarization may vary greatly between various systems. For example, without limitation, in some embodiments the summarization algorithm may be based on natural language processing (NLP), analyzing the text of the search results, identifying key concepts or text fragments, and scoring these concepts or text fragments using various factors such as, but not limited to, relevance. In some embodiments the summarization algorithm may consider document structure, document format, metatags, or other types of data associated with the search results when identifying and scoring the key concepts or text fragments on relevance to the query. In the preferred embodiment, the key concepts and text fragments are organized in order of decreasing relevance; however, in alternate embodiments other factors such as, but not limited to, the position of a concept or text fragment on the source page, may also be taken into account. Other factors that the system may take into account when organizing the concepts and text fragments can be: predefined ranking of concepts; dynamically calculated ranking of concepts based on some criteria; ranking of the document (predefined or dynamically calculated); metadata associated with the concepts or documents; comparative rank of the author of the source text; sentiment implied by the concept or text fragment; target audience characteristics and the corresponding assessment of the concept or text fragment in view of matching those characteristics. For example, level of complexity of the content; or acceptable level of profanity; etc. A multi-document summarization system aims to produce a summary that looks like a coherent text to the user, or to give the user a good overview of the set of documents. The summary can be assembled in many ways depending on the task, without limitations, the audience, and any other factors. For example, when researching a strategy for a government decision, two summaries may be requested—one “pro”, the other “con”. 
     It is expected that the users&#39; quality expectations from a summary of loosely-related documents of different nature, format, and target audience, as is also typical for the Internet, are generally lower than of a coherent, linear text written by a single author for a homogeneous audience. Hence for many types of queries, it is expected that users, particularly Internet users, will prefer a summary, even of an imperfect quality, to numerous links to Web pages. If the user is not satisfied by the summary, the preferred embodiment also provides conventional search results alongside the summary as another option. It is further understood that there are certain types of user queries where a summary is not sensible or not possible to produce. There are also types of queries where the user is not interested in getting a summary on the topic of the query, but rather wants to locate a particular Web page. These searches may not benefit from embodiments of the present invention. However, a great number of other types of searches will. 
     The preferred embodiment combines a search engine and a multi-document summarization engine in a way that is not currently available. Traditionally, search results have been perceived as a list of documents, or links to documents. As for summarization, there are some search systems that provide individual summaries of search results, which is different from multi-document summarization. However, the preferred embodiment of the present invention produces a summary of multiple search results, and treats the said summary as the main result of the user&#39;s search. 
       FIG. 1  illustrates an exemplary search results page from an Internet search engine with an addition of a summary request button  100 , in accordance with an embodiment of the present invention. The page displays the user&#39;s query for “causes of ocean tides” in a query field  101 , and a search results list  103 , as links to documents that were found by the search engine while matching the query. The user&#39;s query may be entered by, without limitations, voice input and/or touch input such as, typing, clicking, etc. In the present example, each search result in search results list  103  is displayed with a title, a URL to the location of the document, and a snippet of text that the search engine has associated with the result. 
     In the present embodiment, the page comprises three additions to the conventional display of search results, summary request button  100 , a text fragments field  105 , and a checkbox  110  for each search result in search results list  103 . In the present embodiment, summary request button  100  is in the top right section of the screen and reads “Get text summary of results!” If the user clicks summary request button  100 , a summary of the results displayed that are displayed on this page is generated by the system. In alternate embodiments, summary request buttons may have various designs with various different commands on the buttons and may be located in various places on the search page and on various pages of the search engine. For example, without limitation, a summary request button may be placed on the main page of the search engine as well as on the results page, in which case the step of displaying the conventional search results can be bypassed altogether, and the user can be taken directly to the summary. Text fragments field  105  indicates the number of text fragments or sentences to be included in the summary, and may be specified by the user in text fragments field  105 . In this example, only six sentences are requested, in order for the display of the summary to fit on a single page. Checkboxes  110  are located next to each search result in search results list  103 , enabling the user to specify which of the search results are to be included in the summary. In the present embodiment, a default setting includes all of the search results in the summary; however, alternate embodiments may have different default settings. 
       FIG. 2  illustrates an exemplary summary  200  on a user&#39;s query, produced by a search system, in accordance with an embodiment of the present invention. In the present embodiment, summary  200  is presented as a list of sentences; however, in alternate embodiments, the summary may be displayed in different formats such as, but not limited to, a list of semantic concepts, a cluster hierarchy, a tag cloud, etc. The sentences or text fragments within summary  200  originated from various sources, which are listed below the summary in a source list  205 . The sources in source list  205  refer to the documents or Web pages found by the search engine as displayed in a conventional search result, shown by way of example in  FIG. 1 . The sources in source list  205  are clickable links, which can take the user to the corresponding Web page. Note that not all sources from the search shown in  FIG. 1  are listed in source list  205 . It is up to the multi-document summarization engine to decide which sources to include and in what order. Factors such as, but not limited to, the quality of the sources and the length of the summary as requested by the user may affect which sources are used in summary  200  and displayed in source list  205 . The multi-document summarization engine may also determine whether duplicates are present in the summary. If a duplicate is present, it may be removed from the summary. 
     Also, the user has an option of removing some of the sources by deselecting checkboxes  210 , which are next to each source in source list  205 , and regenerating summary  200 . When summary  200  is regenerated, the system only uses the sources from source list  205  that remain selected. The user may also change the number of sentences in summary  200  by changing the number in a text fragments field  213 . In alternate embodiments the user may have different options for controlling the length of the summary for example, without limitation, a setting to set the overall number of pages, or a setting to set the length of the summary as a percentage of the total amount of text in the sources. In the present embodiment, a modify summary button  215  is used to regenerate summary  200 . Also the user can click a save summary button  220  to save summary  200  in a file on a local or network drive. In an alternate embodiment, all original sources can be displayed, allowing the user to request a modified summary that would use the sources specified by the user. 
     A group of radio-buttons enabling the user to control the presentation of sources within summary  200  is presented. The setting displayed in the present example is a hide sources setting  223 , which indicates that each sentence in summary  200  is not followed by a reference to its corresponding source. The present embodiment also comprises a show sources setting  225  and a group sentences per source setting  227 . Show sources setting  225  displays the source of each sentence after the sentence within summary  200 , as shown by way of example in  FIG. 3 , and group sentence per source setting  227  groups the sentences in summary  200  by source and lists this source after each group of sentences. Alternate embodiments may have various other features and settings for the user interface such as, but not limited to, a language setting for the query, a rating feature, a print feature, a save feature, a feature enabling users to share summaries, a comment feature, a voting feature, etc. Other user interface setting may include: allowing the user to refine the original query, for example by entering a different wording, or by specifying the concepts that would modify the topic of the query; turn on or off the display of relevance scores; marking some sentences in the summary for removal, and generating a summary without them. The text summary can also be overlayed with graphics, video, and other types of media for presentation purposes. 
       FIG. 3  illustrates an exemplary summary  300  on a user&#39;s query, where each sentence or text fragment in summary  300  is followed by a reference  303  to its source, in accordance with an embodiment of the present invention. This setting is defined by a show sources setting, as shown by way of example in  FIG. 2 . In the present embodiment, references  303  are listed as clickable URLs to the Web pages from which the text fragments are sourced, which can take the user to the corresponding Web page. The present embodiment also comprises a source list  305  and checkboxes  310  that enable the user to select or deselect the sources to be included in summary  300 . 
     The fragments of text comprising summary  300  are ordered according to their semantics as opposed to their order on the source Web pages. Therefore, even though some text fragments are sourced from the same Web page, they are generally not sequentially presented in summary  300 . The exact mechanism of ordering of text fragments is not specified by the present embodiment, however, the example illustrates that the system summarized a set of documents as a whole, as opposed to concatenating individual summaries. Furthermore some embodiments of the present invention may specify how to order the text fragments, for example, without limitation, alphabetically by source, by relevance, etc. 
       FIG. 4  is a flowchart illustrating an exemplary process for the interaction between a search engine and a summarization engine, in accordance with an embodiment of the present invention. The following steps are presented to describe the process according to the present embodiment. In step  400 , a user submits a query to a search engine. In step  410  the search engine receives the query, locates matching documents in the search engine data store, and returns a list of links to the documents. The search results may be in various forms for example, without limitation, documents or files containing text or fragments of text. These documents may be in any format readable by the system, for example, without limitation, HTML, TXT, DOC, RTF, PPT, XLS, XML, etc. Also, the language of the text may be any language, and the language of the various documents in the results may be the same or different. In various embodiments the search results may originate from various sources such as, but not limited to, the Internet, an Intranet, an enterprise network, a LAN, a database or computer file generated by a computer program based on an algorithm, etc. In the present embodiment, the search results are received by a system core, which is a piece of software integrating other pieces of the present embodiment. In step  420  the system core passes the top links and the original user&#39;s query to a multi-document summarization engine. The number of links passed to the multi-document summarization engine may be specified by the user or configured internally. Furthermore, the language of the query and the documents may be specified to the multi-document summarization engine or automatically identified by the multi-document summarization engine, and the multi-document summarization engine may skip a document if the language is not recognized. 
     In step  430  the multi-document summarization engine receives the query and the links to the documents. Then, the multi-document summarization engine parses each individual document to extract key semantic concepts and corresponding text fragments or sentences and performs multi-document summarization of the documents based on the extracted concepts, producing a text summary representing a digest of the search results. The summary may comprise key semantic concepts, text fragments or sentences matching these concepts, or a combination of the two. The user query may be taken into account, to focus the summary on a particular topic using means such as, but not limited to, NLP or metadata to help determine relevance of the results. In the present embodiment, if the system is unable to use the query, for example, without limitation, if the query is unrecognized by the system, empty, or not passed to the system, the system generates a summary of key semantic concepts in the documents without focusing on a particular topic. In an alternate embodiment, if the system is unable to use the query, the system produces a summary based on a topic derived by the system that is based on predefined or built-in criteria or based on additional parameters. In other alternate embodiments, if the system is unable to use the query an error message may be sent to the user that may ask the user to change the query. A relevance score may be calculated for each concept or text fragment, and this relevance score may or may not be displayed to the user in the summary and may be used by the system for learning. 
     In the present embodiment, content dictionaries  435  comprising words, phrases or concepts related to a particular content domain may be used by the multi-document summarization engine. The words, phrases and concepts in content dictionaries  435  may be characteristic for particular information domains, or may be not pertinent to the content domain, enabling the multi-document summarization engine to adjust its algorithm to better suit the particular information domain. Rules that help the system to understand and classify the content may be used. Content dictionaries  435  may be static, dynamically populated by users or administrators, or accumulated by the system through self-learning features of the system. Other information that may be used by the self-learning features includes, without limitation, feedback from users or otherwise and relevance scores. Alternate embodiments may not comprise self-learning features. 
     In step  440  of the present embodiment, the summary is returned to the system core. In step  450  the system core displays the summary to the user. In step  460  the user can perform various functions such as, but not limited to, save the summary on a local or network drive, print the summary, edit the summary if the system core provides a text editor, and navigate through the search engine to the individual sources. If the user is satisfied at this point, the user may end the process. Otherwise, the user can rate the summary based on criteria such as, but not limited to, satisfaction and quality and pass the feedback to the summarization engine in step  465 , “Like”/“Don&#39;t like”, or may request a modified summary in step  470 . The user may have the option to rate the overall summary, individual text fragments, or the source documents returned by the system in step  465 . This feedback may be used by the self-learning feature of the system. The user can also modify parameters such as, but not limited to, the length of the summary, the way references are represented, the sources that should or should not be included in the summary, or any other parameters exposed by the system, by requesting a modified summary in step  470 , and the system returns to step  430  to perform another multi-document summarization of the documents using the new parameters. 
     In an alternate embodiment, a search engine is integrated with the summarization engine into one system. This would enable the system to analyze each individual document as the document is added to the data store of the system rather than during the multi-document summarization process. Therefore, the summarization engine in this case does not need to repeat this analysis in step  430 , thus making the whole operation much faster. In this embodiment both the search engine and the summarization engine have access to the documents, for example, without limitation, through a database or file server. 
     In the alternate embodiment, the system may be implemented without a separate system core. For example, the search engine may be calling the summarization engine, passing the summarization engine the documents. In this case, the search engine implementation would comprise the system core. Alternatively, the summarization engine may be calling the search engine, receiving back the documents to summarize. In this case, the summarization engine implementation would comprise the system core. 
     The preferred embodiment described above comprises a search engine integrated with a multi-document summarization engine. However, an alternate embodiment of the present invention comprises an Internet directory integrated with a multi-document summarization engine instead of a search engine. An Internet directory comprises a hierarchy of categories that the user browses. At the lower levels of the hierarchy, the user is presented with a list of matching documents or Web pages, which may be processed by the multi-document summarization engine. In this case, steps  400  and  410  of the process previously described are not applicable. Instead, the user browses the Internet directory until he finds a page that contains links to the documents pertinent to his topic of interest. Those links are then passed by the system core in step  420  to the multi-document summarization engine. For example, without limitation, a user who is searching for legal advice in a Web directory for example, without limitation, About.com, navigates down to a particular area of his legal issue, and requests a summary of the documents listed on that level of the directory. The summary serves as an overview of the key concepts related to the user&#39;s issue, extracted from the documents in the directory. 
     Another alternate embodiment of the present invention may be implemented in a question answering system. A question answering system accepts a user&#39;s question. The question is then processed by the question answering system, and a number of possible responses or articles are identified. The system then passes the results to a multi-document summarization engine, which produces an overall summary of the results as the answer to the user&#39;s question. A knowledge base residing on a computer network, for example, without limitation, the Internet, the Intranet, or a LAN, or on a standalone computer or server may be implemented in another alternate embodiment. The implementation of a knowledgebase is similar to the implementation of a question answering system. 
       FIG. 5  is a flowchart illustrating an exemplary process for the interaction between a question answering system and a summarization engine, in accordance with an embodiment of the present invention. In the present embodiment, a question answering system is used instead of a search engine. The difference is that the question answering system itself performs a search for documents matching the user&#39;s query in an answer data store  515  comprising answers to various questions or a knowledgebase then passes the results to the summarization engine and returns the multi-document summary as the answer to the user. 
     In the present embodiment, the process begins at step  500  where the user submits a query. In step  510  the question answering system performs a search in answer data store  515  and produces a list of links to documents. In step  520  a system core passes the search results and the query to a multi-document summarization engine. In step  530  the multi-document summarization engine performs a multi-document summarization of the results as previously described in accordance with  FIG. 4 , step  430 . The summary is returned to the system core in step  540 , and in step  550  the system core displays the summary to the user as an answer to the query. In step  560  the user may save or print the summary or may navigate the individual sources cited in the summary. If the user is satisfied with the summary, the process ends. If the user wishes, the user may refine the query or modify the parameters of the search and/or summarization in step  570 . The system then returns to step  530  to perform the multi-document summarization again using the refined query and/or new parameters. 
     In an alternate embodiment, a computer program installed on a standalone computer or a LAN server calls a search engine via an API. This computer program then receives the links to the documents and passes the links to the summarization engine. Then, the computer program receives the summary from the summarization engine and displays the summary to the user. 
     In another alternate embodiment, a computer program installed on a mobile communications device calls a server application passing along a query from the user. This server application then passes the query to a search engine and receives links to documents that the search engine finds as results. The application then passes the links to the summarization engine, receives the summary, and returns the summary to the mobile device to display to the user. 
     In yet another alternate embodiment, an application may be implemented as a computer program running on a standalone computer. In this embodiment, the computer program performs a search on the local computer drives or network drives and summarizes the found search results on the same computer. 
     In yet another alternate embodiment, a web page or number of web pages comprising a web application calls a search engine and receives back links to documents. Then, the web page passes the links to a summarization engine, receives the summary from the summarization engine, and displays the summary to a user. In another alternate embodiment, a web service rather than a web page may be used to call the web application that interacts with the search engine and summarization engine. In this embodiment, once the web service receives the summary, the web service returns the summary to its caller application to peruse the summary in any desired fashion. 
     In yet other alternate embodiments, an Internet browser plug-in or add-on, or an application installed on a mobile communication device may be used. In these embodiments the Internet browser plug-in or add-on may either call on a search engine to receive links to documents or screen-scrape the results of a search on a Web page to receive links to documents. The Internet browser plug-in or add-on then sends the links to a summarization engine, receives back the summary, and displays the summary to a user. 
       FIG. 6  illustrates a typical computer system that, when appropriately configured or designed, can serve as a computer system in which the invention may be embodied. The computer system  600  includes any number of processors  602  (also referred to as central processing units, or CPUs) that are coupled to storage devices including primary storage  606  (typically a random access memory, or RAM), primary storage  604  (typically a read only memory, or ROM). CPU  602  may be of various types including microcontrollers (e.g., with embedded RAM/ROM) and microprocessors such as programmable devices (e.g., RISC or SISC based, or CPLDs and FPGAs) and unprogrammable devices such as gate array ASICs or general purpose microprocessors. As is well known in the art, primary storage  604  acts to transfer data and instructions uni-directionally to the CPU and primary storage  606  is used typically to transfer data and instructions in a bi-directional manner. Both of these primary storage devices may include any suitable computer-readable media such as those described above. A mass storage device  608  may also be coupled bi-directionally to CPU  602  and provides additional data storage capacity and may include any of the computer-readable media described above. Mass storage device  608  may be used to store programs, data and the like and is typically a secondary storage medium such as a hard disk. It will be appreciated that the information retained within the mass storage device  608 , may, in appropriate cases, be incorporated in standard fashion as part of primary storage  606  as virtual memory. A specific mass storage device such as a CD-ROM  614  may also pass data uni-directionally to the CPU. 
     CPU  602  may also be coupled to an interface  610  that connects to one or more input/output devices such as such as video monitors, track balls, mice, keyboards, microphones, touch-sensitive displays, transducer card readers, magnetic or paper tape readers, tablets, styluses, voice or handwriting recognizers, or other well-known input devices such as, of course, other computers. Any of which may be used for entering or inputting search queries and/or instructions. Finally, CPU  602  optionally may be coupled to an external device such as a database or a computer or telecommunications or internet network using an external connection as shown generally at  612 , which may be implemented as a hardwired or wireless communications link using suitable conventional technologies. With such a connection, it is contemplated that the CPU might receive information from the network, or might output information to the network in the course of performing the method steps described in the teachings of the present invention. 
     In the foregoing some embodiments are described as generating a multi-document text summary. While it is the text that is typically analyzed by the system in order to generate a coherent document for the user, in some embodiments the multi-document summary may also include a multiplicity of suitable media in addition to or rather than text. In these embodiments, source documents may contain not only text, yet may also include, without limitation, images, videos, audio, and other media formats. These different media formats may also be included, without limitation, into the generated summary. The inclusion of multiple media formats may help to support the user&#39;s understanding of the summary with visuals, audio, and other media objects, which may enhance the user&#39;s experience. It is contemplated that the logic used to include the media objects may be different in various different embodiments. For example, without limitation, one embodiment may use the metadata accompanying the media objects such as, but not limited to, a title, a description, an author, etc. In another embodiment, the system may analyze the text describing a particular media object, even when such text is not directly a part of the metadata describing the image for example, without limitation, if the text is a user comment or a caption on an image or video, to deem the object relevant to the summary that is being generated by the system. If the system deems the media object relevant, the object is included, without limitation, in the summary, either by itself or alongside other fragment(s) of text or other relevant media objects from the source documents. 
     In the foregoing a variety of non-limiting examples of approaches to implementing multi-document summarization are described. Those skilled in the art will readily recognize, in light of and in accordance with the teachings of the present invention that no particular definition of multi-document summarization, whether from research circles or industry-wide, is essential for search systems according to various embodiments of the present invention to operate. Therefore, in relation to this description, multi-document summarization is not a strict term, and rather generally refers to any compilation of text and other meaningful information from more than one source that attempts to deliver a coherent summary to the user. 
     In one embodiment, a search system may be combined with an Internet service such as, but not limited to, a travel site or a real estate office website to enable a user to obtain information about a hotel, restaurant, town, etc. In this embodiment the system performs a search for information on an object or a multitude of objects being researched, for example, without limitation, hotels, restaurants, real estate areas, attractions, etc. and creates a summary of relevant information from multiple sources such as, but not limited to, Wikipedia, travel sites, newspapers, municipal records, tourists&#39; reviews, etc. Various different types of Internet services may be incorporated into embodiments similar to this such as, but not limited to, retail sites, theater or entertainment rental sites, directories for local service providers, etc. 
     Some embodiments may be implemented with the ability to learn. In some of these embodiments, the system may learn through explicit feedback by analyzing feedback from the user. Some embodiments may also use automated feedback to tune itself or augments in its dictionaries based upon observing implicit metrics including, without limitation, how much time the user spent reading the summary or whether the user used the summary for further navigation and searches. It is contemplated that in some embodiments various different metrics such as, but not limited to, if the user prints or forwards the summary, if the user creates a shortcut to the summary or how many times the user views any videos or listens to any audio files in the summary, may be defined by various different implementations in which the system can learn automatically and tune its summary generation algorithms accordingly with or without human intervention. 
     In some embodiments, the query to the system may not be directly entered by the user, but implied by the system based on various considerations, including but not limited to, user preferences, user search history, an advertiser&#39;s preferences, a preconfigured query, or some default algorithm that the system implements. In other embodiments of the present invention, voice input may be used as a way of entering the search query and an audio summary will be read to the user, as a result of the query. 
       FIG. 7  illustrates the architecture of an exemplary system for metadata-based search summary creation, in accordance with an embodiment of the present invention. Metadata-based search summary creation architecture  700  may comprise of a query module  705 , a search module  710 , a summary module  715 , and a display module  720 . A query module  705  may have a means to receive user input such as, without limitation, a computer terminal  725 , a keyboard, a touchpad, a mouse, a voice input device, or any device possessing computing capabilities within it such as, without limitation, a smartwatch, Google glass, etc. A search module  710  may have a processing means such as, without limitation, a server  730 , a computer platform, a smartphone device. The processing means of search module  710  may be further connected to one or more databases  735  which may contain entries and/or data relevant to any searches performed by search module  710 . A summary module  715  may have a processing means such as, without limitation, server  730 , a computer terminal, a mobile communication device which may process metadata associated with a user and/or any search results and create one or more search summaries. A display module has a display means such as, without limitation, computer terminal  725 , a computer monitor, speakers, TV screen, virtual reality mechanisms, “smart” devices like Google Glass or smartwatch, etc. 
     During typical operation, a user may input a search query and metadata to be part of a search on a user input device such as computer terminal  725 . The search query and metadata is sent to a search module  710  which has a server  730  to process the search query. One or more databases  735  are searched according to the search query and/or metadata sent to search module  710 . A set of search results is created and may be compiled with the metadata sent to search module  710 . The compiled search results and metadata may then be sent to a summary module  715 . Summary module  715  has a processing means such as server  730  and may create a summary of one or more search results. The summaries created by summary module  715  may also factor in the metadata received from search module  715  and create specialized summaries according to the metadata. Summaries may be sent to a display module  720  for display to a user. Display module  720  may receive user input from a user input device such as a computer terminal  725 . User input may be used to control the summaries and/or any summary metadata displayed by display module  720 . Display module  720  may format any summaries and/or summary metadata to accommodate virtually any means to relay information to a user such as, without limitation, hiding and/or highlighting sources, hiding and/or highlighting information, comparing multiple summaries, change the font or any other formatting attributes of the summary, change the language of the summary, include or exclude multimedia elements along with the text, amplify or play down multimedia elements, exclude duplicate or similar sentences or multimedia objects. 
     It may be appreciated by a person with ordinary skill in the art, in light of and in accordance with the teachings of the present invention, that virtually any input device and method may be implemented by query module  705 . Input devices and methods may be, without limitation, physical input from keyboards, audio input from microphones, visual input from cameras, and input from other applications that deduce or generate a query according to the logic they are programmed to. In another embodiment of the present invention, a user may vocally enter a search query by speaking into a microphone. In an alternative embodiment of the present invention, a user may visually enter a search query by signing a query in sign language to a video camera. 
     It may be appreciated by a person with ordinary skill in the art, in light of and in accordance with the teachings of the present invention, that virtually any type of metadata and/or data may be submitted with a search query and/or implemented during summary creation. Metadata and/or data may be, without limitation, user statistics, user rankings of previous search results, desired tone or sentiment of sources, desired length of sources, author&#39;s viewpoint, the audience&#39;s preference or presumed viewpoint, source document format. In another embodiment of the present invention, a search summary may be created with a specific tone. In yet another embodiment of the present invention, one or more search summaries may be created with different sources and/or viewpoints. In an alternative embodiment of the present invention, a user&#39;s profile may be used to determine the complexity of the language of a search summary. 
     It may be appreciated by a person with ordinary skill in the art, in light of and in accordance with the teachings of the present invention, that search summaries may have virtually any metadata associated to virtually any part of the search summary. Search summary metadata may include, without limitation, a tone of language of any line within a search summary, a source material for any line within a search summary, a value for language complexity, search query match metrics, author&#39;s viewpoint, the audience&#39;s preference or presumed viewpoint, source document format, ranking of sources, rating or degree of authority of the author, language of the source. 
     It may be appreciated by a person with ordinary skill in the art, in light of and in accordance with the teachings of the present invention, that one or more modules may be embodied in one or more hardware devices. In another embodiment of the present invention, all the modules in metadata-based search summary creation architecture  700  may be located on one computing platform. In another embodiment of the present invention, metadata-based search summary creation architecture  700  may be embodied in a plurality of computing devices connected over a network. 
       FIG. 8  is a flow chart illustrating an exemplary process for metadata-based search summary creation, in accordance with an embodiment of the present invention. A metadata-based search summary creation process  800  begins with a receive search query step  805 . A user may enter a search query on an input device such as, without limitation, a computer terminal, microphone, keyboard, mouse, virtual reality equipment such as, without limitation, Google Glass or smartwatch. A query can also come from another application, generated according to a particular logic of that application. A query may also be issued via a sign language. The search query is received by a query module to be used for a search. A receive metadata step  810  sends search query related metadata to the query module. Search query related metadata may be virtually any data such as, without limitation, a user profile, prior search results and/or search summary rankings, a sentiment of the source, source language complexity, author&#39;s viewpoint, source document format, ranking of sources, rating or degree of authority of the author, human language of the source an input from another application, generated according to a particular logic of that application. A form search step  815  compiles the search query and any related metadata for searching. A perform search step  820  searches one or more database with the search query and/or metadata. In a receive search results step  825 , the search results from perform search step  820  are compiled for a search summary. A search summary may be created for one or more search results in a create summary step  830 . The search summary may be created with tags and/or metadata that may be informative for the user. Tags and/or metadata may be, without limitation, a comparative rank of an author of a source, a sentiment implied by one or more sources in the search summary, a target audience for one or more sources, a level of profanity, a level of complexity, human language of the summary, digital rights to the media elements of the summary. In a display results step  835 , one or more search summaries may be displayed to a user by virtually any means such as, without limitation, audibly via speakers, visually on a monitor, printouts, via email or a message on a mobile communication device, via virtual reality equipment. A user may also input display commands on an input device such as a computer terminal. A user may also submit a rating and/or metadata to be associated with a search and/or search summary for future searches. 
     It may be appreciated by a person with ordinary skill in the art, in light of and in accordance with the teachings of the present invention, that one or more search summaries may be created from a set of search results. Search summaries may be created for a combination or permutation of search queries and/or metadata related to a search. In another embodiment of the present invention, search results containing opposing viewpoints may result in one or more search summaries being generated for each viewpoint. In yet another embodiment of the present invention, a ‘pro’ and a ‘con’ search summary may be generated for a set of search results. 
     It may be appreciated by a person with ordinary skill in the art, in light of and in accordance with the teachings of the present invention, that a user may input virtually any display command in display results step  835 . Display commands may include, without limitation, highlighting and/or hiding sources, displaying search summary tags and/or metadata, change the length of the summary, request translation into a different language, share the summary, rate the summary, redefine the query, refocus the query using some of the concepts from the summary, mark some sentences for removal, edit the summary, print the summary, save the summary, control the overlay of multimedia elements in the summary. In another embodiment of the present invention, a user may choose to hide all sources in a displayed search summary such that a search summary appears as a single coherent document. In an alternative embodiment of the present invention, a user may choose to sort search summaries according to tags such as language tone or complexity. 
     It may be appreciated by a person with ordinary skill in the art, in light of and in accordance with the teachings of the present invention, that one or more steps in metadata-based search summary creation process  800  may be added, removed, or rearranged. In some embodiments of the present invention, metadata-based search summary creation process  800  may omit the steps  805 ,  810 ,  815 . In other embodiments of the present invention, the order of steps  805 ,  810 ,  815  in metadata-based search summary creation process  800  may occur in any order. In still other embodiments of the present invention, additional steps such as, but not limited to, parallel searches in multiple data stores or search engines, parallel creation of more than one summary, displaying results in more than one format, distributing results to more than one recipient, displaying results via more than one means at the same time, informing the user of the progress, may be added to metadata-based search summary creation process  800 . 
       FIG. 9  is a flow chart illustrating an exemplary process for creating search queries on a query module, in accordance with an embodiment of the present invention. A create search query process  900  begins with a receive search query step  905 . A user inputs a search query on an input device such as, without limitation, a keyboard, microphone, keyboard, mouse, virtual reality equipment such as, without limitation, Google Glass or smartwatch. A query can also come from another application, generated according to a particular logic of that application. A query may also be issued via a sign language. A receive metadata step  910  receives metadata from a user such as, without limitation, a user profile, search tags, prior search ratings, user statistics, user rankings of previous search results, desired tone or sentiment of sources, desired length of sources, author&#39;s viewpoint, the audience&#39;s preference or presumed viewpoint, source document format. A form search data step  915  compiles the search query and metadata into search data. A send search data step  920  sends the compiled search data to a search module. 
     It may be appreciated by a person with ordinary skill in the art, in light of and in accordance with the teachings of the present invention, that a user may generate metadata. In another embodiment of the present invention, a user may rate a previous search result and/or summary by selecting a ‘like’ or ‘dislike’ button. 
     It may be appreciated by a person with ordinary skill in the art, in light of and in accordance with the teachings of the present invention, metadata in receive metadata step  910  may be from virtually any source. Metadata may be from source such as, without limitation, other computing platforms, stored metadata on a non-transitory computer readable medium, data from networked sources, data generated by another application according to some logic used by that application. In another embodiment of the present invention, metadata may be user ratings of past search results and/or summaries stored on a non-transitory computer readable medium. 
     It may be appreciated by a person with ordinary skill in the art, in light of and in accordance with the teachings of the present invention, that one or more steps in create search query process  900  may be added, removed, or rearranged. In some embodiments of the present invention, create search query process  900  may omit the steps of  905 ,  910 . In other embodiments of the present invention, the order of steps  905 ,  910 ,  915  in create search query process  900  may occur in any order. In still other embodiments of the present invention, additional steps such as, but not limited to, parallel searches in multiple data stores or search engines, parallel creation of more than one summary, displaying results in more than one format, distributing results to more than one recipient, displaying results via more than one means at the same time, informing the user of the progress may be added create search query process  900 . 
       FIG. 10  is a flow chart illustrating an exemplary process for finding search results on a search module, in accordance with an embodiment of the present invention. A find search results process  1000  begins with a receive search data step  1005 . Search data is received from a query module and used by a processing means, such as a server, to perform a search. In a perform search step  1010 , the processing means executes computer code and/or software from a non-transitory computer readable medium to perform a search according to the search query information and/or metadata provided in the search data. In an access database step  1015 , the processing means may access one or more databases for matching entries that match and/or are relevant to the search data. Results from searching the one or more databases may be compiled with any metadata from the search data in a compile results step  1020 . The compiled results may be sent to a summary module in a send results step  1025  for search summary creation. 
     It may be appreciated by a person with ordinary skill in the art, in light of and in accordance with the teachings of the present invention, that one or more steps in find search results process  1000  may be added, removed, or rearranged. In some embodiments of the present invention, find search results process  1000  may omit the steps of  1005 ,  1015 . In other embodiments of the present invention, additional steps such as, but not limited to, parallel searches in multiple data stores or search engines, parallel creation of more than one summary, displaying results in more than one format, distributing results to more than one recipient, displaying results via more than one means at the same time, informing the user of the progress, may be added find search results process  1000 . 
       FIG. 11  is a flow chart illustrating an exemplary process for creating search summaries on a summary module, in accordance with an embodiment of the present invention. A create search summary process  1100  begins with a receive search results and metadata step  1105 . Compiled search results and/or metadata are received by the summary module and may be used to create one or more search summaries. In a create summary step  1110 , a processing means, such as a server, may take one or more search results and create one or more search summaries. Search summaries may be created according to the material of the one or more search results and any metadata received in receive search results and metadata step  1105 . Search summary metadata may be formed in create summary step  1110 . Search summary metadata may be data describing the contents of a search summary and/or sources used in a search summary such as, without limitation, a comparative rank of an author of a source, a sentiment implied by one or more sources, a target audience for one or more sources and/or search summary, a general viewpoint of a search summary, a level of language complexity in a source and/or search summary, a level of profanity in a source and/or search summary, search query match metrics, author&#39;s viewpoint of a source, the audience&#39;s preference or presumed viewpoint, source document format, ranking of sources, human language of the source. One or more search summaries may be created for one or more sources in create summary step  1110 . A plurality of summaries may be created with each summary being assembled according to a factor such as, without limitation, viewpoint, language complexity, search results ranking, human language of the sources, relevance threshold of the sources to the query, human language of sources, desired balance between the text and multimedia elements of the summary, desired format of multimedia elements, length of the summary, authority of the source. In a compile results step  1115 , search summaries, search summary metadata, and/or received metadata from receive search results and metadata step  1105  may be compiled into a set of search results. The compiled results are send to a display module for user viewing in a send results step  1120 . 
     It may be appreciated by a person with ordinary skill in the art, in light of and in accordance with the teachings of the present invention, that one or more search summaries may be creating for one or more search results according to virtually any factor in create summary step  1110 . Search summary creation factors may be, without limitation, target audience, opposing views of sources, tone, search metadata, language complexity, search results ranking, human language of the sources, relevance threshold of the sources to the query, human language of sources, desired balance between the text and multimedia elements of the summary, desired format of multimedia elements, length of the summary, authority of the source. In another embodiment of the present invention, a search for a topic may result in two search summaries, a ‘pro’ summary and a ‘con’ summary, to be created. 
     It may be appreciated by a person with ordinary skill in the art, in light of and in accordance with the teachings of the present invention, that one or more steps in create search summary process  1100  may be added, removed, or rearranged. In other embodiments of the present invention, additional steps such as, but not limited to, saving summaries, sharing summaries, categorizing summaries, comparing with other summaries, ranking summaries, self-assessing the quality of the summary by the system and automatically regenerating the summary with adjusted criteria or a modified set of source data, may be added create search summary process  1100 . 
       FIG. 12  is a flow chart illustrating an exemplary process for displaying results on a display module, in accordance with an embodiment of the present invention. A display data process  1200  begins with a receive results data step  1205 . During receive results data step  1205 , a display module receives data from the summary module including, without limitation, one or more search summaries, summary metadata, result snippets or full sources. A user may input commands on an input device such as, without limitation, a keyboard, microphone, mouse, touchpad, virtual reality equipment. The received results data and user commands are used to format a display in a format data step  1215 , wherein the data is converted, by a processing means such as a processor, for specific user interfaces such as, but not limited to, screens, speakers, printers, virtual reality equipment, emails, text and/or multimedia messages. A display data step  1220  presents the formatted data to a user through presentation means such as, but not limited to, screens, speakers, printers, virtual reality equipment, emails, text and/or multimedia messages. 
     It may be appreciated by a person with ordinary skill in the art, in light of and in accordance with the teachings of the present invention, that receive user commands step  1210  may receive virtually any command from a user. User commands may include, without limitation, hiding and/or highlighting search results and/or search summaries, displaying search summary metadata and/or tags, saving summary, printing summary, sharing summary via email or another communication mechanism, editing summary, refocusing the query of the summary, adjusting the length of the summary, ranking or rating the summary, voting for or against the summary (Like/Don&#39;t like), mark some sentences or elements of the summary for removal, controlling the inclusion of multimedia elements into the summary. In another embodiment of the present invention, a user may choose to hide sources such that all search summaries appear as one coherent document originating from one source. In an alternative embodiment of the present invention, a user may display search summaries with a specific tag and/or tone of language. 
     It may be appreciated by a person with ordinary skill in the art, in light of and in accordance with the teachings of the present invention, that format data step  1215  may format data intended for a user for virtually any device. Format data step  1215  may format data for devices such as, but not limited to, smartphones, computer monitors, televisions, stereoscopic displays, listening devices, printers, emails, text or multimedia messages, smart devices such as, but not limited to Google Glass or smartwatch, virtual reality equipment. In another embodiment of the present invention, data intended for a user may be converted to a sound file and audibly played to a user. 
       FIG. 13  is a block diagram depicting an exemplary client/server system which may be used by an exemplary web-enabled/networked embodiment of the present invention. 
     A communication system  1300  includes a multiplicity of clients with a sampling of clients denoted as a client  1302  and a client  1304 , a multiplicity of local networks with a sampling of networks denoted as a local network  1306  and a local network  1308 , a global network  1310  and a multiplicity of servers with a sampling of servers denoted as a server  1312  and a server  1314 . 
     Client  1302  may communicate bi-directionally with local network  1306  via a communication channel  1316 . Client  1304  may communicate bi-directionally with local network  1308  via a communication channel  1318 . Local network  1306  may communicate bi-directionally with global network  1310  via a communication channel  1320 . Local network  1308  may communicate bi-directionally with global network  1310  via a communication channel  1322 . Global network  1310  may communicate bi-directionally with server  1312  and server  1314  via a communication channel  1324 . Server  1312  and server  1314  may communicate bi-directionally with each other via communication channel  1324 . Furthermore, clients  1302 ,  1304 , local networks  1306 ,  1308 , global network  1310  and servers  1312 ,  1314  may each communicate bi-directionally with each other. 
     In one embodiment, global network  1310  may operate as the Internet. It will be understood by those skilled in the art that communication system  1300  may take many different forms. Non-limiting examples of forms for communication system  1300  include local area networks (LANs), wide area networks (WANs), wired telephone networks, wireless networks, or any other network supporting data communication between respective entities. 
     Clients  1302  and  1304  may take many different forms. Non-limiting examples of clients  1302  and  1304  include personal computers, personal digital assistants (PDAs), cellular phones and smartphones. 
     Client  1302  includes a CPU  1326 , a pointing device  1328 , a keyboard  1330 , a microphone  1332 , a printer  1334 , a memory  1336 , a mass memory storage  1338 , a GUI  1340 , a video camera  1342 , an input/output interface  1344 , and a network interface  1346 . 
     CPU  1326 , pointing device  1328 , keyboard  1330 , microphone  1332 , printer  1334 , memory  1336 , mass memory storage  1338 , GUI  1340 , video camera  1342 , input/output interface  1344  and network interface  1346  may communicate in a unidirectional manner or a bi-directional manner with each other via a communication channel  1348 . Communication channel  1348  may be configured as a single communication channel or a multiplicity of communication channels. 
     CPU  1326  may be comprised of a single processor or multiple processors. CPU  1326  may be of various types including micro-controllers (e.g., with embedded RAM/ROM) and microprocessors such as programmable devices (e.g., RISC or SISC based, or CPLDs and FPGAs) and devices not capable of being programmed such as gate array ASICs (Application Specific Integrated Circuits) or general purpose microprocessors. 
     As is well known in the art, memory  1336  is used typically to transfer data and instructions to CPU  1326  in a bi-directional manner. Memory  1336 , as discussed previously, may include any suitable computer-readable media, intended for data storage, such as those described above excluding any wired or wireless transmissions unless specifically noted. Mass memory storage  1338  may also be coupled bi-directionally to CPU  1326  and provides additional data storage capacity and may include any of the computer-readable media described above. Mass memory storage  1338  may be used to store programs, data and the like and is typically a secondary storage medium such as a hard disk. It will be appreciated that the information retained within mass memory storage  1338 , may, in appropriate cases, be incorporated in standard fashion as part of memory  1336  as virtual memory. 
     CPU  1326  may be coupled to GUI  1340 . GUI  1340  enables a user to view the operation of computer operating system and software. CPU  1326  may be coupled to pointing device  1328 . Non-limiting examples of pointing device  1328  include computer mouse, trackball and touchpad. Pointing device  1328  enables a user with the capability to maneuver a computer cursor about the viewing area of GUI  1340  and select areas or features in the viewing area of GUI  1340 . CPU  1326  may be coupled to keyboard  1330 . Keyboard  1330  enables a user with the capability to input alphanumeric textual information to CPU  1326 . CPU  1326  may be coupled to microphone  1332 . Microphone  1332  enables audio produced by a user to be recorded, processed and communicated by CPU  1326 . CPU  1326  may be connected to printer  1334 . Printer  1334  enables a user with the capability to print information to a sheet of paper. CPU  1326  may be connected to video camera  1342 . Video camera  1342  enables video produced or captured by user to be recorded, processed and communicated by CPU  1326 . 
     CPU  1326  may also be coupled to input/output interface  1344  that connects to one or more input/output devices such as such as CD-ROM, video monitors, track balls, mice, keyboards, microphones, touch-sensitive displays, transducer card readers, magnetic or paper tape readers, tablets, styluses, voice or handwriting recognizers, or other well-known input devices such as, of course, other computers. 
     Finally, CPU  1326  optionally may be coupled to network interface  1346  which enables communication with an external device such as a database or a computer or telecommunications or internet network using an external connection shown generally as communication channel  1316 , which may be implemented as a hardwired or wireless communications link using suitable conventional technologies. With such a connection, CPU  1326  might receive information from the network, or might output information to a network in the course of performing the method steps described in the teachings of the present invention. 
       FIG. 14  illustrates a block diagram depicting a conventional client/server communication system. 
     A communication system  1400  includes a multiplicity of networked regions with a sampling of regions denoted as a network region  1402  and a network region  1404 , a global network  1406  and a multiplicity of servers with a sampling of servers denoted as a server device  1408  and a server device  1410 . 
     Network region  1402  and network region  1404  may operate to represent a network contained within a geographical area or region. Non-limiting examples of representations for the geographical areas for the networked regions may include postal zip codes, telephone area codes, states, counties, cities and countries. Elements within network region  1402  and  1404  may operate to communicate with external elements within other networked regions or within elements contained within the same network region. 
     In some implementations, global network  1406  may operate as the Internet. It will be understood by those skilled in the art that communication system  1400  may take many different forms. Non-limiting examples of forms for communication system  1400  include local area networks (LANs), wide area networks (WANs), wired telephone networks, cellular telephone networks or any other network supporting data communication between respective entities via hardwired or wireless communication networks. Global network  1406  may operate to transfer information between the various networked elements. 
     Server device  1408  and server device  1410  may operate to execute software instructions, store information, support database operations and communicate with other networked elements. Non-limiting examples of software and scripting languages which may be executed on server device  1408  and server device  1410  include C, C++, C# and Java. 
     Network region  1402  may operate to communicate bi-directionally with global network  1406  via a communication channel  1412 . Network region  1404  may operate to communicate bi-directionally with global network  1406  via a communication channel  1414 . Server device  1408  may operate to communicate bi-directionally with global network  1406  via a communication channel  1416 . Server device  1410  may operate to communicate bi-directionally with global network  1406  via a communication channel  1418 . Network region  1402  and  1404 , global network  1406  and server devices  1408  and  1410  may operate to communicate with each other and with every other networked device located within communication system  1400 . 
     Server device  1408  includes a networking device  1420  and a server  1422 . Networking device  1420  may operate to communicate bi-directionally with global network  1406  via communication channel  1416  and with server  1422  via a communication channel  1424 . Server  1422  may operate to execute software instructions and store information. 
     Network region  1402  includes a multiplicity of clients with a sampling denoted as a client  1426  and a client  1428 . Client  1426  includes a networking device  1434 , a processor  1436 , a GUI  1438  and an interface device  1440 . Non-limiting examples of devices for GUI  1438  include monitors, televisions, cellular telephones, smartphones and PDAs (Personal Digital Assistants). Non-limiting examples of interface device  1440  include pointing device, mouse, trackball, scanner and printer. Networking device  1434  may communicate bi-directionally with global network  1406  via communication channel  1412  and with processor  1436  via a communication channel  1442 . GUI  1438  may receive information from processor  1436  via a communication channel  1444  for presentation to a user for viewing. Interface device  1440  may operate to send control information to processor  1436  and to receive information from processor  1436  via a communication channel  1446 . Network region  1404  includes a multiplicity of clients with a sampling denoted as a client  1430  and a client  1432 . Client  1430  includes a networking device  1448 , a processor  1450 , a GUI  1452  and an interface device  1454 . Non-limiting examples of devices for GUI  1438  include monitors, televisions, cellular telephones, smartphones and PDAs (Personal Digital Assistants). Non-limiting examples of interface device  1440  include pointing devices, mousse, trackballs, scanners and printers. Networking device  1448  may communicate bi-directionally with global network  1406  via communication channel  1414  and with processor  1450  via a communication channel  1456 . GUI  1452  may receive information from processor  1450  via a communication channel  1458  for presentation to a user for viewing. Interface device  1454  may operate to send control information to processor  1450  and to receive information from processor  1450  via a communication channel  1460 . 
     For example, consider the case where a user interfacing with client  1426  may want to execute a networked application. A user may enter the IP (Internet Protocol) address for the networked application using interface device  1440 . The IP address information may be communicated to processor  1436  via communication channel  1446 . Processor  1436  may then communicate the IP address information to networking device  1434  via communication channel  1442 . Networking device  1434  may then communicate the IP address information to global network  1406  via communication channel  1412 . Global network  1406  may then communicate the IP address information to networking device  1420  of server device  1408  via communication channel  1416 . Networking device  1420  may then communicate the IP address information to server  1422  via communication channel  1424 . Server  1422  may receive the IP address information and after processing the IP address information may communicate return information to networking device  1420  via communication channel  1424 . Networking device  1420  may communicate the return information to global network  1406  via communication channel  1416 . Global network  1406  may communicate the return information to networking device  1434  via communication channel  1412 . Networking device  1434  may communicate the return information to processor  1436  via communication channel  1442 . Processor  1446  may communicate the return information to GUI  1438  via communication channel  1444 . User may then view the return information on GUI  1438 . 
     Those skilled in the art will readily recognize, in light of and in accordance with the teachings of the present invention, that any of the foregoing steps and/or system modules may be suitably replaced, reordered, removed and additional steps and/or system modules may be inserted depending upon the needs of the particular application, and that the systems of the foregoing embodiments may be implemented using any of a wide variety of suitable processes and system modules, and is not limited to any particular computer hardware, software, middleware, firmware, microcode and the like. For any method steps described in the present application that can be carried out on a computing machine, a typical computer system can, when appropriately configured or designed, serve as a computer system in which those aspects of the invention may be embodied. 
     It will be further apparent to those skilled in the art that at least a portion of the novel method steps and/or system components of the present invention may be practiced and/or located in location(s) possibly outside the jurisdiction of the United States of America (USA), whereby it will be accordingly readily recognized that at least a subset of the novel method steps and/or system components in the foregoing embodiments must be practiced within the jurisdiction of the USA for the benefit of an entity therein or to achieve an object of the present invention. Thus, some alternate embodiments of the present invention may be configured to comprise a smaller subset of the foregoing means for and/or steps described that the applications designer will selectively decide, depending upon the practical considerations of the particular implementation, to carry out and/or locate within the jurisdiction of the USA. For example, any of the foregoing described method steps and/or system components which may be performed remotely over a network (e.g., without limitation, a remotely located server) may be performed and/or located outside of the jurisdiction of the USA while the remaining method steps and/or system components (e.g., without limitation, a locally located client) of the forgoing embodiments are typically required to be located/performed in the USA for practical considerations. In client-server architectures, a remotely located server typically generates and transmits required information to a US based client, for use according to the teachings of the present invention. Depending upon the needs of the particular application, it will be readily apparent to those skilled in the art, in light of the teachings of the present invention, which aspects of the present invention can or should be located locally and which can or should be located remotely. Thus, for any claims construction of the following claim limitations that are construed under 35 USC § 112 (6) it is intended that the corresponding means for and/or steps for carrying out the claimed function are the ones that are locally implemented within the jurisdiction of the USA, while the remaining aspect(s) performed or located remotely outside the USA are not intended to be construed under 35 USC § 112 (6). 
     It is noted that according to USA law, all claims must be set forth as a coherent, cooperating set of limitations that work in functional combination to achieve a useful result as a whole. Accordingly, for any claim having functional limitations interpreted under 35 USC § 112 (6) where the embodiment in question is implemented as a client-server system with a remote server located outside of the USA, each such recited function is intended to mean the function of combining, in a logical manner, the information of that claim limitation with at least one other limitation of the claim. For example, in client-server systems where certain information claimed under 35 USC § 112 (6) is/(are) dependent on one or more remote servers located outside the USA, it is intended that each such recited function under 35 USC § 112 (6) is to be interpreted as the function of the local system receiving the remotely generated information required by a locally implemented claim limitation, wherein the structures and or steps which enable, and breathe life into the expression of such functions claimed under 35 USC § 112 (6) are the corresponding steps and/or means located within the jurisdiction of the USA that receive and deliver that information to the client (e.g., without limitation, client-side processing and transmission networks in the USA). When this application is prosecuted or patented under a jurisdiction other than the USA, then “USA” in the foregoing should be replaced with the pertinent country or countries or legal organization(s) having enforceable patent infringement jurisdiction over the present application, and “35 USC § 112 (6)” should be replaced with the closest corresponding statute in the patent laws of such pertinent country or countries or legal organization(s). 
     All the features disclosed in this specification, including any accompanying abstract and drawings, may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise. Thus, unless expressly stated otherwise, each feature disclosed is one example only of a generic series of equivalent or similar features. 
     It is noted that according to USA law 35 USC § 112 (1), all claims must be supported by sufficient disclosure in the present patent specification, and any material known to those skilled in the art need not be explicitly disclosed. However, 35 USC § 112 (6) requires that structures corresponding to functional limitations interpreted under 35 USC § 112 (6) must be explicitly disclosed in the patent specification. Moreover, the USPTO&#39;s Examination policy of initially treating and searching prior art under the broadest interpretation of a “mean for” claim limitation implies that the broadest initial search on 112(6) functional limitation would have to be conducted to support a legally valid Examination on that USPTO policy for broadest interpretation of “mean for” claims. Accordingly, the USPTO will have discovered a multiplicity of prior art documents including disclosure of specific structures and elements which are suitable to act as corresponding structures to satisfy all functional limitations in the below claims that are interpreted under 35 USC § 112 (6) when such corresponding structures are not explicitly disclosed in the foregoing patent specification. Therefore, for any invention element(s)/structure(s) corresponding to functional claim limitation(s), in the below claims interpreted under 35 USC § 112 (6), which is/are not explicitly disclosed in the foregoing patent specification, yet do exist in the patent and/or non-patent documents found during the course of USPTO searching, Applicant(s) incorporate all such functionally corresponding structures and related enabling material herein by reference for the purpose of providing explicit structures that implement the functional means claimed. Applicant(s) request(s) that fact finders during any claims construction proceedings and/or examination of patent allowability properly identify and incorporate only the portions of each of these documents discovered during the broadest interpretation search of 35 USC § 112 (6) limitation, which exist in at least one of the patent and/or non-patent documents found during the course of normal USPTO searching and or supplied to the USPTO during prosecution. Applicant(s) also incorporate by reference the bibliographic citation information to identify all such documents comprising functionally corresponding structures and related enabling material as listed in any PTO Form-892 or likewise any information disclosure statements (IDS) entered into the present patent application by the USPTO or Applicant(s) or any 3 rd  parties. Applicant(s) also reserve its right to later amend the present application to explicitly include citations to such documents and/or explicitly include the functionally corresponding structures which were incorporate by reference above. 
     Thus, for any invention element(s)/structure(s) corresponding to functional claim limitation(s), in the below claims, that are interpreted under 35 USC § 112 (6), which is/are not explicitly disclosed in the foregoing patent specification, Applicant(s) have explicitly prescribed which documents and material to include the otherwise missing disclosure, and have prescribed exactly which portions of such patent and/or non-patent documents should be incorporated by such reference for the purpose of satisfying the disclosure requirements of 35 USC § 112 (6). Applicant(s) note that all the identified documents above which are incorporated by reference to satisfy 35 USC § 112 (6) necessarily have a filing and/or publication date prior to that of the instant application, and thus are valid prior documents to incorporated by reference in the instant application. 
     Having fully described at least one embodiment of the present invention, other equivalent or alternative methods of implementing metadata-based search summary creation according to the present invention will be apparent to those skilled in the art. Various aspects of the invention have been described above by way of illustration, and the specific embodiments disclosed are not intended to limit the invention to the particular forms disclosed. The particular implementation of the metadata-based search summary creation may vary depending upon the particular context or application. By way of example, and not limitation, the metadata-based search summary creation described in the foregoing were principally directed to online search engine implementations; however, similar techniques may instead be applied to big data applications, research tools, and database software, which implementations of the present invention are contemplated as within the scope of the present invention. The invention is thus to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the following claims. It is to be further understood that not all of the disclosed embodiments in the foregoing specification will necessarily satisfy or achieve each of the objects, advantages, or improvements described in the foregoing specification. 
     Claim elements and steps herein may have been numbered and/or lettered solely as an aid in readability and understanding. Any such numbering and lettering in itself is not intended to and should not be taken to indicate the ordering of elements and/or steps in the claims. 
     The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. 
     The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated. 
     The Abstract is provided to comply with 37 C.F.R. Section 1.72(b) requiring an abstract that will allow the reader to ascertain the nature and gist of the technical disclosure. It is submitted with the understanding that it will not be used to limit or interpret the scope or meaning of the claims. The following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment.