Computer implemented system and method of transforming a source file into a transfprmed file using a set of trigger instructions

• US 20040049738A1
• Filed: 08/18/2003
• Published: 03/11/2004
• Est. Priority Date: 08/17/2000
• Status: Abandoned Application

• Current Assignee: Robert James Cullen Thompson, Stephen Sebastian Peruch
• Original Assignee: Robert James Cullen Thompson, Stephen Sebastian Peruch
• Inventors: Peruch, Stephen Sebastian, Thompson, Robert James Cullen
• Application Number:
  US10/362,032
• Publication Number:
  US 20040049738A1
• Time in Patent Office: Days
• US Class Current: 715/513
• CPC Class Codes: G06F 16/116 Details of conversion of file system types or formats

Abstract

A computer implemented method of defining a set of trigger instructions corresponding to a source file type, the source file type including a plurality of data segments and the method including the steps of: receiving a source file having a source file type; displaying the source file; selecting one of the data segments; defining a data segment trigger instruction corresponding to that selected data segment; and storing that data segment trigger instruction in a trigger instruction store.

Claims

1. A computer implemented method of defining a set of trigger instructions corresponding to a source file type, the source file type including a plurality of data segments and the method including the steps of:

(a) receiving a source file having a source file type;

(b) displaying the source file;

(c) selecting one of the data segments;

(d) defining a data segment trigger instruction corresponding to that selected data segment; and

(e) storing that data segment trigger instruction in a trigger instruction store.

2. A method according to claim 1 wherein the trigger instruction store is in a file.

3. A method according to claim 1 wherein the trigger instruction store is in a database.

4. A method according to claim 1 wherein the set of trigger instructions includes data segment trigger instructions, source file type trigger instructions, function calls, statement calls, regional definitions, conditional statements, annotations and processing instructions.

5. A method according to claim 1 wherein the method further includes the additional steps of repeating steps (c) to (e) until a plurality of the data segments each have a corresponding data segment trigger instruction.

6. A method according to claim 1 wherein the step of defining the data segment trigger instruction corresponding to that selected data segment includes the steps of:

(a) identifying location information corresponding to that selected data segment; and

(b) defining structural information corresponding to that selected data segment.

7. A method according to claim 6 wherein the step of identifying location information corresponding to that selected data segment includes the step of receiving the location information from a user.

8. A method according to claim 6 wherein the step of identifying location information corresponding to that selected data segment includes the step of extracting the location information from the source file.

9. A method according to claim 6 wherein the data segment location information includes one or more of:

(i) data segment position information;

or

(ii) data segment pattern information.

10. A method according to claim 1 wherein the step of selecting one of the data segments is performed in response to a user supplied data segment selection.

11. A method according to claim 6 wherein the step of defining structural information corresponding to that selected data segment includes the step of receiving the structural information from a user.

12. A method according to claim 6 wherein the structural information includes one or more of:

(i) data segment names;

(ii) data segment attribute settings;

or

(iii) data segment hierarchical positioning information.

13. A method according to claim 1 wherein the step of defining a data segment trigger instruction corresponding to that selected data segment is achieved using a trigger mapping tool.

14. A method according to claim 1 wherein method further includes the additional steps of:

(a) defining source file type trigger instructions corresponding to the source file type;

(b) storing these instructions in the trigger instruction store.

15. A method according to claim 14 wherein the source file type trigger instructions include instructions relating to one or more of:

(i) transformed file delivery information;

(ii) transformed file conversion information;

(iii) transformed file encryption values;

(iv) transformed file elements;

(v) transformed file attributes;

(vi) transformed file namespaces;

(vii) transformed file data types;

(viii) transformed file data values;

or

(ix) conditional statements that call other region trigger groups or triggers.

16. A method according to claim 15 wherein the transformed file conversion information includes conversion information relating to one or more of the following formats:

(a) XML format;

(b) facsimile format;

(c) email format;

(d) printing format;

(e) HTML format;

(f) PDF format;

(g) FTP format;

(h) EDI format;

(i) pre-printed form format;

(j) unprinted form format;

(k) graphic file format;

or

(l) an application program format.

17. A method according to claim 16 wherein the application program format includes one or more of:

(a) word processor format;

(b) spreadsheet format;

(c) database format;

(d) accounting software format;

(e) graphic software format;

(f) invoice processing software format;

(g) Financial Management Information Systems (FMIS) software;

(h) Enterprise Resource Planning (ERP) software;

(i) Customer Resource Management systems (CRM) software;

(j) Human Resources (HR) systems software;

or

(k) Manufacturing systems software.

18. A method according to claim 1 wherein the transformed delivery information includes delivery information relating to one or more of the following destinations:

(a) email addresses;

(b) facsimile numbers;

(c) postal addresses;

(d) target printers;

(e) IP addresses;

(f) system directories;

or

(g) message queues.

20. A system according to claim 18 wherein the set of trigger instructions includes data segment trigger instructions, source file type trigger instructions, function calls, statement calls, conditional statements and processing instructions.

21. A system according to claim 18 wherein system is repeatedly used until a plurality of data segments each have a corresponding data segment trigger instruction.

22. A system according to claim 18 wherein the definer, which defines the data segment trigger instruction corresponding to that selected data segment:

(a) identifies location information corresponding to that selected data segment; and

(b) defines structural information corresponding to that selected data segment.

23. A system according to claim 22 wherein the system identifies location information corresponding to that selected data segment by receiving the location information from a user.

24. A system according to claim 22 wherein the system identifies location information corresponding to that selected data segment by extracting the location information from the source file.

25. A system according to claim 22 wherein the data segment location information includes one or more of:

(i) data segment position information;

or

(ii) data segment pattern information.

26. A system according to claim 18 wherein the selector selects one of the data segments in response to a user supplied data segment selection.

27. A system according to claim 18 wherein the definer defines structural information corresponding to that selected data segment by receiving the structural information from a user.

28. A system according to claim 27 wherein the structural information includes one or more of:

(i) data segment names;

(ii) data segment attribute settings;

(iii) data segment hierarchical positioning information;

or

(iv) data segment value.

29. A system according to claim 28 wherein the definer is a trigger mapping tool.

30. A system according to claim 22 wherein the system:

(a) defines source file type trigger instructions corresponding to the source file type; and

(b) stores these instructions in the trigger instruction store.

31. A system according to claim 30 wherein the source file type trigger instructions include instructions relating to one or more of:

(i) transformed file delivery information;

(ii) transformed file conversion information;

(iii) transformed file encryption values;

(iv) transformed file elements;

(v) transformed file attributes;

(vi) transformed file namespaces;

(vii) transformed file data types;

or (viii) transformed file data values.

32. A system according to claim 31 wherein the transformed file conversion information includes conversion information relating to one or more of the following formats:

(a) XML format;

(b) facsimile format;

(c) email format;

(d) printing format;

(e) HTML format;

(f) PDF format;

(g) FTP format;

(h) EDI format;

(i) pre-printed form format;

(j) unprinted form format;

(k) graphic file format;

or

(l) an application program format.

33. A system according to claim 32 wherein the application program format includes one or more of:

(a) word processor format;

(b) spreadsheet format;

(c) database format;

(d) accounting software format;

(e) graphic software format;

(f) invoice processing software format;

(g) Financial Management Information Systems (FMIS) software;

(h) Enterprise Resource Planning (ERP) software;

(i) Customer Resource Management systems (CRM) software;

(j) Human Resources (HR) systems software;

(k) Manufacturing systems software;

or

(l) Single Object Application Protocol syntax

34. A system according to claim 31 wherein the transformed delivery information includes delivery information relating to one or more of the following destinations:

(a) email addresses;

(b) facsimile numbers;

(c) postal addresses;

(d) target printers;

(e) IP addresses;

(f) system directories;

or

(g) message queue.

19. A computer implemented system for defining a set of trigger instructions corresponding to a source file type, the source file type including a plurality of data segments and the system including:

(a) a receiver which receives a source file having a source file type;

(b) a display which displays the source file;

(c) a selector which selects one of the data segments;

(d) a definer which defines a data segment trigger instruction corresponding to that data segment; and

(g) storage means which stores that data segment trigger instruction in a trigger instruction store.

35. A computer implemented method of transforming a source file into a transformed file using a set of trigger instructions, wherein:

the source file includes at least one data segment;

the transformed file includes at least one transformed data segment which includes the at least one data segment and structural information corresponding to that segment; and

the set of trigger instructions defines at least;

(i) the location of the data segment within the source file; and

(ii) the structural information corresponding to the segment;

and wherein the method includes the steps of

(a) applying the set of trigger instructions to the source file to;

(i) locate the data segment; and

(ii) add the structural information to the data segment to produce the transformed data segment; and

(b) storing the transformed data segment in the transformed file.

36. A method according to claim 35 wherein the set of trigger instructions includes data segment trigger instructions, source file type trigger instructions, function calls, statement calls, processing instructions and conditional statements.

37. A method according to claim 35 wherein the source file includes a plurality of data segments contained within logical regions within the file, at least some of which are relevant data segments each having a corresponding data segment trigger instruction contained within a corresponding regional trigger group.

38. A method according to claim 35 wherein the method further includes the additional steps of repeating steps (a) and (b) until each relevant data segment has:

(v) been located; and

(vi) had structural data added to it to produce a corresponding relevant transformed data segment;

and until each of the relevant transformed data segments has been stored in the transformed file.

39. A method according to claim 35 wherein there are a plurality of source files, each having a corresponding source file type.

40. A method according to claim 39 wherein each source file type has a corresponding set of source file type trigger instructions, each contained in one or more trigger instructions files.

41. A method according to claim 36 wherein the data segment trigger instructions include one or more of:

(i) data segment location information;

(ii) data segment structural information;

or

(iii) data segment conditional information.

42. A method according to claim 41 wherein the data segment location information includes one or more of:

(i) data segment position information;

or

(ii) data segment pattern information.

43. A method according to claim 41 wherein the data segment structural information includes one or more of:

(i) data segment names;

(ii) data segment attribute settings;

(iii) data segment hierarchical positioning information;

or

(iv) data segment value.

44. A method according to claim 35 wherein the step of applying the set of trigger instructions to the source file to produce the transformed file is preceded by the steps of:

(a) receiving a received source file;

(b) identifying its corresponding received source file type; and

(c) identifying that source file type'"'"'s corresponding set of trigger instructions.

45. A method according to claim 35 wherein the step of storing the transformed data segment in the transformed file includes the step of storing each of the transformed data segments in the transformed file as they are created.

46. A method according to claim 36 wherein the source file type trigger instructions include instructions relating to one or more of:

(i) transformed file delivery information;

(ii) transformed file conversion information;

(iii) transformed file encryption values;

(iv) transformed file elements;

(v) transformed file attributes;

(vi) transformed file namespaces;

r (vii) transformed file data types;

or (viii) transformed file data values.

47. A method according to claim 35 wherein the source file is a relatively unstructured data file.

48. A method according to claim 35 wherein the source file is a generic text data file.

49. A method according to claim 48 wherein the source file is a print file.

50. A method according to claim 35 wherein the transformed file is a relatively structured data file.

51. A method according to claim 35 wherein the transformed file is an XML file.

52. A computer implemented system for transforming a source file into a transformed file using a set of trigger instructions, wherein:

the source file includes at least one data segment;

the transformed file includes at least one transformed data segment which includes the at least one data segment and structural information corresponding to the segment; and

the set of trigger instructions defines at least;

(i) the location of the data segment within the source file; and

(ii) the structural information corresponding to that segment;

and wherein the system;

(a) applies the set of trigger instructions to the source file to;

(i) locate the data segment; and

(ii) add the structural information to the data segment to produce the transformed data segment; and

(b) stores the transformed data segment in the transformed file.

53. A system according to claim 52 wherein the set of trigger instructions includes data segment trigger instructions, source file type trigger instructions, function calls, statement calls, processing instructions and conditional statements.

54. A system according to claim 52 wherein the source file includes a plurality of data segments, at least some of which are relevant data segments each having a corresponding data segment trigger instruction.

55. A system according to claim 52 wherein the system repeatedly performs functions (a) and (b) until each relevant data segment has:

(vii) been located; and

(viii) had structural data added to it to produce a corresponding relevant transformed data segment;

and until each of the relevant transformed data segments has been stored in the transformed file.

56. A system according to claim 52 wherein there are a plurality of source files, each having a corresponding source file type.

57. A system according to claim 56 wherein each source file type has a corresponding set of trigger instructions.

58. A system according to claim 53 wherein the data segment trigger instructions include one or more of:

(i) data segment location information;

or

(ii) data segment structural information.

59. A system according to claim 58 wherein the data segment location information includes one or more of:

(i) data segment position information;

or

(ii) data segment pattern information.

60. A system according to claim 58 or 59 wherein the data segment structural information includes one or more of:

(i) data segment names;

(ii) data segment attribute settings;

or

(iii) data segment hierarchical positioning information.

61. A system according to claim 52 wherein the system applies the set of trigger instructions to the source file to produce the transformed file after it:

(a) receives a received source file;

(b) identifies its corresponding received source file type; and

(c) identifies that source file type'"'"'s corresponding set of trigger instructions.

62. A system according to claim 52 wherein the system stores each of the transformed data segments in the transformed file as they are created.

63. A system according to claim 53 wherein the source file type trigger instructions include instructions relating to one or more of:

(i) transformed file delivery information;

(ii) transformed file conversion information;

(iii) transformed file encryption values;

(iv) transformed file elements;

(v) transformed file attributes;

(vi) transformed file namespaces;

(vii) transformed file data types;

or

(viii) transformed file data values.

64. A system according to claim 52 wherein the source file is a relatively unstructured data file.

65. A system according to claim 52 wherein the source file is a generic text data file.

66. A system according to claim 65 wherein the source file is a print file.

67. A system according to claim 52 wherein the transformed file is a relatively structured data file.

68. A system according to claim 52 wherein the transformed file is an XML file.

69. A computer implemented method of converting a transformed file into one or more object files and delivering the object files to one or more destinations, the transformed file including at least transformed file conversion information and transformed file delivery information, the method including the steps of:

(a) receiving the transformed file;

(b) retrieving the conversion information;

(c) converting the transformed file into the one or more object files in accordance with the conversion information;

(d) retrieving the delivery information; and

(e) delivering the one or more object files to the one or more destinations in accordance with the delivery information.

70. A method according to claim 69 wherein the step of converting the transformed file into one or more object files in accordance with the conversion information includes the step of converting the transformed file into one or more object files in one or more of the following formats:

(a) XML format;

(b) facsimile format;

(c) email format;

(d) printing format;

(e) HTML format;

(f) PDF format;

(g) FTP format;

(h) EDI format;

(i) pre-printed form format;

(j) unprinted form format;

r

(k) an application program format;

or

(l) message queue format.

71. A method according to claim 70 wherein the application program format includes one or more of:

(m) word processor format;

(n) spreadsheet format;

(o) database format;

(p) accounting software format;

(q) graphic software format;

(r) invoice processing software format;

(s) Financial Management Information Systems (FMIS) software;

(t) Enterprise Resource Planning (ERP) software;

(u) Customer Resource Management systems (CRM) software;

(v) Human Resources (HR) systems software;

(w) Manufacturing systems software;

or

(x) Message Queue system software.

72. A method according to claim 69 wherein the destinations include one or more of:

(a) email addresses;

(b) facsimile numbers;

(c) postal addresses;

(d) target printers;

(e) IP addresses;

or

(f) system directories;

or

(g) message queue.

73. A method according to claim 69 wherein the transformed file is a relatively structured data file.

74. A method according to claim 69 wherein the transformed file is in XML format.

75. A computer implemented system for converting a transformed file into one or more object files and delivering the object files to one or more destinations, the transformed file including at least transformed file conversion information and transformed file delivery information, and the system including:

(a) a receiver which receives the transformed file;

(b) a retriever which retrieves the conversion information;

(c a converter which converts the transformed file into the one or more object files in accordance with the conversion information;

(d) a retriever which retrieves the delivery information; and

(e) a deliverer which delivers the one or more object files to the one or more destinations in accordance with the delivery information.

76. A system according to claim 75 wherein the converter converts the transformed file into one or more object files in one or more of the following formats:

(a) XML format;

(b) facsimile format;

(c) email format;

(d) printing format;

(e) HTML format;

(f) PDF format;

(g) FTP format;

(h) EDI format;

(i) pre-printed form format;

(j) unprinted form format;

(k) an application program format;

or

(l) message queue format.

77. A system according to claim 76 wherein the application program format includes one or more of:

(a) word processor format;

(b) spreadsheet format;

(c) database format;

(d) accounting software format;

(e) invoice processing software format;

or

(f) message queue software format.

78. A system according to claim 75 wherein the destinations include one or more of:

(a) email addresses;

(b) facsimile numbers;

(c) postal addresses;

(d) target printers;

(e) IP addresses;

or

(f) message queue.

79. A system according to claim 75 wherein the transformed file is a relatively structured file.

80. A system according to claim 75 wherein the transformed file is in XML format.

81. A computer implemented method of defining a set of trigger instructions corresponding to a source file type, the source file type including a plurality of logical data regions each containing a plurality of data segments and the method including the steps of:

(a) receiving a source file having a source file type;

(b) displaying the source file;

(c) defining logical data regions within a source file;

(d) defining regional groups of triggers that relate to a particular region;

(e) selecting data segments from a region and assigning them to a regional group; and

(f) storing that data segment trigger instruction in a trigger instruction store.

82. A computer implemented method of transforming a source file into a transformed file using a set of trigger instructions, wherein:

the source file includes at least one logical data region;

the source file includes at least one data segment;

the transformed file includes at least one transformed data segment which includes the at least one data segment and structural information corresponding to that segment; and

the set of trigger instructions defines at least;

(i) the location of the data segment within the source file;