# Patent

## Title
Integrated application for manipulating content in a hierarchical data-driven search and navigation system

## Abstract

A data-driven, hierarchical information search and navigation system and method enable search and navigation of sets of materials by certain common attributes that characterize the materials. A rules engine provides for manipulation of the content displayed to the user based on the query entered by the user. The rules engine includes one or more rules with a trigger and an action. The action of a rule is performed only if the trigger is satisfied. A trigger may be specified in terms of expressions of attribute-value pairs and is evaluated against a given query or navigation state. The actions can include various techniques for content manipulation, such as supplementing content, rendering content in a particular way, and sorting content in a particular way. An action may be specified in terms of navigation states. The rules engine may include a script for processing the rules. An integrated application allows a user to observe, in a unified environment, both the rules engine and the search and navigation system. The integrated application allows a user to see the consequences of rule changes to search and navigation results, as well as to use the search and navigation system to create rules.

## Background
1. FIELD OF THE INVENTION
The present invention generally relates to information search and navigation systems.
2. BACKGROUND OF THE INVENTION
Information retrieval from a database of information is an increasingly challenging problem, particularly on the World Wide Web (WWW), as increased computing power and networking infrastructure allow the aggregation of large amounts of information and widespread access to that information. A goal of the information retrieval process is to allow the identification of materials of interest to users. The information provider, user, or a third party may also desire to supplement or otherwise manipulate the content presented to the user.
As the number of materials that users may search and navigate increases, identifying relevant materials becomes increasingly important, but also increasingly difficult. Challenges posed by the information retrieval process include providing an intuitive, flexible user interface and completely and accurately identifying materials relevant to the user's needs within a reasonable amount of time. Another challenge is to provide an implementation of this user interface that is highly scalable, so that it can readily be applied to the increasing amounts of information and demands to access that information. The information retrieval process comprehends two interrelated technical aspects, namely, information organization and access.
Some examples of search and navigation systems, information retrieval systems, and systems for manipulating content in a search and navigation system are described in co-pending application Ser. No. 10/272,557 entitled “System and method for manipulating content in a hierarchical data-driven search and navigation system,” filed Oct. 16, 2002; application Ser. No. 09/998,682, entitled “Hierarchical data-driven search and navigation system and method for information retrieval,” filed Oct. 31, 2001; application Ser. No. 09/961,131, entitled “Scalable hierarchical navigation system and method for information retrieval,” filed Sep. 21, 2001; and application Ser. No. 09/573,305, entitled “Hierarchical data-driven navigation system and method for information retrieval,” filed May 28, 2000, all of which are incorporated herein by reference.
A concern with some search and navigation and information retrieval systems is the ability for content providers to predict how the customized content will appear in the context of the overall user experience. Content providers often have to work in a non-interactive mode, only discovering the implications of their design after the fact.
3. SUMMARY OF THE INVENTION
In a search and navigation system that uses rules to manipulate content presentation, an integrated application allows the information provider, user, or third party to observe and work with, in a unified interface, both a rules script and the search and navigation system that employs a rules engine. The integrated application provides interactive access to the rules script, either through requests inputted by a human user or through programmatic API requests.
The invention can be used in conjunction with a scalable, hierarchical, data-driven information search and navigation system and method.
Although the invention is described herein primarily with reference to a particular WWW-based system for searching and navigating a product database, it should be understood that it could be employed in any database context where materials may be associated with terms and users can identify materials of interest by way of those terms.
The present invention can be used in conjunction with a search and navigation system that uses a knowledge base of information regarding the collection of materials to formulate and to adapt the interface to guide the user through the collection of navigation states by providing relevant navigation options. The search and navigation system may include a user interface for searching and/or a user interface for navigation. The search and navigation system may present users with context-dependent navigation options for modifying the navigation state.
A rules engine allows the information provider, user, or third party to specify rules that manipulate content presentation. In some embodiments, each rule is composed of a trigger and one or more actions. The trigger is generally evaluated using information about a query. An action specifies how the system provides supplemental content, annotates content, or otherwise manipulates the content presentation when the rule is activated. A script may determine how the rules are processed.



4. BRIEF DESCRIPTION OF THE DRAWINGS
The invention, including these and other features thereof, may be more fully understood from the following description and accompanying drawings, in which:
FIG. 1 is a view of a user interface to a search and navigation system.
FIG. 2 is a view of the user interface of FIG. 1, showing a drop-down pick list of navigable terms.
FIG. 3 is a view of the user interface of FIG. 1, showing a navigation state.
FIG. 4 is a view of the user interface of FIG. 1, showing a navigation state.
FIG. 5 is a view of the user interface of FIG. 1, showing a navigation state.
FIG. 6 is a view of the user interface of FIG. 1, showing a navigation state.
FIG. 7 is a view of the user interface of FIG. 1, showing a navigation state.
FIG. 8 is a view of the user interface of FIG. 1, showing a navigation state.
FIG. 9 is a view of a user interface, showing the result of a free-text search.
FIG. 10 is a view of a user interface, showing the result of a free-text search.
FIG. 11 is a view of the user interface of FIG. 10, showing the result of a free-text search.
FIG. 12 is a view of a user interface, showing the result of a free-text search.
FIG. 13 is a view of a user interface, showing information about a particular document.
FIGS. 14A-C are representative examples of how a range of values for an attribute could be partially ordered.
FIG. 15 is a block diagram of a process for collecting and classifying documents.
FIG. 16 is a table illustrating how a set of documents may be classified.
FIG. 17 is a representative partial order of navigation.
FIG. 18 is a block diagram of a process for precomputing a navigation.
FIG. 19 is a view of a user interface to a search and navigation system.
FIG. 20 is a view of a user interface to a search and navigation system, showing disjunctive selection.
FIG. 21 is a view of a user interface to a search and navigation system, showing negational selection.
FIG. 22 is a view of a user interface to a search and navigation, showing negational selection.
FIG. 23 is a block diagram of a method for processing a free-text search query.
FIG. 24 is a block diagram of a system and a method for processing a request across multiple servers.
FIG. 25 is a flow diagram of steps for combining refinement options from slave servers.
FIG. 26 is a flow diagram of a process for evaluating an exemplary rule for supplementing results of a query.
FIG. 27 is a view of a user interface to a search and navigation system, showing content that has been manipulated to add text to a search result.
FIG. 28 is a view of a user interface to a search and navigation system, showing content that has been manipulated to add featured content.
FIG. 29 is a view of a user interface to a search and navigation system, showing content that has been manipulated to add text and supplemental content that is not directly responsive to the query.
FIG. 30 is a table representing a script for a rules engine.
FIG. 31 is a block diagram of an integrated application including a rules engine and a search and navigation system in accordance with an embodiment of the invention.
FIG. 32 shows a split-screen display, in accordance with an embodiment of the invention, in which the rules engine portion of the display shows the applicable rules and resulting actions associated with the current navigation state of the search and navigation system that is presented in the search and navigation system portion of the display.
FIG. 33 shows the same split-screen display as FIG. 32, in which the user has navigated to a new state.
FIG. 34 shows a split-screen display, in accordance with an embodiment of the invention, in which the search and navigation system portion of the display is updated to reflect an edit performed in the rules engine portion of the display.
FIG. 35 shows a split-screen display, in accordance with an embodiment of the invention, in which the trigger for a rule is defined by navigating to a navigation state using the search and navigation engine as an interface.
FIG. 36 shows a split-screen display, in accordance with an embodiment of the invention, in which the action for a rule is defined by navigating to a navigation state using the search and navigation engine as an interface.
FIG. 37 shows a split-screen display, in accordance with an embodiment of the invention, in which the action for a rule is defined by navigating to a navigation state using the search and navigation engine as an interface.
FIG. 38 shows a clarification dialog, in accordance with an embodiment of the invention, in which the action for a rule is defined by a subset of the difference between the navigation states corresponding to the trigger and action.



5. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
Integrated Environment
In an aspect of the invention, an integrated application allows an information provider, user, or third party to observe and work with, in a unified interface, both a rules script and the search and navigation system that employs a rules engine. The integrated application provides interactive access to the rules script, either through requests inputted by a human user or through programmatic API requests.
FIG. 31 illustrates in block form an integrated application including a rules engine and a search and navigation system in accordance with an embodiment of the invention. The integrated application and the search and navigation system are able to receive requests from human users and reside on a common network that allows each to send API requests to the other.
A user runs browser 3105 on, for example, a PC. The browser communicates with server 3120, on which is running web application 3125. Web application 3125 is a hosted application with which an end user or the user of the integrated application interacts. As a user interacts with the hosted application, the hosted application sends queries to navigation engine and rules engine 3130. These engines are described in more detail below. The results are displayed in application 3110.
In addition, the integrated application provides rules display 3115. Rules display 3115 obtains information about the current rules from tools server 3135, a web server that hosts pages for the integrated application. Configuration repository 3140 holds the rules. These rules are sent to navigation engine and rules engine 3130, to be processed, and to tools server 3135 to be displayed to the user at rules display 3115.
Application 3110 communicates with rules display 3115 (in this example, using JavaScript), as the user navigates through the materials. This provides rules display 3115 with information used to create rule triggers and/or actions when rules are configured, as discussed below. When rules are configured, the information is sent back to tools server 3135, which sends the newly configured rules to configuration repository 3140.
The various components are described above as an example of how they can be provided. It should be understood that they can be grouped or separated differently than shown.
Preferably, the integrated application makes it possible to interactively see how a rules script is applied for a navigation state in the search and navigation system. In some embodiments, a split-screen display or similarly partitioned interface makes it possible to navigate to a navigation state in the search and navigation system portion of the display and then see which rules were triggered and the resulting actions in the rules engine portion of the display. In other embodiments, this interface may be combined rather than split.
FIG. 32 shows a split-screen display, in accordance with an embodiment of the invention, in which the rules engine portion 3210 of the display shows the applicable rules and resulting actions associated with the current navigation state of the search and navigation system that is presented in the search and navigation system portion 3210 of the display. In some embodiments, the rules that are triggered by the current navigation state (in this example, the current navigation state is Wine Type: Red) are highlighted or displayed in a particular color, and the corresponding actions are also highlighted or displayed in a particular color. The rules that are not triggered by the current navigation state are grayed out. Rules that the rules engine does not process because of the conditional logic of the rules script may be grayed out or displayed in a different color. In this example, one of the rules in the rules script (the first rule displayed) has a trigger of Price Range Under $10. Because the current navigation state does not include this attribute-value pair, this rule is not triggered and grayed out. The second and third rules “always apply.” The second rule triggered and is highlighted. The results appear in the display within the “Recommended” box 3230, corresponding to the title of the second rule. Of course, the displayed title need not correspond to the rule title in some embodiments. The third rule is not triggered because of conditional logic in the rules script. In this case, the database includes insufficient records matching the search criteria. The conditional logic alternatively might, for example, suppress a rule if other rules already caused the inclusion of sufficient records in the previewed navigation state to fill a particular zone. For example, in FIG. 32 because each rule would cause results to appear in the “right zone,” a rule may be suppressed if the right zone is full from the display from prior rules.
FIG. 33 shows the same split-screen display as FIG. 32, in which the user has navigated to a new state (Price Range: Under $10) by selecting a refinement from the previous navigation state—in this case, by selecting Under $10 from Price Range and removing the selection of Wine Type: Red. The integrated application triggers a refresh of the rules engine portion of the display when the user navigated to a new state. Hence, the rules engine portion of the display updates to show the applicable rules and resulting actions associated with the new state that is presented in the search and navigation system portion of the display. In this example, the first two rules are triggered and highlighted. The first rule triggers because the navigation state includes the trigger (Price Range: Under $10), and the results appear in box 3340 in the display. The second rule triggers because it “always applies” and the logic of the rules script has not prevented it from triggering. Its results (different from the example in FIG. 32 because the search criteria are different) appear in box 3330 in the display. As before, the third rule has not been triggered because the database includes insufficient records matching the search criteria.
Preferably, the integrated application makes it possible to preview the effect of editing a rules script on how the search and navigation system manipulates the content associated with given navigation state. For example, if the rules script is edited by the addition of a new rule that is triggered by that state, the search and navigation system will perform the rules' action for that navigation state. In some embodiments, a split-screen display or similarly partitioned interface makes it possible to edit the rules script in a corresponding portion of the display and then preview the effect for the current navigation state in the search and navigation system portion of the display. In other embodiments, this interface may be combined rather than split.
FIG. 34 shows a split-screen display, in accordance with an embodiment of the invention, in which the search and navigation system portion of the display is updated to reflect an edit performed in the rules engine portion of the display. Specifically, the action of the first rule was edited to display “highly recommended” wines when the rule triggers, instead of wines with a review score between 50 and 60 (as in FIGS. 32 and 33). The results appear in box 3440 in the display, under the heading “Cheap and Highly Recommended,” corresponding to the title of the rule.
Preferably, the integrated application makes it possible to create a rule for use in a rules script using the search and navigation system as an interface to select the trigger and action for that rule. The integrated application either automatically infers or uses a clarification dialog to determine the trigger and action for a rule from the navigation states selected through the search and navigation system.
In some embodiments, it is possible to specify the trigger for a rule by navigating to a navigation state using the search and navigation system. The trigger may be simply the corresponding navigation state. For example, to specify Wine Type: White as a trigger, the user might navigate to the navigation state specified by that single attribute-value pair. Alternatively, it may be a function of the corresponding navigation state, taking into account additional information such as application configuration, user profile, user history, or external information. For example, in a business directory application, the trigger might automatically include geographical constraints corresponding to a location specified in a user profile. In another example, if the user profile include the information that the user's favorite sport is baseball, the trigger inferred from the navigation state Topic: Baseball might simply be Topic: Sports. In some embodiments, determining a trigger from a navigation state may require a clarification dialog, an example of which is discussed below. Such a dialog might allow the trigger for a rule to be defined in a way that generalizes or refines the selected navigation state—for example, through the addition or removal of attribute-value pairs. For example, if the selected navigation state contains the two attribute-value pairs Wine Type: White AND Region: California, a clarification dialog may be used to determine whether the trigger should include one or both of these attribute-value pairs.
FIG. 35 shows a split-screen display, in accordance with an embodiment of the invention, in which the trigger for a rule is defined by navigating to the navigation state specified by the single attribute-value pair Wine Type: Red using the search and navigation engine as an interface. The display includes a rule editing box 3525, in which the rule criteria can be set. The new rule 3550 shown in FIG. 35 has a trigger defined but no action is yet defined.
In some embodiments, it is possible to specify the action for a rule by navigating to a navigation state using the search and navigation system. The action may be simply to navigate to or provide content associated with the corresponding navigation state. For example, the action may be to provide a preview that shows a few documents associated with the corresponding navigation state as well as a link that allows users to navigate to that state. Alternatively, it may be a function of the corresponding navigation state, taking into account additional information such as application configuration, user profile, user history, or external information. For example, if a user profile includes the information that a user prefers French Merlot, then the selection of the navigation state Price: Under $20 for an action could be augmented through the use of the profile to the navigation state {Wine Type: Merlot AND Region: France AND Price: Under $20}. In some embodiments, the inference of an action from a navigation state may require a clarification dialog. Such a dialog might allow the action for a rule to be defined in a way that generalizes or refines the selected navigation state—for example, through the addition or removal of attribute-value pairs.
FIG. 36 shows a split-screen display, in accordance with an embodiment of the invention, in which the action for a rule is defined by navigating to the navigation state specified by the attribute-value pairs Vintage: 1992 AND Body: Complex using the search and navigation engine as an interface. The integrated application infers that the action is to add Vintage: 1992 AND Body: Complex to the navigation state that triggers the rule and provide a preview of and link to the resulting navigation state.
In some embodiments, the inference of an action may be based on the difference between the navigation states corresponding to the trigger and action. For example, if the navigation state corresponding to the action is obtained through a refinement from the navigation state corresponding to the trigger, the action may be inferred as corresponding to application of that refinement to any navigation state that satisfies the inferred or clarified trigger. For example, if the navigation state used to select the trigger contains the two attribute-value pairs Wine Type: White AND Region: California and the navigation state corresponding to the action contains the three attribute-value pairs {Wine Type: White AND Region: California AND Price: Under $20}, then the action may be inferred to be the addition of the attribute-value pair Price: Under $20 to any navigation state that satisfies the trigger. Another example is shown in FIG. 37, in which the navigation state contains the two attribute-value pairs {Wine Type: Red AND Vintage: 1992}. Because the navigation state used to select the trigger contains the attribute-value pair Wine Type: Red, the action is inferred to be the addition of the attribute-value pair Vintage: 1992. Such automatically inferred actions may take into account additional information such as application configuration, user profile, user history, or external information, and may be modified through a clarification dialog. For example, as discussed earlier with respect to how the trigger can be inferred from a navigation state, the action may include additional attribute-value pairs or exclude certain attribute-value pairs corresponding to preferences in a user profile.
FIG. 38 shows a clarification dialog 3805, in accordance with an embodiment of the invention, in which the action for a rule is defined by a subset of the difference between the navigation states corresponding to the trigger and action. Since the difference between the navigation state Wine Type: Red corresponding to the trigger and the navigation state {Wine Type: Red AND Vintage: 1992}, corresponding to the action contains the attribute-value pair Vintage: 1992, a clarification dialog is used to determine if the action should include the addition of Vintage: 1992 to any navigation state that satisfies the trigger or the action should be just the particular combination {Wine Type: Red AND Vintage: 1992}.
Implementation of Integrated Environment
In some embodiments of the present invention, a shared network connects the integrated application to the search and navigation system. In some embodiments, communication between the integrated application is accomplished through HTTP requests. In such an embodiment, server processes may listen to requests over open ports and translate incoming requests into API calls. Preferably, APIs are supported in a variety of commonly used programming languages, such as C++, Perl, Java, COM, and C#.
In some embodiments of the present invention, the search and navigation system annotates query results to include information useful for auditing how a rules script has been processed. Such annotation may include which rules were triggered, which actions were performed, and the order in which rules were processed. This may be in the form of the split screen display shown, for example, in FIGS. 32-37, in which triggered actions and performed rules are highlighted or shown in a different color, and the rules are displayed in the order in which processed. Alternatively, a combined interface may be used in which (for example) the displayed boxes showing the results of the actions (such as boxes 3230, 3330, 3340, and 3440 in FIGS. 32-34) also display the applicable rule and indicate through text or graphically the order in which the rules were processed.
In some embodiments of the present invention, an integrated application may access the rules engine to obtain information about the rules script. The information may be returned in a structured form such as XML to facilitate presentation. This information may be used to present rules to users in an interface that allows users to view or modify the rules script.
In some embodiments, a modification to the rules script results in an immediate API request to the search and navigation system to recompute the results for the current navigation state based on the newly edited rules script. The integrated application itself may be used to make the modifications to the rules script, so it is aware of the need to refresh the results for the current navigation state. Otherwise, this recomputation may be initiated through a callback mechanism, through polling for changes, or any other inter-process communication.
In this environment, a navigation state selected through the search and navigation system can be translated into a representation of a navigation state suitable for representing a trigger in an API request to the rules engine for creating new rules. The representation may be in a structured format such as XML or a structured binary format that facilitates easy communication of objects. This representation may include an expression of attribute-value pairs using identifiers common to both the search and navigation system and the rules engine.
In this environment, a navigation state or refinement selected through the search and navigation system can be translated into a representation suitable for representing an action in an API request to the rules engine for creating new rules. This representation also may be in a structured format such as XML or a structured binary format that facilitates easy communication of objects, and may include an expression of attribute-value pairs using identifiers common to both the search and navigation system and the rules engine.
Exemplary implementations of a user interface for a search and navigation system for use with the integrated environment, of a knowledge base for a search and navigation system for use with the integrated environment, of navigation states for a search and navigation system for use with the integrated environment, of a rules engine for use with the integrated environment, of an implementation of a search and navigation system for use with the integrated environment, and of an implementation of a rules engine for use with the integrated environment are described below.
User Interface for a Search and Navigation System
FIG. 1 shows a user interface 10 to a hierarchical, data-driven search and navigation system. The search and navigation system operates on a collection of documents defined in a knowledge base. As is shown, the user is preferably presented with at least two alternative methods of using the search and navigation system: (1) by selecting terms to navigate through the collection of documents, or (2) by entering a desired query in a search box.
The search and navigation system preferably organizes documents by domain. The user interface 10 shown in FIGS. 1-9 is operating on a set of documents that are part of a wine domain. Preferably, a domain defines a portion of the collection of documents that reflects a natural grouping. Generally, the set of attributes used to classify documents in a domain will be a manageable subset of the attributes used to classify the entire collection of documents. A domain definition may be a type of product, e.g., wines or consumer electronics. A domain may be divided into subdomains to further organize the collection of documents. For example, there can be a consumer electronics domain that is divided into the subdomains of televisions, stereo equipment, etc. Documents may correspond to goods or services.
The user interface may allow users to navigate in one domain at a time. Alternatively, the user interface may allow the simultaneous navigation of multiple domains, particularly when certain attributes are common to multiple domains.
The user interface allows the user to navigate through a collection of navigation states. Each state is composed of an expression of terms and of the set of documents associated with those terms in accordance with that expression. In the embodiment shown in FIGS. 1-9, users navigate through the collection of navigation states by conjunctively selecting and deselecting terms to obtain the navigation state corresponding to each expression of conjunctively selected terms. Preferably, as in FIG. 4, the user interface 10 presents a navigation state by displaying both the list 50 of terms 52 and a list 41 of some or all of the documents 42 that correspond to that state. Preferably, the user interface presents the terms 52 of the navigation state organized by attribute. Preferably, the initial navigation state is a root state that corresponds to no term selections and, therefore, to all of the documents in the collection.
As shown in FIG. 2, the user interface 10 allows users to narrow the navigation state by choosing a value 28 for an attribute 22, or by replacing the currently selected value with a more specific one (if appropriate). Preferably, the user interface 10 presents users with the options available to narrow the present navigation state, preferably with relevant terms organized by attribute. As shown in FIG. 2, users can select values 28 from drop-down lists 26 denoted by indicators 24, that are organized by attributes 22 in the current navigation state. The user interface may present these navigation options in a variety of formats. For example, values can be presented as pictures or as symbols rather than as text. The interface may allow for any method of selecting terms, e.g., mouse clicks, keyboard strokes, or voice commands. The interface may be provided through various media and devices, such as television or WWW, and telephonic or wireless devices. Although discussed herein primarily as a visual interface, the interface may also include an audio component or be primarily audio-based.
Preferably, in the present navigation state, the user interface only presents options for narrowing the navigation state that lead to a navigation state with at least one document. This preferred criteria for providing navigation options ensures that there are no “dead ends,” or navigation states that correspond to an empty result set.
Preferably, the user interface only presents options for narrowing the navigation state if they lead to a navigation state with strictly fewer documents than the present one. Doing so ensures that the user interface does not present the user with choices that are already implied by terms in the current navigation state.
Preferably, the user interface presents a new navigation state as soon as the user has chosen a term 28 to narrow the current navigation state, without any further triggering action by the user. Because the system responds to each user with immediate feedback, the user need not formulate a comprehensive query and then submit the query.
As shown in FIGS. 3 and 4, the user interface 10 may enable broadening of the current navigation state by allowing the user to remove terms 52 from the list 50 of terms conjunctively selected. For example, the interface 10 may provide a list 50 with checkboxes 54 for removing selections and a button 56 to trigger the computation of the new navigation state. In the illustrated embodiment, the user can remove conjunctively selected terms 52 in any order and can remove more than one selection 52 at a time.
Preferably, the navigation options presented to the user are context-dependent. For example, terms that refine previously selected terms may become navigation options in the resulting navigation state. For example, referring to FIG. 5, after the term Flavors: Wood and Nut Flavors 52 is conjunctively selected (the user has selected the value Wood and Nut Flavors 23 for the attribute Flavors), Wood and Nut Flavors 23 then appears in the interface for the new navigation state in the list 20 of attributes and allows conjunctive selection of values 28 that relate to that specific attribute for further refinement of the query. The user interface may also present certain attributes that were not presented initially, as they become newly relevant. For example, comparing FIG. 3 to FIG. 2, the attribute French Vineyards 25 appears in the list 20 of attributes only after the user has already conjunctively selected the term Regions: French Regions in a previous navigation state. Attributes may be embedded in this way to as many levels as are desired. Presenting attributes as navigation options when those attributes become relevant avoids overwhelming the user with navigation options before those options are meaningful.
Additionally, for some attributes 22, multiple incomparable (non-refining) conjunctive selections of values 28 may be applicable. For example, for the attribute Flavor, the values Fruity and Nutty, neither of which refines the other, may both be conjunctively selected so that the terms Flavors: Fruity and Flavors: Nutty narrow the navigation state. Thus, users may sometimes be able to refine a query by conjunctively selecting multiple values under a single attribute.
Preferably, certain attributes will be eliminated as navigation options if they are no longer valid or helpful choices. For example, if all of the documents in the result set share a common term (in addition to the term(s) selected to reach the navigation state), then conjunctive selection of that term will not further refine the result set; thus, the attribute associated with that term is eliminated as a navigation option. For example, comparing FIG. 6 with FIG. 4, the attribute Wine Types 27 has been eliminated as a navigation option because all of the documents 42 in the result set share the same term, Wine Types Appellational Wines. In preferred embodiments, an additional feature of the interface 10 is that this information is presented to the user as a common characteristic of the documents 42 in the result set. For example, referring to FIG. 6, the interface 10 includes a display 60 that indicates the common characteristics of the documents 42 in the result set. Removing a term as a navigation option when all of the documents in the result set share that term prevents the user from wasting time by conjunctively selecting terms that do not refine the result set.
Preferably, the user interface also eliminates values as navigation options if their selection would result in no documents in the result set. For example, comparing FIG. 8 to FIG. 7, after the user selects the term Wine Spectator Range: 95-100, the user interface eliminates as navigation options all the values 28, 29 in the list 26 of values for the attribute Appellations 22 except for the values Alexander Valley 29 and Napa Valley 29. Alexander Valley 29 and Napa Valley 29 are the only two values in the list 26 of values for the attribute Appellations that return at least one document in the result set; all other values 28 return the empty set. Removing values as navigation options that would result in an empty result set saves the user time by preventing the user from reaching dead-ends.
Preferably, the user interface allows users to enter free-text search queries that may be composed of one or more words. The system may interpret free text queries in various ways. In particular, the system may map a free-text query to two types of search results: single-term interpretations and multi-term interpretations. A single-term interpretation maps the complete query to an individual term in the knowledge base. A multi-term interpretation maps the query to a conjunction of two or more terms in the knowledge base—that is, a plurality of terms that corresponds to a conjunctive navigation state. Depending on the particular implementation and application context, a free-text query may be mapped to one or more single-term interpretations, one or more multi-term interpretations, or a combination of both types of interpretations. The user interface may allow users to use a free-text search either to find matching terms or further to find materials associated with matching terms.
As illustrated in FIG. 9, in interface 90, a search box 30 preferably allows users to perform a free-text search for terms of interest, rather than performing a full-text search of the documents themselves. Preferably, the user interface responds to such a search by presenting a list 32 of single-term interpretations 33 including terms organized by attribute 36, and allowing the user to select from among them. Preferably, the user interface responds to the user's selection by presenting the user with the navigation state corresponding to the selection of that term. The user may then either navigate from that state (i.e., by narrowing or broadening it) or perform additional free-text searches for terms.
As illustrated in FIG. 10, the user interface 100 responds to free-text search queries by presenting a list 32 of multi-term interpretations 34, and allowing the user to select from among them. Preferably, the user interface responds to the user's selection by presenting the user with the navigation state corresponding to the selection of that conjunction of terms. The user may then either navigate from that state (i.e., by narrowing or broadening it) or perform additional free-text searches for terms.
As illustrated in FIG. 11, the user interface 100 responds to free-text search queries by presenting a list 32 of single-term interpretations 33 and multi-term interpretations 34, and allowing the user to select from among them. Preferably, the user interface responds to the user's selection by presenting the user with the navigation state corresponding to the selection of that term or conjunction of terms. The user may then either navigate from that state (i.e., by narrowing or broadening it) or perform additional free-text searches for terms.
As illustrated in FIG. 12, the user interface 105 responds to free-text search queries by directly presenting the set of matching documents 35, for example, in accordance with full-text search of the documents. The user may then either navigate from that result (i.e., by narrowing or broadening it) or perform additional free-text searches for terms.
Preferably, the user interface 10 presents a full or partial list 41 of the documents that correspond to the current navigation state. Preferably, if a user is interested in a particular document 42, the user may select it and obtain a record 70 containing further information about it, including the list 72 of terms 74 that are associated with that document, as shown in FIG. 13. Preferably, the user interface 10 allows the user to conjunctively select any subset of those terms 74 and thereby navigate to the navigation state that corresponds to the selected term expression.
Preferably, the user interface 10 also offers navigation options that directly link to an associated navigation state that is relevant to, but not necessarily a generalization or refinement of, the present navigation state. These links preferably infer the user's interests from the present navigation state and enable the user to cross-over to a related topic. For example, if the user is visiting a particular navigation state in a food domain, links may direct the user to navigation states of wines that would complement those foods in the wine domain.
In some systems, the user is preferably presented with additional methods of using the search and navigation system such as: (1) by conjunctively selecting terms, (2) by disjunctively selecting terms, (3) by negationally selecting terms, or (4) by entering a desired keyword in a search box.
The user may broaden the navigation state by disjunctively selecting additional terms. For example, a user could start at {Products: DVDs}, and then broaden by disjunctively selecting a term to {Products: DVDs OR Products: Videos}, and then narrow by conjunctively selecting a term to {(Products: DVDs OR Products: Videos) AND Director: Spike Lee}. FIG. 19 shows a user interface 300 to a hierarchical, data-driven search and navigation system. The user interface 300 is operating on a collection of records relating to mutual funds. The interface 300 presents navigation options, including a list of attributes 310 relating to mutual funds and a list of terms 314 for a particular attribute 312, such as Fund Family, under consideration by a user. A selected term 316 is highlighted. As shown, the attribute-value pair {Fund Family: Fidelity Investments} has previously been selected. The illustrated search and navigation system allows the user to select attribute-value pairs disjunctively. As shown in FIG. 20, after the user subsequently selects {Fund Family: Vanguard Group} in addition, the interface 300 presents a new navigation state {Fund Family: Fidelity Investments OR Fund Family: Vanguard Group}, including mutual funds 320 that match either selected attribute-value pair. Accordingly, both selected attribute-value pairs 316 are highlighted. In some embodiments, for example, to reduce computational requirements, disjunctive combination of attribute-value pairs may be limited to mutually incomparable attribute-value pairs that correspond to the same attribute.
The user may narrow the navigation state by negationally selecting additional terms. For example, a user could start at {Products: DVDs}, narrow by conjunctively selecting a term to {Products: DVDs AND Genre: Comedy}, and then narrow by negationally selecting a term to {Products: DVDs AND Genre: Comedy AND (NOT Director: Woody Allen)}. FIG. 21 shows another interface 400 to a hierarchical, data-driven search and navigation system. The user interface 400 is operating on a collection of records relating to entertainment products. The user interface 400 includes a header 410 and a navigation area 412. The header 410 indicates the present navigation state {Products: DVDs AND Genre:Drama}, and implies the refinement options currently under consideration by the user. The leader “Not Directed By” 414 indicates a negational operation with respect to the Director attribute. The interface lists the attribute-value pairs 416 that can be combined with the expression for the present navigation state under this operation. As shown in FIG. 22, after the user selects the term Director: Martin Scorsese, the interface 400 presents a new navigation state {Products: DVDs AND Genre:Drama AND (NOT Director: Martin Scorsese}.
In some embodiments of the invention, the content presented to the user is manipulated based on information about the user's query and the current navigation state using rules specified in a rules engine. The following kinds of content manipulation are examples of techniques for manipulating content that can be implemented in accordance with the present invention. Particular embodiments may include only some or even none of these types of content manipulation. One kind of content manipulation is the inclusion of documents that may not be in the set of documents specified by the present navigation state, but rather are provided by a rule or plurality of rules activated by the present query or navigation state. The supplemental documents may not be directly responsive to the user's query but may be related to the query in some way that is identified in the rules. Another kind of content manipulation is the providing of options to navigate to a new navigation state based on a rule or plurality of rules activated by the present query or navigation state. The new navigation states can be states that would otherwise require multiple refinements and/or generalizations from the present state to reach.
The content may be manipulated by filtering the documents in the navigation state based on a rule or plurality of rules activated by the present query or navigation state. Also, the content may be manipulated by sorting the documents in the navigation state based on a rule or plurality of rules activated by the present query or navigation state. Or, the content may be manipulated by aggregating the documents in the navigation state into equivalence classes based on an explicit or derived property of those documents. For example, documents representing books might be aggregated according to author and title, so that multiple editions of the same book are grouped into the same equivalence class. Such an aggregation scheme treats two books that share both author and title as equivalent.
The content manipulation may also take the form of rendering the documents in a particular way in the navigation state based on a rule or plurality of rules activated by the present query or navigation state.
Also, the content may be manipulated by providing a transformation of the query based on a rule or plurality of rules activated by the present query or navigation state. The displayed result corresponds to the new query or adds the results of the new query to the results of the original query.
FIGS. 27, 28 and 29 show an interface displaying query results in which content has been manipulated in accordance with some aspects of the invention. FIG. 27 shows a result 630 displayed to the user that includes a list 632 of documents that are directly responsive to the user's query 636. The content of result 630 has also been manipulated to add the text “Expand Your Horizons, Try a White Wine!” 634 in response to the user's query 636 directed to red wines. The text also represents a navigation option that takes the user to a navigation state including white wines. FIG. 28 shows a result 640 displayed to a user that includes a list 642 of documents that are directly responsive to the user's query 644. The list of responsive documents 642 has been sorted to present wines with the highest rating first. In addition, the rendering includes adding the flag of the corresponding country 648 to each responsive document shown in the display. The content of result 640 has been manipulated to add featured content 646. The featured content 646 includes featured items in the collection, as well as featured articles that relate to the collection. FIG. 29 shows a result 650 in which the content has been supplemented by adding a list 654 of documents that are not responsive to the user's query 652 directed to red wines. This may be accomplished, for example, by triggering a rule that generates a new query in its action and returns the results of the new query for inclusion in the display.
Although the interface to the search and navigation system has been described herein as a user interface, the interface could provide other forms of access to the search and navigation system. In alternative embodiments, the interface may be an applications program interface to allow access to the search and navigation system for or through other applications. The interface may also enhance the functionality of an independent data-oriented application. The interface may also be used in the context of a WWW-based application or an XML-based application. The search and navigation system may also support multiple interface modes simultaneously. The search and navigation system may be made available in a variety of ways, for example via wireless communications or on handheld devices.
Knowledge Base for a Search and Navigation System
Preferably, the search and navigation system stores all information relevant to navigation in a knowledge base. The knowledge base is the repository of information from two processes: taxonomy definition and classification. Taxonomy definition is the process of identifying the relevant attributes to characterize documents, determining the acceptable values for those attributes (such as a list or range of values), and defining a partial order of refinement relationships among terms (attribute-value pairs). Classification is the process of associating terms with documents. The knowledge base may also be used to maintain any information assets that support these two processes, such as domains, classification rules and default expectations. Additionally, the knowledge base may be used to maintain supplementary information and materials that affect users' navigation experience.
The taxonomy definition process identifies a set of attributes that appropriately characterize documents. A typical way to organize the taxonomy definition process is to arrange the collections of documents into domains, which are sets of documents that conform to a natural grouping and for which a manageable number of attributes suffice to effectively distinguish and navigate among the documents in that domain. The knowledge base preferably includes a characterization of each domain, which might include rules or default expectations concerning the classification of documents in that domain.
The taxonomy definition process also identifies a full set of values, at varying levels of specificity when appropriate, for each attribute. The values preferably identify the specific properties of the documents in the collection. The values may be enumerated explicitly or defined implicitly. For example, for a “color” attribute, a full set of valid color values may be specified, but for a “price” or “date” attribute, a range within which the values may fall or a general data type, without defining a range, may be specified. The process of identifying these values may include researching the domain or analyzing the collection of documents.
The taxonomy definition process also defines a partial order of refinement relationships among terms (attribute-value pairs). For example, the term Origin: France could refine the term Origin: Europe. The refinement relationship is transitive and antisymmetric but not necessarily total. Transitivity means that, if term A refines term B and term B refines term C, then term A refines term C. For example, if Origin: Paris refines Origin: France and Origin: France refines Origin: Europe, then Origin: Paris refines Origin: Europe. Antisymmetry means that, if two terms are distinct, then both terms cannot refine each other. For example, if Origin: Paris refines Origin: France, then Origin: France does not refine Origin: Paris.
Further, the partial order of refinement relationships among terms is not necessarily a total one. For example, there could be two terms, Origin: France and Origin: Spain, such that neither term refines the other. Two terms with this property are said to be incomparable. Generally, a set of two or more terms is mutually incomparable if, for every pair of distinct terms chosen from that set, the two terms are incomparable. Typically, but not necessarily, two terms with distinct attributes will be incomparable.
Given a set of terms, a term is a maximal term in that set if it does not refine any other terms in the set, and it is a minimal term in that set if no other term in the set refines it. For example, in the set {Origin: France, Origin: Paris, Origin: Spain, Origin: Madrid}, Origin: France and Origin: Spain are maximal, while Origin: Paris and Origin: Madrid are minimal. In the knowledge base, a term is a root term if it does not refine any other terms and a term is a leaf term if no other term refines it.
FIGS. 14A, 14B, and 14C illustrate attributes 112 and values 114, arranged in accordance with the partial order relationships, that could be used for classifying wines. The attributes 112 are Type/Varietal, Origin, and Vintage. Each attribute 112 corresponds to a maximal term for that attribute. An attribute 112 can have a flat set of mutually incomparable values (e.g., Vintage), a tree of values (e.g., Origin), or a general partial order that allows a value to refine a set of two or more mutually incomparable values (e.g., Type/Varietal). The arrows 113 indicate the refinement relationships among values 114.
Attributes and values may be identified and developed in several ways, including manual or automatic processing and the analysis of documents. Moreover, this kind of analysis may be top-down or bottom-up; that is, starting from root terms and working towards leaf terms, or starting from leaf terms and working towards root terms. Retailers, or others who have an interest in using systems in conjunction with the present invention to disseminate information, may also define attributes and terms.
The classification process locates documents in the collection of navigation states by associating each document with a set of terms. Each document is associated with a set of mutually incomparable terms, e.g., {Type/Varietal: Chianti, Origin: Italy, Vintage: 1996}, as well as any other desired descriptive information. If a document is associated with a given term, then the document is also associated with all of the terms that the given term refines.
The classification process may proceed according to a variety of workflows. Documents may be classified in series or in parallel, and the automatic and manual classification steps may be performed one or more times and in any order. To improve accuracy and throughput, human experts may be assigned as specialists to oversee the classification task for particular subsets of the documents, or even particular attributes for particular subsets of the documents. In addition, the classification and taxonomy processes may be interleaved, especially as knowledge gained from one process allows improvements in the other.
FIG. 15 illustrates the stages in a possible flow for the classification process 250. The data acquisition step 252, that is, the collection of documents for the database, may occur in several different ways. For example, a retailer with a product catalog over which the search and navigation system will operate might provide a set of documents describing its products as a pre-defined set. Alternatively, documents may be collected from one source, e.g., one Web site, or from a number of sources, e.g., multiple Web sites, and then aggregated. If the desired documents are Web pages, the documents may be collected by appropriately crawling the Web, selecting documents, and discarding documents that do not fit in the domain. In the data translation step 254, the collected documents are formatted and parsed to facilitate further processing. In the automatic classification step 256, the formatted and parsed documents are processed in order to automatically associate documents with terms. In the manual classification step 258, human reviewers may verify and amend the automatic classifications, thereby ensuring quality control. Preferably, any rules or expectations violated in either the automatic classification step 256 or the manual classification step 258 would be flagged and presented to human reviewers as part of the manual classification step 258. If the collection of documents is divided into domains, then there will typically be rules that specify a certain minimal or preferred set of attributes used to classify documents from each domain, as well as other domain-specific classification rules. When the classification process is complete, each document will have a set of terms associated with it, which locate the document in the collection of navigation states.
In FIG. 16, table 180 shows a possible representation of a collection of classified wine bottles. Preferably, each entry is associated with a document number 182, which could be a universal identifier, a name 184, and the associated terms 186. The name is preferably descriptive information that could allow the collection to be accessed via a free-text search engine as well as via term-based navigation.
The knowledge base may also include a catalog of canonical representations of documents. Each catalog entry represents a conceptually distinct item that may be associated with one or more documents. The catalog allows aggregation of profile information from multiple documents that relate to the item, possibly from multiple sources. For example, if the same wine is sold by two vendors, and if one vendor provides vintage and geographic location information and another provides taste information, that information from the two vendors can be combined in the catalog entry for that type of wine. The catalog may also improve the efficiency of the classification process by eliminating duplicative profiling. In FIG. 15, the catalog creation step 260 associates classified documents with catalog entries, creating new catalog entries when appropriate. For ease of reference, an item may be uniquely identified in the catalog by a universal identifier.
The knowledge base may also define stores, where a store is a subcollection of documents that are grouped to be retrievable at one time. For example, a particular online wine merchant may not wish to display documents corresponding to products sold by that merchant's competitors, even though the knowledge base may contain such documents. In this case, the knowledge base can define a store of documents that does not include wines sold by the merchant's competitors. In FIG. 15, the store creation step 262 may define stores based on attributes, terms, or any other properties of documents. A document may be identified with more than one store. The knowledge base may also contain attributes or terms that have been customized for particular stores.
In FIG. 15, the export process step 264 exports information from the knowledge base to another stage in the system that performs further processing necessary to generate a navigable data structure.
Navigation States for a Search and Navigation System
The search and navigation system represents, explicitly or implicitly, a collection of navigation states. A navigation state can be represented either by an expression of terms, or by the subset of the collection of documents that correspond to the term expression.
By way of example, types of navigation states include conjunctive navigation states, disjunctive navigation states and negational navigation states. Conjunctive navigation states are a special case of navigation states in which the term expression is conjunctive—that is, the expression combines terms using only the AND operator. Conjunctive navigation states are related by a partial order of refinement that is derived from the partial order that relates the terms.
A conjunctive navigation state may have two representations. First, a conjunctive navigation state corresponds to a subset of the collection of documents. Second, a conjunctive navigation state corresponds to a conjunctive expression of mutually incomparable terms. FIG. 18 illustrates some navigation states for the documents and terms based on the wine example discussed above. For example, one navigation state 224 is {Origin: South America} (documents #1, #4, #5); a second navigation state 224 is {Type/Varietal: White AND Origin: United States} (documents #2, #9). The subset of documents corresponding to a conjunctive navigation state includes the documents that are commonly associated with all of the terms in the corresponding expression of mutually incomparable terms. At the same time, the expression of mutually incomparable terms corresponding to a conjunctive navigation state includes all of the minimal terms from the terms that are common to the subset of documents, i.e., the terms that are commonly associated with every document in the subset. A conjunctive navigation state is preferably unique and fully specified; for a particular conjunctive expression of terms, or for a given set of documents, there is no more than one corresponding conjunctive navigation state.
One way preferred to define the collection of conjunctive navigation states is to uniquely identify each conjunctive navigation state by a canonical conjunctive expression of mutually incomparable terms. A two-step mapping process that maps an arbitrary conjunctive expression of terms to a canonical conjunctive expression of mutually incomparable terms creates states that satisfy this property. In the first step of the process, an arbitrary conjunctive expression of terms is mapped to the subset of documents that are associated with all of those terms. Recalling that if a document is associated with a given term, then the document is also associated with all of the terms that the given term refines, in the second step of the process, this subset of documents is mapped to the conjunctive expression of minimal terms among the terms that are common to all of the documents in that document set. The result of this second step is a conjunctive expression of mutually incomparable terms that uniquely identifies the corresponding subset of documents, and, hence, is a canonical representation for a conjunctive navigation state. By way of illustration, referring to the wine example in FIG. 17, the term expression {Origin: France} maps to the subset of documents {documents #8, #11}, which in turn maps to the canonical term expression {Type/Varietal: Red AND Origin: France}.
The conjunctive navigation states 222, 224, 226 are related by a partial order of refinement relationships 220 derived from the partial order that relates terms. This partial order can be expressed in terms of either the subsets of documents or the term expressions that define a conjunctive navigation state. Expressed in terms of subsets of documents, a navigation state A refines a navigation state B if the set of documents that corresponds to state A is a subset of the set of documents that corresponds to state B. Expressed in terms of term expressions, a conjunctive navigation state A refines a conjunctive navigation state B if all of the terms in state B either are in state A or are refined by terms in state A. Referring to FIG. 17, the navigation state 226 corresponding to the term expression {Type/Varietal: Red AND Origin: Chile} (document #4) refines the navigation state 224 corresponding to {Origin: Chile} (documents #4, #5). Since the refinement relationships among navigation states give rise to a partial order, they are transitive and antisymmetric. In the example, {Type/Varietal: Red AND Origin: Chile} (document #4) refines {Origin: Chile} (documents #4, #5) and {Origin: Chile} (documents #4, #5) refines {Origin: South America} (documents #1, #4, #5); therefore, {Type/Varietal: Red AND Origin: Chile} (document #4) refines {Origin: South America} (documents #1, #4, #5). The root navigation state 222 is defined to be the navigation state corresponding to the entire collection of documents. The leaf navigation states 226 are defined to be those that cannot be further refined, and often (though not necessarily) correspond to individual documents. There can be arbitrarily many intermediate navigation states 224 between the root 222 and the leaves 226. Given a pair of navigation states A and B where B refines A, there can be multiple paths of intermediate navigation states 224 connecting A to B in the partial order. For convenience of definition in reference to the implementation described herein, a navigation state is considered to refine itself.
A user browses the collection of documents by visiting a sequence of one or more navigation states typically starting at the root navigation state 222. In one example, there are three basic modes of navigation among these states. The first mode is refinement, or moving from the current navigation state to a navigation state that refines it. The user can perform refinement either by adding a term through conjunctive selection to the current navigation state or by refining a term in the current navigation state; i.e., replacing a term with a refinement of that term. After the user adds or refines a term, the new term expression can be mapped to a canonical term expression according to the two-step mapping described above. The second mode is generalization, or moving from the current navigation state to a more general navigation state that the current state refines. The user can perform generalization either by removing a term from the current navigation state or by generalizing a term in the current navigation state; i.e., replacing a current term with a term that the current term refines. After the user removes or generalizes a term, the new term expression can be mapped to a canonical term expression. The third mode is simply creating a query in the form of a desired term expression, which again can be mapped to a canonical term expression to obtain a navigation state.
In search and navigation systems that can be used with the present invention, there may be additional modes of navigation. In systems that support the corresponding types of navigation states, these modes may include generalization of the navigation state through disjunctive selection, as shown in FIG. 19, as well as refinement of the navigation state through negational selection, as shown in FIG. 20. In general, terms can be combined using Boolean logic. Although term expressions that are not conjunctive do not necessarily have canonical forms, some implementations may be based on a system that uses a collection of conjunctive navigation states. One implementation is based on logical equivalence rules as described below.
Rules Engine
The rules engine may allow an information provider, a user, or a third party to specify rules that manipulate content presentation. In certain embodiments, each rule is composed of a trigger and one or more actions. The trigger is a predicate that identifies a set of conditions that, if satisfied, activate the rule. An action specifies how the system manipulates content presentation when the rule is activated. In certain embodiments, the rules are processed and applied in order to generate a response to a query. The information provider, user, or third party can build a script that combines rules using sequential, conditional, or randomized logic.
A rule's trigger explicitly or implicitly identifies conditions, that if satisfied, make the rule applicable. In some embodiments, when the rule is processed, the conditions are evaluated using information about the query. If the query satisfies the specified conditions of the trigger, the rule's action will be performed. In certain embodiments, triggers are defined in terms of attribute-value pairs. Triggers may be defined in terms of expressions of attribute-value pairs. If the expressions of attribute-value pairs in a trigger correspond to valid navigation states in the search and navigation system, then the trigger is defined in terms of a set of navigation states that is a subset of the collection of all possible navigation states. The rule is activated when the current query, or the current navigation state responsive to that query, satisfies one or more of the expressions that make up the trigger. In other embodiments, a trigger is defined in terms of one or more keywords. The rule is activated when the current query is a free-text query that includes the specified term or terms. In some embodiments, a trigger can be defined in terms of one or more keywords in combination with an expression of attribute-value pairs.
In some embodiments, the rules engine allows a trigger to specify conditions that correspond to a single navigation state. For example, a trigger might only be activated by an initial navigation state that a user first encounters while navigating the document collection. A rule with such a trigger might be used to push content likely to be of interest to most users, such as the set of documents recently added to the collection. In contrast, a trigger might only include a single navigation state that only a fraction of users are likely to encounter. A rule with such a trigger might be used to push content likely to be of interest to only that fraction of users, such as the option to navigate to a closely related navigation state. For example, in an application that represents movies in its collection of materials, a trigger might be activated by a single-term navigation state {Genre: Comedy}. Another trigger might be activated by the conjunctive 2-term navigation state {Genre: Comedy AND Release Year: 1980-1989}. Because the latter trigger is more specific than the first trigger, it can be useful to deliver more specific supplemental content.
In some embodiments, the rules engine allows a trigger to be activated by a plurality of navigation states. This flexibility allows designers of systems with large numbers of materials to avoid the impracticality of writing a different rule for each navigation state. For example, a trigger can be activated by all possible navigation states. In addition, a trigger can be activated by some but not all of the possible navigation states. A plurality of navigation states can be identified without explicitly representing each navigation state. For example, a plurality of navigation states can be included by specifying a particular attribute-value pair and incorporating all navigation states with that attribute-value pair implicitly. For example, in an application that represents movies in its collection of materials, a trigger might be activated by all navigation states that include the term {Genre: Classics}, i.e., the single-term navigation state {Genre: Classics} as well multi-term navigation states like {Genre: Classics AND Release Year: 1980-1989}, {Genre: Classics OR Genre: Drama}.
In some embodiments, the rules engine allows a trigger to be defined in terms of the descendants of a given navigation state. Such a trigger designates a target subset of the document collection—either explicitly as a set of documents or implicitly by characterizing the navigation state—without enumerating every corresponding navigation state, and causes the rule to be activated when the present query is associated with a set of documents that are contained by the target subset. For example, in an application that represents movies in its collection of materials, a trigger might be activated by navigation states that are descendants of the single-term navigation state {Genre: Classics}; the descendants include {Genre: Classics AND Release Year: 1980-1989} but not navigation states like {Genre: Classics OR Genre: Drama}, which is a generalizing rather than a narrowing refinement.
In some embodiments, the rules engine allows the definition of a trigger to refer to the ancestors of a given navigation state—that is, navigation states that represent generalizing refinements from the given navigation state. Such a trigger also designates a target subset of the document collection—either explicitly as a set of documents or implicitly by characterizing the navigation state—and causes the rule to be activated when the navigation state is associated with a set of documents that contain the documents in the target subset. In particular, such a rule could refer to navigation states that do not contain a document or plurality of documents. For example, in an application that represents movies in its collection of materials, a trigger might be activated by navigation states that are ancestors of the single-term navigation state {Genre: Romantic Comedy}; the ancestors include {Genre: Comedy} but not navigation states like {Genre: Romantic Comedy AND NOT Director: Woody Allen}, which is a narrowing rather than a generalizing refinement.
In some embodiments, the rules engine allows the definition of a trigger to refer to the navigation states within a given distance of a given navigation state. In some embodiments, distance may be measured using a set difference function, such as the size of the symmetric difference between two sets of attribute-value pairs. In some embodiments, distance may be measured using a graph distance function, such as the length of the shortest path in the graph of navigation states. In some embodiments, distance may be measured using a dissimilarity measure, such as the measure described in co-pending patent application “Method and System for Similarity Search and Clustering,” Ser. No. 10/027,195, filed Dec. 20, 2001, which is incorporated herein by reference.
In some embodiments, the rules engine allows a trigger to include Boolean operators like AND, OR, and NOT to specify an expression of attribute-value pairs, which may correspond to a navigation state or a plurality of navigation states. For example, in an application that represents movies in its collection of materials, a trigger might be activated by navigation states that are descendants of {Genre: Comedy} OR descendants of {Genre: Drama} AND are descendants of {Release Year: 1980-1989} but are NOT descendants of {Director: Woody Allen}, In some embodiments, the rules engine allows the definition of a trigger to make use of a random or pseudorandom process. For example, a trigger can be specified so that even when the present navigation state otherwise satisfies the trigger the corresponding action is only performed some fraction of the time, based on the results of a random or pseudorandom number generator.
In some embodiments, the rules engine allows the evaluation of a trigger to set or update variables that may be used by the rule's action or by subsequent rules. For example, in an application that represents movies in its collection of materials, a trigger might set a variable to be the Director term in the navigation state (if there is one), so that the action can push featured movies by that director.
The action component of a rule specifies one or more ways in which the system manipulates content presentation when that rule is activated.
In some embodiments, the rules engine allows an action to specify that a document or a plurality of documents be included as supplemental content. The included document or plurality of documents may depend on the query that activated the rule's trigger, or it may be independent of the query that activated the rule's trigger. For example, the action is dependent on the query if the document or plurality of documents that are considered for inclusion are restricted to the documents associated with the present navigation state that satisfies the query. For example, in an application that represents wines in its collection of materials, an action might specify the inclusion, as supplemental content, of a document corresponding to a featured wine associated with the current navigation state.
In some embodiments, actions of a rule may cause content to supplement a query response with documents, navigation states, queries, or other content. In the interface, supplemental content may be offered as a separate section than the results of the query or maybe itself be integrated with the results of the query.
For example, an action could cause a set of documents to be returned along with the query results. These documents could be integrated into the set of documents associated with the query results. Alternatively, the documents pushed by the rule could be returned in a section separately from the query results.
In addition, the supplemental content may itself stand alone, that is the response to the query displayed to the user may include only the results of the activated rules. Thus, in this example, the only content presented to the user would be from rules, i.e., the supplemental content would be the only content presented to users.
By way of example, a flow diagram 600 for processing a rule that supplements the given query results with additional documents is shown in FIG. 26. Block 602 represents the rule presently being processed and block 604 represents the current navigation state, e.g., the navigation state that is directly responsive to the user's query. In step 608, the current navigation state is used to evaluate the trigger. In block 610, if the trigger is valid, i.e., has evaluated to “True,” then the action is executed beginning with step 614, otherwise the rule evaluation fails as indicated in block 612. In step 614, the current navigation state 604 and the rule 602 are used to generate a new query. Subsequently, in step 616, the new query is executed on the appropriate data 606 to obtain the supplemental results that are responsive to the new query. In block 618, the results are checked to determine whether they satisfy certain criteria, namely, whether the supplemental results include at least one document and whether the results are greater than some minimum threshold of results that may have been specified in the rule. If not, the process terminates, in block 612. In step 620, the supplemental documents are sorted as specified in the action of the rule 602. In step 622, the results for the original query, i.e., the results corresponding to the navigation state 604, are also computed. In step 624, the documents corresponding to the current navigation state are then combined with the supplemental documents. In step 626, the combined results are returned by the rules engine and eventually displayed to the user. The process then terminates.
In some embodiments, an action can include supplementing the result with options to navigate to one or more navigation states. The included navigation state or plurality of navigation states may depend on the navigation state that activated the rule's trigger, or they may be independent of the navigation state that activated the rule's trigger. For example, the included navigation state or plurality of navigation states could be restricted to descendants of the navigation state that activated the rule's trigger. In an application that represents wines in its collection of materials, an action that specifies the inclusion as supplemental content of the navigation state that narrows the current state by adding the term {Rating: 96-100} is an example of this type of dependent action.
In some embodiments, an action may not only provide the option to navigate to a navigation state, but also provide a preview of the results of using such an option to navigate. Such a preview could include a document or a plurality of documents, or some other information that summarizes or otherwise describes the navigation state or states in the supplemental content. For example, in an application that represents wines in its collection of materials, an action might specify the inclusion as supplemental content of a preview of the documents in the navigation state that narrows the current state by adding the term {Rating: 96-100}.
In some embodiments, the rules engine allows an action to specify text and/or graphics as supplemental content. Such text and/or graphics may serve to promote particular content, or to fine-tune how the user experiences the content returned in response to a query. The text and/or graphics may depend on the navigation state that activated the rule's trigger, or it may be independent of the navigation state that activated the rule's trigger. For example, in an application that represents wines in its collection of materials, an action triggered by the inclusion of a term like {Price: Under $10} might specify the inclusion as supplemental content of text that says “We have the best prices in the business!”.
In some embodiments, the rules engine allows an action to specify how content presented to a user is logically or physically arranged. A potential logical arrangement may arrange content into groups. These logical groups could be mapped to a physical arrangement of content such as breaking up content into discrete sections. Other kinds of arrangement may include sorting, aggregation, geometric placement, or other arrangement details. The arrangement may depend on the navigation state that activated the rule's trigger, or it may be independent of the navigation state that activated the rule's trigger. For example, in an application that represents movies in its collection of materials, an action triggered by the inclusion of a term like {Price: Under $10} might specify that movies in the navigation state are sorted by price.
In some embodiments, the rules engine allows an action to specify how content presented to a user is rendered. In the context of a visual user interface, rendering includes such considerations as font, size, and color. The rendering may depend on the navigation state that activated the rule's trigger, or it may be independent of the navigation state that activated the rule's trigger. For example, in an application that represents wines in its collection of materials, an action might specify that documents corresponding to wines with a high ratio of rating to price be annotated with a text and/or graphics indicating that these are “best buys.”
In some embodiments, the rules engine allows an action to specify the inclusion of a transformation of the query with the results. This transformation may modify the query by adding, removing, or replacing attribute-value pairs or keywords. The transformation can have the effect of narrowing or generalizing the query, or can have an effect that neither narrows not generalizes the query, but otherwise modifies the query received from the user (e.g., by replacing an attribute-value pair with a related attribute-value pair that neither narrows nor generalizes the given term, or by replacing a keyword with a related attribute-value pair). The query transformation may depend on the query or navigation state that activated the rule's trigger, or it may be independent of the query or navigation state that activated the rule's trigger. For example, in an application that represents wines in its collection of materials, an action might specify that a query that included “red” in a full-text search query add {Type/Varietal: Red} as a term to generate a response to the query; this query transformation is dependent on the user's query.
In some embodiments, the rules engine allows an action to specify the setting or updating of variables to be used by subsequent rules. In some cases, an action may do nothing more than manipulate variables. Such manipulation may be useful for a rules script that uses conditional logic based on those variables. For example, a variable can be defined that stores the number of rules that have been triggered for a given navigation state; this variable would be incremented whenever a rule is triggered for that navigation state. A rules script might specify, using conditional logic, a maximum number of rules to trigger for a navigation state; it could refer to this variable in the conditional logic to determine whether to evaluate additional rules or terminate the script for that navigation state.
The action of a particular rule may include a number of individual actions. These individual actions can be combinations of different types of actions supported by the rules engine in a particular embodiment. For example, the action of a particular rule may include (1) identifying one type of supplemental content; (2) identifying a second type of supplemental content; (3) rendering the response to the query in a particular format; and (4) rendering the supplemental content in a different format.
In some embodiments, the rules engine processes the rules according to a script. The rules engine includes a component for building a script. In various embodiments, an information provider, user, or third party can build a script that combines rules using sequential, conditional, or randomized logic. In certain embodiments, the script uses the current navigation state, e.g., the navigation state responsive to the user's query, to process the rules. The current navigation state is used to evaluate triggers and perform actions.
In some embodiments, a script specifies that rules be ordered in a particular sequence. The order of rules in the sequence may affect the ordering of supplemental content displayed to the user. For example, if the actions of rules cause documents to be included as supplemental content, they may be included in the order of the rules that caused their inclusion. Since rules may also cause variables to be set or updated, the order of rules may be relevant to the overall effect of the script. For example, if a script is intended to return a maximum of 10 supplemental documents for a given navigation state, a variable may be used to store the number of supplemental documents returned as the script progresses. In this example, the order of rules is important, as it may determine which rules supply those 10 documents.
In some embodiments, a script specifies that rules be applied conditionally. In some embodiments, the rules engine allows the result of earlier rules in the sequence—in particular, variables set or updated by those earlier rules—to affect subsequent rules in the sequence. For example, if a present navigation state satisfies the trigger of an earlier rule in the sequence, then the rules engine might not consider later rules in the sequence. For example, if a script is intended to execute a maximum of 3 rules for a given navigation state, a variable may be used to store the number of rules executed as the script progresses. In this example, the order of rules is important, as it may determine which 3 rules are executed. Conditional logic may also be use to avoid duplication in the supplemental content. For example, a rule may be specified so that it does not include content already included by the execution of previous rules.
A script can specify that rules be applied using randomized logic. For example, the rules engine, rather than execute deterministically, could choose which rules to execute according to a procedure that includes a random or pseudorandom process.
Implementation of a Search and Navigation System
The knowledge base is transferred to a navigable data structure in order to implement the system. The navigation states may be fully precomputed, computed dynamically at run-time, or partially precomputed. A cache may be used to avoid redundant computation of navigation states.
In preferred embodiments, the collection of conjunctive navigation states may be represented as a graph—preferably, a directed acyclic multigraph with labeled edges. A graph is a combinatorial structure consisting of nodes and edges, where each edge links a pair of nodes. The two nodes linked by an edge are called its endpoints. In some systems that can be used in conjunction with the present invention, the nodes correspond to conjunctive navigation states, and the edges represent transitions that refine from one conjunctive navigation state to another. Since refinement is directional, each edge is directed from the more general node to the node that refines it. Because there is a partial order on the navigation states, there can be no directed cycles in the graph, i.e., the graph is acyclic. Preferably, the graph is a multigraph, since it allows the possibility of multiple edges connecting a given pair of nodes. Each edge is labeled with a term. Each edge has the property that starting with the term set of the more general end point, adding the edge term, and using the two-step map to put this term set into canonical form leads to a refinement which results in the navigation state that is the other endpoint. That is, each edge represents a refinement transition between nodes based on the addition of a single term.
The following definitions are useful for understanding the structure of the graph: descendant, ancestor, least common ancestor (LCA), proper ancestor, proper descendant, and greatest lower bound (GLB). These definitions apply to the refinement partial order among terms and among nodes. If A and B are terms and B refines A, then B is said to be a descendant of A and A is said to be an ancestor of B. If, furthermore, A and B are distinct terms, then B is said to be a proper descendant of A and A is said to be a proper ancestor of B. The same definitions apply if A and B are both nodes.
If C is an ancestor of A and C is also an ancestor of B, then C is said to be a common ancestor of A and B, where A, B, and C are either all terms or all nodes. The minimal elements of the set of common ancestors of A and B are called the least common ancestors (LCAs) of A and B. If no term has a pair of incomparable ancestors, then the LCA of two terms—or of two nodes—is unique. For example, the LCA of Origin: Argentina and Origin: Chile is Origin: South America in the partial order of terms 110 of FIG. 14B. In general, however, there may be a set of LCAs for a given pair of terms or nodes.
In an implementation that fully precomputes the collection of nodes, computation of the nodes in the graphs is preferably performed bottom-up.
The leaf nodes in the graph—that is, the nodes corresponding to leaf navigation states—may be computed directly from the classified documents. Typically, but not necessarily, a leaf node will correspond to a set containing a single document. The remaining, non-leaf nodes are obtained by computing the LCA-closure of the leaf nodes—that is, all of the nodes that are the LCAs of subsets of the leaf nodes.
The edges of the graph are determined according to a refinement function, called the R function for notational convenience. The R function takes as arguments two nodes A and B, where A is a proper ancestor of B, and returns the set of maximal terms such that, if term C is in R (A, B), then refining node A with term C results in a node that is a proper descendant of A and an ancestor (not necessarily proper) of B. For example, in FIG. 17, R ({Type/Varietal: Red}, {Type/Varietal: Merlot AND Origin: Argentina AND Vintage: 1998})={Type/Varietal: Merlot AND Origin: South America AND Vintage: 1998}. If B, is an ancestor of B2, then R (A, B1) is a subset of R (A, B2)—assuming that A is a proper ancestor of both B1 and B2. For example, R ({Type/Varietal: Red}, {Type/Varietal: Red AND Origin: South America})={Origin: South America}.
In the graph, the edges between nodes A and B will correspond to a subset of the terms in R (A, B). Also, no two edges from a single ancestor node A use the same term for refinement. If node A has a collection of descendant nodes {B1, B2, . . . } such that term C is in all of the R (A, Bi), then the only edge from node A with term C goes to LCA (B1, B2, . . . ), which is guaranteed to be the unique maximal node among the Bi. In FIG. 17, for example, the edge from node {Type/Varietal: Red} with term Origin: South America goes to node {Type/Varietal: Red AND Origin: South America} rather than to that node's proper descendants {Type/Varietal: Merlot AND Origin: South America AND Vintage: 1998} and {Type/Varietal: Red AND Origin: Chile}. The LCA-closure property of the graph ensures the existence of a unique maximal node among the Bi. Thus, each edge maps a node-term pair uniquely to a proper descendant of that node.
The LCA-closure of the graph results in the useful property that, for a given term set S, the set of nodes whose term sets refine S has a unique maximal node. This node is called the greatest lower bound (GLB) of S.
The graph may be computed explicitly and stored in a combinatorial data structure; it may be represented implicitly in a structure that does not necessarily contain explicit representations of the nodes and edges; or it may be represented using a method that combines these strategies. Because the search and navigation system will typically operate on a large collection of documents, it is preferred that the graph be represented by a method that is scalable.
The graph could be obtained by computing the LCAs of every possible subset of leaf nodes. Such an approach, however, grows exponentially in the number of leaf nodes, and is inherently not scalable. An alternative strategy for obtaining the LCA closure is to repeatedly consider all pairs of nodes in the graph, check if each pair's LCA is in the graph, and add that LCA to the graph as needed. This strategy, though a significant improvement on the previous one, is still relatively not scalable.
A more efficient way to precompute the nodes is to process the document set sequentially, compute the node for each document, and add that node to the graph along with any other nodes necessary to maintain LCA-closure. The system stores the nodes and edges as a directed acyclic multigraph. The graph is initialized to contain a single node corresponding to the empty term set, the root node. Referring to FIG. 18, in process 230 for inserting a new node into the graph, in step 232, for each new document to be inserted into the graph that does not correspond to an existing node, the system creates a new node. In step 234, before inserting the new node into the graph, the system recursively generates and inserts any missing LCA nodes between the root node (or ancestor node) and the new node. To ensure LCA-closure after every node insertion, the system inserts the document node last, in steps 236 and 238, after inserting all the other nodes that are proper ancestors of it.
Inserting a new node requires the addition of the appropriate edges from ancestors to the node, in step 236, and to descendants out of the new node, in step 238. The edges into the node are preferably determined by identifying the ancestors that have refinement terms that lead into the new node and do not already have those refinement terms used on edges leading to intermediate ancestors of the new node. The edges out of the node are preferably determined by computing the GLB of the new node and appropriately adding edges from the new node to the GLB and to nodes to which the GLB has edges.
The entire graph of conjunctive navigation states may be precomputed by following the above procedures for each document in the collection. Computation of other types of navigation states is discussed below. Precomputing of the graph may be preferred where the size of the graph is manageable, or if users are likely to visit every navigation state with equal probability. In practice, however, users typically visit some navigation states more frequently than others. Indeed, as the graph gets larger, some navigation states may never be visited at all. Unfortunately, reliable predictions of the frequency with which navigation states will be visited are difficult. In addition, it is generally not practical to precompute the collection of navigation states that are not conjunctive, as this collection is usually much larger than the collection of conjunctive navigation states.
An alternative strategy to precomputing the navigation states is to create indexes that allow the navigation states to be computed dynamically. Specifically, each document can be indexed by all of the terms that are associated with that document or that have refinements associated with that document. The resulting index is generally much smaller in size than a data structure that stores the graph of navigation states. This dynamic approach may save space and precomputation time, but it may do so at the cost of higher response times or greater computational requirements for operation. A dynamic implementation may use a one-argument version of the R function that returns all refinement terms from a given navigation state, as well a procedure for computing the GLB of a term set.
It is also possible to precompute a subset of the navigation states. It is preferable to precompute the states that will cost the most to compute dynamically. For example, if a state corresponds to a large subset of the documents, it may be preferable to compute it in advance. In one possible partial precomputation approach, all navigation states, particularly conjunctive ones, corresponding to a subset of documents above a threshold size may be precomputed. Precomputing a state is also preferable if the state will be visited frequently. In some instances it may be possible to predict the frequency with which a navigation state will be visited. Even if the frequency with which a navigation state will be visited cannot be predicted in advance, the need to continually recompute can be reduced by caching the results of dynamic computation. Most recently or most frequently visited states may be cached.
As described above with respect to the interface, the system supports at least three kinds of navigational operations—namely refinement, generalization, and query by specifying an expression of terms. These operations may be further described in terms of the graph. For query refinement, the system enumerates the terms that are on edges from the node corresponding to the current navigation state. When the user selects a term for refinement, the system responds by presenting the node to which that edge leads. Similarly, for query generalization options, the system enumerates and selects edges that lead to (rather than from) the node corresponding to the current navigation state. Alternatively, query generalization may be implemented as a special case of query by specifying a set of terms. For query by specifying a set of keywords, the system creates a virtual node corresponding to the given term set and determines the GLB of the virtual node in the graph. If no GLB is found, then there are no documents that satisfy the query. Otherwise, the GLB node will be the most general node in the graph that corresponds to a navigation state where all documents satisfy the query.
The above discussion focuses on how the system represents and computes conjunctive navigation states. The user interface may allows users to navigate among the collection of conjunctive navigation states. In some cases, users may be able to navigate to navigation states that are not conjunctive. In particular, when the system supports navigation states that are not conjunctive, the user interface may allow users to select terms disjunctively or negationally.
If the system includes navigation states that are both conjunctive and disjunctive (e.g., {(Products: DVDs OR Products: Videos) AND Director: Spike Lee}), then in some embodiments, the system only precomputes a subset of the states, particularly if the total number of navigation states is likely to be too large to maintain in memory or even secondary (e.g., disk) storage. By using rules for equivalence of Boolean expressions, it is possible to express any navigation state that mixes conjunction and disjunction in terms of a union of conjunctive navigation states. The above example can be rewritten as {(Products: DVDs AND Director: Spike Lee) OR (Products: Videos AND Director: Spike Lee)}. This approach leads to an implementation combining conjunctive and disjunctive navigation states based on the above discussion, regardless of whether all, some, or none of the graph of conjunctive navigation states is precomputed.
In preferred embodiments, disjunctive selections may be made within, but not between, attributes. When determining the set of disjunctive generalizations, the system does not consider other terms from the attribute of the given disjunction to be in the navigation state. For example, if the navigation state is {Type/Varietal: Red AND Origin: Chile} and the system is allowing the disjunctive selection of other countries of origin, then the GLB and R function will be applied to the set {Type/Varietal: Red} rather than to {Type/Varietal: Red AND Origin: Chile}. Accordingly, the other terms for the attribute of country of origin that are incomparable to “Chile” become generalization options for the navigation state.
If the system includes navigation states that use negation (e.g., {Products: DVDs AND Genre: Comedy AND (NOT Director: Woody Allen)}), then the negationally selected terms can be applied to navigation states as a post-process filtering operation. The above example can be implemented by taking the conjunctive navigation state {Products: DVDs AND Genre: Comedy} and applying a filter to it that excludes all movies associated with the term Director: Woody Allen. This approach leads to an implementation including negational navigation states based on the above discussion, regardless of whether all, some, or none of the graph of conjunctive navigation states is precomputed.
As with disjunction, when determining the set of negational generalizations, the system does not consider other terms from the attribute of the given negation to be in the navigation state. For example, if the navigation state is {Medium: Compact Disc AND Artist: Prince} and the system is allowing the negational selection of other artists (e.g., {Artist: Prince AND NOT (Artist: The Revolution)}), then the GLB and R function will be applied to the set {Medium: Compact Disc} rather than to {Medium: Compact Disc AND Artist: Prince}.
Another aspect of the system is the interpretation of free-text search queries. As discussed above, a free-text query may be interpreted in two ways. A single-term interpretation maps the query to an individual term in the knowledge base. A multi-term interpretation maps the query to a conjunction of two or more terms in the knowledge base—that is, a combination of terms that corresponds to a conjunctive navigation state.
A free-text query may be formed of one or more words. In one example, a single-term interpretation of a free-text query maps the query to a term that either contains or is associated with a word or words in that query. A query may have more than one single-term interpretation. For example, a query of computer science might have {Department: Computer Science Department} and {School: School of Computer Science} as single-term interpretations. For another example, a query of zinfandel might have {Wine Type: Zinfandel} and {Wine Type: White Zinfandel} as single-term interpretations. Various query semantics can be used to parse the search query and determine the set of single-term interpretations for a given free-text query. Under conjunctive query semantics, a matching term must contain all of the words in the query. Under disjunctive query semantics, a matching term must contain at least one of the words in the query. Under partial match query semantics, a matching term must contain a subset of the words in the query; the particular rules are application-dependent. It is also possible to vary the above to meet particular application needs. Variations include ignoring common “stop words” such as the and of, treating related words or word forms (e.g., singular and plural forms of nouns, or synonyms) as equivalent, automatic spelling correction, allowing delimited phrases (i.e., two or more words required to occur contiguously in a phrase), and support for negation (i.e., excluding terms that contain particular words).
By way of example, in some systems, a multi-term interpretation of a free-text query maps the query to a conjunction of terms that either contain or are associated with a word or words in that query and that correspond to a conjunctive navigation state in the system. A query may have more than one multi-term interpretation. For example, a query of security books might have {Media Type: Books AND Subject: Computer Security} and {Media Type: Books AND Subject: Financial Security} as multi-term interpretations. As with single-term interpretations, various query semantics can be used to parse the query and determine the set of multi-term interpretations for a given free-text query. Under conjunctive query semantics, a matching conjunction of terms must contain all of the words in the query. Under partial match query semantics, a matching conjunction of terms must contain a subset of the words in the query; the particular rules are application-dependent. It is also possible to vary the above to meet particular application needs. Variations, as discussed above, include ignoring common “stop words”, treating related words or word forms as equivalent, automatic spelling correction, allowing delimited phrases, and support for negation. Regardless of the query semantics used, multi-term interpretations are themselves conjunctions of terms, and therefore preferably correspond to conjunctive navigation states.
In typical embodiments, one-word queries will only have single-term interpretations, while multi-word queries may have single-term interpretations, multi-term interpretations, or both. For example, a query of casual shoes might have {Type: Casual Shoes} as a single-term interpretation and {Type: Athletic Shoes AND Merchant: Casual Living} as a multi-term interpretation.
In some systems, a multi-term interpretation is minimal—that is, the removal of any term from the interpretation would result in an interpretation that no longer satisfies the query. For example, the conjunction of terms {Media Type: Books AND Subject: Computer Security} is a minimal interpretation of the query security books; it is not, however, a minimal interpretation of the query computer security, since removing the term {Media Type: Books} results in the single-term interpretation {Subject: Computer Security} that satisfies the query. For another example, the conjunction of terms {Flower Type: Red Roses AND Quantity: Dozen} is a minimal interpretation of the query dozen red roses; in contrast, the conjunction of terms {Flower Type: Red Roses AND Quantity: Dozen AND Color: Red} is not a minimal interpretation for this query, since removing the term {Color: Red} results is a minimal multi-term interpretation that satisfies the query. In some systems, disjunctive query semantics are not used for multi-term interpretations. Under disjunctive query semantics, all minimal interpretations of a query are single-term interpretations. Single-term interpretations are always minimal, since there is only one term to remove.
In some systems, the computation of single-term search results uses an inverted index data structure that maps words to the terms containing them. Conjunctive query semantics may be implemented by computing the intersection of the term sets returned by looking up each query word in the inverted index, while disjunctive query semantics may be implemented by computing the union of the term sets.
In some systems, the computation of multi-term search results uses both an inverted index data structure that maps words to the terms containing them and an inverted index data structure that maps terms to the materials associated with them.
In some systems, the computation of multi-term search results that correspond to conjunctive navigation states involves a four step procedure. However, alternative procedures may be used. The steps of an algorithm 600 for receiving a query and returning the multi-term search results are indicated in FIG. 23.
Once a query is received in step 610, in the first step 620, the system determines the set of terms that contain at least one word in the search query. This step is equivalent to computing single-term search results using disjunctive query semantics.
In the second step 630, the system partitions the set of terms into equivalence classes. Each equivalence class corresponds to a non-empty subset of words from the query. Two terms which match the same subset of words in the query will be assigned to the same equivalence class.
In the third step 640, the system considers the word subsets corresponding to the equivalence classes from the previous step, and computes which combinations of these subsets correspond to minimal interpretations of the query. A combination of subsets corresponds to a minimal interpretation if its union is equal to the entire query, but the removal of any of its subsets causes the union to not be equal to the entire query.
In the fourth step 650, the system considers, for each combination of subsets that corresponds to a minimal interpretation, the set of multi-term interpretations that can be obtained from terms in the corresponding equivalence classes. These multi-term interpretations can be computed by enumerating, for each combination of subsets, all possible ways of choosing one term from each of the equivalence classes in the combination. Each resulting set of terms that corresponds to a conjunctive navigation state is added to the set of search results as a single-term (if it only contains one term) or multi-term interpretation. Finally in step 660, the results are returned.
For example, a search query of 1996 sweet red in the wines domain obtains multi-term interpretations as follows.
In the first step, the following terms contain at least one of the words in the query:

    
    
        Year. 1996
        Wine Types Sweet Wines
        Flavors: Sweet
        Wine Types Appellational Red
        Wine Types Red Wines
        Wineries: Red Birch
        Wineries: Red Hill
    
    


In the second step, there are 3 equivalence classes:

    
    
        Terms containing 1996
        
            Year: 1996
        
        
        Terms containing sweet
        
            Wine Types Sweet Wines
            Flavors: Sweet
        
        
        Terms containing red
        
            Wine Types Appellational Red
            Wine Types Red Wines
            Wineries: Red Birch
            Wineries: Red Hill
        
        
    
    


In the third step, there is 1 combination of equivalence classes that is a minimal interpretation—namely, the combination of all 3 equivalence classes.
In the fourth step, the 8 candidates for minimal interpretations are:

    
    
        {Year: 1996 AND Wine Types: Sweet Wines AND Wine Types: Appellational Red}
        {Year: 1996 AND Wine Types: Sweet Wines AND Wine Types: Red Wines}
        {Year: 1996 AND Wine Types: Sweet Wines AND Wineries: Red Birch}
        {Year: 1996 AND Wine Types: Sweet Wines AND Wineries: Red Hill}
        {Year: 1996 AND Flavors: Sweet AND Wine Types: Appellational Red}
        {Year: 1996 AND Flavors: Sweet AND Wine Types: Red Wines}
        {Year: 1996 AND Flavors: Sweet AND Wineries: Red Birch}
        {Year: 1996 AND Flavors: Sweet AND Wineries: Red Hill}
    
    


Of these, the following map to conjunctive navigation states in the system and are thus returned as search results:

    
    
        {Year: 1996 and Wine Types: Sweet Wines and Wineries: Red Birch}
        {Year: 1996 AND Wine Types: Sweet Wines AND Wineries: Red Hill}
        {Year: 1996 AND Flavors: Sweet AND Wine Types: Appellational Red}
        {Year: 1996 AND Flavors: Sweet AND Wine Types: Red Wines}
        {Year: 1996 AND Flavors: Sweet AND Wineries: Red Birch}
        {Year: 1996 AND Flavors: Sweet AND Wineries: Red Hill}
    
    


The other two minimal interpretations do not having matching documents and do not map to a navigation state in the system.
For another example, a search query of casual shoes obtains multi-term interpretations as follows.
In the first step, the following terms contain at least one of the words in the query:

    
    
        Type: Casual Shoes
        Merchant: Casual Living
        Brand: Casual Workstyles
        Type: Athletic Shoes
        Type: Dress Shoes
        Brand: Goody Two Shoes
        Merchant: Simple Shoes
    
    


In the second step, there are 3 equivalence classes:

    
    
        Terms containing casual
        
            Merchant: Casual Living
            Brand: Casual Workstyles
        
        
        Terms containing shoes
        
            Type: Athletic Shoes
            Type: Dress Shoes
            Brand: Goody Two Shoes
            Merchant: Simple Shoes
        
        
        Terms containing both casual and shoes
        
            Type: Casual Shoes
        
        
    
    


In the third step, there are 2 combinations of equivalence classes that are minimal interpretations. The first combination consists of the first two equivalence classes. The second combination consists of the third equivalence class by itself.
In the fourth step, the 9 candidates for minimal interpretations are:

    
    
        {Merchant: Casual Living AND Type: Athletic Shoes}
        {Merchant: Casual Living AND Type: Dress Shoes}
        {Merchant: Casual Living and Brand: Goody Two Shoes}
        {Merchant: Casual Living AND Merchant: Simple Shoes}
        {Brand: Casual Workstyles and Type: Athletic Shoes}
        {Brand: Casual Workstyles AND Type: Dress Shoes}
        {Brand: Casual Workstyles AND Brand: Goody Two Shoes}
        {Brand: Casual Workstyles AND Merchant: Simple Shoes}
        {Type: Casual Shoes}
    
    


Of these, the following map to conjunctive navigation states in the system and are thus returned as search results:

    
    
        {Merchant: Casual Living AND Type: Athletic Shoes}
        {Type: Casual Shoes}
    
    


The other minimal interpretations do not have matching documents and do not map to a navigation state in the system. For example, the brand Casual Workstyles does not sell Athletic Shoes in the system.
Another aspect of the system is its scalability through parallel or distributed computation. One way to define scalability in a search and navigation system is in terms of four problem dimensions: the number of materials in the collection, the number of terms associated with each material in the collection, the rate at which the system processes queries (throughput), and the time necessary to process a query (latency). In this definition, a system as scalable if it can be scaled along any of these four dimensions at a subquadratic cost. In other words:

    
    
        1. If the number of materials in the collection is denoted by the variable n1 and the other three problem dimensions are held constant, then the resource requirements are subquadratic in n1.
        2. If the number of terms associated with each material in the collection is denoted by the variable n2 and the other three problem dimensions are held constant, then the resource requirements are subquadratic in n2.
        3. If the number of queries that the system processes per second (i.e., the throughput) is denoted by the variable n3 and the other three problem dimensions are held constant, then the resource requirements are subquadratic in n3.
        4. If the time necessary to process a query (i.e., the latency) is denoted by the variable n4 and the other three problem dimensions are held constant, then the resource requirements are subquadratic in 1/n4.
    
    


Preferably, these resource requirements would be not only subquadratic, but linear. Also included within the concept of scalability, there is an allowance for overhead in creating a network of distributed resources. Typically, this overhead will be logarithmic, since the resources may be arranged in a hierarchical configuration of bounded fan-out.
In some embodiments, the system surmounts the limitations of a single computational server's limited resources by allowing for distributing the task of computing the information associated with a navigation state onto a hierarchy of multiple computational servers that act in parallel.
One insight that drives this feature is that it is possible to partition the collection of materials among multiple “slave” servers, all of which implement the single-server algorithm for multidimensional navigation, and then to have a “master” server compute navigation states by passing requests onto the set of slave machines and combining the responses. From the outside, the collection of servers appears to act like a single server, but with far greater computational resources than would be possible on a single computational device. Indeed, the distinction between master and slave servers is arbitrary; a slave server can itself have slaves, thus creating a nested hierarchy of servers. Such nesting is useful when the number of slaves exceeds the fan-out capability of a single master server. An exemplary embodiment of such a system is illustrated in FIG. 24. In the hierarchical arrangement 500, a master server 520 works with slave servers 530, 540. In the hierarchical arrangement shown, slave servers 530 are in turn master servers with respects to slave servers 540. The search and navigation results are made available to a user on a terminal 510 through a user interface.
The collection of materials may be partitioned by splitting (arbitrarily or otherwise) the materials into disjoint subsets, where each subset is assigned to its own server. The subsets may be roughly equal in size, or they might vary in size to reflect the differing computational resources available to each server.
The algorithm for distributing the task of computing the information associated with a navigation state includes three steps. The steps of the algorithm are indicated in FIG. 24. In the first step, the query, which is a request for a valid navigation state, is submitted to the master server 520, which forwards the query to each of the slave servers 530. If the servers are nested, the requests are forwarded through the hierarchy of servers 500 until they reach the leaf servers 540 in the hierarchy. In the second step, each slave server 530, 540 processes the query independently, based on the subset of the collection of materials that is in its partition. In the third step, the master server 520 combines the responses from the slave servers to produce a response for the original query. The master server 520 returns the response to the terminal 510.
The master server receives the original request and farms it out to the slave servers. Thus, in preferred embodiments, the only computation performed by the master server is to combine the results from the slave servers. Each slave server that receives a request computes the navigation state based on the subset of the collection assigned to it. The computation may involve any combination of conjunction, disjunction, and negation.
The master server, in contrast, only performs a combination step. The combination step involves producing a valid navigation state, including documents and corresponding refinement options, from the responses from the slave servers. Since the collection of materials has been partitioned into disjoint subsets, the documents identified by each of the slave servers can be combined efficiently as a disjoint union. Combining the various refinement options returned by each of the slave servers may require additional processing, as described below.
The slave servers all process the same query, but on different partitions of the collection of materials. They will generally return different sets of refinement options because a set of refinement options that is valid for one partition may be invalid for another. If the different sets are disjoint, and if the refinement options involve terms that do not themselves have refinement relationships, then the combination is a disjoint union.
Typically, there will be some overlap among the different sets of refinement options returned by each slave server. If the sets are not disjoint, duplicates can be eliminated in this combination step.
When there are refinement relationships among the terms that are refinement options returned by the slave servers, the combination algorithm computes, for every set of related terms, the least common ancestor or ancestors (LCA) of the terms, as defined by the partial order among the terms. One algorithm for combining the refinement options is outlined in FIG. 25. In step 552, the master server receives and takes the union of all of the terms, x1, x2, . . . xn, returned as refinement options for the navigation state from the slave servers. In step 554, the master server computes the set of ancestors A1, A2, . . . An, for each of the terms, x1, x2, . . . xn, respectively. In step 556, the master server computes the intersection A of all of the sets of ancestors, A1, A2, . . . An. In step 558, the master server computes the set M of minimal terms in A. The set M, formed of the least common ancestors of the terms x1, x2, . . . xn, returned by the slave servers, is the set of refinement options corresponding to the result navigation state. This combination procedure is applied whether the refinement options are conjunctive, disjunctive, or negational.
In summary, the master server receives a request for a navigation state, forwards this request to each of the slave servers, combines their results with a union operation, and then computes, for every set of terms, the least common ancestor or ancestors of the set.
There are at least two ways to compute the LCA of the terms. One approach is to store all non-leaf terms on the master server. This strategy is reasonably memory efficient, since, in practice, most of the terms are leaves (minimal elements) in the partial order. A second approach is to include the ancestors when returning the terms that are refinements. This approach saves memory at the expense of increasing the size of the data being transferred. The latter overhead is reasonable, since, in practice, a term typically has very few ancestors.
The task of computing results for a free-text search query may also be distributed. In the arrangement described above, for example, the master can simply compute the union of the free-text search results returned by the slave servers. This approach applies to both single-term and multi-term search under both conjunctive and disjunctive query semantics. More complex approaches may be used to accommodate customized query semantics.
Implementation of Rules Engine
Some embodiments include an implementation of the rules engine that defines a language for specifying a rules script and a system for executing that rules script to manage the presentation of content.
In some embodiments in which a trigger is defined in terms of expressions of attribute-value pairs, a trigger is a function that takes a query or its corresponding navigation state as an argument and returns a Boolean value. When the rule is processed, the trigger is first evaluated. When the trigger is evaluated, a return value of true indicates that the query or navigation state satisfies the criteria for activating the rule, while a return value of false indicates that the query or navigation state does not satisfy the criteria for activating the rule. The action is only executed if the trigger is true.
In one embodiment, the language for specifying a trigger may include the following Boolean-valued functions:

    
    
        Query.Equals(Q: Query) returns true if the query being considered by the rule is equal to Q, false otherwise.
        Navigation_State.Equals(N: Navigation_State) returns true if the navigation state being considered by the rule is equal to N, false otherwise.
        Query.Contains_Attribute_Value_Pair(A: Attribute, V: Value) returns true if the query contains the attribute-value pair (A, V), false otherwise.
        Navigation_State.Contains_Attribute_Value_Pair(A: Attribute, V: Value) returns true if the navigation state contains the attribute-value pair (A, V), false otherwise.
        Query.Contains_Keyword (K: Keyword) returns true if the query contains the keyword (K), false otherwise.
        Navigation_State.Is_Ancestor_Of(N: Navigation_State) returns true if the navigation state being considered by the rule is an ancestor of N, false otherwise.
        Navigation_State.Is_Descendant_Of(N: Navigation_State) returns true if the navigation state being considered by the rule is a descendant of N, false otherwise.
        Navigation_State.Contains_Document(D: Document) returns true if the navigation state being considered by the rule contains document D, false otherwise.
        True is simply the literal Boolean value for true.
    
    


In some embodiments, the language for specifying a trigger includes the Boolean operators AND, OR, and NOT.
In some embodiments, the language for specifying a trigger allows for variables local to the rule to be populated based on the navigation state being considered by the rule. Such variables might correspond to terms in the navigation state, and could be specified positionally (e.g., the second term in the navigation state) or in terms of the partial order of terms (e.g., the term or terms in the navigation state that are descendants of a given term). These variables, once populated, can be used by the rule's action.
In one embodiment, the language for specifying an action may include the following operations or a combination thereof:

    
    
        Include_Document(D: Document), where document D either is hard-coded or is partially or fully determined based on variables populated by the trigger.
        Include_Query(Q: Query), where query Q either is hard-coded or is partially or fully determined based on variables populated by the trigger. In some embodiments of the present invention, this operation might provide a preview of the navigation state corresponding to query Q. Such a preview could include a document or a plurality of documents, or some other information that summarizes or otherwise describes the navigation state.
        Include_Navigation_State(N: Navigation_State), where navigation state N either is hard-coded or is partially or fully determined based on variables populated by the trigger. In some embodiments of the present invention, this operation might provide a preview of the included navigation state. Such a preview could include a document or a plurality of documents, or some other information that summarizes or otherwise describes the navigation state.
        Include_Text(T: Text), where text T either is hard-coded or is partially or fully determined based on variables populated by the trigger.
        Include_Graphics (G: Graphics), where graphics G either is hard-coded or is partially or fully determined based on variables populated by the trigger.
    
    


In some embodiments, the language for specifying an action includes operations for filtering, sorting, aggregation, and truncation. These operations can be applied to documents or navigation states. These operations can be applied to query results, to content pushed by rules, or to both. In some embodiments of the present invention, these operations may act in a way that either is hard-coded or is partially or fully determined based on variables populated by the trigger. In some embodiments of the present invention, these operations may make use of randomization.
Document filtering may reduce the number of documents in the query results or the content pushed by rules by restricting the documents in either or both sets to those satisfying a predicate, e.g., the documents containing a particular term specified by the rule. In some embodiments, a document filter can be composed using Boolean operations. Navigation state filtering is analogous, only that it is applied to the set of navigation states included in the results or pushed content rather than to the documents.
Document sorting may reorder the documents in the results, e.g., ordering them by recency or popularity. In some embodiments, a document sort key can be based on explicitly represented document information or can be derived from such information. Navigation state sorting is analogous, only that it is applied to the set of navigation states included in the results or pushed content rather than to the documents.
Document aggregation may group the documents in the results into equivalence classes based on an explicit or derived property of those documents. In some embodiments, the aggregation key can be specified using an attribute or plurality of attributes. In some embodiments, the aggregation key can be based on explicitly represented document information or can be derived from such information.
Document truncation may reduce the number of documents in the results by restricting them to a particular number of documents. In some embodiments, truncation respects document ordering, i.e., truncating to 10 documents eliminates all but the first 10 documents from the results. Navigation state truncation is analogous, only that it is applied to the set of navigation states included in the results rather than to the documents.
These operations may act in a way that either is hard-coded or is partially or fully determined based on variables populated by the trigger. For example, a rule may filter included documents to include only those that contain a majority of the terms in the navigation state. Alternatively, a rule may sort included documents by the first term in the navigation state. In yet another example, a rule may include a number of navigation states that is truncated based on the number of terms in the navigation state.
In some embodiments, these operations may make use of randomization. For example, a rule may determine a set of candidate documents or navigation states to include, and then use a random or pseudorandom process to determine which of those candidates to actually include.
In some embodiments, a single rule may use one or more of these operations. It may order and apply them in any combination, possibly using the same operation more than once. For example, a set of included documents may be (1) filtered, then (2) sorted according to a given sort key, then (3) aggregated according to a given aggregation key, and then (4) truncated to 10 aggregates.
In some embodiments, a language allows a rule or plurality of rules to be specified in a script. In such an embodiment, rules may be combined using sequential, conditional, or randomized execution.
In sequential execution, rules are considered in the order they are specified. For example if two rules triggered by the same query or navigation state are executed sequentially, then the first rule is considered before the second. Sequential execution may be used for prioritization: for example, higher priority rules may be considered before lower priority rules, and the priority may be reflected in the order of results.
In conditional execution, the execution of a rule depends on specified criteria. In some embodiments, conditional execution can be specified using if . . . then . . . else logic. Conditional execution may be combined with sequential execution: the results of considering an earlier rule may partially or completely determine whether a later rule is executed. For example, a rule may be specified to conditionally execute only if less than 3 previous rules have been executed for a given query or navigation state.
In randomized execution, the execution of a rule depends on a random or pseudorandom process. For example, a rule may be specified as executing only half the time that it is considered, in order to vary the results randomly. Randomized execution may be useful in combination with conditional execution. For example, it may be used to execute a randomly selected subset of 3 out of 10 applicable rules.
In some embodiments, the execution of a rules script for a given query or navigation state includes the identification of applicable rules and the execution of those applicable rules. In some embodiments, the identification of applicable rules by evaluating their triggers precedes their execution; for example, the identified rules may be batched up before any are executed. In other embodiments, the identification of applicable rules may be interleaved with their execution; for example, a rule may be executed as soon as it is identified as applicable.
In some embodiments, specified rules may be stored in a linear array. On evaluation of a query, the array may be scanned looking for the applicable rules for a given query or navigation state by evaluating to see if the rule's criteria are met by the query or navigation state. Such a scan approach may be utilized, for example, if the number of rules is not so large as to raise performance concerns.
In addition, the script may specify the step of selecting a subset of rules before processing the rules to narrow the overall set of rules to those that are, for example, more likely to evaluate to true in the given query or navigation state, but without actually evaluating their triggers. In some embodiments, the selected rules to be processed may be identified using index structures that map terms to rules that may be triggered by the presence of those terms in the query or navigation state. The use of such index structures may address performance concerns that arise from a large number of rules. Once a subset of the rules has been selected, their execution depends on the sequential, conditional, and randomized logic specified in the rule script.
In accordance with the sequential logic of the rules script, the rules are considered in order. The order of rules may be represented by assigning an order field to each rule, e.g., 1, 2, 3 . . . . In some embodiments, a plurality of rules might be assigned the same order value in order to indicate that those rules can be performed in arbitrary order, thus making the ordering of rules a partial rather than total order.
In accordance with the conditional logic of the rules script, the execution of a rule depends on two factors. The first factor is any conditional criterion specified for the rule, such as an expression that depends on the results of executing previous rules. Conditional criteria need not be specified for every rule, in which case the second factor is always true for that rule. The second factor is the trigger. Only if both of these evaluate to true is the action of a rule performed. For example, conditional logic and sequential logic may be incorporated in a rule script that includes a set of ten rules numbered 1 to 10, to be executed in numerical sequence. But the evaluation of rules in this set is subject to the condition that a maximum of 2 of these rules may be executed in a single pass, e.g., for a single query from the user, after which time the remaining rules in the group are no longer considered. Logic is built into the script to process the rules sequentially, keeping track of how many rules have been performed (i.e., the rule condition and trigger have both been met and the action has been performed) for the given query.
FIG. 30 shows a script 660 for a collection of materials relating to wines. The script 660 uses sequential logic, and includes seven rules. The script 660 uses the current query to process the rules. For each rule, the script 660 includes its number in the sequence, defined as Rule # in column 662, any applicable conditions, defined as Rule Condition in column 664, the trigger, defined as Trigger Predicate in column 668, and the action, defined as Action(s) in column 668.
Rule #1 has no corresponding conditions, thus Rule Condition 664 is always set to “True.” Rule #1 also has a trigger that is always set to “True;” thus, Rule #1 is applied to the results of every query. Rule #1 specifies in the Action(s) 670 that the result includes documents responsive to the query that have a rating in the specified range. X is a variable that represents the number of rules that have already been applied to include documents in the desired content for that query. X is initially set to zero. X is incremented after the action is performed.
As indicated by Rule Condition 664, Rule #2 is only evaluated if X<3. The Trigger Predicate 668 for Rule #2 is satisfied if the current query includes the attribute-value pair {Type: Varietal: Champagne}. In that case, Dom Perignon 1972 is added to the result. X is incremented. A second variable Y is also set to “True.” Y is used in the Rule Condition 664 of Rule #3—in part because of the way the Rule Condition 664 and Trigger Predicate 668 for Rule #3 is specified, Rule #2 and Rule #3 are alternatives and only one of the two will be applied for a given query.
Rule #4 uses a Keyword in its Trigger Predicate 668. If the word “cheap” is in the query, then the Action(s) 670 specifies that the results are sorted by Price. Here, X is not incremented because the action Sort_Results does not add documents to the result.
Rules #5 and #6 have Trigger Predicates 668 defined in terms of descendants of attribute-value pairs. Rule #7 has an Action(s) 670 that generates a new query by adding a term to the query disjunctively.
In some embodiments, randomized logic can be implemented using standard random or pseudorandom number generators. Randomized logic in the script, for example, in a rule condition, can also be combined with randomized logic in the trigger of a rule.
In another example of the execution of a rule, the rules engine could execute another query composed using the originating navigation state and include the results of that navigation state in the displayed response of the query. In this example, the invention could take the navigation state, add a specific element and execute another query with the augmented navigation state. The results of this secondary query could be then sorted and a subset of which included in the response of the original query by the user. The results of execution of this rule could then be displayed in the response to the user.
In some embodiments, an implementation of the rules engine may overcome the limitations of a single computational server's limited resources by distributing the evaluations of rules in a parallel manner amongst multiple computational servers. Such an implementation could be built to distribute computation while preserving the same semantics as a non-distributed rules engine.
In such an implementation, a master computational server could orchestrate the computation by broadcasting the query and combining the results of the rule evaluation of multiple slave computational servers. In this implementation, the collection of rules is replicated on all master and slave computational servers. Each slave server may have different knowledge bases (or different portions of an overall knowledge base), so that on each client the rules are evaluated with respect to a different knowledge base.
In this implementation, the master server receives queries which are forwarded to each slave server. Each slave server on receipt of a query attempts to evaluate the rules with respect to its knowledge base. The master server then takes the rule evaluation results from each client server and combines the results with respect to the collection of rules.
In this implementation, the slave server begins by determining which of the entire collection of rules' triggers are valid with respect to the query or navigation state and placing the subset of rules in temporary storage. The resulting rules are then evaluated one by one, executing the actions on each rule. In order to preserve the semantics of the collective, slave servers may compute a larger set of rules that modify and conditionally depend on variables than deemed locally necessary. This additional computation allows the master server to combine the results in order to preserve the semantic of the non-distributed rules engine.
In this implementation, the slave servers, when they do not have enough information to fully determine the value of a variable, proceed using an estimate of the variable's value or range of values, based on their partial information. The master server, when it receives responses from the slave servers, determines if the slaves performed their computations correctly. If they did not, it sends information to the servers to correct those estimates. Multiple iterations may be necessary to achieve correct results.
For example, for a set of rules that set a temporary variable limiting the number of rules executed, each client may compute up to the maximum of rules to be executed to minimize the number of iterations from the master to the client. The master, in this case, combines the rules by then merging the results of client rule evaluations, possibly discarding individual results. This example trades additional evaluation by the client servers to eliminate additional iterations.
The search and navigation system described above allows information providers to overlay a search and navigation system over any collection of documents. The knowledge base aspect and the search and navigation aspect can be performed independently by different providers, and information providers may outsource these functions to separate entities. Similarly, a generated knowledge base may be imported by a search and navigation specialist. Information providers may also outsource this search and navigation requirement to a search and navigation system provider. A search and navigation system provider could charge customers a license fee for the system independent of the amount of its usage. Alternatively, a search and navigation system provider could charge customers on a per-click basis, a per-purchase basis if products are available via the system, or per-transaction generated from a click through the search and navigation system. A search and navigation system provider could also function as an aggregator—compiling records from a number of sources, combining them into a global data set, and generating a search and navigation system to search and navigate the data set. The search and navigation system can be implemented as software provided on a disk, on a CD, in memory, etc., or provided electronically (such as over the Internet).
A search and navigation system may also enhance user profiling capability and merchandising capability. The search and navigation system may maintain a profile of users based on the users' selections, including the particular paths selected to explore the collection of navigation states. Using the knowledge base, the system may also infer additional information regarding the users' preferences and interests by supplementing the selection information with information regarding related documents, attributes and terms in the knowledge base. That information may be used to market goods and services related to the documents of interest to the user.
The foregoing description has been directed to specific embodiments of the invention and specific examples of systems with which the invention may be used. The invention may be embodied in other specific forms without departing from the spirit and scope of the invention. The embodiments, figures, terms and examples used herein are intended by way of reference and illustration only and not by way of limitation. The scope of the invention is indicated by the appended claims and all changes that come within the meaning and scope of equivalency of the claims are intended to be embraced therein.

## Claims

1. A computer-implemented search and navigation system for a set of materials comprising:
a plurality of attribute-value pairs associated with the materials, wherein each of a plurality of values has an association with at least one of a plurality of attributes characterizing the materials;
a plurality of navigation states, wherein each navigation state corresponds to a particular expression of attribute-value pairs and to a particular subset of the materials, wherein for each navigation state the particular subset of the materials corresponding to the navigation state consists of those materials that are each described by every attribute-value pair in the particular set of attribute-value pairs corresponding to that navigation state;
wherein within the plurality of navigation states, at least a first navigation state includes a first attribute-value pair having a first attribute in which the first attribute-value pair does not describe all the materials that the first attribute characterizes, and a second navigation state includes at least the first attribute-value pair and a second attribute-value pair having a second attribute, which is not the same as the first attribute, in which the second attribute-value pair does not describe all the materials that the second attribute characterizes;
a set of rules for manipulating content provided in response to a query, a first query corresponding to a third navigation state corresponding to a third particular expression of attribute-value pairs and a third particular subset of materials, at least a first rule being composed of a first trigger for activating the first rule if the third particular expression of attribute-value pairs satisfies the trigger, the trigger including a third attribute-value pair, and a first action for providing a first manipulated subset of materials that is different from the third particular subset of materials if the first rule is activated; and
an interface for providing a plurality of transitions, each transition providing a direct path between two of the navigation states, wherein each transition represents a change from the set of attribute-value pairs corresponding to an originating navigation state to the set of attribute-value pairs corresponding to a destination navigation state, wherein a series of one or more transitions provides a path between any two navigation states, for receiving the first query, for providing a representation of a response to the first query, the response including the third particular subset of materials if the first rule is not activated and including the first manipulated set of materials if the first rule is activated, for modifying one or more rules from the set of rules, and for providing a representation of how modification of one or more rules affects the response to the first query.

2. A computer-implemented search and navigation system for a set of materials comprising:
a plurality of attribute-value pairs associated with the materials, wherein each of a plurality of values has an association with at least one of a plurality of attributes characterizing the materials;
a plurality of navigation states, wherein each navigation state corresponds to a particular expression of attribute-value pairs and to a particular subset of the materials, wherein for each navigation state the particular subset of the materials corresponding to the navigation state consists of those materials that are each described by every attribute-value pair in the particular set of attribute-value pairs corresponding to that navigation state;
wherein within the plurality of navigation states, at least a first navigation state includes a first attribute-value pair having a first attribute in which the first attribute-value pair does not describe all the materials that the first attribute characterizes, a second navigation state includes at least the first attribute-value pair and a second attribute-value pair having a second attribute, which is not the same as the first attribute, in which the second attribute-value pair does not describe all the materials that the second attribute characterizes;
a rules engine for defining and processing a set of rules for manipulating content for display generated from a current navigation state, first content for display being generated using the current navigation state if no rule is activated, wherein each rule is composed of a trigger for activating the rule if the trigger is satisfied, wherein the trigger is evaluated against the current navigation state, and an action for providing second content for display in place of first content for display if the rule is activated, wherein a first rule includes a first trigger that includes a third attribute-value pair, and a first action for providing a first manipulated subset of materials in place of the current particular subset of materials corresponding to the current navigation state if the first rule is activated; and
an interface for providing a representation of the current navigation state and for applying information from the current navigation state to the rules engine to create one or more rules.

3. The search and navigation system of claim 2, wherein the interface further includes a representation of how one or more rules were processed in reaching the current navigation state.

4. The search and navigation system of claim 2, wherein the interface further includes a representation of one or more rules that were triggered and/or one or more actions that resulted from a triggering of one or more rules.

5. A computer-implemented search and navigation system for a set of materials comprising:
a plurality of attribute-value pairs associated with the materials, wherein each of a plurality of values has an association with at least one of a plurality of attributes characterizing the materials;
a plurality of navigation states, wherein each navigation state corresponds to a particular expression of attribute-value pairs and to a particular subset of materials, wherein for each navigation state the particular subset of the materials corresponding to the navigation state consists of those materials that are each described by every attribute-value pair in the particular set of attribute-value pairs corresponding to that navigation state;
wherein within the plurality of navigation states, at least a first navigation state includes a first attribute-value pair having a first attribute in which the first attribute-value pair does not describe all the materials that the first attribute characterizes, a second navigation state includes at least the first attribute-value pair and a second attribute-value pair having a second attribute, which is not the same as the first attribute, in which the second attribute-value pair does not describe all the materials that the second attribute characterizes;
an interface for displaying content including a representation of a current navigation state, using a first representation if no rule is activated; and
a rules engine for specifying a set of rules for manipulating the content displayed by the interface, at least a first rule being composed of a first trigger for activating the first rule if the current navigation state satisfies the first trigger, the first trigger including a third attribute-value pair, and a first action for providing a second representation of the current navigation state in place of the first representation if the first rule is activated;
wherein, the interface further provides a representation of one or more rules associated with the current navigation state, including the first rule.

6. The search and navigation system of claim 5, wherein the interface further provides for modification of one or more rules associated with the current navigation state.

7. The search and navigation system of claim 5, wherein the interface further provides for an addition of one or more rules associated with the current navigation state.

8. The search and navigation system of claim 5, wherein the representation of one or more rules includes a representation of which of the one or more rules are activated.

9. The search and navigation system of claim 5, wherein the interface further provides for applying information from a current navigation state to the rules engine to specify one or more rules.

10. The search and navigation system of claim 5, wherein the displayed content and the representation of one or more rules associated with the current navigation state are combined.

11. The search and navigation system of claim 5, wherein the displayed content and the representation of one or more rules associated with the current navigation state are split.

12. A computer-implemented search and navigation system for a set of materials comprising:
a plurality of attribute-value pairs associated with the materials, wherein each of a plurality of values has an association with at least one of a plurality of attributes characterizing the materials;
a plurality of navigation states, wherein each navigation state corresponds to a particular expression of attribute-value pairs and to a particular subset of the materials, wherein for each navigation state the particular subset of the materials corresponding to the navigation state consists of those materials that are each described by every attribute-value pair in the particular set of attribute-value pairs corresponding to that navigation state;
wherein within the plurality of navigation states, at least a first navigation state includes a first attribute-value pair having a first attribute in which the first attribute-value pair does not describe all the materials that the first attribute characterizes, and a second navigation state includes at least the first attribute-value pair and a second attribute-value pair having a second attribute, which is not the same as the first attribute, in which the second attribute-value pair does not describe all the materials that the second attribute characterizes;
a set of rules for manipulating content provided in response to a query, at least a first rule being composed of a first trigger for activating the first rule if a third navigation state identified as corresponding to a first query satisfies the first trigger, the first trigger including a third attribute-value pair, and a first action for generating a fourth particular expression of attribute-value pairs; and
an interface for providing a plurality of transitions, each transition providing a direct path between two of the navigation states, wherein each transition represents a change from the set of attribute-value pairs corresponding to an originating navigation state to the set of attribute-value pairs corresponding to a destination navigation state, wherein a series of one or more transitions provides a path between any two navigation states, for receiving the first query, for providing a response to the first query, the response including a representation of the third navigation state when the first rule is not activated and a representation of a fourth navigation state having the fourth particular expression of attribute-value pairs when the first rule is activated, for modifying one or more rules from the set of rules, and for providing a representation of how modification of one or more rules affects the response to the first query.

13. The method of claim 12, wherein the fourth particular expression is generated by addition of an attribute-value pair to the third particular expression of attribute-value pairs.

14. The method of claim 12, wherein the fourth particular expression is generated by removal of an attribute-value Pair from the third particular expression of attribute-value pairs.