Data processing: database and file management or data structures – Database design – Data structure types
Reexamination Certificate
1999-03-05
2002-12-24
Feild, Joseph H. (Department: 2176)
Data processing: database and file management or data structures
Database design
Data structure types
C707S793000, C707S793000, C345S215000
Reexamination Certificate
active
06499040
ABSTRACT:
BACKGROUND
Computer systems can store data and information in data files or data sets, often referred to as documents. Documents may be stored temporarily in the computer's memory (e.g. RAM, ROM) while the computer is operating, or may be stored more permanently on a physical medium (e.g. a hard disk or a floppy-disk) from which they may be retrieved for use with the computer. Documents can store a variety of data types including image files, presentations, text documents, databases, sound files, and spreadsheets.
Data in a document can be created, accessed, and modified by a software application. Different applications may be associated with different document types and may include software tools to create, edit, or modify data in the associated document type. For example, a user may create a text document with a word processing application, such as Microsoft Word®, and may use tools, such as those found in the Microsoft Word “File” pull-down menu (e.g. the “new,” “save,” “print” tools), to create, store, and print the text document. Similarly, a user may create a spreadsheet document with a spreadsheet application, such as Microsoft Excel®, and may use mathematical function tools to analyze data in the spreadsheet document and may use graphing tools to graphically present data contained in the spreadsheet document. The appearance and utility of the text and spreadsheet documents is determined by tools in the associated word processing and spreadsheet applications.
Generally, when a user works on a document using the tools of an associated application, only documents of the type associated with the chosen application may be created or modified. For example, when using a word processing program only text documents may be created and modified, and when using a spreadsheet program only spreadsheet documents may be worked on. Thus, application functionality may conform to a document-centric model. A document-centric model of applications suggests a user understanding that certain applications are limited to certain document types and vice-versa.
A document-centric application model can be restrictive to the user when the user wishes to perform multiple tasks that require multiple applications and, therefore, the use of multiple document types. For example, if a user is using one application to work on a document and perform a task, but wishes to perform a related but different task that requires different tools, the user must use tools from a second application. The use of a second application may entail exiting the current document, opening a second document of a type compatible with the second application and performing the desired task in the second document. The user may store the results of the two applications in two documents of different document types.
When documents are independently stored, working on one document in one application does not automatically recall the other related document. Rather, recalling the other related document requires using a different application to retrieve the related document. Thus, the user may need to manually maintain a cataloging system to remember that the two different documents contain related data and information.
Document embedding may be used as an alternative to separate storage of related documents. Embedding may be supported by an operating system or a software application. For example, in a Microsoft Windows 95/98™ implementation, object linking and embedding (OLE) technology is often used to enable the importation and embedding of a secondary document into a primary document. Nevertheless, this requires a user using a primary program first to correctly determine the secondary document type to be imported, second to open such a document, third to insert into the secondary document the data he wants to work on, fourth to use the secondary program to edit the secondary document, and fifth to import the second document into the primary document. This is a long and cumbersome process. Thus, for example, a user may use a word processing application to create a text document and a spreadsheet application to create or modify a spreadsheet document that may be imported into and stored in a text document, but the processing is not user-friendly.
When a user uses a primary software application to work on a document of a particular type associated with the software application, the user may create an object embedded within the document, which may be edited with the tools of a secondary application that is not associated with the particular document type. An object in an application environment may be a discrete element of a document, for example, a spreadsheet, a graphic, or a piece of text. Graphical space is allocated in the document for the object, and the object is stored as part of the document. A user's selection of an object contained within a document may activate a secondary application to edit the data contained in the object. For example, when using Microsoft Word® to work on a text document, a user may create a spreadsheet object in the text document and edit the spreadsheet with the Microsoft Excel® tools. Selection of the spreadsheet object in the Words® document may activate the Excels® tools to edit the spreadsheet. When objects conforming to one document type are embedded in a document of a different type, however, only one document type is created. The single document stores the results of the multiple different applications that conform to different document types. As a consequence, in the example described above, the text and the spreadsheet work would be stored in a text document because the user had been using a word processing program as the primary application. In a group work environment in which multiple users need access to multiple documents on a computer, storing the results of many different tasks in a single document may restrict access and productivity. It may have the effect of making fewer documents simultaneously available to the users, or of forcing users with expertise and experience in using different applications to all use the same document with their applications.
The functional relationship between applications and document types and the document-centric application model is further demonstrated by the way applications and document types are used by standard operating systems (e.g. Microsoft NT, Microsoft Windows). An application is opened, i.e. initialized and displayed on a computer display so that the user may begin working with the application, by typing an instruction at a command line of the operating system or by clicking with a mouse on an icon representing the application. When the application is opened it may display a window, in which a document may be displayed and worked on with the tools of the application. Normally when an application is opened it automatically displays in a window of the computer display a document of a type that is associated with the application. The document may be one that was previously created and then stored on the computer or it may be a new, blank document that the user may modify with the application's software tools and then save. Thus, opening an application with the operating system may automatically open a document of the type associated with the application.
Similarly, opening a document with operation system software functionality, for example by clicking on the document's icon, may automatically trigger the opening of an application that is functionally associated with the document type being opened. Thus, the document type and the associated software application are fundamentally linked.
SUMMARY
Software tools can be collected into task-oriented functional groups known as workbenchs. Workbenches may be created, for example, to perform the different tasks of editing text, designing parts, assembling parts into a machine or device, and analyzing the stresses on a part of a machine or device. Moreover, workbenches may be functionally associated with, and used to work on, particular document types. A document type may be associat
Nicolas Alain
Perroux Francois
Vu Duy-Minh
Clifford Chance (US) LLP
Dassault Systemes
Feild Joseph H.
Mahon James V.
LandOfFree
Document and task coordination system for a computer does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Document and task coordination system for a computer, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Document and task coordination system for a computer will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-2953999