Browse Prior Art Database

METHOD for SUPPORTING NON-TEXT OBJECTS in an INDEX STRUCTURE THAT ORIGINALLY SUPPORTED ONLY TEXT RECORDS

IP.com Disclosure Number: IPCOM000056634D
Original Publication Date: 1988-Jan-01
Included in the Prior Art Database: 2005-Feb-14

Publishing Venue

IBM

Related People

Authors:
Kendrick, MR Killebrew, AJ Rodriguez, BA [+details]

Abstract

A method is described which provides a word processing package the ability to store Text data and Non-Text Objects within the same DOS file. The Non-Text Object data must be capable of being accessed randomly as a named entity of the file. The IBM RFTDCA Datastream Architecture, referred to as Level 3 Datastream (L3), defines the non-text object as a collection of data bytes stored within a non-text unit in L3. The term "non-text object" refers to a collection of data which can contain such things as voice data, images, business graphs, drawings, data tables, format tables, and so on. The term "composite document" refers to a file that contains both text records and non-text objects. (Image Omitted) Each non-text unit has an eight-byte name.