Browse Prior Art Database

Rules for Interchange Objects in a Mixed Object Document Data Stream

IP.com Disclosure Number: IPCOM000035155D
Original Publication Date: 1989-Jun-01
Included in the Prior Art Database: 2005-Jan-28
Document File: 2 page(s) / 14K

Publishing Venue

IBM

Related People

Barker, BA: AUTHOR [+3]

Abstract

A document data stream allowing for the mixing of different types of objects, such as text, image, graphics and the like, can be interchanged among a wide spectrum of diverse document processing products. The amount of useful information that can be interchanged between these products depends on the format of the data defined by the data stream architecture. If the interchange semantics include process or device specific functions, or are not independent of document structure or data stream semantics, the object transform to and from the interchange format is very complex. Also, if the object definition is not "pure," then the non-object specific data is processed differently than if that data were to occur in an object of the specific data type.

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

Page 1 of 2

Rules for Interchange Objects in a Mixed Object Document Data Stream

A document data stream allowing for the mixing of different types of objects, such as text, image, graphics and the like, can be interchanged among a wide spectrum of diverse document processing products. The amount of useful information that can be interchanged between these products depends on the format of the data defined by the data stream architecture. If the interchange semantics include process or device specific functions, or are not independent of document structure or data stream semantics, the object transform to and from the interchange format is very complex. Also, if the object definition is not "pure," then the non-object specific data is processed differently than if that data were to occur in an object of the specific data type. An example is a graphics object that contains non-graphics data or descriptive information, such as image or text data. In this case, the embedded image or text data is processed differently than if the same data were to occur within an image or text object. "Impure" objects result in inefficient processing of a data stream, because the process is required to recognize and understand multiple formats for each data type included in the "impure" object definition.

Problems of this type are avoided when the carrier data stream architecture provides explicit rules covering the types of function that can be described by the syntax and semantics of an object interchanged within a mixed object document data stream. The first rule is process independence. This means that application specific function intended to save bytes or improve performance should not be provided in an object architecture if that function diminishes the ability to interchange the object in a mixed object document data stream. Processors of the interchange format of an object must be able to unambiguously interpret the object without having to understand multiple application specific functions. The second rule is that an interchange object must be device independent. Examples of device dependent data that should not be included in an object definition are cursor or printer controls. Device independence also means that limitations of devices or optimizations for devices should not affect the syntax and semantics of an interchange object. Certain architectures permit embedded image data to be defined within an interchange graphics object because a device, such as the 3270 di...