Browse Prior Art Database

Template-Driven Document-Exchange Specification

IP.com Disclosure Number: IPCOM000118257D
Original Publication Date: 1996-Nov-01
Included in the Prior Art Database: 2005-Apr-01
Document File: 6 page(s) / 159K

Publishing Venue

IBM

Related People

Yong, YM: AUTHOR

Abstract

Disclosed is a document-exchange specification for the Singapore Electronic Procurement System.

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

Template-Driven Document-Exchange Specification

      Disclosed is a document-exchange specification for the
Singapore Electronic Procurement System.

      In electronic commerce, application data can take the shape of
forms that require document workflow, and transaction records which
must be stored in a database, two different and distinct paradigms
crossing within a single application process.  To meet this challenge
in a large-scale government electronic procurement system with
requirements for multiple types of documents, data integrity,
replication, and confidentiality, a template-driven document exchange
specification has been developed.  This specification is designed to
provide a structured yet flexible form-processing paradigm which
includes security, workflow, and visual-control.

      Document Template Layout - Each document template defines how
data in the document should be interpreted.  Thus, related business
policies can be applied.  Each field in the document template should
be coded according to the data type, length, and ordering as defined
for the related document template.

      A document template is organized into three areas of
definition: Table, Header and Detail.  The Table section defines all
database tables which are related to the document template.  There is
only one Table and Header section but there can be one or more Detail
sections.  The Header section depicts the header and summary sections
in a typical business document.  The Detail section describes the
detail section in a typical business document.

      The Table section must begin with a (TABLE) label.  Each entry
in the Table section is described by the logical database table name
and its equivalent physical database table name.  The Table section
is code  as follows:
    (TABLE)
    <Logical database table name>=<Physical database table name>

      The labels for the Header section and Detail section(s) must
be, respectively, (HEADER) and (DETAIL).  Each field in the Header
and Detail sections of the document template should be defined using
the following convention:
  <Field Name> = <Type>;<Length>;<Condition>;<Description>;
    where,
    <Field Name> ::= database table column name.
    <Type>       ::= data type, such as char, num, date,
                      time, or timestamp.
    <Length>     ::= maximum length of field's value.
    <Condition>  ::= condition of field, such as mandatory,
                      optional, dummy, or null.
    <Description>::= purpose of use or as GUI object's label.

      Document Interchange Format (DIF) File Layout - A typical
DIF file must contain the sections:  Mail-Control, Field-Control,
WorkFlow-Control, Document-Header, and Document-Detail, and these are
described in detail below.  Each section's title appears in the order
listed and must appear on a new line, enclosed in square brac...