XML validation processing

• US 20050039166A1
• Filed: 07/09/2004
• Published: 02/17/2005
• Est. Priority Date: 07/11/2003
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Computer Associates Think Inc. (Broadcom, Inc.)
• Inventors: Betts, Christopher, Rogers, Tony
• Granted Patent: US 7,505,988 B2
• Time in Patent Office: Days
• US Class Current: 717/114
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• CPC Class Codes: G06F 40/226 Validation
• CPC Class Codes: G06F 8/70 Software maintenance or management

Abstract

A method for validating acquired data corresponding to a schema includes determining whether object classes of the acquired data corresponds to an object class of the schema, determining whether the acquired data conforms to a syntax of the corresponding object class of the schema, and determining whether the acquired data is executable when applied to the corresponding object class of the schema.

Claims

1. A method for validating acquired data corresponding to a schema, comprising:

determining whether object classes of the acquired data corresponds to an object class of the schema;

determining whether the acquired data conforms to a syntax of the corresponding object class of the schema; and

determining whether the acquired data is executable when applied to the corresponding object class of the schema.

2. The method of claim 1, wherein the acquired data is deemed valid when:

it is determined that the object classes of the acquired data corresponds an object class of the schema;

it is determined that the acquired data conforms to the syntax of the corresponding object class of the schema; and

it is determined that the acquired data is executable when applied to the corresponding object class of the schema.

3. The method of claim 1, wherein the schema is an XML schema.

4. A method for validating acquired data corresponding to a schema, comprising:

automatically converting the schema to a software data structure;

merging a shadow software functionality with the automatically converted software data structure to form a merged software;

determining whether object classes of the acquired data corresponds to an object class of the software data structure;

determining whether the acquired data conforms to a syntax of the corresponding object class of the software data structure; and

determining whether the acquired data is executable when applied to the corresponding object class of the software data structure.

5. The method of claim 4, wherein the acquired data is deemed valid when:

it is determined that object classes of the acquired data correspond to an object class of the software data structure;

it is determined that the acquired data conforms to the syntax of the corresponding object class of the software data structure; and

it is determined that the acquired data is executable when applied to the corresponding object class of the software data structure.

6. The method of claim 4, wherein the schema is an XML schema.

7. The method of claim 4, wherein:

the software data structure is a Java class;

the shadow software functionality is a shadow Java class; and

the merged software is a merged Java class.

8. The method of claim 7, wherein a JAXB compiler is used for automatically converting the schema to the Java class.

9. The method of claim 4, wherein:

the software data structure is a C# software data structure;

the shadow software functionality is a C# shadow software functionality; and

the merged software is a C# merged software.

10. The method of claim 4, wherein the merging of the shadow software functionality with the automatically converted software data structure to form a merged software comprises:

parsing the shadow software functionality into one or more sections;

determining if one or more characteristics are present in the parsed shadow software functionality that are not present in the software data structure; and

adding the one or more characteristics determined to be present in the parsed shadow software functionality that are not present in the software data structure to the software data structure when it is determined that there are one or more characteristics present in the parsed shadow software functionality that are not present in the software data structure.

11. The method of claim 10, wherein the one or more sections includes one or more of the following sections:

import statements;

implement clause;

extends clause;

comment block; and

main code block;

12. The method of claim 4, wherein merging the shadow software functionality with the automatically converted software data structure to form the merged software provides the merged software with extended functionality beyond the functionality of the converted software data structure.

13. The method of claim 4, additionally comprising compiling the merged software.

14. The method of claim 4, wherein the shadow software functionality is substantially syntactically correct.

15. A system for validating acquired data corresponding to a schema, comprising:

an object-class determining unit for determining whether object classes of the acquired data corresponds to an object class of the schema;

a syntax determining unit for determining whether the acquired data conforms to a syntax of the corresponding object class of the schema; and

an executability determining whether the acquired data is executable when applied to the corresponding object class of the schema.

16. The system of claim 15, wherein the acquired data is deemed valid when:

it is determined that the object classes of the acquired data corresponds an object class of the schema;

it is determined that the acquired data conforms to the syntax of the corresponding object class of the schema; and

it is determined that the acquired data is executable when applied to the corresponding object class of the schema.

17. The system of claim 15, wherein the schema is an XML schema.

18. A system for validating acquired data corresponding to a schema, comprising:

a converting unit for automatically converting the schema to a software data structure;

a merging unit for merging a shadow software functionality with the automatically converted software data structure to form a merged software;

an object-class determining unit for determining whether object classes of the acquired data corresponds to an object class of the software data structure;

a syntax determining unit for determining whether the acquired data conforms to a syntax of the corresponding object class of the software data structure; and

an executability determining unit for determining whether the acquired data is executable when applied to the corresponding object class of the software data structure

19. The system of claim 18, wherein the acquired data is deemed valid when:

it is determined that object classes of the acquired data correspond to an object class of the software data structure;

it is determined that the acquired data conforms to the syntax of the corresponding object class of the software data structure; and

it is determined that the acquired data is executable when applied to the corresponding object class of the software data structure.

20. The system of claim 18, wherein the schema is an XML schema.

21. The system of claim 18, wherein:

the software data structure is a Java class;

the shadow software functionality is a shadow Java class; and

the merged software is a merged Java class.

22. The system of claim 21, wherein a JAXB compiler is used for automatically converting the schema to the Java class.

23. The system of claim 18, wherein:

the software data structure is a C# software data structure;

the shadow software functionality is a C# shadow software functionality and the merged software is a C# merged software.

24. The system of claim 18, wherein the merging unit comprises:

a parsing unit for parsing the shadow software functionality into one or more sections;

a determining unit for determining if one or more characteristics are present In the parsed shadow software functionality that are not present in the software data structure; and

an adding unit for adding the one or more characteristics determined to be present in the parsed shadow software functionality that are not present in the software data structure to the software data structure when it is determined that there are one or more characteristics present in the parsed shadow software functionality that are not present in the software data structure.

25. The system of claim 24, wherein the one or more sections includes one or more of the following sections:

import statements;

implement clause;

extends clause;

comment block; and

main code block;

26. The system of claim 18, wherein merging the shadow software functionality with the automatically converted software data structure to form the merged software provides the merged software with extended functionality beyond the functionality of the converted software data structure.

27. The system of claim 18, additionally comprising compiling the merged software.

28. The system of claim 18, wherein the shadow software functionality is substantially syntactically correct.

29. A computer system comprising:

a processor; and

a program storage device readable by the computer system, embodying a program of instructions executable by the processor to perform method steps for validating acquired data corresponding to a schema, the method comprising;

determining whether the acquired data conforms to a syntax of the corresponding object class of the schema; and

determining whether the acquired data is executable when applied to the corresponding object class of the schema.

30. The computer system of claim 29, wherein the acquired data is deemed valid when:

it is determined that the object classes of the acquired data corresponds an object class of the schema;

it is determined that the acquired data conforms to the syntax of the corresponding object class of the schema; and

it is determined that the acquired data is executable when applied to the corresponding object class of the schema.

31. The computer system of claim 29, wherein the schema is an XML schema.

32. A computer system comprising:

a processor; and

a program storage device readable by the computer system, embodying a program of instructions executable by the processor to perform method steps for validating acquired data corresponding to a schema, the method comprising;

automatically converting the schema to a software data structure;

merging a shadow software functionality with the automatically converted software data structure to form a merged software;

determining whether object classes of the acquired data corresponds to an object class of the software data structure;

determining whether the acquired data conforms to a syntax of the corresponding object class of the software data structure; and

determining whether the acquired data is executable when applied to the corresponding object class of the software data structure.

33. The computer system of claim 32, wherein the acquired data is deemed valid when:

it is determined that object classes of the acquired data correspond to an object class of the software data structure;

it is determined that the acquired data conforms to the syntax of the corresponding object class of the software data structure; and

it is determined that the acquired data is executable when applied to the corresponding object class of the software data structure.

34. The computer system of claim 32, wherein the schema is an XML schema.

35. The computer system of claim 32, wherein:

the software data structure is a Java class;

the shadow software functionality is a shadow Java class; and

the merged software is a merged Java class.

36. The computer system of claim 35, wherein a JAXB compiler is used for automatically converting the schema to the Java class.

37. The computer system of claim 32, wherein:

the software data structure is a C# software data structure;

the shadow software functionality is a C# shadow software functionality; and

the merged software is a C# merged software.

38. The computer system of claim 32, wherein the merging of the shadow software functionality with the automatically converted software data structure to form a merged software comprises:

parsing the shadow software functionality into one or more sections;

determining if one or more characteristics are present in the parsed shadow software functionality that are not present in the software data structure; and

adding the one or more characteristics determined to be present in the parsed shadow software functionality that are not present in the software data structure to the software data structure when it is determined that there are one or more characteristics present in the parsed shadow software functionality that are not present in the software data structure.

39. The computer system of claim 38, wherein the one or more sections includes one or more of the following sections:

import statements;

implement clause;

extends clause;

comment block; and

main code block;

40. The computer system of claim 32, wherein merging the shadow software functionality with the automatically converted software data structure to form the merged software provides the merged software with extended functionality beyond the functionality of the converted software data structure.

41. The computer system of claim 32, additionally comprising compiling the merged software.

42. The computer system of claim 32, wherein the shadow software functionality is substantially syntactically correct.