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:
May. 19, 2009
Filed:
Dec. 30, 2004
Reagan W. Moore, San Diego, CA (US);
Arcot Rajasekar, Del Mar, CA (US);
Chaitanya K. Baru, San Diego, CA (US);
Bertram Ludaescher, San Diego, CA (US);
Amarnath Gupta, San Diego, CA (US);
Richard J. Marciano, San Diego, CA (US);
Reagan W. Moore, San Diego, CA (US);
Arcot Rajasekar, Del Mar, CA (US);
Chaitanya K. Baru, San Diego, CA (US);
Bertram Ludaescher, San Diego, CA (US);
Amarnath Gupta, San Diego, CA (US);
Richard J. Marciano, San Diego, CA (US);
General Atomics, San Diego, CA (US);
Regents of the University of California, Oakland, CA (US);
Abstract
A persistent archive of a collection of data objects comprises a self-describing, infrastructure-independent representation of a logical structure for the collection and a self-describing, infrastructure-independent representation of the data objects. The archive is persistent in that it may be instantiated at an indefinite point in time in the future regardless of the state of technology at that time. A knowledge-based persistent archive of a collection of data objects comprises the foregoing two elements but also a self-describing, infrastructure-independent representation of knowledge relevant to the collection. Another embodiment of a knowledge-based persistent archive comprises at least one representation of a collection or the data objects, at least one self-describing, infrastructure-independent, or executable specification of one or more transformations relevant to the collection, and at least one self-describing, infrastructure-independent, or executable specification of one or more rules relevant to the collection.