Methods, apparatuses, system, and articles for associating metadata with datastream

US 20040006745A1
Filed: 10/05/2001
Published: 01/08/2004
Est. Priority Date: 08/31/2001
Status: Abandoned Application

First Claim

Patent Images

1. A method comprising the step of:

a) associating metadata with a presentation datastream.

View all claims

1 Assignment

Timeline View

Assignment View

0 Petitions

Accused Products

Abstract

The disclosed methods, apparatuses, system, and articles can be used to associate metadata with a datastream, or to use metadata in the datastream to transform it into a different datastream. Through the use of metadata, the datastream can be used for purposes other than rendering a presentation. The metadata can also be used by a computer programmer to develop or modify software because the metadata can include extensive information regarding the application, data definition, user interface definition, and data used to render a datastream even though such information is not normally present in the datastream.

83 Citations

View as Search Results

216 Claims

1. A method comprising the step of:
- a) associating metadata with a presentation datastream.
- View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31)
- - 2. A method as claimed in claim 1 further comprising the step of:
    - b) using the metadata to extract at least one element from the presentation datastream by an application to process the data.
  - 3. A method as claimed in claim 2 wherein the presentation datastream is used to render a presentation, and the application processes the data for a purpose other than rendering the presentation.
  - 4. A method as claimed in claim 2 wherein the presentation datastream is used to generate a presentation, and the application processes the data for a purpose other than rendering the presentation.
  - 5. A method as claimed in claim 1 further comprising the step of:
    - b) using the metadata to extract at least one element from the presentation datastream for storage in a data storage unit.
  - 6. A method as claimed in claim 5 wherein the element of the presentation datastream is used to render a presentation, and the element is stored in the data storage unit for a purpose other than rendering the presentation.
  - 7. A method as claimed in claim 5 wherein the presentation datastream is not used to generate a presentation, and the data storage unit stores the element for a purpose other than rendering the presentation.
  - 8. A method as claimed in claim 1 wherein the metadata identifies an application that generated the presentation datastream.
  - 9. A method as claimed in claim 8 wherein an application generates the presentation datastream, and the metadata identifies a memory location of the application in a computing environment.
  - 10. A method as claimed in claim 8 wherein the metadata identifies a purpose of the application.
  - 11. A method as claimed in claim 1 wherein the metadata identifies a data definition defining data used to generate the presentation datastream.
  - 12. A method as claimed in claim 11 wherein the metadata identifies a field length of data stored in the data storage unit.
  - 13. A method as claimed in claim 11 wherein the metadata identifies a data type of the presentation data stored in the data storage unit.
  - 14. A method as claimed in claim 11 wherein the metadata identifies a variable name associated with data.
  - 15. A method as claimed in claim 11 wherein the metadata defines permissible values for the presentation data.
  - 16. A method as claimed in claim 15 wherein the metadata identifies the permissible values for the presentation data as a range of values.
  - 17. A method as claimed in claim 15 wherein the metadata identifies the permissible values for the presentation data as a group of permissible values.
  - 18. A method as claimed in claim 1 wherein the metadata identifies a user interface definition for the presentation data.
  - 19. A method as claimed in claim 18 wherein the user interface definition includes a name of the data rendered on the user interface, and the metadata identifies the name.
  - 20. A method as claimed in claim 18 wherein the user interface definition identifies screen position of data on a user interface display screen, and the metadata identifies the screen position.
  - 21. A method as claimed in claim 20 wherein the screen position is indicated by character row and column on the user interface display screen, and the metadata identifies the row and column of respective data.
  - 22. A method as claimed in claim 20 wherein the user interface definition includes a variable name associated with a data value, and the metadata identifies the variable name and data value.
  - 23. A method as claimed in claim 20 wherein the metadata identifies a screen to which the presentation data pertains.
  - 24. A method as claimed in claim 1 wherein the presentation datastream includes an instruction and data, the instruction indicating the display position of the data in a presentation, and the data indicating at least one character for rendering in the presentation, the metadata associated with the instruction and data.
  - 25. A method as claimed in claim 1 further comprising the step of:
    - b) obtaining the metadata.
  - 26. A method as claimed in claim 25 wherein the metadata is obtained by using a mapping of elements in the presentation datastream to corresponding metadata.
  - 27. A method as claimed in claim 25 wherein the metadata is obtained by using a mapping of elements in the presentation datastream to corresponding metatags, and applying the corresponding metatags to the elements of the presentation datastream.
  - 28. A method as claimed in claim 27 wherein the metadata is generated in step (b) as an eXstensible Markup Language (XML) document.
  - 29. A method as claimed in claim 1 further comprising the step of:
    - b) using the metadata to modify at least one of an application, a user interface definition, and a data definition used to generate the presentation datastream.
  - 30. A method as claimed in claim 1 further comprising the step of:
    - b) developing an application using the metadata in the datastream.
  - 31. A method as claimed in claim 1 further comprising the step of:
    - b) modifying an application using the metadata in the datastream.

32. A method comprising the step of:
- a) using metadata in a first datastream in a context of a first computing environment to map at least one element of the first datastream to a corresponding element of a second datastream in a context of a second computing environment.
- View Dependent Claims (33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58)
- - 33. A method as claimed in claim 32 wherein the mapped element of the second datastream is used for a purpose other than to render a presentation.
  - 34. A method as claimed in claim 32 wherein the mapped element of the second datastream is provided to an application for processing thereof.
  - 35. A method as claimed in claim 34 wherein the mapped element is used to render a presentation, and the element is provided to the application that processes the element for a purpose other than to render the presentation.
  - 36. A method as claimed in claim 34 wherein the mapped element of the second datastream is not used to render a presentation, and the application processes the element for a purpose other than to render the presentation.
  - 37. A method as claimed in claim 32 wherein the mapped element of the second datastream is provided to a data storage unit for storage.
  - 38. A method as claimed in claim 37 wherein the mapped element of the second datastream is used to render a presentation, and the mapped element is provided to the data storage unit for storage for a purpose other than to render a presentation.
  - 39. A method as claimed in claim 37 wherein the mapped element of the second datastream is not used to render a presentation, and the mapped element of the second datastream is provided to the data storage unit for a purpose other than to render the presentation.
  - 40. A method as claimed in claim 32 wherein the first and second datastreams are presentation datastreams.
  - 41. A method as claimed in claim 40 wherein the presentation datastreams include at least one instruction and data, the instruction indicating a screen display position of the data in a presentation, and the data indicating at least one character for rendering in the presentation at the screen position indicated by the instruction, the metadata used to map the instruction and data of the first datastream to corresponding instruction and data of the second datastream.
  - 42. A method as claimed in claim 40 wherein the first datastream is one of VT52, VT100, VT220-78, VT220-8, VT320-7, VT320-8, VT420-7, VT420-8, VT525-7, VT525-8, 3270, 5250, 3270E, 5250E, TN3270E, TN5250E, TDG, SCO ANSI, BBS ANSI, AT 386, AIXTERM, WYSE 50, WYSE 60, TVI 925, and TVI 950 terminal datastreams, and the second datastream is one of HTTP, SGML, HTML, DHTML, XML, WML, WAP, tagging language, and byte code datastreams.
  - 43. A method as claimed in claim 32 wherein the metadata identifies an application that generated the first datastream.
  - 44. A method as claimed in claim 32 wherein an application generates the first datastream, and the metadata identifies a memory location of the application in the first computing environment.
  - 45. A method as claimed in claim 32 wherein an application generates the first datastream, and the metadata identifies a purpose of the application.
  - 46. A method as claimed in claim 32 wherein the metadata identifies a data definition defining data used to generate the first datastream.
  - 47. A method as claimed in claim 46 wherein the metadata identifies a field length of the data.
  - 48. A method as claimed in claim 46 wherein the metadata identifies a type of the data.
  - 49. A method as claimed in claim 46 wherein the metadata identifies a variable name associated with the data.
  - 50. A method as claimed in claim 46 wherein the metadata defines permissible values for the data.
  - 51. A method as claimed in claim 50 wherein the metadata identifies the permissible values for the data as a range of values.
  - 52. A method as claimed in claim 51 wherein the metadata identifies the permissible values for the presentation data as a group of permissible values.
  - 53. A method as claimed in claim 32 wherein the metadata identifies a user interface definition.
  - 54. A method as claimed in claim 53 wherein the user interface definition includes a variable name of data to be rendered in a presentation based on the second datastream.
  - 55. A method as claimed in claim 53 wherein the user interface definition identifies screen position of data on a user interface display screen in a presentation to be rendered by the second datastream, and the metadata identifies the screen position of the data.
  - 56. A method as claimed in claim 55 wherein the screen position is indicated by character row and column on the user interface display screen of a presentation rendered by the second datastream, and the metadata identifies the row and column of the respective data.
  - 57. A method as claimed in claim 32 wherein the user interface definition includes a variable name associated with a data value, and the metadata identifies the variable name and data value.
  - 58. A method as claimed in claim 32 wherein the metadata identifies a presentation screen rendered based on the second datastream.

59. A method comprising the steps of:
- a) using metadata to extract elements of a presentation datastream; and
  
  b) using the extracted elements by processing or storing the extracted elements in addition to rendering the presentation.

60. A method comprising the steps of:
- a) generating a first datastream in a context of a first computing environment;
  
  b) associating metadata with the first datastream to produce a second datastream;
  
  c) transmitting the second datastream to a second computing environment;
  
  d) receiving the second datastream at the second computing environment;
  
  e) transforming the second datastream into a third datastream using the metadata, the third datastream in the context of a third computing environment; and
  
  f) transmitting the third datastream to the third computing environment.
- View Dependent Claims (61, 62, 63, 64, 65, 67, 68, 69, 70, 71)
- - 61. A method as claimed in claim 60 wherein the first and second datastreams are presentation datastreams.
  - 62. A method as claimed in claim 60 wherein the third datastream is used for a purpose other than to render a presentation.
  - 63. A method as claimed in claim 60 wherein the third datastream is provided to an application for processing.
  - 64. A method as claimed in claim 63 wherein the third datastream is used to render a presentation, and the application processes the third datastream for a purpose other than to render a presentation.
  - 65. A method as claimed in claim 63 wherein the third datastream is not used to render a presentation, and the application processes the third datastream for a purpose other than to render the presentation.
  - 67. A method as claimed in claim 63 wherein the third datastream is provided to a data storage unit for storage.
  - 68. A method as claimed in claim 67 wherein the third datastream is used to render a presentation, and the third datastream is stored in the data storage unit for a purpose other than to render the presentation.
  - 69. A method as claimed in claim 67 wherein the third datastream is not used to render a presentation, and the third datastream is stored in the data storage unit for a purpose other than to render the presentation.
  - 70. A method as claimed in claim 60 wherein the first datastream is one of VT52, VT100, VT220-78, VT220-8, VT320-7, VT320-8, VT420-7, VT420-8, VT525-7, VT525-8, 3270, 5250, 3270E, 5250E, TN3270E, TN5250E, TDG, SCO ANSI, BBS ANSI, AT 386, AIXTERM, WYSE 50, WYSE 60, TVI 925, and TVI 950 terminal datastreams, and the third datastream is one of HTTP, SGML, HTML, DHTML, XML, WML, WAP, tagging language, and byte code datastreams.
  - 71. A method as claimed in claim 60 wherein the presentation datastreams include at least one instruction and data, the instruction indicating a screen display position of the data in a presentation, and the data indicating at least one character for rendering in the presentation at the screen position indicated by the instruction, the metadata used to map the instruction and data of the first datastream to corresponding instruction and data of the third datastream.

72. A method comprising the step of:
- a) associating metadata with an interactive datastream.
- View Dependent Claims (73, 74, 75, 76, 77, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106)
- - 73. A method as claimed in claim 72 wherein the interactive datastream is generated by computing environments that communicate with one another.
  - 74. A method as claimed in claim 72 wherein the metadata is associated with at least one element of the datastream to identify the element so as to permit transformation of the element from a context of one computing environment to a context of another computing environment.
  - 75. A method as claimed in claim 72 wherein a first computing environment executes an application to generate at least one element of the datastream, and a second computing environment renders a presentation using the transformed element.
  - 76. A method as claimed in claim 72 wherein the first computing environment executes a first application to generate at least one element of the datastream, and the second computing environment executes a second application using the transformed element of the datastream.
  - 77. A method as claimed in claim 72 wherein the first computing environment executes an application to generate at least one element of the datastream, and the second computing environment stores the transformed element in a data storage unit.
  - 84. A computing environment as claimed in claim 72 wherein the metadata module associates the metadata with the presentation datastream so that at least one element of the presentation datastream can be stored in a data storage unit of another computing environment.
  - 85. A computing environment as claimed in claim 84 wherein the element is used to render a presentation, and the presentation datastream is stored in the data storage unit for a purpose other than to render a presentation.
  - 86. A computing environment as claimed in claim 84 wherein the element of the presentation datastream is not used to render a presentation and the element is stored in the data storage unit for a purpose other than to render a presentation.
  - 87. A computing environment as claimed in claim 72 wherein the metadata identifies an application that generated the presentation data.
  - 88. A computing environment as claimed in claim 72 wherein the metadata identifies a memory location of the application in a computing environment.
  - 89. A computing environment as claimed in claim 72 wherein the metadata identifies a purpose of the application.
  - 90. A computing environment as claimed in claim 72 wherein the metadata identifies a data definition defining data used to generate the presentation datastream.
  - 91. A computing environment as claimed in claim 72 wherein the metadata identifies a field length of data stored in the data storage unit.
  - 92. A computing environment as claimed in claim 72 wherein the metadata identifies a data type of the data stored in the data storage unit.
  - 93. A computing environment as claimed in claim 72 wherein the metadata identifies a variable name associated with data.
  - 94. A computing environment as claimed in claim 72 wherein the metadata defines permissible values for the data.
  - 95. A computing environment as claimed in claim 94 wherein the metadata identifies the permissible values for the data as a range of values.
  - 96. A computing environment as claimed in claim 94 wherein the metadata identifies the permissible values for the data as a group of permissible values.
  - 97. A computing environment as claimed in claim 72 wherein the metadata identifies a user interface definition for the data.
  - 98. A computing environment as claimed in claim 97 wherein the user interface definition includes a variable identifying the data in the datastream to be rendered on the user interface, and the metadata identifies the name.
  - 99. A computing environment as claimed in claim 97 wherein the user interface definition identifies screen position of data on a user interface display screen, and the metadata identifies the screen position.
  - 100. A computing environment as claimed in claim 97 wherein the screen position is indicated by character row and column on the user interface display screen, and the metadata identifies the character row and column of respective data in the presentation datastream.
  - 101. A computing environment as claimed in claim 97 wherein the user interface definition includes a variable name associated with a data value, and the metadata identifies the variable name and data value.
  - 102. A computing environment as claimed in claim 97 wherein the metadata identifies a screen to which the presentation datastream pertains.
  - 103. A computing environment as claimed in claim 72 wherein the presentation datastream includes an instruction and data, the instruction indicating the display position of the data in a presentation, and the data indicating at least one character for rendering in the presentation, the metadata associated with the instruction and data.
  - 104. A computing environment as claimed in claim 72 wherein the metadata module obtains the metadata from a memory device in the computing environment.
  - 105. A computing environment as claimed in claim 72 wherein the metadata module generates the metadata using metatags and a mapping of elements of the presentation datastream to corresponding metatags, and applying the corresponding metatags to corresponding data in the presentation datastream.
  - 106. A computing environment as claimed in claim 72 wherein the metadata is included with the presentation datastream in an eXstensible Markup Language (XML) document.

78. A computing environment executing a metadata module to associate metadata with a presentation datastream.
- View Dependent Claims (79, 80, 81, 82, 83)
- - 79. A computing environment as claimed in claim 78 wherein the metadata module associates the metadata with the presentation datastream to permit another computing environment to use the element from the presentation datastream for a purpose other than to render a presentation.
  - 80. A computing environment as claimed in claim 78 wherein the metadata module associates the metadata with the presentation datastream so that at least one element of the presentation datastream can be used by an application executed in another computing environment.
  - 81. A computing environment as claimed in claim 80 wherein the application processes the presentation datastream for a purpose other than to render a presentation.
  - 82. A computing environment as claimed in claim 80 wherein the presentation datastream is used to render a presentation, and the application processes the presentation for a purpose other than to render the presentation.
  - 83. A computing environment as claimed in claim 80 wherein the presentation datastream is not used to render a presentation, and the application processes the presenation for a purpose other than to render the presentation.

107. A computing environment receiving a first datastream having metadata, the computing environment comprising a metadata interpreter using the metadata in the first datastream to map at least one element of the first datastream to a corresponding element of a second datastream.
- View Dependent Claims (108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133)
- - 108. A computing environment as claimed in claim 107 wherein the second datastream is used for a purpose other than to render a presentation.
  - 109. A computing environment as claimed in claim 107 wherein the second datastream is provided to an application for processing.
  - 110. A computing environment as claimed in claim 109 wherein the second datastream is used to render a presentation and the application processes the second datastream for a purpose other than to render a presentation.
  - 111. A computing environment as claimed in claim 109 wherein the second datastream is not used to render a presentation and the application processes the second datastream for a purpose other than to render a presentation.
  - 112. A computing environment as claimed in claim 111 wherein the second datastream is provided to a data storage unit for storage.
  - 113. A computing environment as claimed in claim 112 wherein the second datastream is used to render a presentation, and the data storage unit stores the second datastream for a purpose other than to render the presentation.
  - 114. A computing environment as claimed in claim 112 wherein the second datastream is not used to render a presentation, and the data storage unit stores the second datastream for a purpose other than to render the presentation.
  - 115. A computing environment as claimed in claim 107 wherein the first and second datastreams are presentation datastreams.
  - 116. A computing environment as claimed in claim 115 wherein the presentation datastreams include at least one instruction and data, the instruction indicating a screen display position of the data in a presentation, and the data indicating at least one character for rendering in the presentation at the screen position indicated by the instruction, the metadata used to map the instruction and data of the first datastream to corresponding instruction and data of the second datastream.
  - 117. A computing environment as claimed in claim 107 wherein the first datastream is one of VT52, VT100, VT220-78, VT220-8, VT320-7, VT320-8, VT420-7, VT420-8, VT525-7, VT525-8, 3270, 5250, 3270E, 5250E, TN3270E, TN5250E, TDG, SCO ANSI, BBS ANSI, AT 386, AIXTERM, WYSE 50, WYSE 60, TVI 925, and TVI 950 terminal datastreams, and the second datastream is one of HTTP, SGML, HTML, DHTML, XML, WML, WAP, tagging language, and byte code datastreams.
  - 118. A computing environment as claimed in claim 107 wherein the metadata identifies an application that generated the first datastream.
  - 119. A computing environment as claimed in claim 107 wherein the metadata identifies a memory location of the application in its computing environment.
  - 120. A computing environment as claimed in claim 107 wherein the metadata identifies a purpose of the application.
  - 121. A computing environment as claimed in claim 107 wherein the metadata identifies a data definition defining data used to generate the first datastream.
  - 122. A computing environment as claimed in claim 107 wherein the metadata identifies a field length of the data.
  - 123. A computing environment as claimed in claim 107 wherein the metadata identifies a type of the data.
  - 124. A computing environment as claimed in claim 107 wherein the metadata identifies a variable name associated with the data.
  - 125. A computing environment as claimed in claim 107 wherein the metadata defines permissible values for the data.
  - 126. A computing environment as claimed in claim 125 wherein the metadata identifies the permissible values for the data as a range of values.
  - 127. A computing environment as claimed in claim 125 wherein the metadata identifies the permissible values for the presentation data as a group of permissible values.
  - 128. A computing environment as claimed in claim 107 wherein the metadata identifies a user interface definition.
  - 129. A computing environment as claimed in claim 128 wherein the user interface definition includes a variable name of data to be rendered in a presentation based on the second datastream.
  - 130. A computing environment as claimed in claim 128 wherein the user interface definition identifies screen position of data on a user interface display screen in a presentation rendered by the second datastream, and the metadata identifies the screen position of the data.
  - 131. A computing environment as claimed in claim 130 wherein the screen position is indicated by character row and column on the user interface display screen of a presentation rendered by the second datastream, and the metadata identifies the row and column of the respective data.
  - 132. A computing environment as claimed in claim 130 wherein the user interface definition includes a variable name associated with a data value, and the metadata identifies the variable name and data value.
  - 133. A computing environment as claimed in claim 107 wherein the metadata identifies a presentation screen to be rendered with the second datastream.

134. A system receiving a first datastream, the system comprising:
- a first computing environment executing a metadata module to associate metadata with the first datastream to generate a second datastream;
  
  a second computing environment coupled to receive the second datastream from the first computing environment, the second computing environment executing a metadata interpreter to map the metadata associated with at least one element of the second datastream to at least one corresponding element of a third datastream, to generate the third datastream.
- View Dependent Claims (135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 176)
- - 135. A system as claimed in claim 134 further comprising:
    - a computing device coupled to receive the third datastream and rendering a presentation based thereon.
  - 136. A system as claimed in claim 134 wherein the first datastream is generated by a host computer, and the computing device renders a presentation that emulates a terminal device corresponding to the first datastream.
  - 137. A system as claimed in claim 134 wherein the first datastream is one of VT52, VT100, VT220-78, VT220-8, VT320-7, VT320-8, VT420-7, VT420-8, VT525-7, VT525-8, 3270, 5250, 3270E, 5250E, TN3270E, TN5250E, TDG, SCO ANSI, BBS ANSI, AT 386, AIXTERM, WYSE 50, WYSE 60, TVI 925, and TVI 950 terminal datastreams, and the third datastream is one of HTTP, SGML, HTML, DHTML, XML, WML, WAP, tagging language, and byte code datastreams.
  - 138. A system as claimed in claim 134 wherein the first datastream is a presentation datastream and the third datastream is not a presentation datastream.
  - 139. A system as claimed in claim 134 wherein the third datastream is used by an application executed on a computing device for processing the third datastream.
  - 140. A system as claimed in claim 139 wherein the third datastream is used to render a presentation, and the application is executed by the computing device for a purpose other than to render the presentation.
  - 141. A system as claimed in claim 139 wherein the third datastream is not used to render a presentation, and the application is executed by the computing device for a purpose other than to render the presentation.
  - 142. A system as claimed in claim 134 wherein the third datastream is supplied to a data storage unit for storage of data contained therein.
  - 143. A system as claimed in claim 142 wherein the third datastream is used to render a presentation, and the data storage unit stores the third datastream for a purpose other than to render the presentation.
  - 144. A system as claimed in claim 142 wherein the third datastream is not used to render a presentation, and the data storage unit stores the third datastream for a purpose other than to render a presentation.
  - 152. A computer-readable medium as claimed in claim 143 wherein the metadata identifies a data type of the presentation data stored in the data storage unit.
  - 153. A computer-readable medium as claimed in claim 143 wherein the metadata identifies a variable name associated with data.
  - 154. A computer-readable medium as claimed in claim 143 wherein the metadata defines permissible values for the presentation data.
  - 155. A computer-readable medium as claimed in claim 143 wherein the metadata identifies the permissible values for the presentation data as a range of values.
  - 156. A computer-readable medium as claimed in claim 143 wherein the metadata identifies the permissible values for the presentation data as a group of permissible values.
  - 157. A computer-readable medium as claimed in claim 143 wherein the metadata identifies a user interface definition for the presentation data.
  - 158. A computer-readable medium as claimed in claim 157 wherein the user interface definition includes a variable name of the data rendered on the user interface, and the metadata identifies the variable name.
  - 159. A computer-readable medium as claimed in claim 157 wherein the user interface definition identifies screen position of data on a user interface display screen, and the metadata identifies the screen position.
  - 160. A computer-readable medium as claimed in claim 157 wherein the screen position is indicated by character row and column on the user interface display screen, and the metadata identifies the row and column of respective data.
  - 161. A computer-readable medium as claimed in claim 157 wherein the user interface definition includes a variable name associated with a data value, and the metadata identifies the variable name and data value.
  - 162. A computer-readable medium as claimed in claim 157 wherein the metadata identifies a screen to which the presentation data pertains.
  - 163. A computer-readable medium as claimed in claim 157 wherein the presentation datastream includes an instruction and data, the instruction indicating the display position of the data in a presentation, and the data indicating at least one character for rendering in the presentation, the metadata associated with the instruction and data.
  - 164. A computer-readable medium as claimed in claim 157 wherein the metadata module obtains the metadata using a mapping of elements in the presentation datastream to corresponding metadata.
  - 165. A computer-readable medium as claimed in claim 157 wherein the metadata module uses a mapping of at least one element in the presentation datastream to at least one corresponding metatag, and applies the corresponding metatag to the element of the presentation datastream.
  - 176. A method as claimed in claim 164 wherein an application generates the first datastream, and the metadata identifies a memory location of the application in the first computing environment.

145. A computer-readable medium storing a metadata module for associating metadata with a presentation datastream.
- View Dependent Claims (146, 147, 148, 149, 150, 151)
- - 146. A computer-readable medium as claimed in claim 145 wherein the computer-readable medium stores metadata for use by the metadata module.
  - 147. A computer-readable medium as claimed in claim 145 wherein the metadata identifies an application that generated the presentation data.
  - 148. A computer-readable medium as claimed in claim 145 wherein an application generates the presentation datastream, and the metadata identifies a memory location of the application in a computing environment.
  - 149. A computer-readable medium as claimed in claim 145 wherein the metadata identifies a purpose of the application.
  - 150. A computer-readable medium as claimed in claim 145 wherein the metadata identifies a data definition defining data used to generate the presentation datastream.
  - 151. A computer-readable medium as claimed in claim 145 wherein the metadata identifies a field length of data stored in the data storage unit.

166. A computer-readable medium comprising a metadata interpreter using metadata in a first datastream in a context of a first computing environment to map at least one element of the first datastream to a corresponding element of a second datastream in a context of a second computing environment.
- View Dependent Claims (167, 168, 169, 170, 171, 172, 173, 174, 175, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190)
- - 167. A method as claimed in claim 166 wherein the second datastream is used for a purpose other than to render a presentation.
  - 168. A method as claimed in claim 166 wherein the second datastream is provided to an application for processing thereof.
  - 169. A method as claimed in claim 166 wherein the second datastream is used to render a presentation, and the application processes the second datastream for a purpose other than to render the presentation.
  - 170. A method as claimed in claim 166 wherein the second datastream is not used to render a presentation, and the application processes the second datastream for a purpose other than to render the presentation.
  - 171. A method as claimed in claim 166 wherein the second datastream is provided to a data storage unit for storage.
  - 172. A method as claimed in claim 166 wherein the first and second datastreams are presentation datastreams.
  - 173. A method as claimed in claim 172 wherein the first datastream is one of VT52, VT100, VT220-78, VT220-8, VT320-7, VT320-8, VT420-7, VT420-8, VT525-7, VT525-8, 3270, 5250, 3270E, 5250E, TN3270E, TN5250E, TDG, SCO ANSI, BBS ANSI, AT 386, AIXTERM, WYSE 50, WYSE 60, TVI 925, and TVI 950 terminal datastreams, and the second datastream is one of HTTP, SGML, HTML, DHTML, XML, WML, WAP, tagging language, and byte code datastreams.
  - 174. A method as claimed in claim 172 wherein the presentation datastreams include at least one instruction and data, the instruction indicating a screen display position of the data in a presentation, and the data indicating at least one character for rendering in the presentation at the screen position indicated by the instruction, the metadata used to map the instruction and data of the first datastream to corresponding instruction and data of the second datastream.
  - 175. A method as claimed in claim 172 wherein the metadata identifies an application that generated the first datastream.
  - 177. A method as claimed in claim 166 wherein the metadata identifies a purpose of the application that generates the first datastream.
  - 178. A method as claimed in claim 166 wherein the metadata identifies a data definition defining data used to generate the first datastream.
  - 179. A method as claimed in claim 166 wherein the metadata identifies a field length of the data.
  - 180. A method as claimed in claim 166 wherein the metadata identifies a type of the data.
  - 181. A method as claimed in claim 166 wherein the metadata identifies a variable name associated with the data.
  - 182. A method as claimed in claim 166 wherein the metadata defines permissible values for the data.
  - 183. A method as claimed in claim 182 wherein the metadata identifies the permissible values for the data as a range of values.
  - 184. A method as claimed in claim 183 wherein the metadata identifies the permissible values for the presentation data as a group of permissible values.
  - 185. A method as claimed in claim 166 wherein the metadata identifies a user interface definition.
  - 186. A method as claimed in claim 185 wherein the user interface definition includes a variable name of data to be rendered in a presentation based on the second datastream.
  - 187. A method as claimed in claim 185 wherein the user interface definition identifies screen position of data on a user interface display screen in a presentation to be rendered by the second datastream, and the metadata identifies the screen position of the data.
  - 188. A method as claimed in claim 185 wherein the screen position is indicated by character row and column on the user interface display screen of a presentation rendered by the second datastream, and the metadata identifies the row and column of the respective data.
  - 189. A method as claimed in claim 185 wherein the user interface definition includes a variable name associated with a data value, and the metadata identifies the variable name and data value.
  - 190. A method as claimed in claim 185 wherein the metadata identifies a presentation screen rendered by the second datastream.

191. A method comprising the step of:
- a) using metadata in a datastream to modify at least one of an application, a user interface definition, and a data definition, used to generate the datastream.
- View Dependent Claims (192, 193, 194, 195, 196, 197, 198)
- - 192. A method as claimed in claim 191 wherein the datastream comprises a presentation datastream.
  - 193. A method as claimed in claim 191 wherein the metadata identifies the application.
  - 194. A method as claimed in claim 191 wherein the metadata comprises application definition.
  - 195. A method as claimed in claim 191 wherein the metadata identifies the user interface definition.
  - 196. A method as claimed in claim 191 wherein the metadata comprises the user interface definition.
  - 197. A method as claimed in claim 191 wherein the metadata identifies the data definition.
  - 198. A method as claimed in claim 191 wherein the metadata comprises the data definition.

199. A method comprising the step of:
- a) developing an application using metadata in a datastream.
- View Dependent Claims (200, 201, 202, 203, 204, 205, 206, 207)
- - 200. A method as claimed in claim 199 wherein the datastream comprises a presentation datastream.
  - 201. A method as claimed in claim 199 wherein the metadata identifies the application.
  - 202. A method as claimed in claim 199 wherein the metadata identifies another application used to generate the datastream.
  - 203. A method as claimed in claim 199 wherein the metadata comprises application definition describing the application.
  - 204. A method as claimed in claim 199 wherein the metadata identifies a user interface definition used to generate the datastream.
  - 205. A method as claimed in claim 199 wherein the metadata comprises a user interface definition used to generate the datastream.
  - 206. A method as claimed in claim 199 wherein the metadata identifies a data definition used to generate the datastream.
  - 207. A method as claimed in claim 199 wherein the metadata comprises a data definition used to generate the datastream.

208. A method comprising the step of:
- b) modifying an application using the metadata in datastream.
- View Dependent Claims (209, 210, 211, 212, 213, 214, 215, 216)
- - 209. A method as claimed in claim 208 wherein the datastream comprises a presentation datastream.
  - 210. A method as claimed in claim 208 wherein the metadata identifies the application.
  - 211. A method as claimed in claim 208 wherein the metadata identifies another application used to generate the datastream.
  - 212. A method as claimed in claim 208 wherein the metadata comprises application definition used to generate the datastream.
  - 213. A method as claimed in claim 208 wherein the metadata identifies a user interface definition used to generate the datastream.
  - 214. A method as claimed in claim 208 wherein the metadata comprises a user interface definition used to generate the datastream.
  - 215. A method as claimed in claim 208 wherein the metadata identifies a data definition used to generate the datastream.
  - 216. A method as claimed in claim 208 wherein the metadata comprises a data definition used to generate the datastream.

Specification

Resources

Litigation Campaign Assessment

Current Assignee
Seagull Business Software BV (Rocket Software Incorporated)
Original Assignee
Seagull Business Software BV (Rocket Software Incorporated)
Inventors
van Helden, Wico, den Haan, Andries Japhet

Application Number

US09/972,673
Publication Number

US 20040006745A1
Time in Patent Office

Days
Field of Search
US Class Current

715/516
CPC Class Codes

G06F 9/451 Execution arrangements for ...

Methods, apparatuses, system, and articles for associating metadata with datastream

First Claim

1 Assignment

0 Petitions

Accused Products

Abstract

83 Citations

216 Claims

Specification

Use Cases

Quick Links

Others

Methods, apparatuses, system, and articles for associating metadata with datastream

First Claim

1 Assignment

Subscription Required

Subscription Required

0 Petitions

Subscription Required

Accused Products

Subscription Required

Abstract

83 Citations

216 Claims

Specification

Subscription Required

Use Cases

Quick Links

Others