Browse Prior Art Database

Object Based Architecture for Multimedia Data Sources

IP.com Disclosure Number: IPCOM000114212D
Original Publication Date: 1994-Nov-01
Included in the Prior Art Database: 2005-Mar-28
Document File: 2 page(s) / 84K

Publishing Venue

IBM

Related People

Ibbotson, JB: AUTHOR

Abstract

When interacting with multimedia data sources such as text, image, video and sound it is desirable that a Graphical User Interface (GUI) can work with a consistent view of the different data types. The GUI will be used to search and retrieve data from a database which will index different multimedia data sources and interact with the retrieved data. The modes of search, retrieval and interaction will differ depending on the type of data being accessed. For example, displaying video data will be different from displaying static images and text.

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

Object Based Architecture for Multimedia Data Sources

      When interacting with multimedia data sources such as text,
image, video and sound it is desirable that a Graphical User
Interface (GUI) can work with a consistent view of the different data
types.  The GUI will be used to search and retrieve data from a
database which will index different multimedia data sources and
interact with the retrieved data.  The modes of search, retrieval and
interaction will differ depending on the type of data being accessed.
For example, displaying video data will be different from displaying
static images and text.

      The architecture described below is based on a data view object
which encapsulates the different types of data sources and presents a
consistent public interface to a GUI.  The view object will also
manage service data which describes where and how the different data
sources can be accessed as local and remote servers on a network.

      The architecture consists of a view object which will create,
manage, and destroy objects in order to fulfil its contracts with the
connected GUI object.  The objects used by the view consist of:
  1.  Service objects.
  2.  Database objects.
  3.  Data server objects.

      Service objects contain data describing the database and data
server resources available to the view object to allow it to fulfil
its contracts with other objects.  Typically, a service object
contains lists of databases together with their addresses and
connection characteristics for access via heterogeneous network
structures.  Each database or data server resource is uniquely
identifiable from the service object by the viewer.  Lists of
available databases or data servers are returned to the view object
from the service object upon receipt of a suitable message.  These
lists may be available to the GUI via the view public interface.  The
service object will return data on a specific database or data
service when a suitable message is received from the viewer.

      Database objects are created and destroyed as and when the view
object receives messages to connect or disconnect...