Browse Prior Art Database

Extendable User Input Data Qualification Architecture

IP.com Disclosure Number: IPCOM000107334D
Original Publication Date: 1992-Feb-01
Included in the Prior Art Database: 2005-Mar-21
Document File: 2 page(s) / 79K

Publishing Venue

IBM

Related People

Malcolm, JW: AUTHOR [+2]

Abstract

Disclosed is an easily extendable architecture that provides encapsulation of data type qualification needed to reduce the impact of changing data type qualification requirements. Described here is a dynamically extendable data qualification architecture. A routine is written to qualify the required data types and then is registered with the architecture. When a data type is encountered that requires the qualification provided in the registered routine, it is called by the architecture to provide the necessary qualification. If a new rule is required, a new routine is written to provide the qualification of that data type and is also registered with the architecture. It will then be called to qualify the new data type when needed.

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

Extendable User Input Data Qualification Architecture

       Disclosed is an easily extendable architecture that
provides encapsulation of data type qualification needed to reduce
the impact of changing data type qualification requirements.
Described here is a dynamically extendable data qualification
architecture.  A routine is written to qualify the required data
types and then is registered with the architecture.  When a data type
is encountered that requires the qualification provided in the
registered routine, it is called by the architecture to provide the
necessary qualification.  If a new rule is required, a new routine is
written to provide the qualification of that data type and is also
registered with the architecture.  It will then be called to qualify
the new data type when needed.  This change does not require any
knowledge or dependency on the previously registered qualification
classes.  If a data type is no longer needed, it can easily be
removed by not registering it with the architecture.

      This architecture is also very valuable when the type of
qualification that is going to be required is unknown until the
application is run.  A very good example of this is providing
National Language and Double-Byte Character Set support.  Before
registering the qualification classes it may be necessary to query
the system to see which type of environment is running.  In a
single-byte environment, different qualification routines may need to
be registered from those needed in a double-byte environment.  With
this architecture it is not required to maintain different versions
of an application per environment because the application can sense
and adapt to the environment it is in.

      The following is a description of the architecture:
      1.  First register all qualification routines needed for your
application with one or more calls similar to the following:
           RegisterQualification(ClassNumber,
           PtrToQualRoutine);
      The ClassNumber parameter is a unique number per class being
registered.  It is used to determine which routine needs to be called
to qualify a particular data type.
      2.  Call the qualification API whenever data qualification is
required:
           QualifyData(QualificationFlag, PtrToData);

      The application always calls this API to have data
qualification performed.  It does not need...