attachment-0001

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <META content="MSHTML 5.50.4611.1300" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <DIV><FONT size=2> <DIV><FONT size=2>Some time ago I proposed five additional marketing documents, which might be added to the UPDF web site.</FONT></DIV> <DIV><FONT size=2>Candidates are:</FONT></DIV> <DIV><FONT size=2>1. The idea of UPDF.</FONT></DIV> <DIV><FONT size=2>I have a small rough document available, which is not exactly on the level I'd like to see it and has to be reviewed.</FONT></DIV> <DIV><FONT size=2>I'll bring with me to Toronto. I asking for help to do this.</FONT></DIV> <DIV><FONT size=2>2. UPDF introduction in 10 minutes.</FONT></DIV> <DIV>Find a proposal below.</DIV> <DIV>Except some typos I think this is my final proposal.</DIV> <DIV>I am asking for comments and editor's review from the field.</DIV> <DIV>3. Comparison between GPD and UPDF.</DIV> <DIV>I am asking for help here.</DIV> <DIV>4. Comparison between PPD and UPDF.</DIV> <DIV> <DIV>I am asking for help here.</DIV></DIV> <DIV>5. How to build your own UPDF description from an existing sample.</DIV> <DIV>Perhaps someone from the sample implementation group could do that, so that we have some different view how to do the task.</DIV> <DIV> </DIV> <DIV>All documents are supposed to be short (like two to four pages).</DIV> <DIV>We do not want to provide indepth information for every detail, but give a newcomer a chance to get the required information as compressed as possible.</DIV> <DIV>All documents have to be final before the fall conference.</DIV> <DIV> </DIV> <DIV>Regards</DIV> <DIV>Norbert Schade</DIV> <DIV> </DIV> <DIV> </DIV></FONT></DIV> <DIV style="FONT: 10pt arial">----- Original Message ----- <DIV style="BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> <A title=norbertschade@mediaone.net href="mailto:norbertschade@mediaone.net">Norbert Schade</A> </DIV> <DIV><B>To:</B> <A title=norbertschade@oaktech.com href="mailto:norbertschade@oaktech.com">Norbert Schade</A> </DIV> <DIV><B>Sent:</B> Tuesday, July 24, 2001 8:00 PM</DIV> <DIV><B>Subject:</B> UPDF introduction in 10 minutes</DIV></DIV> <DIV><FONT size=2></FONT><FONT size=2></FONT><BR></DIV> <DIV><FONT size=2>UPDF (Universal Printer Description Format) is a data driven concept, which provides input parameters drivers need to render and output printer data.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Q.: Is UPDF is new idea?</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>A.: No, there are a other concepts, which try to accomplish a similar target.</FONT></DIV> <DIV><FONT size=2>1. There is PPD.</FONT></DIV> <DIV><FONT size=2>This is a PostScript specific concept.</FONT></DIV> <DIV><FONT size=2>In the view of many printer manufacturers and driver developers it has not evolved to nowadays needs.</FONT></DIV> <DIV><FONT size=2>PPD are not based on XML.</FONT></DIV> <DIV><FONT size=2>PPD do not support Unicode. Font handling is described outside the format.</FONT></DIV> <DIV><FONT size=2>2. GPD</FONT></DIV> <DIV><FONT size=2>This is a Microsoft specific concept, which is dedicated to Microsoft platforms.</FONT></DIV> <DIV><FONT size=2> <DIV><FONT size=2>GPD are not based on XML.</FONT></DIV> <DIV><FONT size=2>GPD do not support Unicode. Font handling is described outside the format.</FONT></DIV></FONT></DIV> <DIV><FONT size=2>3. Proprietary formats.</FONT></DIV> <DIV><FONT size=2>There are a number of company proprietary formats, which are all dedicated to a specific platform or driver system.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Q.: So why UPDF? </FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>A.: UPDF describes all data a generic driver for enterprise printers needs.</FONT></DIV> <DIV><FONT size=2>1. The concept is based on XML.</FONT></DIV> <DIV><FONT size=2>2. It supports Unicode.</FONT></DIV> <DIV><FONT size=2>3. It is platform independent.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Q.: What makes UPDF outstanding against other concepts?</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>A.: It provides some core architecture, which allows the required complexity and flexibility.</FONT></DIV> <DIV><FONT size=2>1. There are the four pillars of UPDF.</FONT></DIV> <DIV><FONT size=2>1.1. The Parameter Converter.</FONT></DIV> <DIV><FONT size=2>To be able to describe text based printer data as well as binary one, it needs a special syntax.</FONT></DIV> <DIV><FONT size=2>The Parameter Converter is the solution for that, as it can describe text based and binary data, the reference to driver keywords, the reference to UPDF keywords and even conditional output.</FONT></DIV> <DIV><FONT size=2>This functionality is not only used to specify PDL data, but is used all over the place in UPDF attributes.</FONT></DIV> <DIV><FONT size=2>1.2. Interdependencies.</FONT></DIV> <DIV><FONT size=2>Interdependencies can easily be converted from other data concepts.</FONT></DIV> <DIV><FONT size=2>The UPDF functionality is exceeding, as it allows more complex conditions by support of 'AND' and 'OR' combinations. It also allows other actions than just filtering like specifying conditional user interface messages.</FONT></DIV> <DIV><FONT size=2>1.3. Event handlers.</FONT></DIV> <DIV><FONT size=2>The order of command sequences in different PDL differs.</FONT></DIV> <DIV><FONT size=2>Event handlers allow specifying a large number of print events including Job start/end, PDL start/end as well as some feature specific events like the description of a raster graphic print sequence.</FONT></DIV> <DIV><FONT size=2>1.4. Composite features.</FONT></DIV> <DIV><FONT size=2>Basic features like media size, media source, device resolution, etc. can be arbitrarily be assembled to composite features to allow the specification of high level features.</FONT></DIV> <DIV><FONT size=2>Samples include predefined settings for subdialogs or driver defaults.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>2. A driver default per locale is supported.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>3. Device fonts are supported.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>4. Localized user interface strings as well as messages are supported.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>5. Extensible configuration.</FONT></DIV> <DIV><FONT size=2>UPDF is prepared to describe devices and installable options known at the time the device is going to be launched as well as installable options, which will be launched at a later date.</FONT></DIV> <DIV><FONT size=2>The device description can grow with the availability of installable options without the need of changing the original device description.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>6.  User group policies.</FONT></DIV> <DIV><FONT size=2>Supervisors and system administrators are always looking for chances to specify user or user group specific descriptions on top of the device description.</FONT></DIV> <DIV><FONT size=2>This includes driver settings different from driver defaults as well as additional features (based on the composite features functionality) to determine the appearance of driver features.</FONT></DIV> <DIV><FONT size=2>This functionality allows presetting certain features or hiding certain features completely for certain users.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Q.: Where will UPDF device description be available?</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>A.: Because of its platform independency the description can be provide on storage media like CD or on web site and even in the device itself.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Q.: When will UPDF be available to the public?</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>A.: UPDF, level 1, is supposed to be introduced to the public in late fall 2001.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Q.: Where can I get information about the current level of UPDF?</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>A.: People interested in the current level can always look at the UPDF web site.</FONT></DIV> <DIV><FONT size=2>The UPDF standard is embraced by the PWG (Printer Working Group) and can be accessed from <A href="http://www.pwg.org">www.pwg.org</A> in the Internet.</FONT></DIV> <DIV><FONT size=2>1. UPDF is currently based on DTD (Document Type Definitions). That may change to schemas in the near future.</FONT></DIV> <DIV><FONT size=2>The current level of dtd files can be accessed from</FONT></DIV> <DIV><FONT size=2><A href="ftp://ftp.pwg.org/pub/pwg/upd/Current_Version/DTD/">ftp://ftp.pwg.org/pub/pwg/upd/Current_Version/DTD/</A></FONT></DIV> <DIV><FONT size=2>2. A UPDF reference sample with a XML description can be accessed from </FONT></DIV> <DIV><FONT size=2><A href="ftp://ftp.pwg.org/pub/pwg/upd/Current_Version/XML_Samples/">ftp://ftp.pwg.org/pub/pwg/upd/Current_Version/XML_Samples/</A></FONT></DIV> <DIV><FONT size=2>3. A functional specification documentation is growing these days.</FONT></DIV> <DIV><FONT size=2>The current level can always be accessed from the UPDF web site.</FONT></DIV> <DIV><FONT size=2>A direct link is</FONT></DIV> <DIV><FONT size=2><A href="ftp://ftp.pwg.org/pub/pwg/www/updf/UPDF_Functional_Specification.pdf">ftp://ftp.pwg.org/pub/pwg/www/updf/UPDF_Functional_Specification.pdf</A></FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Q.: What is the simplified architecture of UPDF?</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>A.: The basic architecture is determined by a small number of XML files.</FONT></DIV> <DIV><FONT size=2>1. The unit configurations. </FONT></DIV> <DIV><FONT size=2>1.1. The device unit configuration. One file per device.</FONT></DIV> <DIV><FONT size=2>This is the driver's data entry point!</FONT></DIV> <DIV><FONT size=2>A driver will find references to the device description file, the command sequence file as well as to all locale files plus a few attributes.</FONT></DIV> <DIV><FONT size=2>1.1. The optional unit configuration. One file per optional unit.</FONT></DIV> <DIV><FONT size=2>Similar structure to the device configuration.</FONT></DIV> <DIV><FONT size=2>The driver will find the references specific to an optional unit plus a few attributes.</FONT></DIV> <DIV><FONT size=2>During installation this information may be moved into the device configuration or a platform specific reference may maintain this information.</FONT></DIV> <DIV><FONT size=2>2. The device description. One file per device.</FONT></DIV> <DIV><FONT size=2>This is the core UPDF file providing the overall device description.</FONT></DIV> <DIV><FONT size=2>You will find a number of references to command sequences and localized user interface strings.</FONT></DIV> <DIV><FONT size=2>It was a learning effect for the group that it might be better to separate the real PDL command sequences from the device description as well as the localization of user interface strings and messages.</FONT></DIV> <DIV><FONT size=2>This leverages the work for PDL experts and translators, as they are not confronted with an overwhelming amount of information they are not interested in when doing there job.</FONT></DIV> <DIV><FONT size=2>3. Command sequences. One file per device description.</FONT></DIV> <DIV><FONT size=2>This XML file holds all the PDL command sequences.</FONT></DIV> <DIV><FONT size=2>A command sequence file may hold more than the command sequences used by one device description to make it reusable. This is not a problem, as the references are totally maintained by the device description.</FONT></DIV> <DIV><FONT size=2>4. Localized user interface strings. One file per locale per device description.</FONT></DIV> <DIV><FONT size=2>This XML file holds all the user interface strings for features and messages.</FONT></DIV> <DIV><FONT size=2> <DIV><FONT size=2>A locale file may hold more than the user interface strings used by one device description to make it reusable. This is not a problem, as the references are totally maintained by the device description.</FONT></DIV></FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Q.: Is an UPDF description supposed to be used in its original XML form?</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>A.: This is left to the actual implementation.</FONT></DIV> <DIV><FONT size=2>By watching the ongoing implementations it looks more that the XML information is converted into some platform specific format. That provides some significant performance advantages and seems to help with platform specific implementations.</FONT></DIV> <DIV><FONT size=2>This may happen during installation.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Q.: How would a developer create device font data?</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>A.: This is left to the UPDF developer.</FONT></DIV> <DIV><FONT size=2>Basically someone could do that manually by filling out the proper attributes.</FONT></DIV> <DIV><FONT size=2>But we are assuming that conversion tools will be written to convert data already available for device fonts supported in other data concepts.</FONT></DIV> <DIV><FONT size=2>We are also in touch with the major font vendors like AGFA and Bitstream to have them develop concerters for their own databases.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Q.: Are there limitations in an UPDF description?</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>A.: Yes, there are.</FONT></DIV> <DIV><FONT size=2>To be able to finish a the current level we have limited ourselves not to support certain features, as there are:</FONT></DIV> <DIV><FONT size=2>1. Palette handling.</FONT></DIV> <DIV><FONT size=2>It is currently discussed, whether this is required to be supported in level 1.</FONT></DIV> <DIV><FONT size=2>2. Raster compression.</FONT></DIV> <DIV><FONT size=2>This is likely not supported in level 1, but is a candidate for the next level.</FONT></DIV> <DIV><FONT size=2>3. Vector graphic.</FONT></DIV> <DIV><FONT size=2>UPDF describes raster graphic for every PDL supported.</FONT></DIV> <DIV><FONT size=2>A driver will find exact information about the PDL supported in a device description. So if a driver supports additional functionality for certain PDL, it can securely make use of it.</FONT></DIV> <DIV><FONT size=2>4. Font download format.</FONT></DIV> <DIV><FONT size=2>UPDF may support the specification of certain download command sequences, but it is not described the structure of a download format.</FONT></DIV> <DIV><FONT size=2> <DIV><FONT size=2>A driver will find exact information about the PDL supported in a device description. So if a driver supports additional functionality for certain PDL, it can securely make use of it.</FONT></DIV> <DIV>5. Application flags.</DIV> <DIV>As applications may work differently under different platforms, this is not considered a feature of UPDF.</DIV> <DIV> </DIV> <DIV> </DIV> <DIV>Q.: Are there certain assumptions UPDF makes?</DIV> <DIV> </DIV> <DIV>A.: Yes, there are.</DIV> <DIV>The current format of UPDF includes the support of JCL (Job Control Language).</DIV> <DIV>The format provides a list of keywords of a JCL like PJL, but it is not specifying the syntax of that JCL.</DIV> <DIV>There is supposed to be a JCL specific library available on the platform, which converts the keywords into proper JCL language.</DIV> <DIV>This concept has been chosen, as there are platform specific components available in a number of cases, which are designed to do exactly that task, and as some newer JCL (Bluetooth, JDF) are described in XML as well. And we don't want to describe that a second time.</DIV> <DIV> </DIV></FONT></DIV></BODY></HTML>