The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Jan. 25, 2000
Filed:
Jul. 03, 1995
David M Bristor, Menlo Park, CA (US);
Sun Microsystems, Inc., Palo Alto, CA (US);
Abstract
A history mechanism is provided in which user data, which represents signals generated by a user, are stored for subsequent recall and regeneration in a history database in one of two or more categories associated with two or more respective component symbols of the user data. For example, in one embodiment, user data includes alphabetic symbols and a respective category is formed for each letter of the alphabet. User data is parsed into components and stored in the history database in each category corresponding to the initial letter of each component of the user data since the initial letter of each component of the user data is prominent. The user recalls and regenerates the user data by selecting a category corresponding to a letter of the alphabet which is the initial letter of any component of the user data. The user then selects the previously generated user data from a list of previously generated user data classified under the selected category. By classifying previously generated user data based on the content of the user data, e.g., prominent symbols of the user data, previously generated user data is stored in a organizational structure without intervention by the user and independently of the user's particular subjective perspective of the user data being classified. By classifying the user data redundantly according to each of one or more components of the user data, reliance on any single component of the user data being particularly memorable or unique is avoided.