Abstract: Historical usage data related to user queries and training properties for a plurality of web pages is received and utilized to train a mathematical model to predict the likelihood of retrieval of a web page during a web search. Properties are extracted from the plurality of web pages in the index and the mathematical model is applied to the properties for each web page to calculate a sortrank value. The index is reordered based on the sortrank value such that the web pages most likely to be retrieved by a user submitting a search query appear first in the index. After a search query is received from a user the index is traversed in an order determined by the sortrank value. Responsive web pages are presented to the user in an order determined by a search engine ranking algorithm.

Abstract: A calculation engine processes user-definable formulas to generate calculation results. A calculation engine may use the following types of data structures: table, column, row, and field. A sub table may be embedded within a row. Operations may be performed at various levels, such as at: table, column, and field. A calculation engine may operate on a calculation table having columns, which may each have an ordered list of formulas. Formulas within such an ordered list may be evaluated in the order specified until one of the formulas is successfully evaluated. A hierarchy of formulas may be formed by a column's formula depending on another column or table. A graph of data dependencies may be prepared for determining an order in which operands and operations should be evaluated and performed.

Abstract: A calculation engine processes user-definable formulas to generate calculation results. A calculation engine may use the following types of data structures: table, column, row, and field. A sub table may be embedded within a row. Operations may be performed at various levels, such as at: table, column, and field. A calculation engine may operate on a calculation table having columns, which may each have an ordered list of formulas. Formulas within such an ordered list may be evaluated in the order specified until one of the formulas is successfully evaluated. A hierarchy of formulas may be formed by a column's formula depending on another column or table. A graph of data dependencies may be prepared for determining an order in which operands and operations should be evaluated and performed.

Abstract: A calculation engine processes user-definable formulas to generate calculation results. A calculation engine may use the following types of data structures: table, column, row, and field. A sub table may be embedded within a row. Operations may be performed at various levels, such as at: table, column, and field. A calculation engine may operate on a calculation table having columns, which may each have an ordered list of formulas. Formulas within such an ordered list may be evaluated in the order specified until one of the formulas is successfully evaluated. A hierarchy of formulas may be formed by a column's formula depending on another column or table. A graph of data dependencies may be prepared for determining an order in which operands and operations should be evaluated and performed.

Abstract: A spreadsheet program saves data into a hypertext markup language (HTML) document that can be viewed with a browser program, but persists all of the information associated with that data necessary to maintain formatting and functionality of the data if reintroduced into the spreadsheet program. The HTML document can then be used both for displaying the data over the Internet or other network in a browser program, and also for opening the data in the spreadsheet program. The information necessary for preserving the format and functionality of the data in the spreadsheet program is incorporated into the HTML document using HTML, Cascading Style Sheets (CSS), and Extended Markup Language (XML).

Abstract: A method for enabling data generated in a parent application to be translated into another format, such as hypertext markup language (HTML), so that formatting functionality unique to the parent application is retained, and so that the data reintroduced into the parent application from an HTML document has all its original formatting and functionality restored. As the data are translated into the other format, formatting information specific to the parent application is included with the data, but in such a manner that the formatting information is ignored by applications such as web browsers that are compatible with the other format. While translating the data into the other format, any formatting commands in the data that are not fully supported in the other format are identified, and if found, are translated so as to emulate the form of the data in the parent application. Included in the translated data is a marker identifying changes in the formatting commands.