Generating visual editors from schema descriptions

• US 7,039,859 B1
• Filed: 11/12/1998
• Issued: 05/02/2006
• Est. Priority Date: 11/12/1998
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Sundaresan, Neelakantan
• Primary Examiner(s): Herndon, Heather R.
• Assistant Examiner(s): DESAI, RACHNA SINGH
• Application Number:
  US09/191,281
• Time in Patent Office: 2,728 Days
• Field of Search: 707/513, 707/102, 715/513
• US Class Current: 715/229
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

A visual editor is automatically generated from an eXtensible Markup Language (XML) schema and then used to edit the data contained in corresponding XML documents. The entities within an XML schema are mapped to components of the visual editor, such as forms, widgets, etc., that are generated as class specifications. These class specifications can be customized through the use of a customization specification file, as desired. The class specifications are then instantiated as objects in a Java Virtual Machine to perform the functions of the visual editor.

Claims

1. A computer-implement method for generating a document editor, comprising:

(a) generating one or more class specifications in the computer from a schema for the document, wherein the class specifications identify user interface components of the editor corresponding to entities defined in the schema; and

(b) instantiating one or more objects in the computer from the class specifications to invoke the editor.

2. The method of claim 1 above, wherein the documents are eXtensible Markup Language (XML) documents and the schemas are XML schemas.

3. The method of claim 2 above, wherein the schemas are selected from a group including Document Type Definition (DTD) schemas, Document Content Definition (DCD) schemas, and XSchema schemas.

4. The method of claim 1 above, wherein the class specifications comprise Java class specifications.

5. The method of claim 1 above, wherein the generating step further comprises converting an entity defined in the schema into the class specification.

6. The method of claim 1 above, wherein the generating step further comprises the step of generating the class specifications in the computer from the schemas and one or more optional customization specifications.

7. The method of claim 6 above, wherein the optional customization specifications define what class names to generate for each entity defined in the schema.

8. The method of claim 1 above, wherein the class specifications include one or more specifications selected from a group comprising (1) a visual editor class specification, (2) a content implementation class specification, and a handler class specification.

9. The method of claim 1 above, further comprising mapping the entities defined in the schema to components of the editor.

10. The method of claim 1 above, wherein the entities are selected from a group comprising elements and attributes of elements.

11. The method of claim 10 above, wherein the attribute has a declaration selected from a group comprising mandatory, optional, and fixed value.

12. The method of claim 11 above, further comprising accepting user input for attributes having a mandatory declaration.

13. The method of claim 11 above, further comprising accepting user input for attributes having an optional declaration.

14. The method of claim 11 above, further comprising entering values from the schema for attributes having a fixed value declaration.

15. The method of claim 10 above, further comprising validating values entered for the attribute.

16. The method of claim 1 above, wherein the class specifications include at least one function for validating at least one entity defined in the schema.

17. The method of claim 1 above, wherein the generating step further comprises the step of generating the class specifications from a regular expression language comprising one or more declarations of elements enclosed within an element.

18. The method of claim 17 above, wherein the regular expression language includes one or more regular expression operators selected from a group comprising:

(1) a “

zero or more”

operator,

(2) a “

one or more”

operator,

(3) a “

one or the other”

operator,

(4) a “

one followed by the other”

operator,

(5) a “

zero or one”

operator,

(6) a “

grouping”

operator, and

(7) an “

any”

operator.

19. The method of claim 18 above, wherein the class specifications define one or more widgets that are associated with each of the operators.

20. The method of claim 1 above, wherein the class specifications define at least one widget associated with an entity in the schema.

21. The method of claim 1 above, further comprising identifying specific widget implementations for use with the editor.

22. The method of claim 1 above, further comprising customizing the editor for use with different regular expression operators.

23. The method of claim 1 above, further comprising attempting to solve correctness, optimization, or aesthetics related issues when generating the visual editor from the schema.

24. A computer-implemented apparatus for generating a document editor, comprising:

(a) a computer; and

(b) an editor maker, executed by the computer, for generating one or more class specifications in the computer from a schema for the document, wherein the class specifications identify user interface components of the editor corresponding to entities defined in the schema, and for instantiating one or more objects in the computer from the class specifications to invoke the editor.

25. The apparatus of claim 24 above, wherein the documents are eXtensible Markup Language (XML) documents and the schemas are XML schemas.

26. The apparatus of claim 25 above, wherein the schemas are selected from a group including Document Type Definition (DTD) schemas, Document Content Definition (DCD) schemas, and XSchema schemas.

27. The apparatus of claim 24 above, wherein the class specifications comprise Java class specifications.

28. The apparatus of claim 24 above, wherein the means for generating further comprises means for converting an entity defined in the schema into the class specification.

29. The apparatus of claim 24 above, wherein the means for generating further comprises means for generating the class specifications in the computer from the schemas and one or more optional customization specifications.

30. The apparatus of claim 29 above, wherein the optional customization specifications define what class names to generate for each entity defined in the schema.

31. The apparatus of claim 24 above, wherein the class specifications include one or more specifications selected from a group comprising (1) a visual editor class specification, (2) a content implementation class specification, and a handler class specification.

32. The apparatus of claim 24 above, further comprising means for mapping the entities defined in the schema to components of the editor.

33. The apparatus of claim 24 above, wherein the entities are selected from a group comprising elements and attributes of elements.

34. The apparatus of claim 33 above, wherein the attribute has a declaration selected from a group comprising mandatory, optional, and fixed value.

35. The apparatus of claim 34 above, further comprising means for accepting user input for attributes having a mandatory declaration.

36. The apparatus of claim 34 above, further comprising means for accepting user input for attributes having an optional declaration.

37. The apparatus of claim 34 above, further comprising means for entering values from the schema for attributes having a fixed value declaration.

38. The apparatus of claim 33 above, further comprising means for validating values entered for the attribute.

39. The apparatus of claim 24 above, wherein the class specifications include at least one function for validating at least one entity defined in the schema.

40. The apparatus of claim 24 above, wherein the means for generating further comprises means for generating the class specifications from a regular expression language comprising one or more declarations of elements enclosed within an element.

41. The apparatus of claim 40 above, wherein the regular expression language includes one or more regular expression operators selected from a group comprising:

(1) a “

zero or more”

operator,

(2) a “

one or more”

operator,

(3) a “

one or the other”

operator,

(4) a “

one followed by the other”

operator,

(5) a “

zero or one”

operator,

(6) a “

grouping”

operator, and

(7) an “

any”

operator.

42. The apparatus of claim 41 above, wherein the class specifications define one or more widgets that are associated with each of the operators.

43. The apparatus of claim 24 above, wherein the class specifications define at least one widget associated with an entity in the schema.

44. The apparatus of claim 24 above, further comprising means for identifying specific widget implementations for use with the editor.

45. The apparatus of claim 24 above, further comprising means for customizing the editor for use with different regular expression operators.

46. The apparatus of claim 24 above, further comprising means for attempting to solve correctness, optimization, or aesthetics related issues when generating the visual editor from the schema.

47. An article of manufacture embodying logic for performing a method for generating a document editor for use in an object-oriented computer system, the method comprising the steps of:

(a) generating one or more class specifications from a schema for the document, wherein the class specifications identify user interface components of the editor corresponding to entities defined in the schema; and

(b) instantiating one or more objects from the class specifications to invoke the editor.

48. The method of claim 47 above, wherein the documents are eXtensible Markup Language (XML) documents and the schemas are XML schemas.

49. The method of claim 48 above, wherein the schemas are selected from a group including Document Type Definition (DTD) schemas, Document Content Definition (DCD) schemas, and XSchema schemas.

50. The method of claim 47 above wherein the class specifications comprise Java class specifications.

51. The method of claim 47 above, wherein the generating step further comprises converting an entity defined in the schema into the class specification.

52. The method of claim 47 above, wherein the generating step further comprises the step of generating the class specifications in the computer from the schemas and one or more optional customization specifications.

54. The method of claim 47 above, wherein the class specifications include one or more specifications selected from a group comprising (1) a visual editor class specification, (2) a content implementation class specification, and a handler class specification.

55. The method of claim 47 above, further comprising mapping the entities defined in the schema to components of the editor.

56. The method of claim 47 above, wherein the entities are selected from a group comprising elements and attributes of elements.

57. The method of claim 56 above, wherein the attribute has a declaration selected from a group comprising mandatory, optional, and fixed value.

58. The method of claim 57 above, further comprising accepting user input for attributes having a mandatory declaration.

59. The method of claim 57 above, further comprising accepting user input for attributes having an optional declaration.

60. The method of claim 57 above, further comprising entering values from the schema for attributes having a fixed value declaration.

61. The method of claim 56 above, further comprising validating values entered for the attribute.

62. The method of claim 47 above, wherein the class specifications include at least one function for validating at least one entity defined in the schema.

63. The method of claim 47 above, wherein the generating step further comprises the step of generating the class specifications from a regular expression language comprising one or more declarations of elements enclosed within an element.

64. The method of claim 63 above, wherein the regular expression language includes one or more regular expression operators selected from a group comprising:

(1) a “

zero or more”

operator,

(2) a “

one or more”

operator,

(3) a “

one or the other”

operator,

(4) a “

one followed by the other”

operator,

(5) a “

zero or one”

operator,

(6) a “

grouping”

operator, and

(7) an “

any”

operator.

65. The method of claim 64 above, wherein the class specifications define one or more widgets that are associated with each of the operators.

66. The method of claim 47 above, wherein the class specifications define at least one widget associated with an entity in the schema.

67. The method of claim 47 above, further comprising identifying specific widget implementations for use with the editor.

68. The method of claim 47 above, further comprising customizing the editor for use with different regular expression operators.

69. The method of claim 47 above, further comprising attempting to solve correctness, optimization, or aesthetics related issues when generating the visual editor from the schema.

53. The method of clam 52 above, wherein the optional customization specifications define what class names to generate for each entity defined in the schema.