Registry driven interoperability and exchange of documents

• US 7,703,008 B2
• Filed: 03/07/2006
• Issued: 04/20/2010
• Est. Priority Date: 07/19/2002
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation
• Original Assignee: Open Invention Network LLC
• Inventors: Clark, Michael, Holmes, Alexander, Kasi, Jayaram Rajan, Yuen, Helen S., Ingersoll, Christopher Todd, Senathi, Sathish Babu K., Aletty, Ashok
• Primary Examiner(s): Hong; Stephen S
• Assistant Examiner(s): Ludwig; Matthew J
• Application Number:
  US11/369,784
• Publication Number:
  US 20060150095A1
• Time in Patent Office: 1,505 Days
• Field of Search: 715/234, 715/229, 715/236, 715/239, 715/523, 715/511, 715/512, 715/524, 707/4
• 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 semantics of a document encoded using a source semantic version and destined for a target, including:

determining from an interface registry at least one target semantic version used by the target, the interface registry including semantic versions used by targets;

identifying from a document family registry one or more transforms that convert the document from the source semantic version to the target semantic version, the document family registry including semantic versions used by document family members and available transforms among the semantic versions; and

applying the transforms to convert the document.

2. The method of claim 1, wherein the document family registry is accessible to but distinct from the source and the target.

3. The method of claim 2, wherein the document family registry is commonly accessible.

4. The method of claim 1, further including receiving the document and outputting the converted document.

5. The method of claim 1, wherein semantic versions 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 the transforms supported by the document family registry include Contivo maps, XSLT maps, and Java maps.

9. The method of claim 1, wherein applying the transforms includes using processing resources of the source, distinct from processing resources of the document family registry.

10. The method of claim 9, wherein applying the transforms further includes retrieving the transforms from a commonly accessible repository of transforms.

11. The method of claim 10, wherein the transforms are retrieved from the commonly accessible repository to a local repository.

12. The method of claim 11, wherein the transforms in the local repository are checked for currency before application.

13. The method of claim 1, wherein the transforms are reusable for additional sources and additional targets, depending on the semantic versions of the additional sources and the additional targets.

14. The method of claim 1, wherein applying the transforms includes preserving source semantic information from the document in a user viewable field of the converted document, when transformation of the source semantic information is suspect.

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

16. The method of claim 1, wherein the document family registry is distributed across a plurality of physical devices.

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

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

document family members, identified by library, document identifier, release version and schema type;

semantic transforms between document family members, including logic executed remotely to implement the semantic transforms;

associations of the semantic transforms with source and target document family members;

responding to requests for the semantic transforms by providing the logic to be executed remotely.

18. The method of claim 17, further including traversing the associations of the semantic transforms between document family members and identifying one or more sequences of one or more transforms from a source document family member into a target document family member.

19. The method of claim 18, wherein:

maintaining the semantic transforms further includes maintaining transform success scores; and

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

20. The method of claim 19, 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.

21. The method of claim 19, 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.

22. The method of claim 17, 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 by providing the logic to be executed remotely is accomplished by reference to privately maintained transforms, maintained separately from the document family registry data structure.

23. The method of claim 17, 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

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