Browse Prior Art Database

Mechanism to Indicate Altering Attributes in Document Content

IP.com Disclosure Number: IPCOM000108070D
Original Publication Date: 1992-Apr-01
Included in the Prior Art Database: 2005-Mar-22
Document File: 2 page(s) / 76K

Publishing Venue

IBM

Related People

Inniss, HA: AUTHOR [+4]

Abstract

A methodology is described which solves the problem of synchronizing modifiable document content with the corresponding modifiable attributes. Synchronizing is important because capabilities of systems which may manage the distribution vary. Some systems manage only modifying attributes in the document content and some only manage attributes in the document profile.

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

Mechanism to Indicate Altering Attributes in Document Content

       A methodology is described which solves the problem of
synchronizing modifiable document content with the corresponding
modifiable attributes.  Synchronizing is important because
capabilities of systems which may manage the distribution vary.  Some
systems manage only modifying attributes in the document content and
some only manage attributes in the document profile.

      Document Interchange Architecture (DIA) needs indication in the
Interchange Document Profile (IDP) that document content and/or
profile attributes may contain matter which requires updating by
receiving or sending systems.  Products pass distributions around
with different implementations of attribute handling for the
distributions. For example, sender, recipient, date/time submitted,
subject and other modifiable attributes associated with a
distribution may reside in the document content itself as well as in
the IDP.  It is the responsibility of the application or system to
alter the textual matter and/or IDP data appropriately.  For example,
as defined by DIA, the recipient list should appear in the
architected COPY LIST of the IDP base profile.  Some products (e.g.,
PROFS*) make the sender and recipient list appear as text in the body
of the note.  Some applications do not update addressing note text
when they should because they do not know if addressing text is
present in the document body.  Applications need to know if the
addressing information is in the note text so the text can be updated
on a RESEND, FORWARD or REPLY.  Also, it is desirabl...