attachment-0001

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=us-ascii"> <META content="MSHTML 6.00.2800.1400" name=GENERATOR> <STYLE>@font-face { font-family: Wingdings; } @page Section1 {size: 612.0pt 792.0pt; margin: 72.0pt 90.0pt 72.0pt 90.0pt; } P.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman" } LI.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman" } DIV.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman" } A:link { COLOR: blue; TEXT-DECORATION: underline } SPAN.MsoHyperlink { COLOR: blue; TEXT-DECORATION: underline } A:visited { COLOR: purple; TEXT-DECORATION: underline } SPAN.MsoHyperlinkFollowed { COLOR: purple; TEXT-DECORATION: underline } P.MsoAutoSig { FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman" } LI.MsoAutoSig { FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman" } DIV.MsoAutoSig { FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman" } SPAN.emailstyle17 { COLOR: windowtext; FONT-FAMILY: Arial } SPAN.EmailStyle20 { COLOR: navy; FONT-FAMILY: Arial } DIV.Section1 { page: Section1 } </STYLE> </HEAD> <BODY lang=EN-US vLink=purple link=blue> <DIV dir=ltr align=left>Hi Norbert,</DIV> <DIV dir=ltr align=left> </DIV> <DIV dir=ltr align=left>Could you please move this discussion to the UPDF reflector?</DIV> <DIV dir=ltr align=left> </DIV> <DIV dir=ltr align=left>Unless there's something I'm missing, it seems more appropriate there.</DIV> <DIV dir=ltr align=left> </DIV> <DIV dir=ltr align=left>Thanks,</DIV> <DIV dir=ltr align=left> </DIV> <DIV dir=ltr align=left>lee</DIV> <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left> <HR tabIndex=-1> From: owner-pwg-announce@pwg.org [mailto:owner-pwg-announce@pwg.org] On Behalf Of Norbert Schade Sent: Wednesday, June 09, 2004 12:10 PM To: pwg-announce@pwg.org Subject: PWG-ANNOUNCE> how are optional units managed? </DIV> <DIV></DIV> <DIV class=Section1> In note 1 I already mentioned that UPDF is supposed to be extensible. That goes for human languages, but for optional units as well.   Glossary A base unit is the printer itself without anything attached to it (except RAM, which is very predictable). An optional unit is anything, which can be attached to the base unit or exchanged like optional trays, a duplexer or a finishing unit.   The challenge: Most other concepts have to know about optional units before the printer driver is compiled. That is a stolid architecture, as you never know, which optional units may come up after the first launching of the driver and device package. There are a few concepts out there, where you can add an optional unit to an existing installation and it will get merged to it. The problem is detaching it again. Imagine a base unit, which can feed Letter and A4, and an additional tray, which can feed Letter and A5. merge the sizes to one list and detach the optional unit. Will Letter size be supported after the removal? That’s what brought us to separate descriptions for optional units. The idea is to keep the description separate. So it can be detached without any problem. An optional unit can be described based on the same set of schemas as the base unit. Just the configuration instance is different (the configuration of the base unit can refer to more modules). That allows it to mirror the real world as much as possible: you connect a real optional unit to a real device à you add a configuration piece of the logical optional unit to the logical base unit.   So the main keyword here is Extensibility.   Regards Norbert Schade     Norbert Schade Software Manager Oasis Semiconductor, Inc. 201 Jones Road Waltham, MA 02451 USA tel. 1-781-370-8929 fax. 1-781-370-8990 email: norbert.schade@oasissemi.com  </DIV></BODY></HTML>