US6562076B2
Expired / Lapsed
US
⏱️ 0.0 years remaining
Extending application behavior through active properties attached to a document in a document management system
Assignee: Xerox Corp
•
Filing: 1998-08-31
•
Granted: 2003-05-13
•
Expires: 2018-08-31
Abstract
Abstract A document management system is provided which organizes, stores and retrieves documents according to properties attached to the documents. A property attachment mechanism allows an application to attach arbitrary static and active properties to a document. The active properties include executable code which perform document management functions to control the state and behavior of the document in response to a triggering event. In this manner, the state and behavior of the document is provided to a user and is accurately maintained even when the application is not running.
Inventors
- 👤 Warren K. Edwards
- 👤 James P. Dourish
- 👤 Anthony G. LaMarca
- 👤 John O. Lamping
- 👤 Karin Petersen
- 👤 Michael F. Salisbury
- 👤 Douglas B. Terry
- 👤 James D. Thornton
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-24 09:37
CPC Classifications
G; G06; G06F; G06F40/00; G06F40/10; G06F16/00; G06F16/90; G06F16/93
Claims Analysis
Total Claims: 13
Claim 1
Independent Claim
152 words
A method of managing a document having a state and a behavior comprising the steps of: maintaining, by a document application, a plurality of management functions, each for controlling the state and the behavior of the document in accordance with the document application; selecting a management function from among the plurality of management functions; attaching, by the document application, the selected management function to the document, the management function, configured as an active property, including executable code for controlling the state and the behavior of the document; assigning a triggering event to the management function such that in response to the triggering event, the executable code of the management function is executed; and in response to the triggering event activating the management function to control the state and behavior of the document when the document application is not running, wherein the document content is stored completely separate from the attached active property.
Claim 2
Independent Claim
152 words
A method of managing a document having a state and a behavior comprising the steps of: maintaining, by a document application, a plurality of management functions, each for controlling the state and the behavior of the document in accordance with the document application; selecting a management function from among the plurality of management functions; attaching, by the document application, the selected management function to the document, the management function, configured as an active property, including executable code for controlling the state and the behavior of the document; assigning a triggering event to the management function such that in response to the triggering event, the executable code of the management function is executed; and in response to the triggering event activating the management function to control the state and behavior of the document when the document application is not running, wherein the document content is stored completely separate from the attached active property.
Claim 3
Dependent Claim
46 words
The method as set forth in claim 1 further including: creating a relationship between the document and a second document; and managing the relationship with the management function attached to the document such that the executable code controls a state and a behavior of the relationship.
Claim 4
Dependent Claim
22 words
The method as set forth in claim 2 further including creating a relationship between the document and a plurality of other documents.
Claim 5
Dependent Claim
18 words
The method according to claim 1 wherein the document management function occurs within a non-hierarchical document management system.
Claim 6
Dependent Claim
28 words
The method according to claim 4 wherein documents of the non-hierarchical document management system are managed based on properties rather than a hierarchical path and a file name.
Claim 7
Independent Claim
153 words
A method of managing a document comprising the steps of: generating a first document; forming a relationship between the first document and a separate second document defining a dependency therebetween; maintaining, by a document application, a plurality of management functions, each for controlling a state and a behavior of the document in accordance with the document application; attaching a management function of the plurality of management functions, to one of the first and second documents, which forms an association between the attached management function and the first and second documents said association being independent of document content and application format used to generate the document; and, managing the relationship between the first and second documents such that an external event is controlled from modifying the relationship, without first notifying a user, in accordance wit the management function, wherein the document content is stored completely separate from the management function attached to the document.
Claim 8
Independent Claim
153 words
A method of managing a document comprising the steps of: generating a first document; forming a relationship between the first document and a separate second document defining a dependency therebetween; maintaining, by a document application, a plurality of management functions, each for controlling a state and a behavior of the document in accordance with the document application; attaching a management function of the plurality of management functions, to one of the first and second documents, which forms an association between the attached management function and the first and second documents said association being independent of document content and application format used to generate the document; and, managing the relationship between the first and second documents such that an external event is controlled from modifying the relationship, without first notifying a user, in accordance wit the management function, wherein the document content is stored completely separate from the management function attached to the document.
Claim 9
Dependent Claim
41 words
The method as set forth in claim 6 further including assigning a triggering event to the management function such that in response to the triggering event, the management function is invoked to control the relationship and perform management of the documents.
Claim 10
Dependent Claim
184 words
In a non-hierarchical document management system having at least a first document, a method of document management comprising: creating, by an application, a second document; attaching active properties to the second document; creating, by the application, a relationship between the second document and the first document; passing the relationship between the second and first documents to a management function in order to manage the relationship even when the application is not operating; ending operation of the application; monitoring, by the document management system, to detect the occurrence of an event; detecting the occurrence of the event; comparing the event to the active properties attached to the second document to determine if the event is a triggering event, for any other of the attached active properties; initiating the management function by the active property to which the event is the triggering event; and providing, by the initiated management function, (i) instructions to the document management system to control the manner the triggering event is applied to the first document or (ii) control of a sequence of instructions which are executed in response to the event.
Claim 11
Dependent Claim
184 words
In a non-hierarchical document management system having at least a first document, a method of document management comprising: creating, by an application, a second document; attaching active properties to the second document; creating, by the application, a relationship between the second document and the first document; passing the relationship between the second and first documents to a management function in order to manage the relationship even when the application is not operating; ending operation of the application; monitoring, by the document management system, to detect the occurrence of an event; detecting the occurrence of the event; comparing the event to the active properties attached to the second document to determine if the event is a triggering event, for any other of the attached active properties; initiating the management function by the active property to which the event is the triggering event; and providing, by the initiated management function, (i) instructions to the document management system to control the manner the triggering event is applied to the first document or (ii) control of a sequence of instructions which are executed in response to the event.
Claim 12
Dependent Claim
27 words
The method according to claim 8 wherein the documents are managed based on their properties, including active properties, rather than a hierarchical path and a file name.
Claim 13
Dependent Claim
32 words
The method according to claim 8 wherein the second document has content, and the content of the second document is stored completely separate from the active properties attached to the second document.
References Cited (Backward Citations)
US4959769A
Cited
EP0185904A1
Cited
US4823303A
Cited
US5274757A
Cited
US5089956A
Cited
US4993880A
Cited
US5140676A
Cited
US5339392A
Cited
WO1991014222A1
Cited
US5132900A
Cited
US5517655A
Cited
US5404435A
Cited
US5806068A
Cited
US5357631A
Cited
US5715441A
Cited
US5809317A
Cited
US5649192A
Cited
US5812862A
Cited
US5546534A
Cited
US5499330A
Cited
US5905992A
Cited
US5613134A
Cited
US5621874A
Cited
US6012072A
Cited
US6012074A
Cited
US5528739A
Cited
US5600833A
Cited
US5544051A
Cited
US5812995A
Cited
US5634062A
Cited
US5473691A
Cited
US5584023A
Cited
US5445945A
Cited
US5913032A
Cited
US5727195A
Cited
US5659676A
Cited
US5752055A
Cited
US5950215A
Cited
US5982891A
Cited
US5835758A
Cited
US5664180A
Cited
US5872974A
Cited
US5729733A
Cited
US5802365A
Cited
US5740455A
Cited
US5761684A
Cited
US5708780A
Cited
US5664109A
Cited
US6014677A
Cited
US5860073A
Cited
US6199082B1
Cited
US6040832A
Cited
WO1997015018A1
Cited
US5805889A
Cited
CA2192237A1
Cited
US5754782A
Cited
US5713032A
Cited
US6023715A
Cited
US5890176A
Cited
US5933841A
Cited
US6507858B1
Cited
US6122649A
Cited
US5758154A
Cited
US5818447A
Cited
US5812773A
Cited
US5987480A
Cited
US5890171A
Cited
US5933811A
Cited
US5940830A
Cited
US5765176A
Cited
US5903902A
Cited
US5845067A
Cited
US5956737A
Cited
US5895477A
Cited
US5892909A
Cited
US6029182A
Cited
US5893908A
Cited
US5887133A
Cited
US6101510A
Cited
US6031989A
Cited
US5864850A
Cited
US5930801A
Cited
US5951300A
Cited
US6023714A
Cited
US6049799A
Cited
US6059838A
Cited
US6263492B1
Cited
US6108661A
Cited
US6182092B1
Cited
US6016492A
Cited
US6072481A
Cited
US6173297B1
Cited
US6009442A
Cited
US5991756A
Cited
US6112181A
Cited
US5999664A
Cited
US6003040A
Cited
US6038567A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2006-05-12 | 2006-11-11 | 2007-05-13 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2010-05-12 | 2010-11-11 | 2011-05-13 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2014-05-12 | 2014-11-11 | 2015-05-13 | $7700.00 | Window Closed / Lapsed |