Volume 26, Number
`ISSN: 0736-7260 .
`. Febru;ll-y 24, 1997
`
`13 Optronics sold to Fong. A 60%
`share ofOptronics\Vas sold to the, .
`California dealer by In~ergraph; : .
`ensuring Fang control over a CTP
`system approved fC!!.salein China.
`14 Linotype-HeB debuts scanner.
`Introduced at the company's User
`group meeting, Tango, i $65,000
`vertical drum sCanller illcludes
`GeoAssistant, the new LinoColor
`automation module.
`15 Sdkxloses $2s~m:m, keyek.
`Revenue and profit dropped for both
`the fourth quarter and fiscal year. At
`Scitex America, Shainir has replaced
`Kareiva aspi:esident~d CEO.
`17 Printware unveils platesetter.
`Priced under $50,000, the Plate(cid:173)
`Stream, 2-up polyester platesetter
`also images silver-halide film.
`18 MetaTools, Fractal to merge.
`The move could create a powerful
`new competitor for Adobe, Corel
`and Macrom~dia, particularly strong
`in freeform or natural art media.
`20 Mihalchik starts Atex anew.
`Split from Sysdecoahd ,armed with
`$25 million, Mihalchik: hopes to .
`overcome prior damage and regain a
`leading place in the market for Atex.
`2 Patterson leaves Cascade. After ·
`19 years in graphic arts, Patterson
`will take his genius to other fields.
`13 Sound Vision debuts digital camera
`15 Bitstream to acquire Archetype .
`17 Baseview places ISO-seat IQue system
`24 Obsidian drops digital cameras
`24 Kodak cuts price on DC50
`
`22 People: Managing Editor, Adobe,
`Harlequin, InContext, Information
`Access, Iris Graphics, Apple, Indigo,
`DAX, Cascade, Vidar
`23 Lean Times for Printers: A regular
`column from SeyboldisWeb site
`
`www.seyboldreport.com
`
`AtexOu'tAprill
`
`Agili:at New~week:
`Fillitlg Atex&hoeswifu PC~
`
`SINCE ~F()~THWAVE overtook the '~~blishirig system business, there havdbeen a'
`lot of differ~rit;attempts to modernize"fli~ publishing process using Macintoshes, PCS
`and varioUs appr9aches to datab~se requifements. But to many of us--especially those
`of us who both study the market and~~e these systems in ~ur work-'-the ultimate
`challenge has}een to duplicate, using standard components, the functionality and
`productivity oran Atex editorial system.. Though some of this feeling surely qn be
`attributed to romanticism, it can never be refuted that Atex built its systems welli from
`the keyboards ,to the workflow-routines to the central architecture.
`,.
`When NeWSwee~a preerriinenipublication \vith demanding editorialneeds--'(cid:173)
`decided to replace its aging Atex system \vith a customized system from Agile Enter(cid:173)
`prise built arOund pcs, we took notice. The goalwas a "warts and all" rendition of
`Atex-save/gerkeys, a "notes" mode . ' .. and no mice need apply.
`,
`The systemJ:as been p~ased in gradu,allyand is producing the whole magazine on
`a weekly basis. So confident are the participants that it.will continue to meet their :
`needs that they have plann:ed a formal shutting down of the Atex system for April 1.
`Like any system these days, the Newsweek installation offers opportunities for debate
`on many fronts,.fromthe database approach to the use ofXpress for pagination. We
`haven't tried to resolve all those issues. But we think this is an interesting story to ten.
`
`Coris: NeW" Systetn·9 ·
`For Managing Content
`
`THE NAME R.R. DONNELLEY is almost synonymous \vith the service business. But
`Donnelley's Corls'subsidiary is embarking on a new effort to sell its content-management
`system to end users. Even more interesting, though, is th~t the system, called Coris
`Publisher, is intended to be a flexible tool for managing content to be published using
`a variety of media, not only print. It's built around client-server architecture, an Oracle
`database and the object-oriented capabilities of Oracle's InterOffice. It includes an
`output planning module for handling versioning, extraction, conversion of data, and
`so on. Workflow tools will be added in an upcoming release. Part of the Coris strategy
`is to provide customization with the systems it sells.
`
`© 1997 by Seybold Publications, PO Box 644, Media, PA 19063, phone (610) 565-2480.
`R ep roduction in whole or in pm't without written permission is prohibited.
`
`Petitioners' Exhibit 1018, pg. 1
`
`

`
`Volume 26, Number 11
`
`The Seybold Report on Publishing Systems
`
`Donnelley's Coris Publisher 3.0:
`Enterprise-Wide Content Management
`
`calalog
`
`: I
`
`pubUahar toolbox )
`
`System architecture. The Coris Publisher enterprise publishing system features (left) three gate(cid:173)
`ways for accessing the database, a centtal database and toolbox (center), and provision for output
`to the Web, print, CD-ROM, etc. (right).
`
`C ORIS . INC., a subsidiary of R.R.
`
`Donnelley, has just released Coris
`Publisher 3.0. The product marks a
`turning point for Donnelley because it is
`being sold to users, rather than being kept
`inhouse as the basis for a service business,
`the traditional Donnelley approach. More
`significant, it reflects publishers' growing
`desire for a flexible tool that can help
`them manage their content effectively so
`it can be published in a variety of ways, or
`"repurposed. "
`Publishers of many kinds are begin(cid:173)
`ning to view editorial and graphic work as
`the creation of "publishing assets" to be
`stored in archives or repositories, ready for
`repurposing. At the heart of such a vision is a database, suitable for
`storing raw materials of all kinds, surrowlded by software provid(cid:173)
`ing access and conversions to all the required formats. This is the
`sort of system Coris has developed.
`The use of databases in publishing is not new, of course. Di(cid:173)
`rectory publishers were among the first to recognize the value of
`a database; some of them have been using databases for decades.
`In recent years, some catalog publishers have begt.m expanding the
`scope of their databases beyond tile traditional business informa(cid:173)
`tion' such as price, catalog number and order history, to encom(cid:173)
`pass product images, sales copy and page layout information as
`well.
`But in many areas of publishing, though the concept of a
`neutral repository is attractive, there are few successful implemen(cid:173)
`tations to point to so far. To some extent, this is because publishers
`have lacked a strong motivation for establishing such a repository.
`Several factors, most notably the rise of the Web as a publishing
`medium, are now beginning to provide that motivation, and we
`are seeing activity in this area beginning to pick up .
`The success of companies like Documentum and Cascade
`Systems, and of Quark's QPS product, have shown that there is a
`market for document management tools in publishing environ(cid:173)
`ments, and a variety of otiler players have joined the competition.
`In this article, we'll tal(e a look at what distinguishes Coris Pub(cid:173)
`lisher from other approaches, and why Coris thi.tl.kS it has an op(cid:173)
`portunity to be successful in an i.ncreasingly crowded market.
`
`Defining enterprise publishing
`
`Coris calls its product an enterprise publishing system, distinguish(cid:173)
`ing this from document management systems and workgroup
`publishing systems. Coris differentiates these terms in this fashion:
`• Document management doesn't involve the publishing steps of
`layout and composition, and high-quality images aloe not used.
`
`I
`
`II ~ill .
`II ~[~
`
`Office-oriented document management packages like PC Docs
`fit this category, as does Documentum when it is used (as it
`generally is) for managing office documents and monochrome
`images of scanned pages_
`• Workgroup publishing includes products like QPS and Canto's
`Cumulus image archive-products that serve a relatively narrow
`publishing purpose, but may lack the extensibility to handle ilie
`overall publishing needs in a large organization where many of
`the users are not publishing professionals.
`• Enterprise publishing requires a highly scalable system. It needs
`enormous capacity for all types of publishing content; it must be
`accessible across the organization; and it must support a variety
`of publishing outputs. As a practical matter, this type of capability
`is rarely necessary in small companies. Coris thinks 150 employees
`is about the minin1um size for enterprise publishing. As Coris sees
`it, Cascade is the only other company focusing on this area.
`
`Who needs enterprise publishing? Prime examples of firms
`that could benefit from an enterprise publishing system would be
`producers of catalogs and other marketing communications,
`multititle magazine publishers, some book publishers and large
`journal publishers. Coris plans to target business-to-business cata(cid:173)
`logs in particular at the start. (Coris mentions industrial catalogs of
`such things as machinery alld equipment, medical and scientific
`supplies, electronics, auto parts, and the like. ) Once it has a strong
`presence in that market, it will expand into others.
`Coris expects large numbers of companies to begin to adopt
`enterprise publishing. They will be pushed in tiut direction by a
`number of factors: the need to lower production costs; the need to
`publish on the Web as well as on paper (and perhaps CD); the
`requirement for more targeted publications; ilie impending arrival
`of electronic commerce; al1d the need to share assets more broadly
`aroLU1d tile corporation.
`Existing Coris customers include National Semiconductor; the
`Ame11Call Medical Association; Farnell Electronics, an electronic
`
`9
`
`Petitioners' Exhibit 1018, pg. 2
`
`

`
`February 24,1997
`
`The Seybold .Report on Publishing Systems
`
`The next release of InterOffice will support
`workflow creation, attaching attributes to a
`job and notification of the arrival of new jobs.
`
`component distributor in EUrope; and ABN Amro, a worldwide
`bank with its headquarters in the Netherlands. Stream International;
`a DOlmelley spinoff, is also a user.
`
`Publisher Database, the core component
`
`Coris Publisher is a client-server product. The server component,
`called the Publisher Database, is built from Oracle InterOffice object
`management software. Coris chose Oracle InterOffice for its object(cid:173)
`oriented approach, which is well suited to the tasks and diverse file
`types of publishing. Oracle's InterOffice facility will also provide
`Coris with some built-in features for workflow in the next release.
`The Publisher Database is where all the ingredients for pub(cid:173)
`lishing-photos, drawing, text, layouts, tables, etc.-reside. It is
`also the part of the system that handles backup and, in large instal(cid:173)
`lations, the automatic migration of less-used material to slower
`forms of storage, such as recordable CDs or tape cartridges.
`The Publisher Database is supplemented by other modules
`for such remaining tasks as user interaction and output processing.
`Most of the other modules are optional, and not every user will
`need all of them.
`
`3 interfaces to the Publisher Database
`
`Coris supports three different user interfaces for access to the
`Publisher Database: the Publisher Gateway, the Web Gateway and
`the Creative Gateway.
`
`Publisher Gateway. The Publisher Gateway, the standard user
`interface, is designed for Lfu'Js and corporate networks. It runs on
`
`the PC and the Mac. Wlitten in the PowerBuilder cross-platform
`development environment, it offers both Power Mac and Win-
`dows support.
`.
`The main function of the Publisher Gateway is to supply access
`to the information residing in the Publisher Database. Searches are .
`enabled by a wide variety of criteria. Results are presented either as
`lists or as (in the case of images) a set of thumbnails. A tree-struc(cid:173)
`tured arrangement of projects and files is provided, so the operator
`who knows where something is in the hierarchy can navigate down
`through the tree and select it directly, without searching.
`Once the right item is found, it can be checked out for review
`and modification. The Publisher Database offers file locking so
`that only one user has editing access to a file at a time. Additional
`users can have read-only access.
`Automating the flow of work from one person or process to
`the next is a common element in document management systems.
`Coris Publisher currently has a rudimentary way of handling
`workflow, featuring the ability to send projects from one step to
`the next and to keep track of approvals. A more sophisticated
`approach, including a graphical user interface that will show
`workflow as a diagram, will be available with Oracle's next release
`of InterOffice, due out later this year. InterOffice will provide
`support for workflow creation, for attaching workflow attributes
`to a job and for notification of the arrival of new jobs.
`
`Web Gateway (Java-based interface). The second version of
`the user interface has essentially the same features as the Publisher
`Gateway, but it is written in Java to support remote users across
`the Internet. Tlus gives Coris Publisher some valuable flexibility,
`especially in publishing environments with outside contributors and
`freelancers. If they have tl1e necessary pernLissions, Web Gateway
`users can see and do the same things as Publisher Gateway users,
`
`\ ,
`
`i .
`
`I
`I
`I
`. i
`
`I ,
`
`I
`I
`
`TJFFlma{le
`TIFF Image
`Folder
`TIFF Image
`N
`N MSVideo
`PDF
`N
`
`IMAGE
`Mo nJun2409:2e
`IMAGE
`WedSep 25 14"27 PU9_u.NGUAGE
`FriOct 04 12:40
`IMAOE
`MonJun 24 09:)5 CM_CONTHIT
`MonSep13 16:)9 PUB_PAGE
`
`Search results in Publisher Gateway. Publisher Gateway users can
`search for an object in the database by any of its attributes and they can
`see the results of a search as either a list of objects or a set of thumbnail
`images, as shown here.
`
`10
`
`Web Gateway interface. This interface enables remote users to navigate
`the Coris Publisher database hierarchy. It is almost identical to the stan(cid:173)
`dard Publisher Gateway interface, but it is written entirely in Java and
`runs under the user's Web browser (Netscape, in this example). This lets
`users who don't have any Coris software to access the Coris database. All
`they need is a Web browser and the necessary permissions.
`
`Petitioners' Exhibit 1018, pg. 3
`
`

`
`1
`" I
`I
`1
`
`, ' , ,
`
`, I
`
`· 111
`
`11'1'
`'Ii
`
`: III~ ,
`
`i
`
`111!!1
`
`IIII!I
`
`111111
`
`Volume 26, Number 11
`
`The Seybold Report on Publishing Systems
`
`Annotating a file in Acrobat. This is the Acrobat interface for adding
`annotations to a PDF me. Coris's Creative Gateway feature will transfer
`these annotations to the Xpress page. The Xpress operator creates a draft
`docmnent, saves it as PDF, and sends it out for approval. The reviewers·
`add their corriments as annotations and return the document.
`
`Display of annotations with Xpress. Coris's Creative Gateway pro(cid:173)
`vides support for the display of Acrobat annotations on an Xpress page.
`This capability allows the Xpress operator to review and implement the
`.suggestions and corrections made by the people who reviewed the PDF
`document.
`
`but the interface is implemented, through Java, within the remote
`user's Web browser.
`The development of the Web Gateway was initially funded by
`Sun. Sun wanted to underwrite some creative Java applications to
`show what the language could do, and Coris's project was one of
`them. We find it impressive.
`The hierarchical navigation window is almost identical to the
`one on the Publisher Gateway, but nodes are expanded and lists of
`available files are changed through Java programs that interact with
`the Publisher Database. A row of buttons across the bottom of the
`screen handles tasks including searching, creating new folders,
`checking things in and out, downloading, copying and deleting.
`These, too, are implemented via Java routines.
`
`Creative Gateway (Quark interface). While Coris Publisher
`is designed to support multiple meclia, it has many features specifi(cid:173)
`cally intended to benefit publishing on paper. One of these is the
`Creative Gateway, d1e interface with Xpress. It is based on Coris(cid:173)
`developed Xtensions.
`The Creative Gateway provides a way for feedback on draft
`material to be available to the Quark operator without generating
`lots of paper copies. Draft pages sent out as PDF files can be anno(cid:173)
`tated by the recipient through the alU10tation layer in Acrobat.
`Several people may receive PDPs at the same time and add com(cid:173)
`ments. When the annotated PDFs are remrned, the Creative Gate(cid:173)
`way software compiles the annotations so that the Quark operator
`sees them in the context of the Quark page. The page can then be
`moclified accordingly. This is a clever approach, one that we think
`would be appreciated in a variety of publishing environments.
`
`Other modules
`
`On ilie output side, there al'e two modules: the Output Plalmer
`and ilie Web Publisher. The Output Planner comes standard with
`Caris Publisher; the Web Publisher is an extra-cost option.
`
`Output Planner. The Output Planner is d1e main output tool
`for Caris Publisher. This module handles ilie special tasks usually
`associated with publishing from a database: versioning, extraction
`of current data, converting to multiple formats, and so on.
`For certain products (directories, legal material, some indus(cid:173)
`tlial catalogs, some kinds of documentation), automatic pagina(cid:173)
`tion software is the efficient way to mal(e pages, eid1er for Plinting
`or for clissemination as PDP files. Coris provides tools to help set up
`ilie appropriate filtering for Xyvision pagination software (which is
`what Donnelley has used internally for much of its database-pub(cid:173)
`lishing work). The same kinds of processes COl.lld be used with
`oilier pagination software. The pagination sofuval"e itself is not
`part of Coris Publisher.
`For oilier products, more creative layouts are required alld
`automatic pagination isn't appropriate. But the Output Planner
`does automate some processes for iliese pages, including preflight
`checking and spread extraction. For material destined for the Web,
`
`Coris Publisher Pricing
`Coris Publisher solutions start at around $150,000 and can reach
`$700,000 or more, depending on the size and complexity of the
`customization. The basic pricing, w hich includes licenses and
`customization, is as follows:
`
`Product
`Coris Publisher, with 16 users (Publisher Gateway,
`Publisher Database and Output Planner)
`Additional Publisher Gateway users
`To add the Web Gateway (server and 16 users)
`Additional Web Gateway users
`To add the Creative Gateway (Quark Xtensions,
`8 users)
`Additional Creative Gateway users
`Publisher Toolbox
`Web Publisher
`
`Price
`
`$94,500
`$ 5,000 for each 8 users
`$30,000
`$5,000 for each 8 users
`
`$10,000
`$5,000 for each 8 users
`$25,000
`not yet priced
`
`11
`
`Petitioners' Exhibit 1018, pg. 4
`
`

`
`February 24, 1997
`
`The Seybold Report on Publishing Systems
`
`Coris Publisher has unique advantages in its
`handling of remote users via the Web and its
`tools for collecting annotations and bringing
`them to the page.
`
`the Output Planner handles HTML generation for automatic Web
`site updates.
`These processes are driven by attributes stored in the data(cid:173)
`base. The Output Planner manages, tracks and reports on the status
`of all of thein.
`A big piece of what the Output Planner does involves filtering
`and conversion steps. Programming, either by Coris or by the user,
`is required to set up or modifY m any kinds of conversions. In the
`demonstration we saw, OrnniMark was used as the conversion tool
`in the Output Planner. Coris may decide, however, to switch to a
`different approach, such as providing a Perl programming facility.
`
`Web Publisher for catalogs. Web Publisher is a special-purpose
`module for the automatic update of catalogs on the World Wide
`
`Web. Unlike the more general HTML conversion capabilities of thee
`Output Planner, Web Publisher is catalog specific. Coris developed
`it for National Semiconductor, whose online product catalog was
`one of the early success stories of Web publishing.
`Once the process is properly set up, an entire Web catalog can
`be regenerated automatically, from the latest data in the database,
`as often as desired.
`
`Publisher Toolbox. This optional module provides an Applica-
`tion Programming Interface through which the user--or an inte~
`grator-can create programs that interact with the Publisher
`Database. It might be employed, for example, to.tie existing busi-
`ness systems into a catalog-publishing process residing in Coris
`Publisher.
`
`',','A Look '~t Coris
`"';'';:'.' .. ".,
`The narrwCoris, which may be unfamiliar to many readers, is
`. the product of several reorganizations at R.R. Dormelley. It dates
`from 1995,. when Dohnelley's Database Technology Seruices
`group and itsMobiumci'esign-seriticesgrQup were combined
`into a single operation called Coris, The database publishing ·
`software dates back farther than that, having started under
`the 'namePowerBas'e three years ago, It has been in proql,lc(cid:173)
`tionuse for aboLit two and a half years, Coris says.
`
`PowerBase 1,0 was the database publishing engine that drove .
`theXeikon printers within Don nelle/s Digital Division. A year
`and a half ago, PowerBase 2 .0 was released as the first
`Donnelley product to be put t o nori-Donnelley use. For the
`firsttime, it was supplied to a half dozen or so of Donnelley's
`customers for use in its service business,.
`
`In the next phase of the reorganization, late in 1996, the design(cid:173)
`services group was broken off again, once more becoming a
`separate organization. The database group then shifted its fqw; .
`from services to software products, At about this time, version
`3,0 of the publishing software was readied with a new name,'
`CorisPublisher ~.O, and a new marketing thrust.
`
`,In the past, Donnelley had provided database hosting, data
`input, management and output services for database-publishing
`clients. With Coris Publisher, the software is being viewed, as a
`product available for general distribution in the market. In the
`future, Caris will offer services only when Coris publishing so(cid:173)
`lutions are running at the custo mer site or when Coris is host(cid:173)
`ing the database. The focus w ill be squarely on selling 'and
`supporting Caris publishing software and associated services.
`Coris, Inc.
`7501 South Quincy st.
`Willowbrook, lL 60521-5544
`Phone (800) 351-3311 or (630) 655-7660
`Fax (630) 655-7799
`jgawkowski@coris.com
`
`www,coris,com
`
`Conclusions
`
`Coris has put together a system that provides an attractive combi-
`nation of tools for maintaining a neutral-format archive (providing
`outputs in multiple media), while still giving good support to paper
`publishing. While database approaches to help with Web publish-
`ing are numerous, most of them don't provide help with traditional
`publishing on paper (which turns out to be the more difficult task,
`in many cases).
`The initial focus 011 catalogs malces sense, given Donnelley's
`history of service to catalog publishers and the relatively limited
`installed base of catalog systems to date. We think COlis will be
`able to win over some clients that are also considering more catalog-
`focused solutions, such as the Pindar Catalog Management System
`and CatTra,'{' Coris's strength in both the database and traditional
`paper-publishing areas is an important asset, and Coris Publisher
`has some unique advantages in its handling of remote users via the
`Web and its tools for collecting annotations and bringing them to
`the page.
`
`The DOlUlelley issue. On the other hand, the path for Caris
`may not be easy. The company is trying to transform itself into a
`software vendor, and to do so it must overcome its history as a
`service provider. If Coris continues as a Donnelley subsidiary, the
`patience and understanding of the corporate parent will be an issue
`to worry about, especially given Donnelley's recent spate of bad
`financial results. On the other hand, ifit is spun oft~ it will have the
`same difficulties as any small company trying to weather the initial
`period of operation while attempting to crack open a major market.
`The market, meanwhile, seems ready for growth, but perhaps
`not rapid growth. Publishers know that they want to move in the
`direction of databases, document management and reuse of con-
`tent, but they find it hard to move fast because of the major re-
`structuring of workflow (and, sometimes, changes to the printed
`product as well) that the new methods entail. So we see moderate
`but steady growth ahead in the market for systems like this one,
`and we think Coris can play an important role in that growth if it
`can manage to stick with it.
`
`Gem;ge Alexander
`
`12
`
`Volume .. Th
`, -.j
`
`"!
`
`Optl
`. \ adE
`I
`., j
`·1
`, ,
`i
`
`I
`
`i
`
`I
`I
`!
`'"
`
`" ~
`
`Stafft
`After c
`OptrOJ
`graph .
`ers of)
`includ
`has sol
`in the
`comm
`Franci
`T
`Broth,
`ingb(
`ing,ol
`Coml
`firm a
`field, ~
`1.
`expec
`Marc]
`intere
`be di,
`Opm
`to rna
`at lea:
`expcc
`inCh
`]
`
`aru10'
`leavir
`
`Linll
`Brotl
`Inter
`ing(
`Imag
`DP~
`the s
`Chin
`invol
`• A
`tic
`B(
`ca
`al:
`m
`pi
`de
`w
`
`~
`
`Petitioners' Exhibit 1018, pg. 5