EP1386262A4

EP1386262A4 - Internet-based patent and trademark application management system

Info

Publication number: EP1386262A4
Application number: EP02723671A
Authority: EP
Inventors: Steven W Lundberg
Original assignee: Schwegman Lundberg Woessner and Kluth PA
Current assignee: CPA SOFTWARE Ltd
Priority date: 2001-03-29
Filing date: 2002-03-28
Publication date: 2007-12-19
Also published as: AU2002254440B2; WO2002080039A1; CA2444437A1; EP1386262A1

Abstract

A system for managing patent and trademark application data via the Internet, comprising matter, task, and security modules. The matter module is operable to manage data such as docketing data relating to patent matters (303), the tasks module manage tasks related to patenting matters (301) and the security module restricts access to tasks and patenting matters to selected system users.

Description

Internet-Based Patent and Trademark Application Management System

Field of the Invention

The invention relates generally to managing patent and trademark applications, and more specifically to an internet-based system for management of patent and trademark applications.

Claim of Priority This application claims priority from and is related to the provisional application "Internet-Based Patent and Trademark Application Management System", Steven W. Lundberg, Inventor, serial number 60/280,386, filed March 29, 2001, and from the application "Internet-Based Patent and Trademark Application Management System", Steven W. Lundberg, Inventor, serial number 09/872,701, filed June 1, 2001.

Background of the Invention Patent agents and attorneys that specialize in patent prosecution typically draft dozens of patent applications per year, and are engaged in prosecution of many more. Each of these must be carefully tracked by the patent attorney or legal assistant, so that important status information such as potential bar dates, deadlines for response to office action amendments and responses, and other data are not overlooked. Management of this data has historically been managed by inclusion of each item on a docket that is tracked on paper docketing calendars, or more recently using commercially available electronic docketing software that serves the same purpose as a calendar.

But, when multiple attorneys are involved in docketed matters for multiple clients, when complex client or legal rules must be applied, or when corporate clients wish to participate in the docket management of matters on a law firm or attorney's docket, docket management using paper calendars and simple docketing software can become labor-intensive and subject to errors. It is not uncommon for paper checklists of application drafting guidelines from clients, e-mail messages relating to a case, and multiple copies of docketing information to be kept separately for each patent or trademark application managed by an attorney or firm. Coordination and communication of this information is not a trivial task, and requires a significant amount of time and attention from the typical patent attorney or agent. A system for managing patent and trademark applications and information related to these applications is desired, as well as a system to facilitate communication and coordination of this application-related information.

Summary of the Invention A system for managing patent application data via the Internet, comprising matter, task, and security modules. The matter module is operable to manage data such as docketing data relating to patent matters, the tasks module is operable to manage tasks related to each matter managed by the matter module, and the security module is operable to restrict access to task and matter data management to selected system users. The system is implemented in some embodiments as a World Wide Web site on the Internet, which in further embodiments comprises various components such as an application server, a Java server, and a database.

Brief Description of the Figures Figure 1 shows a web page from an Internet-based patent and trademark management system, consistent with an embodiment of the present invention.

Figure 2 shows a messages web page, consistent with an embodiment of the present invention.

Figure 3 shows a new tasks web page, consistent with an embodiment of the present invention.

Figure 4 shows a new matters web page, consistent with an embodiment of the present invention.

Figure 5 shows an organization view web page, consistent with an embodiment of the present invention. Figure 6 shows a templates web page, consistent with an embodiment of the present invention. Figure 7 shows an activities web page, consistent with an embodiment of the present invention.

Figure 8 shows a user management web page, consistent with an embodiment of the present invention. Figure 9 shows a message list web page, consistent with an embodiment of the present invention.

Figure 10 shows an activities web page, consistent with an embodiment of the present invention.

Figure 11 shows an entities view web page for a selected matter, consistent with an embodiment of the present invention.

Figure 12 shows an associated parties web page for a selected matter, consistent with an embodiment of the present invention.

Figure 13 shows an IDS documents web page of data associated with a selected matter, consistent with an embodiment of the present invention. Detailed Description

In the following detailed description of sample embodiments of the invention, reference is made to the accompanying drawings which form a part hereof, and in which is shown by way of illustration specific sample embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that other embodiments may be utilized and that logical, mechanical, electrical, and other changes may be made without departing from the spirit or scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the invention is defined only by the appended claims.

The present invention provides a system for managing a docket of patent or trademark-related applications, and for coordinating and communicating such information among multiple parties involved in the patent or trademark application process. The invention comprises in one embodiment a system for managing patent application data via the Internet, and comprises matter, task, and security modules. The matter module is operable to manage data such as docketing data relating to patent matters, the tasks module is operable to manage tasks related to each matter managed by the matter module, and the security module is operable to restrict access to task and matter data management to selected system users. The system is implemented in some embodiments as a World Wide Web site on the Internet, which in further embodiments comprises various components such as an application server, a Java server, and a database.

Figure 1 illustrates one embodiment of a front World Wide Web (WWW) web page of a system consistent with the present invention. A user will log in to the example system shown here by entering a user name at 101, and a password at 102. If a prospective user does not have an account but wishes to create one, the user may do so by selecting to register at 103.

Upon logging in, the user is presented with a home screen presenting the user with various options. For example, the user may be presented with or may select to view his new messages, as is shown generally in Figure 2. Each message as shown in Figure 2 includes a message type represented by an icon at

201, an indication of the number of attachments to the message at 202, a matter title indicating a matter related to the message at 203, an indication of who the message is from at 204, a message title at 205, and the time and date the message was received at 206. The user may select a message to view the message, may select a user to send a reply message to the user, may select the message title to display the message, may select the number of attachments indicator to view the attachments, or may take other actions in response to the mew messages screen shown in Figure 2.

The user may also be presented with or select to view a new tasks screen as shown in Figure 3, which illustrates new tasks associated with the particular logged in user. Each task has associated data that is displayed in the new tasks view, including the task name at 301, the type of task at 302, the title of the matter the task is related to at 303, the status of the task at 304, and a date associated with the task if appropriate at 305. Tasks may be flagged as shown at 306, so that a user may elect to view only flagged tasks or only new and flagged tasks, thereby viewing a subset of tasks that are of higher importance to the user. In some embodiments of the invention, the user will be able to generate similar task lists, where the lists are limited to or sorted by client, by date due, by date completed, by status, by type, or by other similar criteria.

Users may also elect from the home page of the example embodiment of the invention described here to view new matters, as shown in Figure 4. The title of each new matter is shown at 401, and the type of matter is shown at 402. The matter status is shown at 403, and additional matter material may be shown in further embodiments of the invention. As with tasks, users may also view in further embodiments of the invention other matter summary views similar to the one shown in Figure 4, such as a view of all matters relating to a particular client, all matters with tasks due during a certain time period, all matters with a certain matter status, or any other such customized matter view.

Matters and users maybe associated in some embodiments of the invention with organizations, such as with particular client companies or particular law firms. These organizations are managed by the example embodiment of the system discussed here as is shown in Figure 5. Each organization is identified by name as shown at 501, and has a type associated with it to identify the nature and role of the organization. The contact or agent for each organization is shown at 503, along with a contact phone number 504 and e-mail address 505 for each contact. Organization data may in some embodiments of the invention be edited or added only by system administrators, and in further embodiments select members who are part of an organization will be given authority to edit existing organization data.

Tasks may be created for matters by manually entering tasks, or in some embodiments of the invention may further be created automatically via templates or other predefined task generation utilities. Figure 6 illustrates a view of templates available for application to matters in one embodiment of the invention. The template name is shown at 601, and the organization associated with the template is shown at 602. The last modification of the template is reflected at 603 and 604, where the modifying user's identity and the date and time of the last modification are shown. The user has the option to delete existing templates as shown at 606, to create new templates, or to edit existing templates as shown at 605.

Templates include such items as creating checklists to ensure proper drafting criteria are met, creating tasks with associated dates such as deadlines for responses, and other similar tasks that are common to many applications and have predictable elements. For example, a client may request that a certain checklist of drafting criteria be completed before each filing, and the checklist may be implemented as a task associated with each of the client's matters via use of a template. Also, creation of docket dates and tasks associated with those dates in a system such as the present invention may be automatically calculated and created by a template, ensuring proper application of applicable rules. Many other such examples of tasks common to many applications with predictable elements exist, and all are within the scope of the template function as implemented in the example of the present invention presented here. Figure 7 illustrates the activities that are associated with an amendment and response to a typical United States Patent and Trademark Office issued Office Action. The typical shortened statutory three-month date for response is shown as an activity item at 701, and is followed by subsequent deadlines for taking each allowable extension of time past that date. These items will then automatically be added to the task list of each matter to which the template is applied, creating appropriate task entries for that matter.

Figure 8 illustrates a user management view of all users that have registered with the embodiment of the present invention described here. The user name or alias is shown at 801, the entity type is shown at 802, the full name of the entity is shown at 803, and contact information including phone and e- mail are shown at 804 and 805. The user management screen shown here allows a system administrator to delete users at 806, and indicates the source of the user at 807.

An example message list is shown in Figure 9, which illustrates a variety of messages for a particular user. The subject or name of the message is shown at 901, and the title of the matter to which the message pertains is shown at 902. The sender of the message is shown at 903, and the date the message was received is shown at 904. At 905, the user is shown a Delete object that may be selected to delete the associated message. The type of message is indicated at 906, and the number of attachments to the message are shown at 907. Note that in this example, several automatically generated messages such as reports of actions completed or docket dates are shown in the message box.

Figure 10 shows a view of tasks or activities associated with a particular matter. The activity is shown at 1001, and is selectable by the user. Selecting the activity by name will open the detail list for that particular activity. Any restrictions on access to the activity are shown at 1002, and the status of the activity is shown at 1003. Relevant dates for the activity, which may vary in type depending on the activity status, are shown at 1004. At 1005, the user may edit or delete listed activities. Because the matter shown here is an issued patent, the patent number, issue date, and other information are known and are displayed at 1006 in a matter page header. Figure 11 shows an entities view of a particular selected matter. The parties in interest in this example comprise Intel Corp., as shown at 1101. The law firm associated with the matter is shown at 1102.

The embodiment of the invention shown here also shows additional associated parties, such as corporate counsel responsible for overseeing the matter, the attorney and paralegals involved with the case, and other users or entities involved with the matter. This is shown in Figure 12, where the associated users are listed at 1201. The role each user has in the matter is shown at 1202, and the status of the user is shown at 1203. Note that a user may be invited to join a matter, but is not listed as active in this embodiment of the invention until the user takes affirmative steps to join in a matter.

Figure 13 is an IDS documents view of data associated with a matter, and shows documents that must be disclosed in an Information Disclosure Statement or IDS to the USPTO. Because no documents have been associated with this example matter, none are illustrated here. For patent documents that must be cited, the patent number, issue date, country of issue, name, and translation are shown at 1301. For documents that are not patent documents but are other publications, the author's name, document title, citation, referred pages, and publication date are recorded and are shown at 1302.

The example embodiment of the present invention explained above and in the figures is further described in the following use case, which describes ways in which the functionality of the present invention may be used by various users and organizations to facilitate more efficient management of a patent or trademark docket.

The use case system will be used in a decentralized way as a web-based application where multiple law-firms and corporations, as well independent lawyers and consultants, can all come together to collaborate on patents in which they are involved.

The service provider will deal with various law-firms and corporations to create a community where patents filing process can be vastly streamlined. All such law firms and corporations (referred to as 'Business entities') will be dealing directly with the service provider (sending all the materials to be scanned, etc. to them). There will be an administrator at the service provider, who will be to verify business entities details and assign them a account number (provided by our system).

The business entities will assign an account administrator who will be responsible for managing who participates on behalf of the entity in the patent process. The business entity does this by sending an invitation to a prospective participant with an access code that allows him to access information relating to the business entity. In this process, the administrator may also authorize such participant to charge matter and other related costs to specified account number. Membership in groups is regulated such that anyone can create a user account and associated login. This person can then create a new matter to be managed via the service provider's web site, and can specify other participants for that matter. The service provider then sends e-mail to these invited participants with an invitation to join and a password or secure link. An invitee can then log in, and select to access the matter from his matters list, and supply a password received in the e-mail to associate the new matter with his particular user account and matters list.

One example involves an attorney who logs on, opens a new matter, then sends invitations to inventor, paralegals, etc. For each one of these, he provides an email address to which an invitation is sent, and a password with which the invited users can access the matter. Inventor gets email with a site URL, matter number and password. When he clicks it, he is required to sign in. When he gets to my matters, he presses 'Access New Matter' button, which asks him for matter number and password. He fills in this information from what he received by email. This matter is now made available on his matter list. In a second example scenario, Thomas Edison signs up with the service, and creates a new matter. He fills in notes regarding the invention and other information, and finally decides on an attorney or law firm to work with. He sends invitations to selected attorneys there. The attorney accepts the invitation, and then sends out additional invitations to paralegals and other associated users.

In a third scenario, Idle Joe signs up, and goes to 'My matters'. He sees nothing there. He cannot access any existing matters to which he has not been invited. He opens a new matter, and plays around with the functions provided by the website. He realizes there's nothing at the service provider for him, then logs off and goes on to cause trouble elsewhere. New users who do not have any associated matters and are not members of any group will periodically have their accounts deactivated to ensure smooth operation of the service provider system. This use case example further provides billing functionality. The service provider provides the option of billing for each open matter, and allows creating billing entries for services associated with a matter, such as docketing, prior art searches, drafting, drawing preparation, or other related services or products. The service provider's system is configured such that the entities that interact with the system are categorized into individuals, businesses, clients, law firms, the USPTO, and the service provider, as explained in greater detail below. Individuals includes ordinary individual users who could be attorneys working for a law-firm, independent attorneys, employees of corporations, independent consultants, paralegals, etc. In short, it includes any person who is involved or expected to be involved in the managing of a matter through to completion. Business entities allows several individuals to participate in the process under the same umbrella. Two types of Businesses are recognized: Client, and Law Firm businesses. A Client participates as a requester of patent services and law firm acts as provider of such services.

Clients are the entities that are seeking patent services. The client can be a corporation, university, or other entity, and essentially defines a grouping of individuals who can share information that is common to them by virtue of their association with the client entity. For example, a corporation will have a preferred set of law firms, a preferred set of foreign associates, and other preferences and relationships. An account administrator for the corporation can assign privileges to different people for different pieces of information associated with the Corporation.

A law firm is a grouping of individuals, including lawyers, paralegals, and other individuals who can share information common to them by virtue of their association with a legal services provider. For example, lists of client companies and information about individuals within them is information may be accessible to various degrees throughout a law firm. A law firm administrator can invite people to be members of the law firm group and give privileges to them for access to various information.

Still other entities may be created and invited to participate in a matter to facilitate patent legal services. The United States Patent and Trademark Office and select examiners may be given certain access to relevant matters, outside service providers such as scanning service providers may be given access to certain data, and the service provider operating the website may have varying degrees of access to data.

The service provider will desirably manage the various accounts and grouping of entities, and provide customer support for the various services and functions of the website. The service provider will not only have access to certain data, but will be able to determine billing for services provided via the website, account information of the member entities, and will have account management capability. The various matters managed via the service provider include a client name, a client contact name, a law firm or service provider name, a law firm matter number, a client reference number, a unique reference number provided by the service provider, a foreign associate for various corresponding foreign filings, and identification of the various law firm members assigned to the matter. Law firm roles include billing attorney, working attorney, signature attorney, paralegal, docketing specialist, IDS specialist, and various secretaries that may be associated with the other law firm members.

Individuals can have one or more roles in a client organization, and may belong to several organizations or groups via a single user name or login ID. It is anticipated that a typical individual will serve various roles in a number of different matters, and will have access via a single login or user ED to information related to each of the various matters with which he is associated.

Business entities may further have approved lists of law firms, foreign associates, and other approved entities. Individual attorneys may also be approved, and lists of individuals working with the business entity matters within other entities may be used. For this use case example, assume an administrator representing a business or corporate entity desires to use the service provider to manage patent- related legal services. The administrator creates a new account within which matters created by its approved members can be created, managed, and billed. The business account manager can add new law firms, attorneys, foreign associates, business representatives, inventors, and other members. The business account administrator can further deactivate or remove various members from the business account or matters owned by the business account, and can generate reports and retrieve information relating to the various matters and entity involvement in the matters owned by the business account. A law firm entity will have the ability to create new client records, including invitation to business entities to join matters or create accounts. The law firm will also have the ability to enter billing and fee data, including calculation of fees for particular services or hourly rates, and entry of fee codes and billing descriptions. The law firm further can invite new users to be members of the law firm, assign users to roles within specific matters, and manage the role of various users within the law firm and within matters with which the law firm is associated. Individuals will be able to join existing business groups , law firms, or other entities with the approval of the entity. Association with an entity may be ad the individual's request, or by invitation from the entity. Each individual, whether a member of another entity or not, will be able to create matters, invite others to participate in the matters, receive and send e-mail regarding the matters, and view the status of his matters. The individual can create or update notes associated with his matters, check outstanding actions or dates for his matters, generate matter reports, print documents, and browse other information relating to his matters. This information includes viewing invited and associated entities for each matter, viewing matter task information, viewing billing or invoice information, viewing related case information, and viewing docketing information.

The individual will also be able to copy, delete, remove, archive, or verify matters, and will be able to search for matter information via law firm docket number, client name, serial number, prior docket number, related case number, inventor name, and other information. The matters will have a notes or discussion area for maintaining matter-related notes, and will have data records enabling automated e-mail reminders of actions due and case status.

Trademarks may be managed as matters, and will have information including the actual trademark sought, action data, country-related data, conflict opposition data, auxiliary files or tables, reports, recurring date menus, utility menus, agent details, and country details. Managed patents will similarly have record space configured for storing invention or disclosure data, country application data, actions due or docketing data, auxiliary files and tables, reports, maintenance fee data, utility menus, actions menus, and cost tracking and budgeting data.

Information disclosure statement (IDS) records are associated with various other matters such as filed or unfiled patent applications, and are managed via functions that include the ability to copy documents to or from other matters to which the user has access, to delete or add documents associated with a particular matter, to combine references cited from various matters, to scan or view images of various references, to view US patent documents by patent number, title, or other identifier, to view foreign patent documents, to view non-patent documents, or to view all associated documents. Documents associated with an IDS may be marked as relevant or not relevant, or may be unmarked. The documents associated with an IDS for a particular matter may therefore be viewed, printed, merged, sorted, or otherwise managed based on whether they are marked relevant, marked not relevant, or unmarked.

Marked documents may be merged into forms such as a standard form 1449 for citing relevant known art to the USPTO. Documents that have been cited are marked separately from those that have been marked but not yet sent, to enable accurate tracking and determination of which documents have been cited and which documents are yet to be cited.

Each EDS reference document will have associated records that enable accurate identification of the document, such as US patent number, foreign patent number, issue date, priority date, inventor names or author names, publication name or other citation of non-patent publications, and title. It is desired that the records associated with each EDS reference be sufficient to meet the formal reporting requirements in citing the document to the USPTO via a form 1449 or other appropriate method.

Some members, such as scanning centers, may have very limited capabilities relative to a typical member or entity. A scanning center, for example, may be limited to uploading scanned data to be associated with a particular matter, entering billing or invoice charges and descriptions, and generating reports of uploaded data and billing charges.

Finally, in a use case such as that described here, a business entity or other client can easily change law firms, attorneys, or the role of other members in various matters managed via the service provider with minimal effort or expense.

Although specific embodiments of the present invention have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that any arrangement which is calculated to achieve the same purpose may be substituted for the specific embodiments shown. This application is intended to cover any adaptations or variations of the invention. It is intended that this invention be limited only by the claims, and the full scope of equivalents thereof.

Claims

1. A system for managing patent application data via the Internet, comprising: a matter module, the matter module operable to manage data relating to patent matters, the managed data comprising docketing data; > a tasks module, the tasks module operable to manage tasks related to each matter managed by the matter module, the tasks comprising docketing tasks; and a security module, the security module operable to restrict access to task and matter data management to selected system users.

2. The system of claim 1, wherein managing data relating to patent matters comprises creating new patent matter data.

3. The system of claim 1, wherein managing data relating to patent matters comprises retrieving patent matter data.

4. The system of claim 1, wherein managing data relating to patent matters comprises editing patent matter data.

5. The system of claim 1 , wherein managing tasks related to managed matters comprises automated creation of tasks.

6. The system of claim 1, wherein managing tasks related to managed matters comprises user creation of tasks.

7. The system of claim 1, wherein managing tasks related to managed matters comprises retrieving tasks for a particular matter.

8. The system of claim 1, wherein managing tasks related to managed matters comprises retrieving tasks for a particular user.

9. The system of claim 1, wherein managing tasks related to managed matters comprises retrieving tasks for a particular organization.

10. The system of claim 1, wherein managing tasks related to managed matters comprises editing tasks.

11. The system of claim 1, wherein managing tasks related to managed matters comprises viewing a calendar of tasks.

12. The system of claim 1 , wherein the security module requires a user to log in before granting access to matter or task data, and wherein the security module further grants the logged in user access only to those matters and tasks to which the user has been granted access.

13. The system of claim 12, wherein users are granted access to matters and tasks by the creator of each matter or task.

14. The system of claim 1, further comprising a messaging module operable to provide messaging to users of the system.

15. The system of claim 14, wherein the messaging comprises automated messages to particular users, the messages relating to matters and tasks associated with the particular users.

16. The system of claim 14, wherein the messaging comprises a user sending messages to other users.

17. The system of claim 14, wherein the messaging module is further operable to send electronic mail (e-mail) to users, the e-mail comprising information relating to the user's role in managed tasks and matters.

18. The system of claim 1, wherein the system comprises a World-Wide Web site (Internet web site).

19. The system of claim 18, wherein the web site comprises application server pages.

20. The system of claim 18, wherein the web site comprises Java server pages.

21. The system of claim 18, wherein the system further comprises a database for managing patent application data.

22. The system of claim 21, wherein the system comprises multiple databases and is able to exchange data between the multiple databases.

23. The system of claim 22, the system further operable to synchronize data in the databases by publishing changes to one database to other associated databases within the system.

24. The system of claim 1, wherein multiple matters may be associated with each other, such that data relating to one of the multiple matters will be visible when viewing data relating to another of the multiple matters.

25. A machine-readable medium with instructions stored thereon, the instructions when executed operable to cause a computerized system to manage patent application data via the Internet by: managing data relating to patent matters via a matter module, the managed data comprising docketing data; managing tasks related to each matter managed by the matter module via a task module, the tasks comprising docketing tasks; and restricting access to task and matter data management to selected system users via a security module.

26. The machine-readable medium of claim 25, wherein managing data relating to patent matters comprises creating new patent matter data.

27. The machine-readable medium of claim 25, wherein managing data relating to patent matters comprises retrieving patent matter data.

28. The machine-readable medium of claim 25, wherein managing data relating to patent matters comprises editing patent matter data.

29. The machine-readable medium of claim 25, wherein managing tasks related to managed matters comprises automated creation of tasks.

30. The machine-readable medium of claim 25, wherein managing tasks related to managed matters comprises user creation of tasks.

31. The machine-readable medium of claim 25, wherein managing tasks related to managed matters comprises retrieving tasks for a particular matter.

32. The machine-readable medium of claim 25, wherein managing tasks related to managed matters comprises retrieving tasks for a particular user.

33. The machine-readable medium of claim 25, wherein managing tasks related to managed matters comprises retrieving tasks for a particular organization.

34. The machine-readable medium of claim 25, wherein managing tasks related to managed matters comprises editing tasks.

35. The machine-readable medium of claim 25, wherein managing tasks related to managed matters comprises viewing a calendar of tasks.

36. The machine-readable medium of claim 25, wherein the security module requires a user to log in before granting access to matter or task data, and wherein the security module further grants the logged in user access only to those matters and tasks to wliich the user has been granted access.

37. The machine-readable medium of claim 36, wherein users are granted access to matters and tasks by the creator of each matter or task.

38. The machine-readable medium of claim 25, further comprising a messaging module operable to provide messaging to users of the system. .

39. The machine-readable medium of claim 38, wherein the messaging comprises automated messages to particular users, the messages relating to matters and tasks associated with the particular users.

40. The machine-readable medium of claim 38, wherein the messaging comprises a user sending messages to other users.

41. The machine-readable medium of claim 38, wherein the messaging module is further operable to send electronic mail (e-mail) to users, the e-mail comprising information relating to the user's role in managed tasks and matters.

42. The machine-readable medium of claim 25, wherein the system comprises a World-Wide Web site (Internet web site).

43. The machine-readable medium of claim 42, wherein the web site comprises application server pages.

44. The machine-readable medium of claim 42, wherein the web site comprises Java server pages.

45. The machine-readable medium of claim 42, wherein the system further comprises a database for managing patent application data.

46. The machine-readable medium of claim 45, wherein the system comprises multiple databases and is able to exchange data between the multiple databases.

47. The machine-readable medium of claim 46, the instructions further operable to synchronize data in the databases by publishing changes to one database to other associated databases within the system.

48. The machine-readable medium of claim 25, wherein multiple matters may be associated with each other, such that data relating to one of the multiple matters will be visible when viewing data relating to another of the multiple matters.

49. A system for managing trademark application data via the Internet, comprising: a matter module, the matter module operable to manage data relating to trademark matters, the managed data comprising docketing data; a tasks module, the tasks module operable to manage tasks related to each matter managed by the matter module, the tasks comprising docketing tasks; and a security module, the security module operable to restrict access to task and matter data management to selected system users.

50. The system of claim 49, wherein managing data relating to trademark matters comprises creating new trademark matter data.

51. The system of claim 49, wherein managing data relating to trademark matters comprises retrieving trademark matter data.

52. The system of claim 49, wherein managing data relating to trademark matters comprises editing trademark matter data.

53. The system of claim 49, wherein managing tasks related to managed matters comprises automated creation of tasks.

54. The system of claim 49, wherein managing tasks related to managed matters comprises user creation of tasks.

55. The system of claim 49, wherein managing tasks related to managed matters comprises retrieving tasks for a particular matter.

56. The system of claim 49, wherein managing tasks related to managed matters comprises retrieving tasks for a particular user.

57. The system of claim 49, wherein managing tasks related to managed matters comprises retrieving tasks for a particular organization.

58. The system of claim 49, wherein managing tasks related to managed matters comprises editing tasks.

59. The system of claim 49, wherein managing tasks related to managed matters comprises viewing a calendar of tasks.

60. The system of claim 49, wherein the security module requires a user to log in before granting access to matter or task data, and wherem the security module further grants the logged in user access only to those matters and tasks to which the user has been granted access.

61. The system of claim 60, wherein users are granted access to matters and tasks by the creator of each matter or task.

62. The system of claim 49, further comprising a messaging module operable to provide messaging to users of the system.

63. The system of claim 62, wherein the messaging comprises automated messages to particular users, the messages relating to matters and tasks associated with the particular users.

64. The system of claim 62, wherein the messaging comprises a user sending messages to other users.

65. The system of claim 62, wherein the messaging module is further operable to send electronic mail (e-mail) to users, the e-mail comprising information relating to the user's role in managed tasks and matters.

66. The system of claim 49, wherein the system comprises a World-Wide Web site (Internet web site).

67. The system of claim 66, wherein the web site comprises application server pages.

68. The system of claim 66, wherein the web site comprises Java server pages.

69. The system of claim 66, wherein the system further comprises a database for managing trademark application data.

70. The system of claim 69, wherein the system comprises multiple databases and is able to exchange data between the multiple databases.

71. The system of claim 70, the system further operable to synchronize data in the databases by publishing changes to one database to other associated databases within the system.

72. The system of claim 49, wherein multiple matters may be associated with each other, such that data relating to one of the multiple matters will be visible when viewing data relating to another of the multiple matters.

73. A machine-readable medium with instructions stored thereon, the instructions when executed operable to cause a computerized system to manage trademark application data via the Internet by: managing data relating to trademark matters via a matter module, the managed data comprising docketing data; managing tasks related to each matter managed by the matter module via a task module, the tasks comprising docketing tasks; and restricting access to task and matter data management to selected system users via a security module.

74. The machine-readable medium of claim 73, wherein managing data relating to trademark matters comprises creating new trademark matter data.

75. The machine-readable medium of claim 73, wherein managing data relating to trademark matters comprises retrieving trademark matter data.

76. The machine-readable medium of claim 73, wherein managing data relating to trademark matters comprises editing trademark matter data.

77. The machine-readable medium of claim 73, wherein managing tasks related to managed matters comprises automated creation of tasks.

78. The machine-readable medium of claim 73, wherein managing tasks related to managed matters comprises user creation of tasks.

79. The machine-readable medium of claim 73, wherein managing tasks related to managed matters comprises retrieving tasks for a particular matter.

80. The machine-readable medium of claim 73, wherein managing tasks related to managed matters comprises retrieving tasks for a particular user.

81. The machine-readable medium of claim 73, wherein managing tasks related to managed matters comprises retrieving tasks for a particular organization.

82. The machine-readable medium of claim 73, wherein managing tasks related to managed matters comprises editing tasks.

83. The machine-readable medium of claim 73, wherein managing tasks related to managed matters comprises viewing a calendar of tasks.

84. The machine-readable medium of claim 73, wherein the security module requires a user to log in before granting access to matter or task data, and wherein the security module further grants the logged in user access only to those matters and tasks to which the user has been granted access.

85. The machine-readable medium of claim 84, wherein users are granted access to matters and tasks by the creator of each matter or task.

86. The machine-readable medium of claim 73, further comprising a messaging module operable to provide messaging to users of the system.

87. The machine-readable medium of claim 86, wherein the messaging comprises automated messages to particular users, the messages relating to matters and tasks associated with the particular users.

88. The machine-readable medium of claim 86, wherein the messaging comprises a user sending messages to other users.

89. The machine-readable medium of claim 86, wherein the messaging module is further operable to send electronic mail (e-mail) to users, the e-mail comprising information relating to the user's role in managed tasks and matters.

90. The machine-readable medium of claim 73, wherein the system comprises a World-Wide Web site (Internet web site).

91. The machine-readable medium of claim 90, wherein the web site comprises application server pages.

92. The machine-readable medium of claim 90, wherein the web site comprises Java server pages.

93. The machine-readable medium of claim 90, wherein the system further comprises a database for managing trademark application data.

94. The machine-readable medium of claim 93, wherein the system comprises multiple databases and is able to exchange data between the multiple databases.

95. The machine-readable medium of claim 94, the instructions further operable to synchronize data in the databases by publishing changes to one database to other associated databases within the system.

96. The machine-readable medium of claim 73, wherein multiple matters may be associated with each other, such that data relating to one of the multiple matters will be visible when viewing data relating to another of the multiple matters.