`
`
`
`
`
`Merrill Communications LLC
`d/b/a Merrill Corporation
`Exhibit 1006 pt. 4
`
`

`

`ADEPT•Editor:
`Edit for content----(cid:173)
`management
`
`I Structured authoring
`
`I Automated document systems
`
`-~1 Batch composition
`
`©1998 THE XML HANDBOOKTM
`
`

`

`Chapter __ ~
`~2.
`
`s:.<u•>.U··~···vns with large amount of document information
`rypically require an XML authorjng and editing tool that
`integrates with content management tools and comel}t
`delivery tools. That combination yields a complete automated docu(cid:173)
`ment system.
`
`22.1 1 Automated document systems
`
`An automated document system can be the key to an organization gaining
`significant competitive advantage through improvements in information
`quality, time to market, and production costs (see Figure 22-1).
`The designs of these systems usually emphasize data integrity, data reus(cid:173)
`ability, process automation, and workflow consistency. Data integrity is key
`to the other design factors because without absolutely consistent data, the
`rest becomes difficult or impossible to achieve.
`Two key concepts, stn-tcture and co·ntent matta.gement play pivotal role in
`rhe ·ucces ful deployment and operation of a high-performance automated
`look at what these terms mean and
`deeumem publishing system. Ler u
`why they are important.
`
`© I 9 9 R T H IC X M L H A I' ll R o o K nl
`
`297
`
`

`

`298
`
`CHAPTER 22 I ADEPT•EDITOR: EDIT fOR CONTENT MANAGEMENT
`
`Structured
`XML
`Editor
`
`Content
`Management
`
`Document
`Delivery
`
`Document
`Component
`Database
`
`Figm·e 22-1 Automated document system co mpon ents.
`
`22.1. 1 Structure
`
`The contents of documents are often described as unstructured information,
`in contrast to the structured information stored in a relational database. But
`if you look at the right-hand view in Figure 22-2, the rendered document
`clearly exhibits a structure. It is conveyed to the reader by stylistic conven(cid:173)
`tions, such as type size, numbering, and indentions.
`So if the terms "structured" and "unstructured" information aren't really
`accurate, what then do we mean when we use them?
`If you look in the computer .fil
`for a word pr.oce sing doctune nt, you
`will flnd the sLyle informati n mixed in with tb real information - the data
`content - of the document. In a database, however, rhere is nothing there
`but pure abstract data.
`So it isn't that documents have no structure, it is that the way most docu(cid:173)
`ments are stored obscures the abstract data with information about the way
`it should look when presented. In a word, while databases contain abstrac(cid:173)
`tions, most document files contain renditions.
`
`i(J I 'I 9 H THE X M L HA N J) u () () ~ '"
`
`

`

`--
`
`2 2 . 1
`
`AUTOMATED DOCUMENT SYSTEMS
`
`299
`
`DESCRIPTION
`
`FEED CIRCUIT RESISTANCE TEST
`
`El
`
`FEED CffiCUTT RESISTANCE
`
`Before proceeding wit1l this operation, r eview
`Diagnostic Preparation and Statter Feed Circwt
`Tests. The foUowing operation will t equll·e a
`voltmeter. accurate to 1/10 of a volt
`Ignition and Fuel systems m1.1st be disabled to
`prevent engme start while pe1 fanning the followll1g
`
`l. To ells able the Ignihon and Fuel systems,
`discotmect the Automatic Shutdo\'!n Relay
`(ASD) Tile Af~D 1elay 1s located in th-:! Power
`Distribution Center (PDC) , Refe1 to tl1c PDC
`cover fo1· proper t•elay locatwn
`With all wirll1g hamesses and components
`properly connected, perfonn the following·
`a Connect the negative lead of the volhnete1 to
`the batt:ery negative pos~ and positive lead to
`the batt:e1y negative cable clatnp + Rotate
`and hold tl1e ignition switch lll the START
`position Observe the voltmetet , If voltage ts
`detected, correct poor contact between cable
`
`17HID para
`@.] ptxl - Before proceeding v:llh this
`operation, review Diagnostic Prep araban and
`StatterFeedCircuil Test::, The following
`operation will require a voll..meler, accurate lo
`1110 of a volt
`EJ ptxl -
`Ignitwn andJi'uel systems must be
`disabled to prevent engin.e stat1 while perfmuJng
`I I
`the following tests.
`f7i ~ s1
`1.
`I !_ EJ pt:d
`To disable the Igxlition a.nd Ji'uel
`I
`systems, disconnect the Automatic Shutdovrn
`Relay(ASD) The A30 relay is located in the
`Power Di:>ltibution Center(PDG) Refer to 1he
`PDC cover for proper relay location
`,b C1J s1
`- 2
`~~ ptxt
`With all wiring harnesses hlld
`j
`components properly connected, perfotm the
`followingJ
`!~\ liD s2
`8 !:[! ptxt
`Connect the negat ive lead of1he
`voltmeter to the batte:tyne.gative po:::t, and po:::ilive
`lead to the baltety negative cable clamp
`· ~ ~ fiuureref
`. Rotate ancllwlcllj1c lgnitwn switch in 1he START
`position, Obsetve 1he voltmeter, If voltage is
`cleteclec~ correct poor contact between cable cl.:..mp
`and posl
`1
`I~ :!] Sl - b
`
`I I
`I
`
`d
`
`I
`
`[
`
`Figru·e 22-2
`(WYSIWYG).
`
`Two v1ews of a document: structured and
`
`rendered
`
`But what if that could be different? What if you could store a document
`so that its natural structure and data content could always be distinguished
`from style information? What if you could handle documents as if they
`were data?
`
`It can be different! And XML turns out to be the key, because XML
`allows you to identifY and preserve the structure of any collection of text.
`With XML, documents and databases are just two different places to keep
`abstract structured data.
`
`Because XML is a notation that preserves abstractions, the data in XML
`documents can be treated just like other data, which can be automated,
`
`© 1 'l '! H T H " X M J. H 11 N D n r 1 o ~ '"'
`
`

`

`300
`
`CHAPTER 22 I ADEPT• EDITOR: EDIT FOR CONTENT MANAGEMENT
`
`processed, reused, protected, classified, and extracted for use in a limitless
`variety of ways (see Figure 22-3.)
`Using XML yields several key benefits:
`
`Multiple outputs
`XML document data is often described as "presentation independent"
`because it is stored in a way that is independent of any particular medium.
`That allows organizations to deliver their information automatically from a
`single repository to the Web, CD-ROM, print, and other media. This is a
`huge contrast to word processing and desktop publishing file formats,
`which are already rendered with a specific output in mind, usually publish(cid:173)
`mg on paper.
`
`On-line
`www
`
`Paper
`
`CD-ROM
`
`Other delivery processes
`
`Document
`Component
`Database
`
`Figure 22-3 Multiple outputs from a single XML source.
`
`Reuse
`Many organizations re-create existing information far more often than
`they reuse existing information. That inefficiency causes inaccuracies, version
`skew, delivery slips, and inflated costs. One of the primary reasons to build a
`structured document repository is to eliminate those costs by enabling the
`maximum possible reuse of existing information. Storing that information in
`
`©1998 THE XML HANDBOOKTM
`
`

`

`2 2 . 1
`
`I Au T 0 MAT E D D 0 cu M EN T s ysTEMs
`
`301
`
`a structured database provides the controls needed to maintain the integrity
`of the data regardless of when, where, and how often it is used.
`
`Jnte1·change
`Organiza ions can interchange their data freely with suppliers, partners,
`and customers when the data is based on a standardized document repre(cid:173)
`sentation like XML.
`
`Automation
`Representing your document data in XlvlL and sto ring .it in a repository
`can yield process improv ments through intensive automation th at are sim(cid:173)
`llat in kind and degr e ro the benefits of implementing relational databases
`to replace handwritten ledgers.
`
`tt. l.t Content management
`
`Any organization that manages large amounts of document information
`should, sooner or later, seek both to structure that information and to store
`that information in a content management system.
`The specific method of content management varies. In some applica(cid:173)
`tions, document information is stored directly in a database. In many oth(cid:173)
`ers, it is stored under the control of a document management system.
`Regardless of the specific approach, these system primarily ensure data
`integrity through security controls that prevent unauthorized viewing and
`changing, and revision controls that keep track of changes from one version
`to the next.
`Content management systems for XML documents invariably must keep
`track of information at a highly granular level (see Figure 22-4). For exam(cid:173)
`ple, instead of storing complete books in a single chunk, "compound docu(cid:173)
`ments" are assembled from small components that are stored separately.
`Some components are tiny. For example, individual cells in a table may
`be stored in various places and appear together only when delivered as a
`publication.
`It can be a challenge to create such documents. Typical document cre(cid:173)
`ation tools are designed to create rendered pages, whether they are printed
`pages or Web pages. But building compound documents out of reusable
`components requires a structured authoring tool that is designed to handle
`highly granular unrcndered documenrs. The tool must also integrate tightly
`
`@1998 TH E X ML H AN DBO OK ™
`
`

`

`302
`
`CHAPTER 22 I ADEPT• EDITOR: EDIT FOR CONTENT MANAGEMENT
`
`Figure 22-4 Compound documents are composed of a hierarchy of
`components.
`
`with databases of all kinds, including relational databases, document man(cid:173)
`agement systems, and content management systems.
`Such systems can display collections of document components as if they
`were single documents while preserving the properties of each individual
`component. That approach allows an author to view every document com(cid:173)
`ponent within the context in which it is used, while at the same time ensur(cid:173)
`ing that the author changes only those components for which the author is
`permitted to make changes, and that are not currently under revision by
`another author.
`
`© 1 9 9 H T H F X M L H A N 0 ll 0 ll K 1
`
`M
`
`

`

`22.2 I W H AT INF O RMATION W ARRAN TS THESE TO OLS?
`
`303
`
`22.2 1 What information warrants these
`tools?
`
`Should your organization approach its document applications through the
`use of structured XML authoring tools integrated with content manage(cid:173)
`ment systems?
`The answer depends on the characteristics of the information you create
`and the processes you use to create it. There are a number of criteria to con-
`sider.
`
`tt.t.l High volume
`
`Unless your organization publishes thousands or even millions of pages,
`current content-management-based products may be too expensive to jus(cid:173)
`tify the return. If yours is a manufacturing organization larger than $100
`million or a publishing company larger than $25 million, then you are
`likely to reap sizable rewards from implementing an automated document
`system.
`
`tt.t.t Multiple publications
`
`Most organizations need to publish their information on multiple outputs,
`the most popular being the Web, CD-ROM, and print. That requirement
`alone has been sufficient to justify an investment in a new automated docu(cid:173)
`ment system. But if you are aiming not only to deliver on multiple outputs,
`but also to leverage the capabilities of electronic media, then it is even more
`important for you to build a document repository that is media-indepen(cid:173)
`dent so that you can use each medium to its full advantage.
`
`tt.2.il High value
`
`The type of information we are talking about represents a large investment
`in the "intellectual capital" required to create it, becau e it i the sort of
`informacion that js either viral to a related produ t or is the product itself
`Examples include operating guides, ervice manuals, parts catalogs, policy
`
`©!9 98 THE XML HANDDOOK™
`
`

`

`304
`
`CHAPTER 22 I ADEPT• EDITOR: EDIT FOR CONTENT MANAGEMENT
`
`and procedure manuals, and reference manuals (e.g., encyclopedias, legal
`case books, legislation, regulations, and medical drug information).
`
`t t.t.4 Long life
`
`Closely associated with "high value" is "long life." Most types of informa(cid:173)
`tion that are worth a significant investment last for years or even decades. In
`addition to the initial investment, this information often receives additional
`investment throughout its lifetime in the form of revisions.
`
`t t.t.s Reusable
`
`Although there are exceptions, much of the information in a typical publi(cid:173)
`cation from a large organization either already existed before within other
`documents or will be reused in the future.
`
`tt.t.6 Consistent
`
`Using XML makes the most sense if there are many documents of the same
`type, or single large documents that have repetitive structures. For example,
`while it is likely to be worth the investment to create a DTD for service
`bulletins if you publish 30 every year, it is probably too costly to do the
`same for a single annual report. On the other hand, single books like dictio(cid:173)
`naries and catalogs have benefited from the use ofXML.
`
`tt.t.l Created by formal processes
`
`This is the clearest differentiator of all. Virtually all information that comes
`out of a process is that is formally defined can benefit from a formal struc(cid:173)
`ture. When applied to document information, a "formal" process normally
`has the following characteristics: defined and repeatable workflow, assigned
`resources, and mission-critical deliverables.
`
`© 1 998 THE XML HANDBO O K™
`
`

`

`22.3 I CHARACTERISTICS TO CONSIDER
`
`305
`
`22.:1 1 Characteristics to consider
`
`There are a numb r of importanr characteristics to look for in a structured
`XML editor chat integrates with content management systems. These char(cid:173)
`acteristics are divided into th ree main categories:
`
`Authoring issues
`These issues affect those who create and revise the information,
`not only full-time writers but also those who are occasional
`contributors to the process.
`
`Application development issues
`These issues affect those who develop and maintain the products,
`applications, and infrastructure to support the process.
`
`Business issues
`These issues affect those who have to approve the investment in
`new technologies and who risk the most when an investment goes
`wrong.
`
`To illustrate these key characteristics, we will use illustrations based on
`ArborText's ADEPT•Editor, a structured XML authoring tool that has
`been integrated with several content management systems.
`
`ll.il. l Authoring issues
`
`When you look at a structured XML editor, you should look first to see if it
`provides all the usual editing features such as cut, copy, paste, and drag and
`drop, and convenience features such as a preferences panel and multi-level
`undo.
`Then you should look for two specific capabilities that are designed spe(cid:173)
`cifically for structured authoring:
`
`Task-matched authoring tools
`Creating highly structured documentation involves more than just
`typing. An editor with "task-matched" authoring tools provides
`editing tools that are appropriate for the type of data being
`entered.
`
`©1998 THE XML HANDBOOKTM
`
`

`

`306
`
`CHAPTER 22 I ADEPT• EDITOR: EDIT FOR CONTENT MANAGEMENT
`
`Enforced consistency
`that it remains
`To maintain the integrity of your data so
`processable and reusable, you should look for a tool that prevents
`your authors from creating data that is inconsistent or invalid.
`
`Let's take a closer look at these two capabilities.
`
`22.3.1.1
`
`"Task-matched" tools
`
`Writing a user manual involves a lot more than writing paragraphs and
`heads. Typical technical documentation consists of large amounts of differ(cid:173)
`ent types of information. A portion of that information, of course, is rela(cid:173)
`tively "free-form" text, such as titles, paragraphs, and lists.
`
`INSTALLATION
`
`For installation, reverse the above procedures. Clean corrosion/dirt from
`the cable and wire terminals before installing wiring to the solenoid
`
`STARTER RELAY
`
`The relay is located in the Power Distribution Center (PDC). Refer to the
`PDC cover for relay location.
`
`OTHER SPECIFICATIONS
`
`Figure 22-5 Rendered view of"free-form" fragment of an XML document.
`
`But even the character data is organized into a structure, and a structured
`authoring tool should provide a way to navigate and edit the structure itself.
`This capability should be provided through an alternative "structure view"
`of the document.
`Other information, especially the information in tables, is better suited
`to a restricted form of data entry such as the various controls you see in the
`dialog boxes of software programs. These controls include pushbutrons,
`check boxes, radio buttons, drop-down selection lists, sliders (e.g., volume
`controls), and other controls. These are shown in Figure 22-7
`
`©1998 THE XML HANDBOOK™
`
`

`

`2 2. 3
`
`C!-!ARA CT F.RISTIC S
`
`'J'O CONSID E R
`
`307
`
`INSTALLATION
`
`G@ tO)JiC
`- i @ title
`~ @I para
`I @ ptxt
`For installation, reverse the above
`p!Dcedmes, Clean corrosionldi!i ftorn the cable and
`wit~ tenaimus befote it~Stallit>g witit~g to the solenoid
`
`! <[,( servinfo
`
`STARTERRELAY
`
`@title
`@ 11ara
`- The telay is located itt the Power
`I [[] )Jtxt
`Distnbution Centel (PDC). R•)fet to the PDC
`cover for tehy location,
`
`_ @I servinfotype
`t-• @] spec-other
`~ ' 8 @ ~ servinfo
`Figure 22-6 Structure view offragment in Figut~e 22-5.
`
`OTHER SPECIF1CATIONS
`
`fi< Work Package
`
`Figure 22-7 Dialog box v1ew fat~ entering specialized data
`documents.
`
`in XML
`
`An authoring tool for structured XML information should allow you to
`match the type of information to be entered with the best view for the job.
`In some cases, you will want all three capabilities concurrently for the same
`document (see Figure 22-8).
`
`22.3.1.2
`
`Structure consistency
`
`Data integri~·y is the single most important factor in building a highly auto(cid:173)
`mated system that is built on top of structured data. The integrity of your
`data is crucial because automated processes must rely on the validity and
`consistency of your data in order to perform their functions properly.
`
`~~~
`
`l ~J lJ H T. 1-1
`
`1~ X M L
`
`I I 1\ N P n l) ') K T M
`
`

`

`308
`
`CHAPTER 22 I ADEPT• EDITOR: EDIT FOR CONTENT MANAGEMENT
`
`ClooeFCJJm
`
`!NSTAIJ.ATION
`
`r ~ @e
`EJ ~para
`1 00 phd -
`For installati:ln,. reverse the ab1
`procedures Clean corrosiorJdirt ftorn tiD
`wire terminals before installing wiring to
`
`€? servinfo
`@ !Hie
`
`STARTER RELA V
`
`I§ IHtra
`1 @ phrt
`The relay is located in the Power
`DistnbutionCenter(PDC) Refer to th.e!PDC
`cover for relay location
`
`OTIIER SPECIFICATIONS
`
`STARTER 2
`Table L
`
`otflrtyJoe
`oec-other
`~ seiVinfo
`[;;] tnle
`@ ~ table
`IIIII table
`1!01 vara
`1:1 ptxt
`
`J
`
`For installation, reverse the above procedures, Clean
`corrosion/dirt from the cable and wire tenninals before
`installing wiring to the solenoid
`
`STARTER RELAY
`
`·
`
`The relay is located in the Power Distribution Center
`(PDC) Refer to the1PDC cover for relay location
`
`OTHER SPECIFICATIONS
`
`• Engine should be up to operating
`
`STARTER2
`
`Figure 22-8 ADEPT•Editor showing three views concurrently.
`
`One of the most important features of a structured XML editor is its
`capability to ensure that documents remain consistently structured at all
`times. This capability is especially important when that structured data is
`stored in a repository that is accessible to other authors and to automated
`processing applications.
`
`Data integrity enforcement is illustrated in Figure 22-9, which illustrates
`that an author is dragging the first step of the "Removal" procedure to the
`"Starter" title. The cursor "prohibited" symbol shows that the current drop
`point is invalid and will not be allowed. For valid drop points, the cursor
`changes to a checkmark or plus sign.
`Continuous consistency is also vital to ensure efficient workflow and
`repeatable processes. Authors who are allowed to create invalid and incon(cid:173)
`sistent data must either clean up their data later or turn it over to someone
`else to clean up. Either way, the organization pays the cost of extra work
`that adds no value but increases costs and time to market.
`
`© 1998 TH E XML HANDDOOK™
`
`

`

`2 2 . 3
`
`I cHARAcTER Is T I c s T 0
`
`c 0 N s I D E R
`
`309
`
`INSTALLATION
`
`SAFETY SWITCHES
`
`For Removal and Installation of the ParkiN eutral Switch,
`refer to Group 21, l'ransaxle.
`l?s
`I. D!scpnnect battery negative cable
`l
`STARTER
`
`3.3LENGINE
`
`REMOVAL
`
`2. Raise vehicle.
`3. For easier servicing. do not remove the wiring from
`
`Figure .2.2-9 ADEPT • Editor showing prohibited drop point.
`
`22.11.2 Development issues
`
`Developing a powerful system to handle large amounts of structured XML
`documents is no different from other large automation projects. Building a
`system to suit your needs will i.nvolve a combination of standard produce
`and additional application development work in the form of onfiguring,
`programming, and other customizations.
`This section describes the key characteristics of a structured XML editor
`integrated with content management that primarily affect those who have
`to develop systems based on that tool.
`
`22.3.2.1
`
`Content management integration
`
`As Figure 22~ 1 illustrates, a structured XML authoring roo! is just one of
`several pieces that comprise an nrerpri e olution for creating, managing,
`and delivering d cum nt informacion. One of the key additional tools is a
`content management system.
`Organizations can integrate structured XML authoring tools with many
`different tools for content management. Some start out by building their
`applications on the file system. Others plunge right into document man-
`
`©!99 8 TH E XML HA ND BO O K™
`
`

`

`310
`
`CHAPTER 22 I ADEPT• EDITOR: EDIT FOR CONTENT MANAGEMENT
`
`agemenc or c mpon nr management. (Some ompooem management sy _
`th ir products as "authoring supporc" too ls because they are
`t ms describ
`specifically designed with information authoring- and not jusr do umenc
`management- in mind.)
`Whatever system you choose to manage your cont nc, the approach you
`take to integrating your authoring tools with your con tent management
`t ol has an normous impa ron performance, calabiliry, and ease of use.
`Ideally, you would choose an authoring tool with an API (Application
`Program Interface) specifically designed to interface with content manage(cid:173)
`ment systems. Through that API, the authoring tool can "speak" with the
`content management system at a component level and not just at a docu(cid:173)
`ment level.
`Let's examine the facilities that this type of connection enables.
`
`Seamless user interface
`Instead of switching back and forth between the authoring tool and the
`user interface of the content management system, it is possible to "build in"
`to the authoring tool everything the user needs to browse, search, and select
`documents and document components from the content management sys(cid:173)
`tem. Figure 22-10 shows an example from ADEPT•Editor, which provides
`an interface that displays the contents of the content management system.
`
`Compound document authoring
`There are clear advantages to reusing existing information instead of wast(cid:173)
`ing the time and resources to create it again. To achieve optimum reuse, you
`should create your information in small, easily reusable components and
`build "compound documents" that are simply collections of these compo(cid:173)
`nents.
`But when the time comes to edit that information, you should look for a
`tool that can load compound documents without first combining all the
`separate components into a single monolithic document. That feature
`allows the authoring tool to deliver the following benefits:
`
`• You can open a compound document and check out only
`those components you want to change, which leaves the
`remaining components available for other authors to revise.
`
`© 1 9 98 TH E X ML HANDB OOKTM
`
`

`

`2 2 . . 1
`
`C H A R A C T F. R I S T I C S T 0 C 0 N S I D lc R
`
`311
`
`El"'l Demo Virtual FS Adapter [c:\adept\objo[
`
`- @ '"" report
`- [§) &l
`rnerno
`• &I{::\:,
`j2008
`~-t t~\, vehicle
`-tEl
`rnodeldesc
`- §
`configlist
`- $1 "'"' servinfot_ype
`ffi- ~ re air·rrl
`,,1 c
`'
`
`~
`
`servinfotype, Starter Models
`
`1-User Demo DMS Adapter
`
`Figm·e 22-10 Browsing documents and components directly within a
`structut·ed X ML authoring tool.
`
`f.' You can open enormous documents very quickly because the
`authoring tool only loads the components necessary to fill the
`screen.
`
`ll)l You can perform "granular updates", where components that
`are changed can be reloaded without reloading everything else.
`
`Collaborative authoring
`
`Several users may have the same compound document open for viewing,
`but by enforcing p~rmissions and checkout at the component level, each
`user is restricted to editing the components he or she has checked out. This
`means that in a workgroup authoring environment, all subject matter
`experts can simultaneously edit their portions of the publication while see(cid:173)
`ing it in the context of the full publication.
`
`~~ l lJ l) R 'r II l', X M J. H /1. ~~ l" ll () o t-: l~-1
`
`

`

`312
`
`CHAPTER 22 I ADEPT• EDITOR: EDIT FOR CONTENT MANAGEMENT
`
`22.3.2.2 Customization
`
`Customizing the document system can provide dramatic improvements in
`productivity, information quality, and/or performance.
`For example, some of the customization that is desirable for an auto(cid:173)
`mated document system is to build tools for authors. For example, forms
`and dialog boxes may provide a faster and easier user interface to certain
`types of information (see Figure 22-11).
`
`jill Ia
`
`i:O adept
`Fie Ed~ Toots
`
`Paul Klock
`Brian Mullo_y
`Phil Storey
`
`Select names from the list$ above
`
`~Memo Sty!<
`
`I
`
`r Business
`
`r Clossic
`
`r. ContempoJaly
`
`Figrn·e 22-11 Custom dialog box for entet·ing header information.
`
`The key to efficient application development is to choose products that
`come with appropriate tools for the purpose. For instance, Arbor Text's ACL
`Designer product supports customizing the ADEPT•Editor user interface.
`You can set up forms within the ADEPT window itself (see Figure 22-7)
`and you can set up dialog boxes that pop up when needed (Figure 22-11).
`
`<P I 9 9 H T II " X M L
`
`1-l A N I) ll U 0 K ''"
`
`

`

`2 2 . 5
`
`I c II A I\ A c T E R I s T I c s T () c () N s I D E R
`
`31 ?,
`
`J
`
`Many of rhc issues surrounding th e selection, implementation, and opera~
`tion of an automated document system represent a significant impact on
`the busin ess SllCCCSS of' the projec t.
`Organizations tkn have earned outsGu1.diug returns from automated
`document systems built on XML or its parent, SCML, include the follow(cid:173)
`ing examples :
`
`•
`
`1:-:[c:tvy equipment manuftcturer improves author produ ctiviry
`by 100°/tJ, saving the th e l1iring of600 professionals over a
`five-year period.
`• Publisher of daily report reduces .~0% of its payroll costs by
`clirnillaLin g regular ovenirn c cilmugh streamlining its
`processcs.
`• Tc:x d->Ook publisher iucreas es revcnm:s substantially by oHering
`CIJStomiz.ed versions of irs tex tbooks at prices competitive to
`standard versions.
`.
`
`IJ.I I~ l) 8 T II F, J< M I,
`
`IIi\ i~ I) ll ()ilK TI- l
`
`

`

`314
`
`CHAPTER 22 I ADEPT• EDITOR: EDIT FOR CONTENT MANAGEMENT
`
`• Electronic equipment manufacturer reduces production lags
`from three weeks to two days.
`
`Let's consider the characteristics you should look for in an automated
`document system to help you achieve the sort of business successes
`described above.
`
`22.3.3.1 Authoring productivity
`
`Have you ever spent ten minutes writing a memo to your boss and another
`ten minutes formatting it to make it look good? If so, then you know how
`much time you can waste on tasks that add little value.
`With the adven ofWY fWYG w rd processing and desktop publishing
`software, authors spend as much as half rheir time manipulating the appear(cid:173)
`ance of their documents, and only the other half creacing coment. For
`many organizations, this is a tremendous unnecessary expense.
`In principle, authors are experts in the subject matter of the document
`while graphics designers are experts in the appearance of a document. When
`that principle is violated in practice, the productivity of the subject matter
`experts - the authors - drops by half or more.
`For those organizations that publish only on paper, using authors for
`document design represents a costly inefficiency. But for many organiza(cid:173)
`tions who deliver their information in multiple forms (e.g., in print and on
`the Web) and who aim to "personalize" documents through automatic
`assembly of document components to suit individual needs, WYSIWYG no
`longer makes any sense at all because the information may never be deliv(cid:173)
`ered in the same form in which it was created.
`With some tools, you may find that it is possible to force authors to leave
`the document design alone but still show them how the printed page will
`look. The problem with that approach is that the only way an author can
`affect a page layout is by rewriting to add or remove words. That could lead
`to an even greater loss of efficiency.
`Structured XML authoring .tools can separate content from presentation
`completely by showing a view of the data that uses formatting only to pro(cid:173)
`vide cues about meaning, instead of showing the actual rendition. For
`example, emphasized words are shown in italics and titles are shown in large
`bold letters, but column breaks and page breaks are not displayed (see Fig(cid:173)
`ure 22-13).
`
`© 1998 TH E XML HANDB OO KTM
`
`

`

`22.3
`
`I CHARACTERISTICS TO CONS IDER
`
`315
`
`:REMOVAL,
`REPLACEMENT, AND
`INSTALLATION
`
`SAFETY S\~CHES
`
`For Removal and Installation of the Park/Neutral Switch,
`re fer to GJoup 21, TtansaYJe
`
`S ARTER
`
`3.31 • .ENGINE
`
`REMOVAl.
`
`,
`
`1 Disconnect battery negative cable
`2 Raise vehicle
`3 For easier servicmg, do not t emove the \oVlring from
`statter at tlus time
`4, Remove tht ee starter attaching bolts from
`engine/trans axle
`' 5, Remove starler assembly from transmission housing
`Position the startet to gJm ac ces s to the wU1ngi
`
`REMOVAL, REPLACEMENT,
`AND INSTALLATION
`
`SAFETY SWITCHES
`
`For Removal and Installation
`of the Park/Neutral Switch,
`refer to Group 21, Transaxle.
`
`STARTER
`
`3.3L ENGINE
`
`REMOVAL
`
`1. Disconnect battery negative
`cable .
`
`IC..'OIC$1 DIM I
`
`Figru·e 22-13 Two views of a document, rendered with different
`stylesheets.
`
`Views designed only for aurh ring can provide addidonal assistance by
`displaying in easy-to-read form information chat may be tiny when finally
`presented. For example, copyright infoxmation may be print d in ciny let(cid:173)
`tel's but may be displayed in larger letters for authoring wirhot.u enlarging
`the entire view.
`
`22.3.3.2
`
`Batch composition
`
`In traditional WYSIWYG environments, authors manually inspect and
`adjust column breaks and page breaks to keep related elements together and
`reduce excessive white space. But using a structured XML editor allows you
`
`

`

`316
`
`CHAPTER 22 I ADEPT• EDITOR: EDIT FOR CONTENT MANAGEMENT
`
`c create a system that automates page layouts and relieves authors from this
`low-value work. "Batch composition" is the technology that makes this pos(cid:173)
`ible.
`ADEPT•Publisher fmmArborTexr is one example of a tool that provides
`batch composition capabilities. By automaticaUy balancing pag "fullness''
`with th need to keep related
`lements togeth r, the product produces
`atuactive pages with no need for manual imervention or inspe rion. ln
`addi i n, it an automaci ally generate supplemental rext, footnotes, end(cid:173)
`notes, tables of contents, cross references, indexes, and lists of figures, equa(cid:173)
`tions, and tables.
`Some organizations must lay out their documents to conform ro legal
`r quirements ud1 as the formatting of safety warnings. For example, it
`may be a requiremem that safety warnings appear in their entirety on rhe
`same page as rhe text to whid1 tb y are related. ADEPT•PubLisher can
`ensure that the document complies with that legal reqLLiremenr or issue a
`fatal error if ompJiance i not po ible (for example, if the safely warning
`exceeds the size of the page). This eliminates man ual inspe ri n and elJmi(cid:173)
`nates the liability risk from those errors that manual inspection inevitably
`overlooks.
`
`22.3.3.3
`
`Presentation independence
`
`By its nature, information stored in XML is indep ndent of any particular
`way of presencing it. That means that through rhe application of a
`stylcsheer or other transformation method , XML information can be deliv(cid:173)
`ered from a sing! information base to multiple outputs, usually automati(cid:173)
`cally (see Figure 22-3).
`The alternative to this approach, which is in common practice today, is
`to set up apr cess where authors create th.e information with the goal of
`printing it and then hand off the in