Abstract: A vertical search engine may rank items based on both the quality of data associated with each item and the popularity of each item. The vertical search engine may access data associated with items from a variety of different sources, including feed sources and crawl sources. Data quality inputs are determined for each item based on the quality of the data associated with each respective item. In addition, popularity inputs are determined for each item based on user interest in each respective item. A global rankings score is then calculated for each item based on the data quality inputs and popularity inputs for each respective item. The global ranking score may be used to order search results for search queries in such a way that items from feed data and items from crawl data may be displayed in a unified manner, rather than being segregated by data source.

Abstract: Maintaining versions and workspaces in an object repository is disclosed. The system provides an efficient way to manage versions of objects by only copying objects when absolutely necessary, i.e. when a property value in a particular object has changed. In addition, the system provides a mechanism to control whether or not relationships are propagated to successor versions of an object. A further aspect of the system is that resolution of objects during a relationship traversal can be customized depending on whether or not an application accessing the objects is version-aware. If the application is not version aware, a means for resolving the relationship to a particular object is provided. A still further aspect of the system is that merge behavior is parameterized. When two versions of an object are merged, flags control how conflicts in property values and relationship contents are managed.

Abstract: Maintaining versions and workspaces in an object repository is disclosed. The system provides an efficient way to manage versions of objects by only copying objects when absolutely necessary, i.e. when a property value in a particular object has changed. In addition, the system provides a mechanism to control whether or not relationships are propagated to successor versions of an object. A further aspect of the system is that resolution of objects during a relationship traversal can be customized depending on whether or not an application accessing the objects is version-aware. If the application is not version aware, a means for resolving the relationship to a particular object is provided. A still further aspect of the system is that merge behavior is parameterized. When two versions of an object are merged, flags control how conflicts in property values and relationship contents are managed.

Abstract: Natural language (NL) text entered by a user in a document is recognized as corresponding to a tag, causing an action or action associated with the tag to be implemented in the document. Linguistic information, tags, and related actions are managed in a centralized catalog from which they can be accessed. An NL Parser called by a tag recognizer analyzes and normalizes the text using semantic information and returns a parse tree to the tag recognizer. The tag recognizer then compares the parse tree to a corresponding parse tree provided in a dictionary. If a match is found, an instance or tag related to the parse tree in the dictionary is returned to an application in which the document is open to carry out the action associated with the tag. If an ambiguity causes multiple matches to be returned, the user can select one of the instances and related action.