Browse Prior Art Database

Data Stream Conversion: a Method to Correct Invalid Field Names and Field Descriptors

IP.com Disclosure Number: IPCOM000042955D
Original Publication Date: 1984-Jun-01
Included in the Prior Art Database: 2005-Feb-04
Document File: 2 page(s) / 14K

Publishing Venue

IBM

Related People

Yu, KM: AUTHOR [+2]

Abstract

In the transmission of word-processing information files via communications lines, invalid field names or descriptors in the word-processing information file document being received can, in some systems, cause reception and processing to halt. This article describes expedients for continuing the reception and processing of data despite such invalid field names or field descriptors. Validity Checking in Data Stream Conversion When data is exchanged between different word-processing systems via communications lines, it is typically essential for common compatible field names and other field descriptors to be used in the word-processing information file documents being exchanged. These field names and other descriptors are checked for validity to ensure such compatibility.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 1 of 2

Data Stream Conversion: a Method to Correct Invalid Field Names and Field Descriptors

In the transmission of word-processing information files via communications lines, invalid field names or descriptors in the word-processing information file document being received can, in some systems, cause reception and processing to halt. This article describes expedients for continuing the reception and processing of data despite such invalid field names or field descriptors. Validity Checking in Data Stream Conversion When data is exchanged between different word-processing systems via communications lines, it is typically essential for common compatible field names and other field descriptors to be used in the word-processing information file documents being exchanged. These field names and other descriptors are checked for validity to ensure such compatibility. However, on occasion -- especially when systems of different vendors are being utilized -- invalid field names or other descriptors can arise. Typically, such a situation brings reception, and data processing, to a halt. However, this article presents methods enabling information reception and processing to proceed in certain word-processing systems (such as the Displaywriter system) despite such invalid items if other conditions of compatibility are met. Invalid Field Names The simplest case of invalidity concerns invalid field names. The word-processing system's validity checker -- a process in the data stream conversion -- checks the syntax of field names in the word-processing information file document being received. If an invalid field name is found, the remainder of the file typically is unusable, and operation is terminated. However, if the validity checker were able to correct the field name,
i.e., render it valid in some manner, the remainder of the file would still be usable and processing could continue. Such a method is presented here. This method is applicable in word-processing systems with software packages which support fields without names (such as the Displaywriter Report Pack). Based on the procedures within such software, the invalid field names detected in field descriptors can simply be deleted, and the processing of the information can continue. This method has an advantage in that the field name correction does not increase data length in the output buffer, yet attains greater productivity and flexibility. O...