System and method for schema evolution in an e-commerce network

• US 7,594,167 B1
• Filed: 01/28/2000
• Issued: 09/22/2009
• 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: Koistinen, Jari, Andrew, Davidson, Fuchs, Matthew
• Primary Examiner(s): Ries; Laurie
• Assistant Examiner(s): Nguyen; Maikhanh
• Application Number:
  US09/493,517
• Time in Patent Office: 3,525 Days
• Field of Search: 715/513, 715/501.1, 715/200, 715/201, 715/205, 715/234, 715/202, 715/253, 715/254, 715/255, 715/256, 715/273, 715/713, 715/760, 700/100, 705/26, 705/23, 709/203, 709/201, 709/213, 797/10
• 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 method of extending a definition of a first tag used in a first electronic document, wherein the first electronic document is encoded in a markup language, and the first electronic document is stored on a server in a computer network, the method comprising:

defining the first tag in a first schema, wherein the definition of the first tag includes a plurality of elements from the markup language;

defining a second tag in a second schema, wherein a definition of the second tag includes

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

an additional element from the markup language; and

providing references for locating the first schema and second schema in a second electronic document, wherein the second tag is polymorphically used to encode text within the second electronic document;

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

wherein the markup language is XML.

2. The method of claim 1, further comprising:

parsing the first electronic document, wherein the first electronic document is parsed by a parser for the markup language, the parser being stored on the server.

3. The method of claim 1, wherein the first electronic document corresponds to 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.

4. The method of claim 1, further comprising:

parsing the second electronic document, wherein the second electronic document is parsed by a parser for the markup language, the parser being stored on the server.

5. The method of claim 4, wherein the second electronic document corresponds to a commercial transaction.

6. The method of claim 5, wherein the commercial transaction is selected from the group consisting of a purchase order, a purchase order acknowledgement, an order status check, an availability check, a price check, an invoice, an invoice acknowledgement.

7. A computer network system including at least one processor for processing a document instance of a markup language, the computer network system comprising:

means for defining a first tag, including a plurality of elements from a markup language, in a first schema in the computer network system;

means for polymorphically extending a definition of the first tag by use of a second schema residing on the computer network system, the second schema defining a second tag by reference to the first tag that incorporates in the second schema the plurality of elements from the markup language and by including additional elements, including using the second tag in a location otherwise used by the first tag in the document instance; and

means for importing reference to the second schema into the document instance;

wherein the markup language is XML.

8. A method of extending a definition of a first tag used in a first electronic document, wherein the first electronic document is encoded in a markup language, and the first electronic document is stored on a server in a computer network, the method comprising:

defining the first tag in a first schema, wherein a definition of the first tag includes plurality of elements from the markup language; and

defining a second tag in a second schema, wherein a definition of the second tag includes a reference to the first tag and an additional element from the markup language; and

providing references for locating the first schema and second schema in the first electronic document, wherein the first and second tags are polymorphically available to encode text within the first electronic document;

whereby an application designed to work with the first tag in the first schema can process the text encoded using the second tag in the second schema, when the encoding is within the scope of the first tag, without modifying the application, whereby document types and applications can evolve separately;

wherein the markup language is XML.

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