SYSTEM AND METHOD FOR SCHEMA EVOLUTION IN AN E-COMMERCE NETWORK

• US 20090292985A1
• Filed: 07/29/2009
• Published: 11/26/2009
• Est. Priority Date: 10/16/1998
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Open Invention Network LLC
• Inventors: Koistinen, Jari, Fuchs, Matthew, Andrew, Davidson
• Granted Patent: US 8,266,523 B2
• Time in Patent Office: Days
• US Class Current: 715/234
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 99/00 Subject matter not provided for in other groups of this subclass

Abstract

A method and computer system are described for conducting commercial transactions. An enhanced type of XML schema may be used which supports integrity constraints and polymorphism. Schemas are identified by the use of Uniform Resource Names. XML processors residing on transaction servers or trading partner servers parse document instances by retrieving the URNs corresponding to the schemas used to interpret the document. The URNs are converted to location-dependent URIs in order to locate the schemas. URNs are resolved to location-dependent URIs by use of the LDAP protocol. URNs may be converted to LDAP URLs which are used to search LDAP compliant directories. The directories serve as registries for the URI values corresponding to the URNs.

Claims

1. A computer network system for processing electronic documents encoded in XML markup language, the computer network system comprising:

a communications channel;

a first server, the first server being in communication with the communications channel, wherein the first server stores a first schema that defines a first tag which includes a plurality of elements from the markup language;

a second server, the second server being in communication with the communications channel, wherein the second server stores a second schema that defines a second tag including

a reference to the first tag defined in the first schema, wherein the reference identifies the first tag as being extended; and

an additional element from the markup language that is not included in the first schema as part of the definition of the first tag;

wherein the second tag is polymorphically defined to be used to encode data within an electronic document, such that the first and second schemas respectively allow use of the first or second tag in the electronic document;

whereby applications and document types that use the first or second tag can evolve separately.

2. The computer network system of claim 1, further including an XML parser running on a third server, in communication with the communications channel, the parser being adapted to recognize the polymorphic encoding of the second schema and to parse the XML document and the second tag, even if business logic receiving the XML document is not adapted to process the additional element of the second tag.

3. The computer network system of claim 1, wherein the communications channel includes a local area network (LAN).

4. The computer network system of claim 1, wherein the communications channel includes a wide area network (WAN).

5. The computer network system of claim 1, wherein the communications channel includes the Internet.

6. The computer network system of claim 1, further comprising:

a third server, the third server in communication with the communications channel, wherein the third server stores a first XML document instance, wherein the first document instance is interpreted by use of the first schema.

7. The computer network system of claim 6, wherein the first document instance includes the first element.

8. The computer network system of claim 6, wherein the first document instance includes the second element, such that the second element is used in a location reserved for the first element in the first document instance.

9. The computer network system of claim 8, further comprising:

a fourth server, the fourth server in communication with the communications channel, wherein the fourth server stores a second XML document instance, wherein the second document instance is interpreted by use of the second schema.

10. The computer network system of claim 9, wherein the second document instance includes the second element.

11. The computer network system of claim 10, wherein the second element is used in a location reserved for the first element in the second document instance.

12. The computer network system of claim 9, wherein the first document instance and the second document instance correspond to a document type, wherein the document type is at least one of a purchase order, a purchase order acknowledgement, an order status check, an availability check, a price check, an invoice, an invoice acknowledgement.

13. A method of using a second tag in place of a first tag in an XML document, the method including:

receiving an XML document that includes a second tag defined in a second schema and a reference to the second schema stored on a second server;

processing the second schema, which defines the second tag including

a reference to a first tag defined in a first schema stored on a first server, wherein the reference identifies the first tag as being extended; and

an additional element from the markup language that is not included in the first schema as part of the definition of the first tag;

processing the second tag as a polymorphic encoding of data in the XML document, such that the first and second schemas respectively allow use of the first or second tag in the electronic document;

whereby applications and document types that use the first or second tag can evolve separately.

14. The method of claim 13, further including parsing the XML document using an XML parser, the parser being adapted to recognize the polymorphic encoding of the second schema and to parse the XML document and the second tag, even when business logic receiving the XML document is not adapted to process the additional element of the second tag.

15. The method of claim 13, wherein the first and second schemas reside on separate servers.

16. The method of claim 14, wherein the first and second schemas reside on separate servers.

17. A method of an online service processing an XML document that extends a first XML document, the method including:

receiving the XML document that includes a second tag,

wherein the XML document references a second schema on a second server that defines the second tag, including

a reference to a first tag in a first schema on a first server, wherein the reference identifies the first tag as being extended; and

an additional element from the markup language, not included in the first tag; and

wherein the first tag is defined in the first schema to include a plurality of elements from the XML markup language;

further including processing the XML document containing the second tag, in case the online service is adapted to process data according to the second schema, by processing the additional element of the second tag and, in case the online service is adapted to process data according to the first schema but not the second schema, by not processing the additional element of the second tag but still processing the plurality of elements of the first tag;

wherein the second tag polymorphically encodes data within the XML document;

whereby the first and second schemas respectively allow use of the first or second tag and whereby applications and document types that use the first or second tag can evolve separately.

18. The method of claim 17, further including parsing the XML document using an XML parser, the parser being adapted to recognize the polymorphic encoding of the second schema and to parse the XML document and the second tag, even if business logic receiving the XML document is not adapted to process the additional element of the second tag.

19. The method of claim 17, wherein the first and second schemas reside on separate servers.

20. The method of claim 18, wherein the first and second schemas reside on separate servers.