SGML VERSION MANAGER (VM)

Creating and managing multiple versions or "effectivities" of the same data for different audiences or media is a growing challenge in electronic publishing. (view background data) ISI's SGML Version Manager has become the SGML industry's most widely-used tool to aid authors in this demanding editorial task.

In addition, VM is integrated with ISI's Link Manager application to ensure that changes to effectivity do not invalidate existing links in data files.

Versioning, also called "effectivity" allows a single SGML data file to create multiple output products containing both common and product-specific content. Versioning can create products in different languages, for different customers, different media or any combination of these and other categories.

SGML Version Manager supports five major processes:

• Establishment of Versioning in new and revised data files.

• Evaluation and display of Versioning in force at any specified point in a data file.

• Validation of Version tagging within data files, both upon entry of new Versioning and for evaluation of files prior to publication.

• Visual Resolution of Versioning notation in files, to simplify the task of authoring and managing files containing complex version tagging.

• Tracking of the effects of Versioning changes on "hyperlinks" in the content repository.

SGML DATA STRUCTURES USED IN VERSION MANAGER:

Version Manager is based on the entry of specific SGML data structures into text files. These non-intrusive structures are added to the content DTD as a basis for automated support for the authoring and control of versioned content.

The EFFEC Element: This is the basic vehicle for Versioning content within SGML elements.

The EFFEC Attribute: This is an SGML attribute added to selected elements in the DTD. It allows the user to designate Versioning for an entire SGML element.

The EFFEC GROUP element: This element causes Version Manager to treat elements within it as a single logical structure for the purpose of enforcing mutual exclusivity and, at the author's option, to ensure that the contents of the group cover all output versions.

SPECIAL SGML STRUCTURE CONTROLS FOR VERSION AUTHORING:

The content of any specific EFFEC_ITEM or EFFEC_GROUP must adhere to the SGML rules for data surrounding it so that it will not create an invalid structure when resolved. To accommodate this requirement, VM presents a customized insert markup window, modified to reflect only those tags permitted in normal text at the point of the EFFEC element.

The Versioning Menu: This addition to the standard Arbor Text menu bar provides user access to several Version related functions, including:

• View/Modify to display and modify the Versioning in force at the Arbor Text Insertion Point..
• Version Element to "break up" an element containing multiple Versioning items into a user-defined set of individually versioned elements.
• Validate to analyze the file or selected element and report any invalid Version settings located.
• Resolve to create and validte a read-only display of any or all of the individual versions represented in the file.
• The Virtual Resolution Window: This facility allows the user to create a visually "resolved" copy of the open file for each desired version. Each of these virtual files is processed in background to remove all non-applicable material, leaving a visually "pure" version of the file according to the Version settings for which it is intended.

COMPUTER-AIDED VERSION ASSIGNMENT AND MAINTENANCE:

VM allows authors to set, manipulate and manage versioning via the "Versioning" menu item on the Arbor Text menu bar and perform the following functions. When activated through the "View/Modify" menu item, the Versioning Panel displays a view of the Versioning both in force and available for the element in which the Arbor Text cursor resides. Each display is a button which, when pushed, will set or clear its Versioning code for insertion into the file.

The specific configuration and functions of the Versioning Panel is designed to meet the needs of each user site. The example below illustrates the panel configured to provide all functions without resort to the Arbor Text menu.

Tell me more . . . ISI Home Page