Evolving Technology for Electronic Printing and Publishing

1. Evolving Technology for Electronic Printing and Publishing Richard Marisa Cornell University rjm2@cornell.edu

2. Outline • EP&P Challenges in a period of rapid innovation • Solutions in place • Emerging Technology

3. Challenge:Student Printing in Public Labs • Authentication • Authorization • Page Description Languages • Transport • Billing

4. Challenge:Printing Finished Documents • character is often different from “casual” document • on demand vs. in bulk • multiple printshops: local, special, remote • multiple page description languages • push vs. pull printing

5. Challenge:Digital Archives • pull printing • implementing terms/conditions • naming document components • combining multiple document sources

6. Student Printing / Public Labs:Cornell’s Net-Print • replacement for VendaCards • now ca. 7,000 users • ca. 1,400,000 paid pages per year • peaking over 13,000 pages/day • average document length < 3 pp • expected to double volume in 1998-99

7. Net-Print Technology • workstation’s native print mechanisms • authentication: Kerberos • authorization: SQL database • page description language: Postscript • transport: LPD • job ticket: LPD

8. Page description language (PDL): Postscript • now common technology • legacy problems: old printers • new features cause incompatibilities: color spaces • hard to do “easy” things: page counting • Postscript version 3: PDF, prepress, pull printing, web page for drivers, management

9. PDL issue: repurposing • Simple problem: duplexing • create a document • put “<< /Duplex true >> setpagedevice”in the postscript • “publish” the postscript • print again simplex (how?)

10. PDL: PDF • “open” standard published by Adobe • integrates with web browser via free reader plug-in • complicated (or expensive) methods to use advanced features • similar repurposing problems:PDFmarks, fonts • forms, byteserving, spot rendering

11. Net-Print Transport: LPD • out of Berkley Unix • long lived, widely used • TCP based, described in RFC1179(1990) • one “file” per job, simple “job ticket” • originally line printer model, plus other formats (PS, CIF, nroff) • customized/updated by vendors and users

12. Net-Print Challenges • Large documents on the web in many formats (PDLs): HTML, PDF, Word, ... • Increasing use of electronic reserves • Faculty placing course material on the web in lieu of creating course-paks • Workstations need utilities for pull/push printing • Large jobs need to be routed to appropriate printers

13. Transport: CUPID • Consortium for University Printing and Information Distribution • Delivery of high quality printing services to remote users • Architecture proposal (1992) • Successive prototype implementations

14. CUPID:Features and benefits • a core suite of protocols and network services • enables a broad range of application specific services • supports a range of document sources • supports a range of printers: desktop to advanced function networked printers

15. CUPID:Applications • print on demand from a digital library • MOA, J-STOR • local printing of custom textbooks • local editions of news reports, business briefings, product reviews

16. CUPID:Capabilities • manage complexity • ability to query capabilities, price • mitigates software distribution • process multiple PDLs • finishing options • print preview (print to archive) • security, transactions, etc.

17. CUPID:A 3-layer architecture • publisher’s client (user / gui / application) • originating server (“middleware”) mediates end-to-end transactions • printshop client

18. EZ-Publish • pre-web printing to Docutech • interface, documents and devices all “broke” • re-implementation in CUPID: EZ-Publish II • Printing to local printers, on-demand printers, digital printshop, off-campus

19. Internet Printing Protocol • The Printer Working Group (or PWG) is an unincorporated alliance among printer manufacturers, print server developers, operating system providers and print management application developers chartered to make printers and the applications and operating systems supporting them work together better.

20. Internet Printing Protocol • Focus is to develop requirements and describe a model and semantics for Internet Printing, and ultimately define a new application level Internet Printing Protocol. • IPP 1.0 protocol submitted as Internet Draft to IETF in January, 1998

21. IPP • Client / Server protocol • Transport: HTTP • PDL: several • Ticket: binary format, content specification • Struggling with notification, local printer protocol, universal print drivers

22. Job Ticket: LPD Hcupid.cit.cornell.edu Proot Jjobname Ccupid.cit.cornell.edu Lroot fdfA059cupid.cit.cornell.edu UdfA059cupid.cit.cornell.edu Nfilename.txt

23. Job Ticket: Soleil %XRXbegin: 003.0132 %XRXdisposition: PRINT %XRXprinterName: classq %XRXdeleteSource: True %XRXPDLformat: TIFF %XRXrequirements: duplex %XRXdocumentPaperColors: dt8 %XRXpaperType-size: 216 279 %XRXcopyCount: 1 %XRXtitle: Painleve - Math Library %XRXaccount: L70-3700 %XRXjobStartMessage: No message supplied %XRXmessage: Raj - 115 White Hall %XRXsenderName: jps21 %XRXxImageShift: -5 %XRXsourceFile: UNIX:/var/spool/xerox/netqreq/CUPID895684211/cu1.0001

24. Job Ticket: CUPID opspecs => { Creator => 'jps21', 'Number of Copies' => 1, Service => 'Docutech', NetID => 'jps21', 'Account Number' => ’xxxxxxxx', 'Paper Color' => 'dt8', 'Document Sequence' => 1, Plex => 'Duplex', 'X Image Shift' => -5, 'Banner Message' => 'Raj - 115 White Hall', 'Job Name' => 'Painleve - Math Library', 'Cover Color' => '' },

25. Job Ticket: Adobe PJTF • PDF format • Documents • Page Layout • signature of “sheets” to image upon • Stand alone or embedded in PDF files

26. Job Ticket: Net-Paper

27. XML • eXtensible Markup Language • “HTML done right”, “SGML lite” • W3C recommendation (ca. Jan ‘98) <presenter>Rich Marisa</presenter> <presentation audio=“no”> Electronic Printing and Publishing </presentation> <authsys program=“MSPowerPoint” />

28. XML is for… ? • creating extensions to HTML • object data marshalling • representing hierarchic (non-flat) data records • e-commerce transactions • protocol implementation, content markup, metadata, structure, extended link information

29. Documents • content • metadata • structure • ancillary data: reviews, commentary, citations, hyperlinks

30. XML: Document Type Definitions • what elements and/or attributes are valid? • Validating parsers • DTD’s provide the “rules” • (TITLE, AUTHOR+, SUMMARY*, NOTE?) • valid values • boilerplate content

31. XML • currently supported in IE 4.0 • to be in Netscape 5.0 • several Java, Python and C++ -based parsers and utilities are available • full support soon in Perl 5 • Unicode • assists automated search tools • needed: well-known DTDs

32. H * e H e Element 1644 notation sharps / flats for maxima/minima ax + b <apply><plus/> <apply><times/> <ci> a </ci> <ci> x </ci> </apply> MathML: Content MarkupH multiplied with e

33. <apply> <power/> <apply> <plus/> <ci>a</ci> <ci>b</ci> </apply> <cn>2</cn></apply> <msup> <mfenced> <mrow> <mi>a</mi> <mo>+</mo> <mi>b</mi> </mrow> </mfenced> <mn>2</mn> </msup> MathML:(a + b)2Content and Presentation

34. PGML: Precision Graphic Markup Language • 2D graphics language that provides precise control of layout, fonts, color and printing • specification that enables Web users to readily and reliably post, control and interact with graphics on the Web • “PDF in XML”: scalable, smaller, faster than raster images

35. PGML • submitted to the W3C by Adobe, IBM, Netscape and Sun • reference code implemented in Java • imaging model used by Postscript, PDF, and the Java 2D API • Java may quickly go from a poor printing platform to one of the best

36. PGML <?XML version="1.0"?><!DOCTYPE PGML SYSTEM "pgml1.0.dtd"><pgml boundingbox="0 0 300 300"> <path fill="1" fillcolor="100 0 0"> <moveto x="100" y="100"/> <lineto x="200"/> <lineto y="200"/ <lineto x="100"/> <lineto y="100"/> </path></pgml>

37. PGML • If the workstation is doing the ripping, what will the printer look like? • If the printer is pulling documents, what will document archives look like? • If job tickets are in the documents… • If...

38. Dienst 5 • open, distributed digital library

39. Dienst structure metadata <?xml version="1.0" ?> <structure> <view type="volume"> <title>Georgetown Law Journal</title> <date>1912-1913</date> <div type="titlepage"> <display>Title Page</display> <pageimage id="1" /> <pageimage id="2" /> </div> …

40. Example: Hunter • Digital library project • Collaborative with • William S. Hein, Inc. • Cornell Law Library • Technology • Dienst • XML (based on e-bind dtd) • CUPID

41. Document Object Model • evolving technology used largely in client side scripting • makes every paragraph, image, style, even every character a distinct, individual entity • address, manipulate, change, respond to event handlers

42. MS Style Sheet Printing Extension • “coming soon to a browser near you” • style applied to printing only • <STYLE MEDIA=PRINT> • properties • page-break-after • page-break-before • values: auto always left right

43. Summary • Covered several EP&P challenges • Looked at technologies in place • Looked at a few emerging technologies • Wow: there are a lot of them! • Look at / for deconstructions

44. Some Projects at Cornell • Net-Print (student printing) • Hunter (Dienst) • EZ-Publish II (CUPID) • Net-Paper Collaboration (XML)

45. Evolving Technology for Electronic Printing and Publishing Richard Marisa Cornell University rjm2@cornell.edu