Abstract: A method to support ad hoc collaboration and generation of workflows for a team of users may comprise providing data from a provenance graph to launched applications, selectively using the provided data from the provenance graph and additional input to create derived data and derived outputs, and routing the derived data and the derived outputs to the provenance graph; recording, in the provenance graph, subsequences of the launched applications; recommending one of the recorded subsequences, based on the history of execution of the recorded subsequences of the launched applications; creating a new application with the recommended subsequences of the launched applications; launching the newly created application, and storing the newly created application in a catalog of applications for use by the user.

Abstract: A method to support ad hoc collaboration and generation of workflows for a team of users may comprise providing data from a provenance graph to launched applications, selectively using the provided data from the provenance graph and additional input to create derived data and derived outputs, and routing the derived data and the derived outputs to the provenance graph; recording, in the provenance graph, subsequences of the launched applications; recommending one of the recorded subsequences, based on the history of execution of the recorded subsequences of the launched applications; creating a new application with the recommended subsequences of the launched applications; launching the newly created application, and storing the newly created application in a catalog of applications for use by the user.

Abstract: The mapping system and method comprises receiving a query identifying a source entity, the source entity being of a first entity-type; generating a plurality of candidate entities from an analysis of an entity-relationship graph in response to the query based on the source entity; and computing feature values for each candidate entity of the plurality of candidate entities by passing the source entity and the plurality of candidate entities to a type-specific entity recommender particular to the first entity-type.

Abstract: A mechanism is provided for creating modules from an XML schema. The mechanism includes creating a syntax tree from a sample XML fragment of the XML schema, creating a module with a list of parameters based on the syntax tree, identifying variable pieces of information in the syntax tree to be inserted in the list of parameters with a variable sign, and inserting the variable information into the list of parameters. The mechanism includes inserting another module in the syntax tree of the module, in which the other module corresponds to another sample XML fragment and has another list of parameters, and identifying the other module with the variable sign in the syntax tree of the module. The mechanism includes inserting the other module into the list of parameters of the module in which the other module to serve as a parameter, and providing an option for constraining the module.

Abstract: The mapping system and method comprises receiving a query identifying a source entity, the source entity being of a first entity-type; generating a plurality of candidate entities from an analysis of an entity-relationship graph in response to the query based on the source entity; and computing feature values for each candidate entity of the plurality of candidate entities by passing the source entity and the plurality of candidate entities to a type-specific entity recommender particular to the first entity-type.

Abstract: A mechanism is provided for creating modules from an XML schema. The mechanism includes creating a syntax tree from a sample XML fragment of the XML schema, creating a module with a list of parameters based on the syntax tree, identifying variable pieces of information in the syntax tree to be inserted in the list of parameters with a variable sign, and inserting the variable information into the list of parameters. The mechanism includes inserting another module in the syntax tree of the module, in which the other module corresponds to another sample XML fragment and has another list of parameters, and identifying the other module with the variable sign in the syntax tree of the module. The mechanism includes inserting the other module into the list of parameters of the module in which the other module to serve as a parameter, and providing an option for constraining the module.

Abstract: An external service at a service provider server is invoked from a database by accessing from over a network a description of the external service published by the service provider external to the database. A database invocation mechanism is generated from the accessed description of the external service, wherein the database invocation mechanism comprises code within the database. A database program invokes the database invocation mechanism code within the database to invoke and interact with the external service. The database receives data from the external service in response to invoking and interacting with the external service.

Abstract: A mechanism is provided for creating modules from an XML schema. The mechanism includes creating a syntax tree from a sample XML fragment of the XML schema, creating a module with a list of parameters based on the syntax tree, identifying variable pieces of information in the syntax tree to be inserted in the list of parameters with a variable sign, and inserting the variable information into the list of parameters. The mechanism includes inserting another module in the syntax tree of the module, in which the other module corresponds to another sample XML fragment and has another list of parameters, and identifying the other module with the variable sign in the syntax tree of the module. The mechanism includes inserting the other module into the list of parameters of the module in which the other module to serve as a parameter, and providing an option for constraining the module.

Abstract: A mechanism is provided for creating modules from an XML schema. The mechanism includes creating a syntax tree from a sample XML fragment of the XML schema, creating a module with a list of parameters based on the syntax tree, identifying variable pieces of information in the syntax tree to be inserted in the list of parameters with a variable sign, and inserting the variable information into the list of parameters. The mechanism includes inserting another module in the syntax tree of the module, in which the other module corresponds to another sample XML fragment and has another list of parameters, and identifying the other module with the variable sign in the syntax tree of the module. The mechanism includes inserting the other module into the list of parameters of the module in which the other module to serve as a parameter, and providing an option for constraining the module.

Abstract: Methods, systems, and articles of manufacture for indexing annotations made for a variety of different type (i.e., heterogeneous) data objects are provided. A set of parameters uniquely identifying an annotated data object may be converted to an index comprising a set of index values, each corresponding to a column in a homogeneous index table. In order to accommodate the indexing of heterogeneous data objects, a mapping may be provided for each different type (or classification) of data object that may be annotated, that defines how the identifying parameters of that type will be mapped to the columns of the homogeneous index table.

Abstract: A method for simplifying a process for creating a transformation of an extensible markup language XML document is described. The method includes: creating a target model by incremental user selection of elements in a source model; interpreting the target model to create an XML schema of the target model; and creating a mapping between the source model of the XML document and the target model, wherein the mapping is stored on a memory device.

Abstract: An extensible markup language (XML) document transformation system, including: a user interface configured to receive a user input; a transformation engine configured to: create a target model by incremental user selection of elements in a source model; interpret the target model to create an XML schema of the target model; and create a mapping between the source model of the XML document and the target model; and a memory device configured to store the mapping.

Abstract: An XML wrapper queries an XML document in an on-the-fly manner so that only parent nodes in the document that satisfy the query are extracted and then unnested. The parent nodes and associated descendent nodes are located using XPath expressions contained as options in data definition language (DDL) statements. The parent nodes satisfying the query and associated descendent nodes are extracted and stored outside of a database according to a relational schema. The wrapper facilitates applications that use convention SQL queries and views to operate on that information stored according to the relational schema. The wrapper also responds to query optimizer requests for costs associated with queries against external data sources associated with the wrapper.

Abstract: An XML wrapper queries an XML document in an on-the-fly manner so that only parent nodes in the document that satisfy the query are extracted and then unnested. The parent nodes and associated descendent nodes are located using XPath expressions contained as options in data definition language (DDL) statements. The parent nodes satisfying the query and associated descendent nodes are extracted and stored outside of a database according to a relational schema. The wrapper facilitates applications that use convention SQL queries and views to operate on that information stored according to the relational schema. The wrapper also responds to query optimizer requests for costs associated with queries against external data sources associated with the wrapper.

Abstract: Methods, systems, and articles of manufacture for indexing annotations made for a variety of different type (i.e., heterogeneous) data objects are provided. A set of parameters uniquely identifying an annotated data object may be converted to an index comprising a set of index values, each corresponding to a column in a homogeneous index table. In order to accommodate the indexing of heterogeneous data objects, a mapping may be provided for each different type (or classification) of data object that may be annotated, that defines how the identifying parameters of that type will be mapped to the columns of the homogeneous index table.

Abstract: The present invention provides a method, system and program product for integrating a service external to a database into a database such that the service may be easily invoked from the database. Preferably, the service is a web service available over the internet The service may be invoked from any of a number of invoking mechanisms of the database. In a first specific embodiment, the mechanism comprises a user-defined function within an SQL statement. In a second specific embodiment, the mechanism comprises a virtual table. In a third specific embodiment, the mechanism comprises a stored procedure. In a fourth specific embodiment, the mechanism comprises a trigger. In a fifth specific embodiment, the mechanism comprises a federated table accessed via a nickname and implemented using a wrapper.

Abstract: An XML wrapper queries an XML document in an on-the-fly manner so that only parent nodes in the document that satisfy the query are extracted and then unnested. The parent nodes and associated descendent nodes are located using XPath expressions contained as options in data definition language (DDL) statements. The parent nodes satisfying the query and associated descendent nodes are extracted and stored outside of a database according to a relational schema. The wrapper facilitates applications that use convention SQL queries and views to operate on that information stored according to the relational schema. The wrapper also responds to query optimizer requests for costs associated with queries against external data sources associated with the wrapper.

Abstract: An XML wrapper queries an XML document in an on-the-fly manner so that only parent nodes in the document that satisfy the query are extracted and then unnested. The parent nodes and associated descendent nodes are located using XPath expressions contained as options in data definition language (DDL) statements. The parent nodes satisfying the query and associated descendent nodes are extracted and stored outside of a database according to a relational schema. The wrapper facilitates applications that use convention SQL queries and views to operate on that information stored according to the relational schema. The wrapper also responds to query optimizer requests for costs associated with queries against external data sources associated with the wrapper.

Abstract: An XML wrapper queries an XML document in an on-the-fly manner so that only parent nodes in the document that satisfy the query are extracted and then unnested. The parent nodes and associated descendent nodes are located using XPath expressions contained as options in data definition language (DDL) statements. The parent nodes satisfying the query and associated descendent nodes are extracted and stored outside of a database according to a relational schema. The wrapper facilitates applications that use convention SQL queries and views to operate on that information stored according to the relational schema. The wrapper also responds to query optimizer requests for costs associated with queries against external data sources associated with the wrapper.

Abstract: An XML wrapper queries an XML document in an on-the-fly manner so that only parent nodes in the document that satisfy the query are extracted and then unnested. The parent nodes and associated descendent nodes are located using XPath expressions contained as options in data definition language (DDL) statements. The parent nodes satisfying the query and associated descendent nodes are extracted and stored outside of a database according to a relational schema. The wrapper facilitates applications that use convention SQL queries and views to operate on that information stored according to the relational schema. The wrapper also responds to query optimizer requests for costs associated with queries against external data sources associated with the wrapper.