Abstract: In a complex workflow environment, a data-type-definition (DTD) schema drives a dynamic business component instantiation and execution framework that integrates documents with data and information created by various applications, potentially operating on several different platforms, enabling complex workflow and collaboration to occur over a communication network such as the Internet. The DTD execution language is preferably an industry specific XML-based tag set that defines business component instantiation, execution, input and output parameters, workflow, user profile, and collaboration specifications for a given task or data in a complex workflow process. Business and data processing components available on systems both within and outside the complex workflow system are called upon to provide the processing, interpretation, and transformation functions for the complex workflow system.

Abstract: In a complex workflow environment, a data-type-definition (DTD) schema drives a dynamic business component instantiation and execution framework that integrates documents with data and information created by various applications, potentially operating on several different platforms, enabling complex workflow and collaboration to occur over a communication network such as the Internet. The DTD execution language is preferably an industry specific XML-based tag set that defines business component instantiation, execution, input and output parameters, workflow, user profile, and collaboration specifications for a given task or data in a complex workflow process. Business and data processing components available on systems both within and outside the complex workflow system are called upon to provide the processing, interpretation, and transformation functions for the complex workflow system.

Abstract: In a complex workflow environment, a data-type-definition (DTD) schema drives a dynamic business component instantiation and execution framework that integrates documents with data and information created by various applications, potentially operating on several different platforms, enabling complex workflow and collaboration to occur over a communication network such as the Internet. The DTD execution language is preferably an industry specific XML-based tag set that defines business component instantiation, execution, input and output parameters, workflow, user profile, and collaboration specifications for a given task or data in a complex workflow process. Business and data processing components available on systems both within and outside the complex workflow system are called upon to provide the processing, interpretation, and transformation functions for the complex workflow system.

Abstract: In a complex workflow environment, a data-type-definition (DTD) schema drives a dynamic business component instantiation and execution framework that integrates documents with data and information created by various applications, potentially operating on several different platforms, enabling complex workflow and collaboration to occur over a communication network such as the Internet. The DTD execution language is preferably an industry specific XML-based tag set that defines business component instantiation, execution, input and output parameters, workflow, user profile, and collaboration specifications for a given task or data in a complex workflow process. Business and data processing components available on systems both within and outside the complex workflow system are called upon to provide the processing, interpretation, and transformation functions for the complex workflow system.

Abstract: A system and method for developing rules for validating a process having one or more parameters. The system or method may be used with a knowledge management system to validate the process. In one example, one or more rules are created to be used to validate the process, and the one or more rules are stored in a repository. One or more parameters relating to the process are obtained, one or more rules associated with the process are obtained from the repository, and the one or more rules obtained are used to validate the one or more parameters of the process. If the one or more parameters comply with the one or more rules, an indication thereof may be provided. Or if the one or more parameters do not comply with the one or more rules, an indication thereof may be provided.

Abstract: A system and method for converting an extensible markup language (XML) file, such as a WellXML™ file, to data elements that are accessible by a server. In one example, an XML file is received and the type of data provided in the XML file is determined. At least one metafile is identified as associated with the type of data determined by the determining operation, wherein the metafile specifies one or more parameters present in the type of data determined by the determining operation. One or more data elements in the XML file are identified as corresponding to the one or more parameters, and an output file is generated which includes the one or more data elements. The output file may be stored on a server accessible by clients in a network. In this manner, a large number of files converted into XML or the like can be made accessible over a network.

Abstract: A system and method for developing rules for validating a process having one or more parameters. The system or method may be used with a knowledge management system to validate the process. In one example, one or more rules are created to be used to validate the process, and the one or more rules are stored in a repository. One or more parameters relating to the process are obtained, one or more rules associated with the process are obtained from the repository, and the one or more rules obtained are used to validate the one or more parameters of the process. If the one or more parameters comply with the one or more rules, an indication thereof may be provided. Or if the one or more parameters do not comply with the one or more rules, an indication thereof may be provided.

Abstract: In a complex workflow environment, a data-type-definition (DTD) schema drives a dynamic business component instantiation and execution framework that integrates documents with data and information created by various applications, potentially operating on several different platforms, enabling complex workflow and collaboration to occur over a communication network such as the Internet. The DTD execution language is preferably an industry specific XML-based tag set that defines business component instantiation, execution, input and output parameters, workflow, user profile, and collaboration specifications for a given task or data in a complex workflow process. Business and data processing components available on systems both within and outside the complex workflow system are called upon to provide the processing, interpretation, and transformation functions for the complex workflow system.