Transformational conversation definition language
First Claim
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 Assignments
0 Petitions
Accused Products
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.
-
Citations
18 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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 16)
-
-
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. - View Dependent Claims (9, 10, 11, 12, 13, 14, 15, 17, 18)
-
Specification