Documents for commerce in trading partner networks and interface definitions based on the documents

• US 8,006,177 B1
• Filed: 10/16/1998
• Issued: 08/23/2011
• Est. Priority Date: 10/16/1998
• Status: Expired due to Fees

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Open Invention Network LLC
• Inventors: Allen, Terry, Maloney, Murray, Glushko, Robert John, Fuchs, Matthew Daniel, Meltzer, Bart Alan
• Primary Examiner(s): HUYNH, CONG LAC T
• Application Number:
  US09/173,858
• Time in Patent Office: 4,694 Days
• Field of Search: 715/513, 715/514, 715/500, 715/501.1, 715/200, 715/234, 715/700, 705/24, 705/75
• US Class Current: 715/234
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/209 Specified transaction journal output feature, e.g. printed receipt or voice output
• CPC Class Codes: G06Q 99/00 Subject matter not provided for in other groups of this subclass

Abstract

Machine readable documents connect businesses with customers, suppliers and trading partners. The self defining electronic documents, such as XML based documents, can be easily understood amongst the partners. Definitions of these electronics business documents, called business interface definitions, are posted on the Internet, or otherwise communicated to members of the network. The business interface definitions tell potential trading partners the services the company offers and the documents to use when communicating with such services. Thus, a typical business interface definition allows a customer to place an order by submitting a purchase order or a supplier checks availability by downloading an inventory status report. Also, composition of the input and output documents, coupled with interpretation information in a common business library, programs the transaction in a way which closely parallels the way in which paper based businesses operate.

Claims

1. An interface for transactions among nodes in a network including a plurality of nodes which execute processes involved in the transactions, the interface being stored in a computer readable medium, comprising:

a machine readable specification of an interface to transaction processes stored in memory accessible by at least one node in the network, including interpretation information providing a definition of an input document, and a definition of an output document, the definitions of the input and output documents comprising respective descriptions of sets of storage units and logical structures for the sets of storage units.

2. The interface of claim 1, wherein the interpretation information includes data type specifications for at least one logical structure in the definitions of the input and output documents.

3. The interface of claim 1, wherein the interpretation information includes at least one data structure mapping predefined sets of storage units for a particular logical structure in the definitions of the input and output documents, to respective entries in a list.

4. The interface of claim 1, including a repository in memory accessible by at least one node in the network storing a library of logical structures, and interpretation information for logic structures.

5. The interface of claim 1, wherein the machine readable specification includes a document compliant with a definition of an interface document including logical structures for storing an identifier of a particular transaction, and at least one of definitions and references to definitions of input and output documents for the particular transaction.

6. The interface of claim 1, wherein the machine readable specification includes a document compliant with a definition of an interface document including logical structures for storing an identifier of the interface, and for storing at least one of specifications and references to specifications of a set of one or more transactions supported by the interface.

7. The interface of claim 6, wherein the machine readable specification includes a reference to a specification of a particular transaction, and the specification of the particular transaction includes a document including logical structures for storing at least one of definitions and references to definitions of input and output documents for the particular transaction.

8. The interface of claim 1, wherein the storage units comprise parsed data.

9. The interface of claim 8, wherein the parsed data in at least one of the input and output documents comprises:

character data encoding text characters in the one of the input and output documents, and

markup data identifying sets of storage units according to the logical structure of the one of the input and output documents.

10. The interface of claim 9, wherein at least one of the sets of storage units encodes a plurality of text characters providing a natural language word.

11. The interface of claim 8, wherein the interpretation information for at least one of the sets of storage units identified by a particular logical structure of at least one of the input and output documents, encodes respective definitions for sets of parsed characters.

12. The interface of claim 8, wherein the storage units comprise unparsed data.

13. The interface of claim 1, including a repository stored in memory accessible by at least one node in the network of document types for use in a plurality of transactions, and wherein the definition of one of the input and output documents includes a reference to a document type in the repository.

14. The method of claim 13, wherein the repository of document types includes a document type for identifying participant processes in the network.

15. The interface of claim 1, wherein the definitions of the input and output documents comprise document type definitions compliant with a standard Extensible Markup Language XML.

16. The interface of claim 1, wherein the machine readable data structure including interpretation information comprises a document organized according to a document type definition compliant with a standard Extensible Markup Language XML.

17. A method for programming a commercial transaction in a network, comprising:

defining a machine readable definition of an input document for a node in the network including resources to execute a process in the transaction, and a machine readable definition of an output document for the node, the definitions of the input and output documents comprising respective descriptions of sets of storage units and logical structures for the sets of storage units; and

providing interpretation information for the logical structures to the node.

18. The method of claim 17, wherein the interpretation information includes data type specifications for at least one logical structure in the definitions of the input and output documents.

19. The method of claim 17, wherein the interpretation information includes at least one data structure mapping predefined sets of storage units for a particular logical structure in the definitions of the input and output documents, to respective entries in a list.

20. The method of claim 17, the step of providing interpretation information includes providing a repository in memory accessible by at least one node in the network storing a library of logical structures, and interpretation information for logic structures.

21. The method of claim 17, including defining a machine readable specification of an interface including a document compliant with a definition of an interface document including logical structures for storing an identifier of a particular transaction, and at least one of the definitions and references to the definitions of the input and output document.

22. The method of claim 17, wherein the storage units comprise parsed data.

23. The method of claim 22, wherein the parsed data in at least one of the input and output documents comprises:

character data encoding text characters in the one of the input and output documents, and

markup data identifying sets of storage units according to the logical structure of the one of the input and output documents.

24. The method of claim 23, wherein at least one of the sets of storage units encodes a plurality of text characters providing a natural language word.

25. The method of claim 23, wherein the interpretation information for at least one of the sets of storage units identified by a particular logical structure of at least one of the input and output documents, encodes respective definitions for sets of parsed characters.

26. The method of claim 22, wherein the storage units comprise unparsed data.

27. The method of claim 17, wherein the definitions of the input and output documents comprise document type definitions compliant with a standard Extensible Markup Language XML.

28. The method of claim 17, including:

providing a parser to generate event signals in response to logical structures in the definition of the input document; and

providing event listener programs which respond to the event signals to execute the process.

29. An interface for transactions among nodes in a network including a plurality of nodes which execute processes involved in the transactions, the interface being stored in a computer readable medium, comprising:

a machine readable specification of an interface to an operation stored in memory accessible by at least one node in the network, including interpretation information providing a definition of an input document, and a definition of an output document, the definitions of the input and output documents comprising respective descriptions of sets of storage units and logical structures for the sets of storage units.

30. The interface of claim 29, wherein the interpretation information includes data type specifications for at least one logical structure in the definitions of the input and output documents.