IP Library Granted Patent US 8,117,534
Granted Patent B1
US 8,117,534 · App. 10/865,177 · Granted Feb 14, 2012

Context translation

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,117,534
App. No.
10/865,177
Granted
Feb 14, 2012
Kind
B1
Abstract

In accordance with one embodiment of the present invention, there is provided a technique for context translation. According to an aspect of the technique, a mapping is consulted. The mapping maps a first message to a second message. The first message comprises a rule-specific error message that indicates one or more rules that were violated by a portion of a document. The second message comprises a context-specific message that sets forth the meaning of the error message in a particular implementation context. The second message is provided as output. Thus, the rule-specific error message is translated into the context-specific message. According to an aspect of the technique, the mapping is not embodied in executable code. As a result, the mapping can be modified without modifying and recompiling the source code of a program that consults the mapping and outputs the second message.

Claims (42)

1. A method performed by a computer program, the method comprising:

receiving a first message that comprises a rule-specific error message that indicates one or more rules that were violated by a portion of an Extensible Markup Language (XML) document as a result of that portion not complying with a specified schema that is one of: (a) an XML schema and (b) a Document Type Definition (DTD);

wherein the computer program does not receive, with the first message, a second message that comprises a context-specific message that sets forth the meaning of the error message in a particular implementation context;

in response to receiving the first message, determining, based on a first mapping, that the first message is mapped to the second message, wherein the first mapping is not embodied in executable code; and

in response to determining that the first message is mapped to the second message, outputting the second message.

2. The method of claim 1 , further comprising:

validating the document relative to a set of rules, wherein the set of rules contains the one or more rules; and

generating the first message in response to a determination that the portion of the document violates the one or more rules.

3. The method of claim 1 , wherein the schema is an Extensible Markup Language (XML) Schema; and wherein receiving the first message comprises reading the first message from a computer-readable storage medium to which a validator that validated the document against the specified schema wrote the first message.

4. The method of claim 1 , wherein the schema is a Document Type Definition (DTD).

5. The method of claim 1 , wherein the first message does not set forth the meaning of the error message in the particular implementation context.

6. The method of claim 1 , wherein the first mapping is indicated in an Extensible Markup Language (XML) document.

7. The method of claim 1 , wherein the first mapping comprises a first node, wherein the first node is a parent of a second node and a third node, wherein the second node indicates the first message, and wherein the third node indicates the second message.

8. The method of claim 1 , wherein the first mapping can be modified without modifying the program.

9. The method of claim 1 , further comprising:

consulting a second mapping that maps a third message to the second message, wherein the second mapping differs from the first mapping, wherein the third message differs from the first message, wherein the third message comprises a rule-specific error message that indicates one or more rules that were violated by a portion of a document, and wherein the second mapping is not embodied in executable code; and

outputting the second message in response to a determination that the third message is mapped to the second message.

10. The method of claim 1 , wherein the particular implementation context is a network configuration context.

11. The method of claim 1 , wherein the first message indicates that a particular attribute must be specified for a particular element type, and wherein the second message indicates that a server lacks an Internet Protocol (IP) address.

12. The method of claim 1 , wherein the first message indicates that the content of a particular element is incomplete, and wherein the second message indicates that a server is not connected to a network.

13. The method of claim 1 , wherein the first message indicates that an element with a particular identifier must appear in the document, and wherein the second message indicates that a network lacks a subnet that is identified by the particular identifier.

14. A non-transitory computer-readable medium carrying one or more sequences of instructions, which instructions, when executed by one or more processors, cause the one or more processors to carry out the steps of:

receiving, at a computer program, a first message that comprises a rule-specific error message that indicates one or more rules that were violated by a portion of an Extensible Markup Language (XML) document as a result of that portion not complying with a specified schema that is one of: (a) an XML schema and (b) a Document Type Definition (DTD);

wherein the computer program does not receive, with the first message, a second message that comprises a context-specific message that sets forth the meaning of the error message in a particular implementation context;

in response to receiving the first message, determining, based on a first mapping, that the first message is mapped to the second message, wherein the first mapping is not embodied in executable code; and

in response to determining that the first message is mapped to the second message, outputting the second message.

15. The non-transitory computer-readable medium of claim 14 , further comprising instructions for carrying out the steps of:

validating the document relative to a set of rules, wherein the set of rules contains the one or more rules; and

generating the first message in response to a determination that the portion of the document violates the one or more rules.

16. The non-transitory computer-readable medium of claim 14 , wherein the schema is an Extensible Markup Language (XML) Schema; and wherein receiving the first message comprises reading the first message from a computer-readable storage medium to which a validator that validated the document against the specified schema wrote the first message.

17. The non-transitory computer-readable medium of claim 14 , wherein the schema is a Document Type Definition (DTD).

18. The non-transitory computer-readable medium of claim 14 , wherein the first message does not set forth the meaning of the error message in the particular implementation context.

19. The non-transitory computer-readable medium of claim 14 , wherein the first mapping is indicated in an Extensible Markup Language (XML) document.

20. The non-transitory computer-readable medium of claim 14 , wherein the first mapping comprises a first node, wherein the first node is a parent of a second node and a third node, wherein the second node indicates the first message, and wherein the third node indicates the second message.

21. The non-transitory computer-readable medium of claim 14 , wherein the first mapping can be modified without modifying the program.

22. The non-transitory computer-readable medium of claim 14 , further comprising instructions for carrying out the steps of:

consulting a second mapping that maps a third message to the second message, wherein the second mapping differs from the first mapping, wherein the third message differs from the first message, wherein the third message comprises a rule-specific error message that indicates one or more rules that were violated by a portion of a document, and wherein the second mapping is not embodied in executable code; and

outputting the second message in response to a determination that the third message is mapped to the second message.

23. The non-transitory computer-readable medium of claim 14 , wherein the particular implementation context is a network configuration context.

24. The non-transitory computer-readable medium of claim 14 , wherein the first message indicates that a particular attribute must be specified for a particular element type, and wherein the second message indicates that a server lacks an Internet Protocol (IP) address.

25. The non-transitory computer-readable medium of claim 14 , wherein the first message indicates that the content of a particular element is incomplete, and wherein the second message indicates that a server is not connected to a network.

26. The non-transitory computer-readable medium of claim 14 , wherein the first message indicates that an element with a particular identifier must appear in the document, and wherein the second message indicates that a network lacks a subnet that is identified by the particular identifier.

Assignments (2)
MERGER AND CHANGE OF NAME Recorded Dec 16, 2015
From: ORACLE USA, INC.; SUN MICROSYSTEMS, INC.; ORACLE AMERICA, INC.
To: ORACLE AMERICA, INC.
Reel/Frame 037311/0150 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 9, 2004
From: HATTIANGADI, ANAND; CLARK, JAMES ANDREW; KRUPNIKOV, KONSTANTIN
To: SUN MICROSYSTEMS, INC.
Reel/Frame 015459/0468 →