Registry driven interoperability and exchange of documents

• US 8,683,321 B2
• Filed: 04/19/2010
• Issued: 03/25/2014
• Est. Priority Date: 07/19/2002
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: Open Invention Network LLC
• Inventors: Ingersoll, Christopher Todd, Kasi, Jayaram Rajan, Holmes, Alexander, Clark, Michael, Aletty, Ashok, Senathi, Sathish Babu K., Yuen, Helen S.
• Primary Examiner(s): Hong, Stephen
• Assistant Examiner(s): LUDWIG, MATTHEW J
• Application Number:
  US12/763,136
• Publication Number:
  US 20100205522A1
• Time in Patent Office: 1,436 Days
• Field of Search: 715/229, 715/234, 715/236, 715/239
• US Class Current: 715/234
• CPC Class Codes: G06F 16/245 Query processing
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• CPC Class Codes: G06F 40/154 Tree transformation for tree-structured or markup documents, e.g. XSLT, XSL-FO or stylesheets
• CPC Class Codes: G06F 40/197 Version control for software G06F8/71
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation

Abstract

The present invention relates to systems and methods for registry driven transformation of a document exchanged between businesses or applications. More particularly, it relates to systems and protocols for using one or more commonly accessible registries to transform electronic commerce documents among dissimilar interfaces, preferably XML documents. Particular aspects of the present invention are described in the claims, specification and drawings.

Claims

1. A computer-assisted method of transforming a document with semantic encoding destined for a target service, including:

electronically requesting by target service identifier and receiving from an interface registry at least one target document version used by a target service from among a plurality of document versions in a document family; and

electronically requesting by source and target document versions and receiving from a document family registry one or more transforms or references to transforms to be applied sequentially to convert a document from the source document version to the target document version.

2. The method of claim 1, further including applying the transforms to convert the document from the source document version to the target document version.

3. The method of claim 2, wherein the target service identifier is a party/service/action triplet.

4. The method of claim 2, wherein the source and target document versions use different semantic encoding of data, which requires transformation.

5. The method of claim 4, wherein versions of the semantic coding include major versions distinguished by system standard and minor versions distinguished by release version within a particular system standard.

6. The method of claim 1, wherein the document family registry includes for document family members identifications of a system standard, a document identifier, a release version and a schema type.

7. The method of claim 1, wherein the transforms include one or more of Contivo maps, XSLT maps, XST maps, XSD-SOX classes, and Java maps.

8. The method of claim 1, wherein applying the transforms includes using processing resources of a requesting service, distinct from processing resources of the document family registry.

9. The method of claim 1, wherein the transforms are stored in the local repository and are checked against a non-local repository for currency before application.

10. The method of claim 1, wherein applying the transforms includes preserving semantically coded source data from the document in a user viewable field of a transformed document.

11. The method of claim 1, further including selecting among alternative sequences of transforms based on a transform success score.

12. A computer-assisted method of exposing transforms applicable to a document family, including:

maintaining a document family registry data structure, including for a particular document family

document family versions;

transforms including program instructions that transform data between document family versions;

responding to requests that identify first and second document family versions by providing one or more sequences of transforms or references to transforms to be executed remotely, that transform the data from the first document family version to the second document family version.

13. The computer-assisted method of claim 12, wherein the document family versions in the document family registry data structure are identified by library, document identifier, release version and schema type.

14. The method of claim 12, further including traversing the document family registry data structure and identifying one or more sequences of multiple transforms that collectively transform from the first document family version into the second document family version.

15. The method of claim 14, wherein:

maintaining the transforms further includes maintaining transform success scores; and

responding to requests further includes calculating composite transform success scores for the sequences of transforms.

16. The method of claim 15, wherein the transform success scores correspond to a fraction of fields translated verbatim from a field of the source document to a field of the target document.

17. The method of claim 15, wherein the transform success scores correspond to a fraction of text in fields of the source document found verbatim in fields of the target document.

18. The method of claim 12, wherein:

maintaining the document family registry data structure further includes maintaining special rules for transforms to be applied corresponding to one or more participants in a document exchange.

19. The method of claim 12, wherein:

the transforms to be executed remotely are privately maintained transforms, maintained separately from the document family registry data structure.

20. The method of claim 12, wherein:

maintaining the document family registry data structure further includes maintaining special rules for transforms to be applied corresponding to one or more participants in a document exchange; and

responding further includes referring to private transforms, maintained securely within the document family registry data structure.