Site News  |   Monitor Keywords  |   Monitor Archive  |   Organizer  |   Account Info  |

Preview mode

Preview mode description/claims

This patent application claims priority to commonly assigned co-pending U.S. patent application Ser. No. 10,435,712, U.S. Pat. No. 7,257,603 (Applicant Docket No. MS1-1533US), entitled “Preview Mode” to Derek Murman, Edward H. Wayt, Jeffrey Bisset, Jing Wu, Kim Cameron, Max L. Benson, and Jie Liu for, filed on May 8, 2003, which are incorporated by reference herein for all that it teaches and discloses.

This patent application is related to commonly assigned co-pending U.S. patent application Ser. No. 10/434,725, (Applicant Docket No. MS1-1532US), entitled “Attribute Value Selection for Entity Objects” to Kim Cameron, Max L. Benson, Matthias Leibmann, Edward H. Wayt, Kevin Miller and James Booth filed on May 8, 2003; U.S. patent application Ser. No. 10/435,113 (Applicant Docket No. MS1-1535US), entitled “Declarative Rules for Metadirectory” to Kim Cameron, Max L. Benson, and James Booth, filed on May 8, 2003; U.S. patent application Ser. No. 10/434,726 (Applicant Docket No. MS1-1576US) entitled “Relational Directory” to Kim Cameron, James Booth, Matthias Leibmann, Max L. Benson and Mark Brown, filed on May 8, 2003; U.S. patent application Ser. No. 10/435,720 (Applicant Docket No. MS1-1534US), entitled “Associating and Using Information in a Metadirectory” to Max L. Benson filed on May 8, 2003; U.S. patent application Ser. No. 10/434,411 (Applicant Docket No. MS1-1555US), entitled “Automated Information Management and Related Methods” to Max L. Benson, Stephen Siu, and James Booth filed on May 8, 2003; U.S. patent application Ser. No. 10/435,708 (now U.S. Pat. No. 7,240,073) (Applicant Docket No. MS1-1554US), entitled “Rules Customization and Related Methods” to Max L. Benson, Michael Jerger, Edward H. Wayt, Kenneth Mark, Kim Cameron, Matthias Leibmann, and Jing Wu filed on May 8, 2003; which are incorporated by reference herein for all that they teach and disclose.

The subject matter relates generally to synchronizing information and more specifically to administration of synchronizing processes that aim to synchronize information from a plurality of information sources.

Often a company stores important information in various data sources. For example, a human resources department may store information about employees in a human resources data source wherein the information is arranged or organized according to a human resources specific information structure or hierarchy and a finance department may store information about employees, clients, suppliers, etc., in a finance department data source wherein the information is arranged or organized according to a finance department information structure or hierarchy. In this example, some common information may exist in both data sources. Thus, a need for synchronizing the information arises.

A synchronizing process typically implements rules and/or specifications to adequately harmonize information in various data sources. Further, such a process may rely on an engine capable of executing software and a storage capable of storing the information, as appropriate. In general, a synchronizing process replicates information from various data sources in a central storage, wherein the replicated information has some degree of integrity. To achieve this task, information from the various data sources are either pushed or pulled into the synchronizing process. In addition, information may be pulled or pushed out of such a central storage to various data sources. Maintaining efficiency and information integrity in such an environment can become a daunting task. Various exemplary methods, devices and/or systems described below are directed to meeting this task.

Various exemplary metadirectories, systems and/or methods include or allow for executing a software module on an execution engine, emitting semantic information based on the executing, and analyzing the executing using the semantic information. An exemplary execution engine includes an input for receiving software modules, an output for emitting semantic information, and an output for outputting generated output information. Upon execution, an exemplary software module may cause processing of information in a metadirectory and emitting of semantic information pertaining to the processing. Various exemplary metadirectories, systems and/or methods emit and/or store semantic information in a self-defining language, an extensible language, and/or a markup language. Other exemplary metadirectories, systems, and/or methods are also disclosed.

FIG. 1 is a diagram of an exemplary system that includes metadirectory and a plurality of data sources.

FIG. 2 is a block diagram of an exemplary system that includes a metadirectory and a data source.

FIG. 3 is a block diagram of an exemplary scenario that includes a services module for communicating information from a data source to a storage layer of an exemplary metadirectory.

FIG. 4 is a block diagram of an exemplary scenario that includes a plurality of data sources, an exemplary services layer and an exemplary storage layer wherein a join and/or project service module executes on a service engine.

FIG. 5 is a block diagram of an exemplary scenario that includes an exemplary services layer and an exemplary storage layer wherein a flow service module executes on a service engine.

FIG. 6 is a block diagram of an exemplary services layer that includes a plurality of modules and an engine capable of emitting semantic information.

FIG. 7 is a block diagram of an exemplary scenario wherein service modules are executed on a service engine capable of emitting semantic information to a storage layer and capable of generating output information.

• Provisional Patent
• Utility Patent

• What Is a Patent?
• What Is a Trademark or Servicemark?
• What Is a Copyright?
• Patent Laws