Transformational conversation definition language

• US 7,970,826 B2
• Filed: 12/06/2001
• Issued: 06/28/2011
• Est. Priority Date: 12/06/2001
• Status: Expired due to Fees

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Lemon, Michael J., Karp, Alan H., Kuno, Harumi Anne
• Primary Examiner(s): Chea; Philip J
• Application Number:
  US10/003,349
• Publication Number:
  US 20030120730A1
• Time in Patent Office: 3,491 Days
• Field of Search: 717/114, 709/246, 709/204, 709/223, 709/219, 715/513, 715/523, 715/239
• US Class Current: 709/204
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/085 specially adapted for interworking of IP-based networks with other networks
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A computer language for facilitating communication between web services, where web services may use disparate input and output document formats, and system using same. A Conversation Definition Language (CDL) is extended with transformational information to a Transformational Conversation Definition Language (TCDL). The CDL defines document types, transitions and interactions of a conversation between two or more web services. In a preferred embodiment, the transformational information is a subset of the interaction information. Stylesheets are used to define the semantics of the required transformation and the appropriate stylesheets are identified in the TCDL file. A conversation controller component reads the TCDL files that correspond to a given conversation and utilizes the transformation information, when necessary to transform documents between web services without human intervention.

Claims

1. At least one non-transitory computer-readable medium storing a computer language, said computer language comprising:

(a) a plurality of defined document type descriptions, each document type description specifying a type of document within a common document structure that can be used;

(b) a set of defined interactions describing respective document exchanges, each interaction specifying any expected inbound document types and any resulting outbound document types;

(c) a set of transformations for use in connection with the defined interactions, each transformation specifying how to convert one document type in the common document structure to another document type, also in the common document structure, together with instructions for applying said transformations to compensate for mismatches between documents actually received and expected inbound document types, wherein each of at least some of the interactions has a transformation sub-element to describe a corresponding one of the transformations; and

(d) a transition structure that maps all permissible flows for a given conversation by identifying interactions from the set of defined interactions and specifying transitions between the identified interactions,

wherein each of (a)-(d) is a separately defined component of said computer language.

2. At least one computer-readable medium according to claim 1, wherein at least one of the defined interactions allows for any of a plurality of inbound document types, and wherein the transition structure specifies different transitions depending upon which document type is actually received.

3. At least one computer-readable medium according to claim 1, wherein the plurality of defined document type descriptions comprise XML stylesheets.

4. At least one computer-readable medium according to claim 1, wherein the defined document type descriptions, the defined interactions and the set of transformations are available for defining additional transition structures that specify interactions and transitions for other desired conversations.

5. At least one computer-readable medium according to claim 1, wherein the computer language comprises a second transition structure, corresponding to a second conversation, that identifies a second group of interactions from the set of defined interactions and specifies transitions between the interactions in the second group.

6. At least one computer-readable medium according to claim 5, wherein at least some of the interactions in the second group also specify any applicable transformations.

7. At least one computer-readable medium according to claim 1, wherein the set of defined interactions models states of the given conversation, the transition structure defines flows between states for the given conversation, and each state is defined independently of how the given conversation was navigated to reach said state.

16. At least one computer-readable medium according to claim 1, wherein the common document structure comprises an extensible markup language (XML).

8. A system comprising:

a computer having a conversation controller for controlling a conversation between a Web service and an external entity, and

a communications interface for exchanging documents with a Web service and an external entity, wherein the conversation controller comprises;

(a) a plurality of defined document type descriptions, each document type description specifying a type of document within a common document structure that can be used;

(b) a set of defined interactions describing respective document exchanges, each interaction specifying any expected inbound document types and any resulting outbound document types;

(c) a transition structure that maps all permissible flows for a given conversation by identifying interactions from the set of defined interactions and specifying transitions between the identified interactions;

(d) a set of transformations, each transformation specifying how to convert one document type in the common document structure to another document type, also in the common document structure, wherein each of at least some of the interactions has a transformation sub-element to describe a corresponding one of the transformations;

(e) a control processor for exchanging documents with the Web service and with the external entity through the communications interface in accordance with the transition structure; and

(f) a transformation component that maps document types using the set of transformations to compensate for mismatches between documents actually received from the external entity and expected inbound document types,

wherein each of (a)-(d) is a separately defined component of said conversation controller.

9. A system according to claim 8, wherein both the transition structure and a plurality of transition structures for other Web services are accessible through a central Web-based registry.

10. A system according to claim 8, wherein the transition structure defines permissible conversation flows from the perspective of the Web service.

11. A system according to claim 8, wherein at least one of the specified interactions allows for any of a plurality of inbound document types, and wherein the transition structure specifies different transitions depending upon which document type is actually received.

12. A system according to claim 8, wherein the conversation controller further comprises a second transition structure, corresponding to a second conversation, that identifies a second group of interactions from the set of defined interactions and specifies transitions between the interactions in the second group.

13. A system according to claim 8, wherein the plurality of defined document type descriptions comprise XML stylesheets.

14. A system according to claim 8, wherein the defined document type descriptions, the defined interactions and the set of transformations are available for defining additional transition structures that specify interactions and transitions for other desired conversations.

15. A system according to claim 8, wherein the control processor is located remotely from a processor executing the Web service.

17. A system according to claim 8, wherein the common document structure comprises an extensible markup language (XML).

18. A system according to claim 8, wherein the conversation controller is compiled from a description file.