The application server 1 further connects to the database 2 via a connection 5. The database 2 is configured for storing different kinds of data, such as legal documents, terms and conditions of the legal documents, definitions of the terms and conditions, and so on. The connection 5 is a database connectivity, such as an open database connectivity (ODBC) or a Java database connectivity (JDBC).
The application server 1 is configured for managing the legal documents stored in the database 2, such as managing classification, edition, and creation of the legal documents. In the preferred embodiment, the legal documents are contracts, in other embodiments, the legal documents may be agreements, indictments, and responses to office actions, etc.
The document organizing module 10 is configured for constructing and applying a classification system for the legal documents by classifying and grouping the legal documents into classes in the classification system, and then further classifying and grouping the legal documents in each of the classes into subclasses (as shown in
The document organizing module 10 is further configured for organizing existed legal documents (if any) into the class and the subclass in the classification system. The existed legal documents may be finalized legal documents having been signed/approved by managers of the enterprise and the contracting party, may be the legal documents that are ready for review or approved, and may be other kinds of legal documents stored in the database 2.
The option extracting module 11 is configured for extracting terms and conditions entries from the legal documents (i.e., the finalized legal documents), and for setting extracted terms and conditions entries as class entry options and subclass entry options correspondingly. Each of the class entry options is applicable/insertable to the legal documents in a same class regardless of the subclass of the legal documents. Each of the subclasses entry options is applicable/insertable to the legal documents in a same subclass (described in detail below in relation to
The classification selection module 12 is configured for selecting a class and a subclass of a new legal document. The subclass option manager 13 is configured for displaying all of the subclass entry options applicable to the subclass of the new document, and for selecting one or more subclass entry options from the displayed subclass entry options for the new legal document.
The class option manager 14 is configured for displaying all of the class entry options applicable to the class of the new document, and for selecting one or more class entry options from the displayed class entry options for the new legal document.
The new entry manager 15 is configured for defining/creating new entries for the new legal document. The new entry manager 15 is also configured for defining attributes of the new entries correspondingly. The new entries are neither subsets of the class entry options, nor subsets of the subclass entry options. The attributes may provide a range of data values such as dates or numbers selectable for the new entries.
The new entry manager 15 is further configured for inserting the new entries into the class entry options or the subclass entry options so as to expand the class entry options and the subclass entry options.
The creating module 16 is configured for creating the new legal document by integrating the selected subclass entry options, the selected class entry options, and the new entries into the new legal document.
The creating module 16 is also configured for exporting the created legal document, and submitting the created legal document for review and approval by the managers of the enterprise and the contracting party. The created legal document may be exported to a display, a memory (i.e., the application server 1, the database 2, and the clients 3), mailboxes or somewhere else as a PDF™ file, a WORD™ file, a TIFF file or other kinds of files. The creating module 16 is further configured for storing corresponding data into the database 2, such as the created legal document, the new entries, the attributes of the new entries, exported files, and so on.
Each class has a plurality of class entry options that are applicable/insertable to the legal documents in the same class regardless of the subclass of the legal documents. For example, the class 60 has class entry options 600. One of the class entry options 600 may be described as: all payments shall be made in U.S. dollars and are fixed amounts regardless of exchange rate fluctuations. The class entry option is applicable/insertable to a legal document 612, a legal document 613, a legal document 622, and a legal document 623.
Each subclass has a plurality of subclass entry options that are applicable/insertable to the legal documents of the same subclass, such as the subclass 610 has subclass entry options 611, and the subclass 620 has subclass entry options 621. For example, one of the subclass entry options 611 may be described as: all fees due and prices are net amounts due to A company, exclusive of all taxes, customs, duties, or other fees that may be governmentally imposed. The subclass entry option is just applicable/insertable to the legal document 612 and the legal document 613, but not applicable to the legal document 622 and the legal document 623.
The class entry options (i.e., the class entry options 600) and the subclass entry options (i.e., the subclass entry options 611 and the subclass entry options 621) are extracted from the legal documents in the database 2 by the option extracting module 11.
In step S12, the option extracting module 11 extracts the terms and conditions entries from the legal documents (i.e., the finalized legal documents), and sets the extracted terms and conditions entries as the class entry options and the subclass entry options correspondingly. Each of the class entry options is applicable/insertable to the legal documents in the same class regardless of the subclass of the legal documents. Each of the subclasses entry options is applicable/insertable to the legal documents of the same subclass (described in detail below in relation to
In step S14, the class and the subclass of the new legal document are assigned/selected through the classification selection module 12. In step S16, the subclass option manager 13 displays all of the subclass entry options applicable to the subclass of the new document, and each of the displayed subclass entry options may be selected as the selected subclass entry options for the new legal document through the subclass option manager 13.
In step S18, the class option manager 14 displays all of the class entry options applicable to the class of the new document, and each of the displayed class entry options may be selected as the selected class entry options for the new legal document through the class option manager 14.
In step S20, the new entry manager 15 determines whether the new entries need to be defined/created for the new legal document. If the new entries need to be defined/created, in step S22, the new entry manager 15 defines/created one or more new entries and their attributes correspondingly for the new legal document. Afterwards, the new entry manager 15 may insert the new entries into the class entry options or the subclass entry options, so as to expand the class entry options and the subclass entry options. Otherwise, if the new entries do not need to be defined, the procedure directly goes to step S24.
In step S24, the creating module 16 creates the new legal document by integrating the selected subclass entry options, the selected class entry options, and the new entries into the new legal document.
In step S26, the creating module 16 exports the created legal document and submits the created legal document for review and approval by the managers of the enterprise and the contracting party. The created legal document may be exported as the PDF™ file, the WORD™ file, the TIFF file or other kinds of files.
In step S28, the creating module 16 stores corresponding data into the database 2, such as the created legal document, the defined entries, the attributes of the defined entries, exported files, and so on.
It should be emphasized that the above-described embodiments, particularly, any “preferred” embodiments, are merely possible examples of implementations, merely set forth for a clear understanding of the principles of the invention. Many variations and modifications may be made to the above-described preferred embodiment(s) without departing substantially from the spirit and principles of the invention. All such modifications and variations are intended to be included herein within the scope of this disclosure and the above-described preferred embodiment(s) and protected by the following claims.
Number | Date | Country | Kind |
---|---|---|---|
200610200790.3 | Aug 2006 | CN | national |