From sandram at boi.hp.com Mon Aug 3 11:30:50 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:46 2009 Subject: UPD> minutes from last two meetings Message-ID: <01BDBEC1.67E88860.sandram@boi.hp.com> Hi, I've placed minutes from the last two meetings on the ftp site at: ftp://ftp.pwf.org/pub/pwg/upd/minutes. In the minutes I added links to various sites we discussed such as the ICC spec. I'll add them here if people don't want to get the minutes yet. The Adobe PPD spec is at: http://www.adobe.com/supportservice/devrelations/PDFS/TN/5003.PPD_Spec_v4.3.pdf ICC Specification is at www.color.org. There is a link to the spec in PS and PDF formats. Actual pdf file is at ftp://sgigate.sgi.com/pub/icc/icc34.pdf From sandram at boi.hp.com Wed Sep 2 12:07:19 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:46 2009 Subject: UPD> NT 50 DDK is on web site Message-ID: <01BDD659.790BECE0.sandram@boi.hp.com> Hi, The NT 5.0 DDK is on the Microsoft web site. I pulled it off yesterday and installed the documentation and samples. It has an extensive write up of the GPD format. It's in html format - however you can print the whole topic at once. After installing the DDK go to Graphics Drivers => Design Guide => Part 3: Printer Drivers... => 4.0 Microsoft Universal Printer Driver. Remember I won't be able to bring printed copies due to the copyright and license agreement. However if everybody prints out their own copy I believe we are ok. thanks, Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Thu Sep 3 18:25:37 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:46 2009 Subject: UPD> FW: NT 50 DDK is on web site Message-ID: <01BDD757.7CAA3CE0.sandram@boi.hp.com> -----Original Message----- From: Sandra Matts [SMTP:sandram@boi.hp.com] Sent: Wednesday, September 02, 1998 10:07 AM To: Universal Printer Driver (E-mail) Subject: NT 50 DDK is on web site Hi, The NT 5.0 DDK is on the Microsoft web site. I pulled it off yesterday and installed the documentation and samples. It has an extensive write up of the GPD format. It's in html format - however you can print the whole topic at once. After installing the DDK go to Graphics Drivers => Design Guide => Part 3: Printer Drivers... => 4.0 Microsoft Universal Printer Driver. Remember I won't be able to bring printed copies due to the copyright and license agreement. However if everybody prints out their own copy I believe we are ok. thanks, Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Fri Sep 4 12:55:34 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:46 2009 Subject: UPD> NT 50 DDK is on web site Message-ID: <01BDD7F2.8B5FA2C0.sandram@boi.hp.com> Sorry about that...In my world that URL is just universally known. www.microsoft.com/ddk On the web page click "Windows NT 5.0 Beta 2 DDK" Then download DDK. The DDK is huge if you install everything - I usually just get the documentation and some of the samples. Sandra -----Original Message----- From: Jay Martin [SMTP:jkm@underscore.com] Sent: Thursday, September 03, 1998 8:52 PM To: sandram@boi.hp.com Cc: upd@pwg.org Subject: Re: UPD> NT 50 DDK is on web site Sandra, Would you mind posting the full URL for the NT 5.0 DDK to the UPD DL? Thanks. ...jay Sandra Matts wrote: > > Hi, > The NT 5.0 DDK is on the Microsoft web site. I pulled it off yesterday and installed the documentation and > samples. It has an extensive write up of the GPD format. It's in html format - however you can print the whole topic > at once. After installing the DDK go to Graphics Drivers => Design Guide => Part 3: Printer Drivers... => > 4.0 Microsoft Universal Printer Driver. > Remember I won't be able to bring printed copies due to the copyright and license agreement. However if > everybody prints out their own copy I believe we are ok. > > thanks, > Sandra > > ------------------------------------------------------------------- > Sandra Matts > Engineer / Scientist > Hewlett-Packard > 11311 Chinden Blvd. > Boise, ID 83714 > sandram@boi.hp.com > (208) 396-4755 From egglestn at lexmark.com Tue Sep 8 10:29:16 1998 From: egglestn at lexmark.com (egglestn@lexmark.com) Date: Wed May 6 14:04:46 2009 Subject: UPD> 9/8/98 Test Message-ID: <199809081430.AA18620@interlock2.lexmark.com> this is just a test....please ignore Roger From rbergma at dpc.com Fri Sep 11 12:30:13 1998 From: rbergma at dpc.com (Ron Bergman) Date: Wed May 6 14:04:46 2009 Subject: UPD> Obtaining the Microsoft GDP Documents (fwd) Message-ID: I seem to have a difficult time typing UPD. Ron ---------- Forwarded message ---------- Date: Fri, 11 Sep 1998 08:47:51 -0700 (Pacific Daylight Time) From: Ron Bergman To: udp@pwg.org Cc: sandram@boi.hp.com, paulmo@microsoft.com Subject: UDP> Obtaining the Microsoft GDP Documents After loading all the DDK files from the Microsoft site and then moving them to a system that has the recommended capacity and OS, I find that I must also have the NT 5.0 Beta 2 as the OS. Am I doing something wrong? If this is true, the document will not be available to those that cannot or will not setup NT 5.0 on a system. I personally have no objection to running NT 5.0, but cannot expend the time required simply to obtain this document. Ron Bergman Dataproducts Corp. From sandram at boi.hp.com Fri Sep 11 16:55:05 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:46 2009 Subject: UPD> How to get the Unidriver help file Message-ID: <01BDDD94.29D70E60.sandram@boi.hp.com> I managed to get the CAB files for the DDK Doc and extract the info. It's not pretty but it will keep you from having to install nt 5. The CAB extraction tool is at: www.microsoft.com/workshop/management/cab/cadl.asp The ddk file you want is graphics.exe. It's to big for me to attach so the link is at: www.microsoft.com/hwdev/ddk/download/50/graphics.exe Get the file graphics.exe and execute it. It also is a self-extracting archive. You should get a graphics.cab and a graphics.inf. The cab-sdk extracts into a bin and lib directory. Run bin\cabarc x graphics.cab This will produce the files: help_graphics.chi help_graphics.chm - this is the compiled html file Then you have to get the HTML help Workshop to view the compiled HTML file. IE version 5.0 also can view it. I don't know about IE version 4.01. www.microsoft.com/workshop/author/htmlhelp/htmlhelp.exe After installing the HTML help workshop - run it and go to View --> Compiled File. Since I've already gone through the million steps to do this, maybe Paul M. will just let me copy the the compiled html file and help viewer to the UPD archive. What do you think Paul? Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Fri Sep 11 17:18:14 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:46 2009 Subject: UPD> Typo in link address Message-ID: <01BDDD97.661515E0.sandram@boi.hp.com> -----Original Message----- From: Sandra Matts [SMTP:sandram@boi.hp.com] Sent: Friday, September 11, 1998 2:55 PM To: Universal Printer Driver (E-mail) Subject: UPD> How to get the Unidriver help file I managed to get the CAB files for the DDK Doc and extract the info. It's not pretty but it will keep you from having to install nt 5. [Sandra Matts] Real address is here The CAB extraction tool is at: www.microsoft.com/workshop/management/cab/cabdl.asp [Sandra Matts] get and install the cabinet developers kit. The ddk file you want is graphics.exe. It's to big for me to attach so the link is at: www.microsoft.com/hwdev/ddk/download/50/graphics.exe Get the file graphics.exe and execute it. It also is a self-extracting archive. You should get a graphics.cab and a graphics.inf. The cab-sdk extracts into a bin and lib directory. Run bin\cabarc x graphics.cab This will produce the files: help_graphics.chi help_graphics.chm - this is the compiled html file Then you have to get the HTML help Workshop to view the compiled HTML file. IE version 5.0 also can view it. I don't know about IE version 4.01. www.microsoft.com/workshop/author/htmlhelp/htmlhelp.exe After installing the HTML help workshop - run it and go to View --> Compiled File. Since I've already gone through the million steps to do this, maybe Paul M. will just let me copy the the compiled html file and help viewer to the UPD archive. What do you think Paul? Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Fri Sep 11 17:24:07 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:46 2009 Subject: UPD> Viewing the .chm file Message-ID: <01BDDD98.38210EE0.sandram@boi.hp.com> According to the documentation, the help_graphics.chm file can be viewed in IE 4.01. Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From don at lexmark.com Mon Sep 14 15:35:45 1998 From: don at lexmark.com (don@lexmark.com) Date: Wed May 6 14:04:46 2009 Subject: UPD> Mailing lists Message-ID: <199809141936.AA14887@interlock2.lexmark.com> The mailing lists are back up and running. Just to test everything out, I have sent this mail to ALL the mailing lists. If you get this mail on one list and not on another you think you should be on then I suggest you resubscribe by sending e-mail to: majordomo@pwg.org with the body of the note containing subscribe when is the name of the list you wish to subscribe to. You can include multiple subscriptions in the same note. Thanks for your patience during this transfer. ********************************************** * Don Wright don@lexmark.com * * Product Manager, Strategic Alliances * * Lexmark International * * 740 New Circle Rd * * Lexington, Ky 40550 * * 606-232-4808 (phone) 606-232-6740 (fax) * ********************************************** From adamsc at pogo.WV.TEK.COM Wed Sep 16 20:25:41 1998 From: adamsc at pogo.WV.TEK.COM (Chuck Adams) Date: Wed May 6 14:04:46 2009 Subject: UPD> Information on Adobe's "Portable Job Ticket Format" Message-ID: <36005705.F4379A4B@pogo.wv.tek.com> Folks, Adobe has published their Portable Job Ticket Format on their web site. To get a copy of it go to: http://www.adobe.com/supportservice/devrelations/PDFS/TN/5620.pjtf.pdf Chuck Adams Tektronix, Inc. From sandram at boi.hp.com Thu Sep 17 15:57:30 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:46 2009 Subject: UPD> update to ftp site Message-ID: <01BDE243.1D26A500.sandram@boi.hp.com> Hi all, I copied minutes from the last meeting to the upd minutes directory and the revised Charter Proposal to the archive directory. It's called UPDChrtr.doc and pdf. The plan is to propose the Charter in Savannah. If you feel this is a problem, please email me soon so the Charter can be changed. I'll copy the requirements doc this weekend. Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Thu Sep 17 15:45:47 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:46 2009 Subject: UPD> update to ftp site Message-ID: <01BDE241.79DFBEA0.sandram@boi.hp.com> Hi all, I copied minutes from the last meeting to the upd minutes directory and the revised Charter Proposal to the archive directory. It's called UPDChrtr.doc and pdf. The plan is to propose the Charter in Savannah. If you feel this is a problem, please email me soon so the Charter can be changed. I'll copy the requirements doc this weekend. Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From hastings at cp10.es.xerox.com Tue Sep 22 19:47:31 1998 From: hastings at cp10.es.xerox.com (Hastings, Tom N) Date: Wed May 6 14:04:46 2009 Subject: UPD> UPD Charter Comment: doesn't mention IPP Message-ID: <918C79AB552BD211A2BD00805F15CE8527ED0B@x-crt-es-ms1.cp10.es.xerox.com> How does the new UPD project fit with IPP? The PWG would be making a serious mistake if the new UPD project was only providing the old style of passing print instructions in the PDL data, thereby not allowing UPD printer drivers to make use of the IPP method of putting the print instructions in the protocol as an application/ipp MIME type in front of (but separated from) the PDL data. The charter includes an API to a OS independent PDL generator. It would be nice if an OS that is supporting the IPP protocol could intercept the API calls and use the semantics being passed in the API calls to wrap the IPP protocol around the document as an application/ipp MIME type. Therefore, the UPDF format needs to also include means to specify IPP Job Template attributes (and maybe operation attributes too?). So the UPD charter has to say something about IPP. (Presumably also the UPD requirements which are still being developed). Tom Hastings (310) 333-6413 From don at lexmark.com Tue Sep 22 23:48:50 1998 From: don at lexmark.com (don@lexmark.com) Date: Wed May 6 14:04:46 2009 Subject: UPD> UPD Charter Comment: doesn't mention IPP Message-ID: <199809230351.AA28253@interlock2.lexmark.com> Sorry Tom, I don't think the UPD charter _has_ to say anything about IPP. It _will_ talk about late binding and print attributes in general but UPD should not be limited to an IPP environment. I have no objection to mentioning IPP as a client to printer protocol that might take advantage of late binding but I do not believe we should structure UPD around IPP. Don "Hastings, Tom N" on 09/22/98 07:47:31 PM To: upd%pwg.org@interlock.lexmark.com cc: (bcc: Don Wright/Lex/Lexmark) bcc: Don Wright/Lex/Lexmark Subject: UPD> UPD Charter Comment: doesn't mention IPP How does the new UPD project fit with IPP? The PWG would be making a serious mistake if the new UPD project was only providing the old style of passing print instructions in the PDL data, thereby not allowing UPD printer drivers to make use of the IPP method of putting the print instructions in the protocol as an application/ipp MIME type in front of (but separated from) the PDL data. The charter includes an API to a OS independent PDL generator. It would be nice if an OS that is supporting the IPP protocol could intercept the API calls and use the semantics being passed in the API calls to wrap the IPP protocol around the document as an application/ipp MIME type. Therefore, the UPDF format needs to also include means to specify IPP Job Template attributes (and maybe operation attributes too?). So the UPD charter has to say something about IPP. (Presumably also the UPD requirements which are still being developed). Tom Hastings (310) 333-6413 From Angelo.Caruso at usa.xerox.com Wed Sep 23 09:16:44 1998 From: Angelo.Caruso at usa.xerox.com (Caruso, Angelo ) Date: Wed May 6 14:04:46 2009 Subject: UPD> UPD Charter Comment: doesn't mention IPP Message-ID: <576F850CF0D5D111A38100805FC7FA0E1A850F@usa0111ms2.eng.mc.xerox.com> Tom, Sounds like an IPP driver, as opposed to a universal print driver. Ang -----Original Message----- From: Hastings, Tom N [mailto:hastings@cp10.es.xerox.com] Sent: Tuesday, September 22, 1998 7:48 PM To: upd@pwg.org Subject: UPD> UPD Charter Comment: doesn't mention IPP How does the new UPD project fit with IPP? The PWG would be making a serious mistake if the new UPD project was only providing the old style of passing print instructions in the PDL data, thereby not allowing UPD printer drivers to make use of the IPP method of putting the print instructions in the protocol as an application/ipp MIME type in front of (but separated from) the PDL data. The charter includes an API to a OS independent PDL generator. It would be nice if an OS that is supporting the IPP protocol could intercept the API calls and use the semantics being passed in the API calls to wrap the IPP protocol around the document as an application/ipp MIME type. Therefore, the UPDF format needs to also include means to specify IPP Job Template attributes (and maybe operation attributes too?). So the UPD charter has to say something about IPP. (Presumably also the UPD requirements which are still being developed). Tom Hastings (310) 333-6413 From sandram at boi.hp.com Wed Sep 23 12:19:58 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:46 2009 Subject: FW: UPD> UPD Charter Comment: doesn't mention IPP Message-ID: <01BDE6DB.B8005DE0.sandram@boi.hp.com> I agree with Don. It important to keep it as independent as possible from the transport mechanism. However I can see it will be very important to have the implementer's guide which will show how the UPDF can be wrapped in a protocol. The req. doc currently only references IPP - it doesn't have it as a requirement. I'm trying to allocate some time to updating the req doc. I'll try to post it tomorrow. Sandra -----Original Message----- From: don@lexmark.com [SMTP:don@lexmark.com] Sent: Tuesday, September 22, 1998 9:49 PM To: Hastings, Tom N Cc: Upd@pwg.org Subject: Re: UPD> UPD Charter Comment: doesn't mention IPP Sorry Tom, I don't think the UPD charter _has_ to say anything about IPP. It _will_ talk about late binding and print attributes in general but UPD should not be limited to an IPP environment. I have no objection to mentioning IPP as a client to printer protocol that might take advantage of late binding but I do not believe we should structure UPD around IPP. Don "Hastings, Tom N" on 09/22/98 07:47:31 PM To: upd%pwg.org@interlock.lexmark.com cc: (bcc: Don Wright/Lex/Lexmark) bcc: Don Wright/Lex/Lexmark Subject: UPD> UPD Charter Comment: doesn't mention IPP How does the new UPD project fit with IPP? The PWG would be making a serious mistake if the new UPD project was only providing the old style of passing print instructions in the PDL data, thereby not allowing UPD printer drivers to make use of the IPP method of putting the print instructions in the protocol as an application/ipp MIME type in front of (but separated from) the PDL data. The charter includes an API to a OS independent PDL generator. It would be nice if an OS that is supporting the IPP protocol could intercept the API calls and use the semantics being passed in the API calls to wrap the IPP protocol around the document as an application/ipp MIME type. Therefore, the UPDF format needs to also include means to specify IPP Job Template attributes (and maybe operation attributes too?). So the UPD charter has to say something about IPP. (Presumably also the UPD requirements which are still being developed). Tom Hastings (310) 333-6413 From hastings at cp10.es.xerox.com Mon Sep 28 19:49:32 1998 From: hastings at cp10.es.xerox.com (Hastings, Tom N) Date: Wed May 6 14:04:46 2009 Subject: UPD> UPD Charter Comment: doesn't mention IPP Message-ID: <918C79AB552BD211A2BD00805F15CE8527F0E6@x-crt-es-ms1.cp10.es.xerox.com> I did not intend that UPDF only work with IPP, but I'm still concerned about how UPDF will work with IPP. I agree that UPDF should work with any job submission protocol and be as independent of job submission protocols as possible. On the other hand, if that means that a job submitted by a print driver using UPDF will be unable to contain any of the IPP Job Template attributes in the protocol, then I think we have a problem. So help me understand the intended architecture of a print driver that is using a UPDF description and the new print API with an IPP Printer. How do the capabilities described in the UPDF file about the printer, say, that it can do two-sided printing or support xxx media, get into the IPP protocol? Thanks, Tom -----Original Message----- From: Sandra Matts [mailto:sandram@boi.hp.com] Sent: Wednesday, September 23, 1998 09:20 To: 'upd@pwg.org' Subject: FW: UPD> UPD Charter Comment: doesn't mention IPP I agree with Don. It important to keep it as independent as possible from the transport mechanism. However I can see it will be very important to have the implementer's guide which will show how the UPDF can be wrapped in a protocol. The req. doc currently only references IPP - it doesn't have it as a requirement. I'm trying to allocate some time to updating the req doc. I'll try to post it tomorrow. Sandra -----Original Message----- From: don@lexmark.com [SMTP:don@lexmark.com] Sent: Tuesday, September 22, 1998 9:49 PM To: Hastings, Tom N Cc: Upd@pwg.org Subject: Re: UPD> UPD Charter Comment: doesn't mention IPP Sorry Tom, I don't think the UPD charter _has_ to say anything about IPP. It _will_ talk about late binding and print attributes in general but UPD should not be limited to an IPP environment. I have no objection to mentioning IPP as a client to printer protocol that might take advantage of late binding but I do not believe we should structure UPD around IPP. Don "Hastings, Tom N" on 09/22/98 07:47:31 PM To: upd%pwg.org@interlock.lexmark.com cc: (bcc: Don Wright/Lex/Lexmark) bcc: Don Wright/Lex/Lexmark Subject: UPD> UPD Charter Comment: doesn't mention IPP How does the new UPD project fit with IPP? The PWG would be making a serious mistake if the new UPD project was only providing the old style of passing print instructions in the PDL data, thereby not allowing UPD printer drivers to make use of the IPP method of putting the print instructions in the protocol as an application/ipp MIME type in front of (but separated from) the PDL data. The charter includes an API to a OS independent PDL generator. It would be nice if an OS that is supporting the IPP protocol could intercept the API calls and use the semantics being passed in the API calls to wrap the IPP protocol around the document as an application/ipp MIME type. Therefore, the UPDF format needs to also include means to specify IPP Job Template attributes (and maybe operation attributes too?). So the UPD charter has to say something about IPP. (Presumably also the UPD requirements which are still being developed). Tom Hastings (310) 333-6413 From BEN_BREZINSKI at HP-Vancouver-om1.om.hp.com Fri Oct 2 19:43:55 1998 From: BEN_BREZINSKI at HP-Vancouver-om1.om.hp.com (BEN_BREZINSKI@HP-Vancouver-om1.om.hp.com) Date: Wed May 6 14:04:46 2009 Subject: UPD> UPD Charter Comment: doesn't mention IPP In-Reply-To: <918C79AB552BD211A2BD00805F15CE8527F0E6@x-crt-es-ms1.cp10.es.xe> Message-ID: I think we agreed Tuesday night that the UPDF was intended to describe the printer in a OS and transport independent manner. So it should be sufficient for the UPDF to say that, in this case, that the printer suports two sided printing or some other feature. I don't think the charter of the UPD extends to the binding or suggested binding of anything described in the UPDF to any transport mechanism. The UPD can and probably should suggest implementations, but the exact implementations are up to implemntor, and the implementation will likely be different for various OS's and transports. If the transport is IPP, then the features will map into the Job template, or if the transport is something simple like HPPCL then it will map into an escape, or perhaps some transports won't support it all. Regards, Ben Brezinski ______________________________ Reply Separator _________________________________ Subject: RE: UPD> UPD Charter Comment: doesn't mention IPP Author: Non-HP-hastings (hastings@cp10.es.xerox.com) at HP-Vancouver,mimegw1 Date: 9/28/98 4:49 PM I did not intend that UPDF only work with IPP, but I'm still concerned about how UPDF will work with IPP. I agree that UPDF should work with any job submission protocol and be as independent of job submission protocols as possible. On the other hand, if that means that a job submitted by a print driver using UPDF will be unable to contain any of the IPP Job Template attributes in the protocol, then I think we have a problem. So help me understand the intended architecture of a print driver that is using a UPDF description and the new print API with an IPP Printer. How do the capabilities described in the UPDF file about the printer, say, that it can do two-sided printing or support xxx media, get into the IPP protocol? Thanks, Tom -----Original Message----- From: Sandra Matts [mailto:sandram@boi.hp.com] Sent: Wednesday, September 23, 1998 09:20 To: 'upd@pwg.org' Subject: FW: UPD> UPD Charter Comment: doesn't mention IPP I agree with Don. It important to keep it as independent as possible from the transport mechanism. However I can see it will be very important to have the implementer's guide which will show how the UPDF can be wrapped in a protocol. The req. doc currently only references IPP - it doesn't have it as a requirement. I'm trying to allocate some time to updating the req doc. I'll try to post it tomorrow. Sandra -----Original Message----- From: don@lexmark.com [SMTP:don@lexmark.com] Sent: Tuesday, September 22, 1998 9:49 PM To: Hastings, Tom N Cc: Upd@pwg.org Subject: Re: UPD> UPD Charter Comment: doesn't mention IPP Sorry Tom, I don't think the UPD charter _has_ to say anything about IPP. It _will_ talk about late binding and print attributes in general but UPD should not be limited to an IPP environment. I have no objection to mentioning IPP as a client to printer protocol that might take advantage of late binding but I do not believe we should structure UPD around IPP. Don "Hastings, Tom N" on 09/22/98 07:47:31 PM To: upd%pwg.org@interlock.lexmark.com cc: (bcc: Don Wright/Lex/Lexmark) bcc: Don Wright/Lex/Lexmark Subject: UPD> UPD Charter Comment: doesn't mention IPP How does the new UPD project fit with IPP? The PWG would be making a serious mistake if the new UPD project was only providing the old style of passing print instructions in the PDL data, thereby not allowing UPD printer drivers to make use of the IPP method of putting the print instructions in the protocol as an application/ipp MIME type in front of (but separated from) the PDL data. The charter includes an API to a OS independent PDL generator. It would be nice if an OS that is supporting the IPP protocol could intercept the API calls and use the semantics being passed in the API calls to wrap the IPP protocol around the document as an application/ipp MIME type. Therefore, the UPDF format needs to also include means to specify IPP Job Template attributes (and maybe operation attributes too?). So the UPD charter has to say something about IPP. (Presumably also the UPD requirements which are still being developed). Tom Hastings (310) 333-6413 From henrik.holst at i-data.com Mon Oct 5 05:39:30 1998 From: henrik.holst at i-data.com (henrik.holst@i-data.com) Date: Wed May 6 14:04:46 2009 Subject: IPP> RE: UPD> UPD Charter Comment: doesn't mention IPP Message-ID: I think the right thing to do would be to do it in the same way as the IPP spec. One model document (a transport independent document) and one or more protocol mapping documents. /HOLST I think we agreed Tuesday night that the UPDF was intended to describe the printer in a OS and transport independent manner. So it should be sufficient for the UPDF to say that, in this case, that the printer suports two sided printing or some other feature. I don't think the charter of the UPD extends to the binding or suggested binding of anything described in the UPDF to any transport mechanism. The UPD can and probably should suggest implementations, but the exact implementations are up to implemntor, and the implementation will likely be different for various OS's and transports. If the transport is IPP, then the features will map into the Job template, or if the transport is something simple like HPPCL then it will map into an escape, or perhaps some transports won't support it all. Regards, Ben Brezinski ______________________________ Reply Separator _________________________________ Subject: RE: UPD> UPD Charter Comment: doesn't mention IPP Author: Non-HP-hastings (hastings@cp10.es.xerox.com) at HP-Vancouver,mimegw1 Date: 9/28/98 4:49 PM I did not intend that UPDF only work with IPP, but I'm still concerned about how UPDF will work with IPP. I agree that UPDF should work with any job submission protocol and be as independent of job submission protocols as possible. On the other hand, if that means that a job submitted by a print driver using UPDF will be unable to contain any of the IPP Job Template attributes in the protocol, then I think we have a problem. So help me understand the intended architecture of a print driver that is using a UPDF description and the new print API with an IPP Printer. How do the capabilities described in the UPDF file about the printer, say, that it can do two-sided printing or support xxx media, get into the IPP protocol? Thanks, Tom -----Original Message----- From: Sandra Matts [mailto:sandram@boi.hp.com] Sent: Wednesday, September 23, 1998 09:20 To: 'upd@pwg.org' Subject: FW: UPD> UPD Charter Comment: doesn't mention IPP I agree with Don. It important to keep it as independent as possible from the transport mechanism. However I can see it will be very important to have the implementer's guide which will show how the UPDF can be wrapped in a protocol. The req. doc currently only references IPP - it doesn't have it as a requirement. I'm trying to allocate some time to updating the req doc. I'll try to post it tomorrow. Sandra -----Original Message----- From: don@lexmark.com [SMTP:don@lexmark.com] Sent: Tuesday, September 22, 1998 9:49 PM To: Hastings, Tom N Cc: Upd@pwg.org Subject: Re: UPD> UPD Charter Comment: doesn't mention IPP Sorry Tom, I don't think the UPD charter _has_ to say anything about IPP. It _will_ talk about late binding and print attributes in general but UPD should not be limited to an IPP environment. I have no objection to mentioning IPP as a client to printer protocol that might take advantage of late binding but I do not believe we should structure UPD around IPP. Don "Hastings, Tom N" on 09/22/98 07:47:31 PM To: upd%pwg.org@interlock.lexmark.com cc: (bcc: Don Wright/Lex/Lexmark) bcc: Don Wright/Lex/Lexmark Subject: UPD> UPD Charter Comment: doesn't mention IPP How does the new UPD project fit with IPP? The PWG would be making a serious mistake if the new UPD project was only providing the old style of passing print instructions in the PDL data, thereby not allowing UPD printer drivers to make use of the IPP method of putting the print instructions in the protocol as an application/ipp MIME type in front of (but separated from) the PDL data. The charter includes an API to a OS independent PDL generator. It would be nice if an OS that is supporting the IPP protocol could intercept the API calls and use the semantics being passed in the API calls to wrap the IPP protocol around the document as an application/ipp MIME type. Therefore, the UPDF format needs to also include means to specify IPP Job Template attributes (and maybe operation attributes too?). So the UPD charter has to say something about IPP. (Presumably also the UPD requirements which are still being developed). Tom Hastings (310) 333-6413 From owner-upd at pwg.org Thu Oct 22 22:03:46 1998 From: owner-upd at pwg.org (owner-upd@pwg.org) Date: Wed May 6 14:04:46 2009 Subject: No subject Message-ID: <199810230203.WAA18236@pwg.org> From owner-upd at pwg.org Thu Oct 22 22:23:57 1998 From: owner-upd at pwg.org (owner-upd@pwg.org) Date: Wed May 6 14:04:46 2009 Subject: No subject Message-ID: <199810230223.WAA18447@pwg.org> From egglestn at lexmark.com Fri Oct 23 11:12:15 1998 From: egglestn at lexmark.com (egglestn@lexmark.com) Date: Wed May 6 14:04:46 2009 Subject: UPD> Test Message-ID: <199810231513.AA25627@interlock2.lexmark.com> I have fixed the problem. Roger From sandram at boi.hp.com Fri Oct 23 10:53:31 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:46 2009 Subject: UPD> FW: new UPDF charter on ftp site Message-ID: <01BDFE62.9C8A4780.sandram@boi.hp.com> Hi All, I copied the slimmed down version of the UPDF charter. Please take a look and send me feedback by Tuesday. I want to finalize the charter and take a prelim vote by email on Wed or Thursday. The "real" PWG vote is scheduled for the PWG plenery in Tucson. The charter is named UPDChrtr2.doc and .pdf in the archive. I've also copied the gpd spec from Paul. It's in word format. Thanks Paul. Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Mon Oct 26 10:05:04 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:46 2009 Subject: FW: UPD> FW: new UPDF charter on ftp site Message-ID: <01BE00B7.576F9C20.sandram@boi.hp.com> Sorry - sloppy language. I've copied it to the UPD FTP archive. I will bring it to the next meeting - but I hope people read it before so that we can discuss over the reflector. Sandra -----Original Message----- From: Farrell, Lee [SMTP:Lee_Farrell@cissc.canon.com] Sent: Friday, October 23, 1998 3:14 PM To: 'sandram@boi.hp.com' Subject: RE: UPD> FW: new UPDF charter on ftp site Sandra, When you say you've copied the GPD spec, are you making it available to anyone else via e-mail or at the next meeting? lee ====================================== Lee Farrell Canon Information Systems 110 Innovation Drive Irvine, CA 92612 ph: (949) 856-7163 fax: (949) 856-7510 lee_farrell@cissc.canon.com ====================================== -----Original Message----- From: Sandra Matts [mailto:sandram@boi.hp.com] Sent: Friday, October 23, 1998 7:54 AM To: Universal Printer Driver (E-mail) Subject: UPD> FW: new UPDF charter on ftp site Hi All, I copied the slimmed down version of the UPDF charter. Please take a look and send me feedback by Tuesday. I want to finalize the charter and take a prelim vote by email on Wed or Thursday. The "real" PWG vote is scheduled for the PWG plenery in Tucson. The charter is named UPDChrtr2.doc and .pdf in the archive. I've also copied the gpd spec from Paul. It's in word format. Thanks Paul. Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From hastings at cp10.es.xerox.com Mon Oct 26 15:48:08 1998 From: hastings at cp10.es.xerox.com (Hastings, Tom N) Date: Wed May 6 14:04:46 2009 Subject: UPD> Article in InfoWorld on "universal print driver" (InfoWorld) (htt p://www.infoworld Message-ID: <918C79AB552BD211A2BD00805F15CE853A38B9@x-crt-es-ms1.cp10.es.xerox.com> ? ? top Group forms to develop universal print driver By Ephraim Schwartz InfoWorld Electric Posted at 5:49 AM PT, Oct 24, 1998 Working quietly, an informal group of the leading printer manufacturers is working to create a single universal print driver that will replace the more than 3,000 drivers that are currently required. The goal is to have only one driver included in the operating system, or a Universal Printer Driver Format (UPDF), with the individual characteristics of a particular printer described in a text file residing within the printer itself. "We are hoping the [bidirectional] characteristics of the UPDF will help IT managers, in that less support of printers is needed," said Sandra Matts, chair of the UPDF committee in the Printer Working Group (PWG) and an engineer scientist for Workgroup Color LaserJets at Hewlett-Packard, in Boise, Idaho. "They won't have to configure every client's computer for each printer the client will use." Commands would reside in the text file within the printer to invoke the printer's capabilities. If a user wanted to do duplex printing, for example, the text file would send the correct data stream. On the operating system side, the driver is universal. It is on the client side that unique features are described. "There is no such thing as a device-independent data stream," said Harry Lewis, a member of the PWG and a printing systems architect at IBM Printing Systems Division, in Boulder, Colo. Every device may have different characteristics that can change. A so-called meta-language developed by the PWG would be able to describe all of the features of the printer for access by the single driver in the OS. "Basically, it is similar to PostScript page description language," said Dan Wright, another PWG member and the product manager for alliances for standards at Lexmark, in Lexington, Ky. According to group members, the finished driver will be available for testing in eight months to one year, with another two months needed for interoperability testing before it ships. The universal driver will require the support of operating system vendors, such as Microsoft, as well as Unix operating system vendors. Currently, Microsoft ships a CD with more than 3,000 printer drivers with each package of Windows NT. Microsoft support appears to be in place, according to Paul Moore, program manager for Windows NT 5.0 printing. The Redmond, Wash., software company currently has Unidrive 5 in Beta 2 of NT 5.0, which is similar to technology that might be used as the basis for the UPDF, according to Moore. Moore believes the UPDF will benefit IT departments. "We think that a lot of IT manager problems arise from having too many printer drivers. The benefits [of a universal driver] would be all around," Moore said. "It will reduce the administrative load." The single driver as envisioned by members of the PWG allow a UPDF to query the printer device for capabilities. "Today, we really rely on the user selecting in the UI features of the printer," Matts said. "It's really a best guess at times. UPDF will allow our drivers to truly know what is attached to the printer at the start of the print job." The Printer Working Group can be reached at www.pwg.org . Ephraim Schwartz is an editor at large for InfoWorld. Go to the Week's Top News Stories Please direct your comments to InfoWorld Deputy News Editor, Carolyn April Copyright ? 1998 InfoWorld Media Group Inc. InfoWorld Electric is a member of IDG.net ? From labonte at zk3.dec.com Mon Oct 26 16:30:48 1998 From: labonte at zk3.dec.com (labonte@zk3.dec.com) Date: Wed May 6 14:04:46 2009 Subject: UPD> Need copy of UPD mail sent Sept and Oct Message-ID: <199810262130.AA07407@tropic.zk3.dec.com> Hi, I need a copy of the UPD e-mail sent during September and October. I noticed I had not received any UPD mail since mid September. I checked majordomo and found that my name was no longer on the list. It may have been dropped during the cut-over to Lexmark. I have subscribed again but could use a copy of all e-mail sent to UPD since September. Thanks, Ernest LaBonte Compaq Computer Corporation From sandram at boi.hp.com Tue Oct 27 12:55:39 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:46 2009 Subject: UPD> GPD doc is on UPD ftp site Message-ID: <01BE0198.56ABA9A0.sandram@boi.hp.com> Hi All, I copied the gpd spec to the ftp site in upd\Archive. It's in word format. Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Tue Oct 27 12:59:33 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:46 2009 Subject: UPD> RE: UPD Charter Proposal Message-ID: <01BE0198.E1ACAF40.sandram@boi.hp.com> good point. This is true for Windows based drivers so I will change and update the charter. Unix doesn't have a notion of driver vs OS. Does anyone want additional sentences for the Unix case? Sandra Matts -----Original Message----- From: mwu@kodak.com [SMTP:mwu@kodak.com] Sent: Monday, October 26, 1998 9:22 AM To: sandram@boi.hp.com Subject: UPD Charter Proposal >From Lotus Notes user: Michael Wu Sandra: I have a question on the Charter Proposal Line #28. I think the UPDF is for the printer driver to configure itself after read the UPDF not the operating system. UPDF will not require the OS to configure the driver. This will ensure the driver will have the dynamic discovery features. For example, when the user selectes a different printer, the driver (the same driver) should read in the UPDF and re-configure itself to be the new printer driver by changing the UI etc. OS should have no knowledge of it. On the requirement statement: since we are defining a text file format for the drivers, there is no any issues with hardware or software requirement. So any issues with hardware and software limitation should be removed. Let me know if you want specific items that I indicated above. Michael Wu Printer Driver Group Eastman Kodak Company 901 Elmgrove Road Rochester NY 14653 Office: 716.726.0654 Fax: 716.726.0374 eMail: mwu@kodak.com From labonte at zk3.dec.com Tue Oct 27 15:28:01 1998 From: labonte at zk3.dec.com (labonte@zk3.dec.com) Date: Wed May 6 14:04:47 2009 Subject: UPD> UPDF File format Message-ID: <199810272028.AA04522@tropic.zk3.dec.com> Hi, Reading the InforWorld article and comments made by Michael Wu it would seem it has been decided to use text file format. Is this correct? Past e-mail messages and posted minutes don't indicate a decision was made on the file type. For UPDF to be of any benefit I require the UPDF format be compatible between UNIX and PC's. Using a text file format works for me but I would like to know if a decision has been made. Ernest LaBonte Compaq Computer Corporation From sandram at boi.hp.com Tue Oct 27 16:06:02 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: FW: UPD> UPDF File format Message-ID: <01BE01B2.EF16AE00.sandram@boi.hp.com> We are going on the assumption that the UPDF is a text file - similiar to the PPD and GPD format. It's maybe a bit early to specify exactly the text format since we are just at the charter and requirement phase. I'll make a note to make sure we address after the Charter is approved and we start the actual specification. Sandra Matts -----Original Message----- From: labonte@zk3.dec.com [SMTP:labonte@zk3.dec.com] Sent: Tuesday, October 27, 1998 1:28 PM To: upd@pwg.org Subject: UPD> UPDF File format Hi, Reading the InforWorld article and comments made by Michael Wu it would seem it has been decided to use text file format. Is this correct? Past e-mail messages and posted minutes don't indicate a decision was made on the file type. For UPDF to be of any benefit I require the UPDF format be compatible between UNIX and PC's. Using a text file format works for me but I would like to know if a decision has been made. Ernest LaBonte Compaq Computer Corporation From mwu at kodak.com Tue Oct 27 16:10:26 1998 From: mwu at kodak.com (mwu@kodak.com) Date: Wed May 6 14:04:47 2009 Subject: UPD> UPDF File format Message-ID: <852566AA.0073A62E.00@knotes.kodak.com> >From Lotus Notes user: Michael Wu I don't know if the decision is being made. The comments I made was specific to the Charter Proposal and the Charter is to be voted on next UPDF meeting. After that, the group will "Sit Down" to discuss the requirement. In other words, there is no any kind of decisions I konw of it since the Charter has not beeen established yet. Michael Wu Printer Driver Group Eastman Kodak Company From sandram at boi.hp.com Wed Oct 28 15:37:15 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> modified UPDF Charter Message-ID: <01BE0278.141E1740.sandram@boi.hp.com> I made a minor change on line 28 of the Charter to reflect that UPDF are read in by printer drivers and not the operating system - this was a comment by Michael Wu. The file is still names UPDChrtr2.doc and PDF. I am keeping versions on my system for history but I didn't feel the need to change the Charter name since it is a short document and earlier versions aren't critical. Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From krister.svard at skandia.se Thu Nov 5 08:11:58 1998 From: krister.svard at skandia.se (krister.svard@skandia.se) Date: Wed May 6 14:04:47 2009 Subject: UPD> Amendment to UPD Message-ID: <67BE63A4EE6BD111A9220001FAD4053BB5050D@ESKP1217> Sandra, I hope you welcome influences outside the PWG/UPD circle of people. Within the UPD-specs are that the printer dynamically should be able to configure/reconfigure the UPD-driver on the host-side. I.e, the printer tells the printer driver how it is configured to relieve the end user/admin person from doing this task and keep them out of trouble. This dynamic configuration calls for a "configuration"-metalanguage to be defined that the UPD/operating system can interpret. It would be of equal of worth to be able to do configuration the other way around. I.e configure the PRINTER through a standard metalanguage, things like turning network protocolls on/off, set printer defaults and more. Would it be impossible for you, or some other PWG group, to put into your/their scope of work to define a standard "printer configuration"-metalanguage that all printers could interpret. As it is now it is a jungle. There are postscript snippets, vendor proprietary languages, private SNMP MIBs, HTTP and other ways to configure the actual printer. There could be a multiple of ways to send this configuration file to the printer. Either do a copy over the parallell port or send the file over the network via lpr, ftp or do a automatic download via bootp/tftp. Kind regards Krister Sv?rd Skandia Utdata Teknik Telefon: +46 8 788 28 87 S-103 50 STOCKHOLM Mobil: +46 70 689 28 87 E-mail: krister.svard@skandia.se http://www.skandia.se From harryl at us.ibm.com Thu Nov 5 13:23:39 1998 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:04:47 2009 Subject: UPD> Re: PWG-ANNOUNCE> vote on UPDF Charter Message-ID: <5030100028148684000002L042*@MHS> I like the charter, but I also like (and recommend) Stuarts suggestion to tighten up the goals. Stuart has done such a great job articulating these that I nominate him for editor! '-) Harry Lewis - IBM Printing Systems harryl@us.ibm.com owner-pwg-announce@pwg.org on 11/05/98 11:10:33 AM Please respond to owner-pwg-announce@pwg.org To: sandram@boi.hp.com, pwg-announce@pwg.org cc: Subject: Re: PWG-ANNOUNCE> vote on UPDF Charter Sandra, Although there is good descriptive text in the Abstract, in my opinion, the bulleted goals are too nebulous. Hopefully, the the UPDF work will result in reduced development time, simplified installation, etc. but I believe the listed goals should be more definite, describing what will actually be created by the effort, such as: Goals of UPDF: * To define a universal printer description file format that enables a printer driver to configure itself based on the unique printer characteristics. * To design or specify a description format that can be used by multiple operating systems. * To enable dynamic configuration of printers via bi-directional communication of configuration information. * To support the largest possible number of existing printers. * To provide extremely flexible mechanisms for extensibility to enable support for as yet unimagined printers and features. Since this effort used to be called Universal Printer Driver, perhaps it would also be useful to include some more descriptive text in addition to the currently terse "Also out of scope is the definition of the Universal Printer Driver", stating how this effort may relate to a Universal Printer Driver. Just my two cents. Thanks, Stuart ------------------------------------------------------------------------ Stuart Rowley Kyocera Technology Development, Inc. Network Product Dev. Mgr. 3675 Mt. Diablo Blvd. #330 Printer Division Lafayette, CA 94549 stuart.rowley@kyocera.com 925 299-7206 Fax: 925 299-2489 ------------------------------------------------------------------------ ______________________________ Reply Separator _________________________________ Subject: PWG-ANNOUNCE> vote on UPDF Charter Author: Sandra Matts at ~internet Date: 11/3/98 2:42 PM Hi All, I've copied the Charter to the UPD ftp archive. Please read it and let me know if it conveys our goal of UPDF or not. If it you don't agree - let me know by Thursday or Friday at the latest. If no one replies - I'm assuming the PWG Wed meeting participates will vote affirmatively for the Charter. Sandra Matts ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Thu Nov 5 12:35:17 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> RE: PWG-ANNOUNCE> vote on UPDF Charter Message-ID: <01BE08A7.FB9291C0.sandram@boi.hp.com> I also like the additional goal text so I will add and repost the Charter. Sandra -----Original Message----- From: Harry Lewis [SMTP:harryl@us.ibm.com] Sent: Thursday, November 05, 1998 11:24 AM To: upd@pwg.org Cc: stuart.rowley@kyocera.com; :;@us.ibm.com Subject: Re: PWG-ANNOUNCE> vote on UPDF Charter I like the charter, but I also like (and recommend) Stuarts suggestion to tighten up the goals. Stuart has done such a great job articulating these that I nominate him for editor! '-) Harry Lewis - IBM Printing Systems harryl@us.ibm.com owner-pwg-announce@pwg.org on 11/05/98 11:10:33 AM Please respond to owner-pwg-announce@pwg.org To: sandram@boi.hp.com, pwg-announce@pwg.org cc: Subject: Re: PWG-ANNOUNCE> vote on UPDF Charter Sandra, Although there is good descriptive text in the Abstract, in my opinion, the bulleted goals are too nebulous. Hopefully, the the UPDF work will result in reduced development time, simplified installation, etc. but I believe the listed goals should be more definite, describing what will actually be created by the effort, such as: Goals of UPDF: * To define a universal printer description file format that enables a printer driver to configure itself based on the unique printer characteristics. * To design or specify a description format that can be used by multiple operating systems. * To enable dynamic configuration of printers via bi-directional communication of configuration information. * To support the largest possible number of existing printers. * To provide extremely flexible mechanisms for extensibility to enable support for as yet unimagined printers and features. Since this effort used to be called Universal Printer Driver, perhaps it would also be useful to include some more descriptive text in addition to the currently terse "Also out of scope is the definition of the Universal Printer Driver", stating how this effort may relate to a Universal Printer Driver. Just my two cents. Thanks, Stuart ------------------------------------------------------------------------ Stuart Rowley Kyocera Technology Development, Inc. Network Product Dev. Mgr. 3675 Mt. Diablo Blvd. #330 Printer Division Lafayette, CA 94549 stuart.rowley@kyocera.com 925 299-7206 Fax: 925 299-2489 ------------------------------------------------------------------------ ______________________________ Reply Separator _________________________________ Subject: PWG-ANNOUNCE> vote on UPDF Charter Author: Sandra Matts at ~internet Date: 11/3/98 2:42 PM Hi All, I've copied the Charter to the UPD ftp archive. Please read it and let me know if it conveys our goal of UPDF or not. If it you don't agree - let me know by Thursday or Friday at the latest. If no one replies - I'm assuming the PWG Wed meeting participates will vote affirmatively for the Charter. Sandra Matts ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From harryl at us.ibm.com Thu Nov 5 14:06:00 1998 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:04:47 2009 Subject: UPD> Amendment to UPD Message-ID: <5030100028151362000002L022*@MHS> Skandia, I believe that, today, the Printer MIB addresses most of your concerns and is widely supported. Harry Lewis - IBM Printing Systems harryl@us.ibm.com owner-upd@pwg.org on 11/05/98 06:19:09 AM Please respond to owner-upd@pwg.org To: upd@pwg.org, sandram@boi.hp.com cc: Subject: UPD> Amendment to UPD Sandra, I hope you welcome influences outside the PWG/UPD circle of people. Within the UPD-specs are that the printer dynamically should be able to configure/reconfigure the UPD-driver on the host-side. I.e, the printer tells the printer driver how it is configured to relieve the end user/admin person from doing this task and keep them out of trouble. This dynamic configuration calls for a "configuration"-metalanguage to be defined that the UPD/operating system can interpret. It would be of equal of worth to be able to do configuration the other way around. I.e configure the PRINTER through a standard metalanguage, things like turning network protocolls on/off, set printer defaults and more. Would it be impossible for you, or some other PWG group, to put into your/their scope of work to define a standard "printer configuration"-metalanguage that all printers could interpret. As it is now it is a jungle. There are postscript snippets, vendor proprietary languages, private SNMP MIBs, HTTP and other ways to configure the actual printer. There could be a multiple of ways to send this configuration file to the printer. Either do a copy over the parallell port or send the file over the network via lpr, ftp or do a automatic download via bootp/tftp. Kind regards Krister Sv?rd Skandia Utdata Teknik Telefon: +46 8 788 28 87 S-103 50 STOCKHOLM Mobil: +46 70 689 28 87 E-mail: krister.svard@skandia.se http://www.skandia.se From sandram at boi.hp.com Thu Nov 5 17:06:56 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> another updated charter Message-ID: <01BE08CD.EEAEBEE0.sandram@boi.hp.com> Hi, I modified the Goals section using Stuart's suggested text. And I expanded the out of scope slightly. Please take a look. Remember - We vote this Wed in Tucson. Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From nschade at xionics.com Thu Nov 5 14:04:39 1998 From: nschade at xionics.com (NSchade) Date: Wed May 6 14:04:47 2009 Subject: UPD> UPD Charter Message-ID: <005e01be08ef$23a9f760$1c1343ce@nschade.xionics.com> We studied the newest version of the Charter and think this is a good start. So Xionics appreciates this as the overall direction. Regards Norbert From rbergma at dpc.com Wed Nov 18 11:42:35 1998 From: rbergma at dpc.com (Ron Bergman) Date: Wed May 6 14:04:47 2009 Subject: UPD> Adobe PPD Specification Posted Message-ID: I have loaded version 4.3 of the Adobe PPD Specification to the PWG server for your reference. The complete URL is: ftp://ftp.pwg.org/pub/pwg/upd/Archive/503_43_PPDSpec.pdf Ron Bergman Dataproducts Corp. From nschade at xionics.com Mon Dec 7 06:19:48 1998 From: nschade at xionics.com (NSchade) Date: Wed May 6 14:04:47 2009 Subject: UPD> SRS conceptional proposals Message-ID: <000f01be21d3$80aeada0$1c1343ce@nschade.xionics.com> All, find attached a four pages document with some comments on the SRS. It mainly contains eight paragraphs: 1. Work in virtual units 2. Real life parameters 3. A general parameter converter 4. Modular model descriptions where useful 5. Refer to global descriptions where useful 6. Individual technical keys per element 7. Offer printer driver support 8. Extendibility of an open format Please give it an overview to find out, if I'm in sync with you. Norbert -------------- next part -------------- A non-text attachment was scrubbed... Name: updf srs conceptional proposals.doc Type: application/msword Size: 30208 bytes Desc: not available Url : http://www.pwg.org/archives/upd/attachments/19981207/c3a22959/updfsrsconceptionalproposals.doc From sandram at boi.hp.com Tue Dec 15 11:51:18 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:04:47 2009 Subject: UPD> Agenda for friday meeting Message-ID: <01BE2810.77398A40@hpb13858.boi.hp.com> Hi All, Here's the agenda for Friday's meeting. If people have items to add or discuss, email me. 8:30 - 9:00 Agenda review and Intros 9:00 - 10:00 Adobe Job tickets 10:00 - 10:15 break 10:15 - 11:15 GPD presentation 11:15 - 12:00 Requirements document 12:00 - 1:?? lunch 1:?? - 2:30 XML Sandra Matts From robert.herriot at Eng.Sun.COM Fri Dec 18 21:25:59 1998 From: robert.herriot at Eng.Sun.COM (Robert Herriot) Date: Wed May 6 14:04:47 2009 Subject: UPD> additional comment from today's meeting about XML In-Reply-To: <01BE01B2.EF16AE00.sandram@boi.hp.com> Message-ID: <199812190220.SAA12293@woden.eng.sun.com> I would like to make one additional comment about XML that I forgot to say before I left today's meeting. XML is a potential encoding method for UPD and probably a good choice, but before we work about encoding details, we should work out the UPD model (as we did in the IPP work). The model semantics should be independent of the encoding. Bob Herriot -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/19981218/3c69a39c/attachment.html From jkm at underscore.com Tue Feb 10 17:33:17 1998 From: jkm at underscore.com (Jay Martin) Date: Wed May 6 14:05:03 2009 Subject: UPD> Background for the upcoming Austin meeting (3 March 98) Message-ID: <199706121548.AA27330@interlock2.lexmark.com> This is a multi-part message in MIME format. --------------687EAB7FDC2369E2CDD9E156 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit For the record, the attached message serves as the first background material for the expected UPD meeting to be held as part of the regularly scheduled PWG meeting series. Note that as of this writing, the UPD meeting is tentatively planned for Tuesday *night*, March 3rd. To be consistent with all other PWG projects, all correspondence about UPD (and related discussions) should be directed to the official PWG UPD mailing list (mailto:upd@pwg.org). As usual, cross-postings to other lists should be avoided whenever possible. ...jay PS: This message is cross-posted to the IPP list so as to encourage IPP participants to use the UPD list, as necessary. ---------------------------------------------------------------------- -- JK Martin | Email: jkm@underscore.com -- -- Underscore, Inc. | Voice: (603) 889-7000 -- -- 41C Sagamore Park Road | Fax: (603) 889-2699 -- -- Hudson, NH 03051-4915 | Web: http://www.underscore.com -- ---------------------------------------------------------------------- --------------687EAB7FDC2369E2CDD9E156 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Received: from smtp3.ny.us.ibm.com (smtp3.ny.us.ibm.com [198.133.22.42]) by uscore.underscore.com (8.8.4/8.7.2) with ESMTP id RAA21712 for ; Tue, 10 Feb 1998 17:11:05 -0500 (EST) Received: from relay1.server.ibm.com (relay1.server.ibm.com [9.14.2.98]) by smtp3.ny.us.ibm.com (8.8.7/8.8.7) with ESMTP id RAA21286; Tue, 10 Feb 1998 17:06:29 -0500 Received: from US.IBM.COM (d03lms03.boulder.ibm.com [9.99.80.13]) by relay1.server.ibm.com (8.8.7/8.7) with SMTP id RAA98380; Tue, 10 Feb 1998 17:07:57 -0500 Received: by US.IBM.COM (Soft-Switch LMS 2.0) with snapi via D03AU032 id 5030300017787455; Tue, 10 Feb 1998 17:15:47 -0500 From: Harry Lewis To: Cc: Subject: Re: PWG> Austin Agenda Message-ID: <5030300017787455000002L052*@MHS> Date: Tue, 10 Feb 1998 17:15:47 -0500 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 In case anyone missed it... >What topic(s) are driving the need for a meeting? Can you give >some sort of an overview or explanation as to why the meeting >is being held? (Or did I miss that in another message?) here is an excerpt form the Maui PWG minutes regarding UPD... where it = was determined that there was enough interest in UPD to warrant more discus= sion. Universal Print Driver Microsoft has incorporated a technology, similar to the Postscript PPD,= for describing printer characteristics to drivers in NT5.0. They call it th= e GPD. They already have support for about 1000 printers (including the NP12/1= 7/24). Microsoft is offering the GPD specification to the PWG for standardizat= ion and potential cross platform adoption. If this occurs, print driver develo= pment could (hypothetically) be reduced to simply producing a PPD file for Po= stscript and a GPD file for PCL. The topic will be discussed further in March an= d also in a private meeting with Microsoft which I am hoping to achieve, here = in Boulder, during February. Further - Paul Moorue reintroduced the idea of a Universal Printer Driv= er, this time, based on Microsoft's GPD (Generic Printer Description) printer dr= iver syntax. This new driver technology for Windows uses a printer descripti= on file like the Postscript PPD but applies it to any raster printer (PCL etc).= The result is one "universal" driver with many GPD files that enable the cl= ient build the right PDL for each printer. About 1000 printers are already d= escribed in this syntax on the NT5.0 Beta DDK. A GPD is about 30K bytes per prin= ter. The ASCII GPD file can express device options, limitations between feat= ures (ex. "don't allow envelopes unless AUX tray is installed" or ("can't st= aple if media is transparency") and may be used to dynamically build the pri= nt driver UI. Settings can be grouped, for example, for the "fastest", or = "highest quality". Currently, the GPD is static or manually updated. A future improvement could be to dynamically update the GPD from something like = a Printer MIB database, preferable using IPP. Microsoft is offering the syntax as a model for standardization, beyond= the Windows platform. There was enough interest that an agenda item has bee= n agreed to for the March meeting in Austin. People would like an opportunity to= look at the spec prior to this meeting. Concern was expressed that, in general= , job control should be migrated out of PDLs into the control of job submissi= on languages or protocols (like IPP, PJL or the Adobe Job Ticket). Some participants were also concerned about loss of product differentiation = if one Universal Print Driver were to become ubiquitous. Others wondered if it= would be possible to structure the GPD in XML. Harry Lewis - IBM Printing Systems = --------------687EAB7FDC2369E2CDD9E156-- From jjv at page.kodak.com Wed Feb 11 09:35:09 1998 From: jjv at page.kodak.com (Jeffrey J. Van Wie) Date: Wed May 6 14:05:03 2009 Subject: UPD> How to get on UPD mailing list Message-ID: <34E1B71D.5883@page.kodak.com> How do you get on the upd@pwg.org (Universal Print Driver) groups mailing list. I am presently on the IPP.. Also, how do you get on the pwg@pwg.org. Thanks... -- Jeffrey Van Wie Eastman Kodak Company Tel: 716-253-6104 Fax: 716-726-9950 Email: jjv@page.kodak.com From jds at underscore.com Thu Feb 12 10:47:55 1998 From: jds at underscore.com (Jeffrey D. Schnitzer) Date: Wed May 6 14:05:03 2009 Subject: UPD> PWG Mail Server Message-ID: <34E1B71D.5883@page.kodak.com> It looks like the PWG mail server is healthy again, unfortunately several messages were lost yesterday. The IPP hypermail archive had grown quite large, so I've split off a new archive. The old IPP hypermail archive is available at HTTP://www.pwg.org/hypermail/ipp-pre980212/ The new (current) IPP hypermail archive is still HTTP://www.pwg.org/hypermail/ipp/ Be aware that some messages (those with large attachments) do not always get archived successfully by hypermail. People should not be attaching large files in any case; rather they should upload their contribution to the FTP server and include just the pointer in their mail to the list. /Jeff --------------------------------------------------------------- Jeffrey D. Schnitzer | Email: jds@underscore.com Underscore, Inc. | Voice: (603) 889-7000 41-C Sagamore Park Rd | Fax: (603) 889-2699 Hudson, NH 03051-4915 | Web: http://www.underscore.com --------------------------------------------------------------- From jds at underscore.com Fri Feb 20 09:52:16 1998 From: jds at underscore.com (Jeffrey D. Schnitzer) Date: Wed May 6 14:05:03 2009 Subject: UPD> UPD mailing list (was IPP> UPD meeting) Message-ID: <34E1B71D.5883@page.kodak.com> Keith Carter asked: > > Is there a UPD mailing list? > The UPD mailing list is . To add yourself to the list, send mail to with the following as the body of the message: subscribe upd end The list has been in place since May'97, but there was little traffic on it. It's hypermail archive is at: http://www.pwg.org/hypermail/upd /Jeff --------------------------------------------------------------- Jeffrey D. Schnitzer | Email: jds@underscore.com Underscore, Inc. | Voice: (603) 889-7000 41-C Sagamore Park Rd | Fax: (603) 889-2699 Hudson, NH 03051-4915 | Web: http://www.underscore.com --------------------------------------------------------------- From Angelo.Caruso at usa.xerox.com Fri Feb 20 12:54:22 1998 From: Angelo.Caruso at usa.xerox.com (Caruso, Angelo ) Date: Wed May 6 14:05:03 2009 Subject: UPD> RE: IPP> UPD meeting Message-ID: <34E1B71D.5883@page.kodak.com> Keith, Any chance of setting up a dial-in number for those of us who cannot be in Austin? Thanks, Angelo -----Original Message----- From: Keith Carter [SMTP:carterk@us.ibm.com] Sent: Friday, February 20, 1998 9:25 AM To: p1394@pwg.org; pwg@pwg.org; fin@pwg.org; jmp@pwg.org; ipp@pwg.org Subject: IPP> UPD meeting >I have one of our printer driver guys that wants to come JUST for the >discussion on UPD. But I really need to able to tell him a firm agenda >for this meeting in Austin. Is there a final decision on when the UPD >meeting will be held? > >Thanx > >R. Ok, here's a stake in the lake. The UPD meeting will be 7:00PM-10:00PM CST on Tuesday, March 3. The meeting is in the Texas 5 meeting room. For directions to the room, look at the meeting board in the lobby or ask the hotel desk. I am recruiting a chair for the meeting who can then drive the agenda. I understand Paul Moore of Microsoft will discuss their Universal Print Driver at this meeting. Is there a UPD mailing list? Have a super day, Keith Carter Senior Software Engineer IBM Network Computing Software Division in Austin, Texas internet email: carterk@us.ibm.com Notes email: Keith Carter/Austin/IBM@IBMUS phone: 512-838-2155 tie-line: 678-2155 fax: 512-838-0169 From Angelo.Caruso at usa.xerox.com Thu Feb 26 14:01:37 1998 From: Angelo.Caruso at usa.xerox.com (Caruso, Angelo ) Date: Wed May 6 14:05:03 2009 Subject: UPD> RE: IPP> Universal Print Driver session in Austin on Tuesday nigh t Message-ID: <34E1B71D.5883@page.kodak.com> By the way, a week or so ago I made a request that someone please set up a dial in number for the UPD session. Is anyone else interested in that but me? Thanks, Angelo -----Original Message----- From: Carl-Uno Manros [SMTP:cmanros@cp10.es.xerox.com] Sent: Thursday, February 26, 1998 12:41 PM To: ipp@pwg.org Subject: IPP> Universal Print Driver session in Austin on Tuesday night Hi all, I have just spoken to Don Wright about who chairs the UPD meeting. Don will, so that issue is settled. Carl-Uno Carl-Uno Manros Principal Engineer - Advanced Printing Standards - Xerox Corporation 701 S. Aviation Blvd., El Segundo, CA, M/S: ESAE-231 Phone +1-310-333 8273, Fax +1-310-333 5514 Email: manros@cp10.es.xerox.com From robertt at vcd.hp.com Fri Feb 27 20:20:22 1998 From: robertt at vcd.hp.com (Bob Taylor) Date: Wed May 6 14:05:03 2009 Subject: UPD> RE: IPP> Universal Print Driver session in Austin on Tuesday nigh t Message-ID: <34E1B71D.5883@page.kodak.com> I'd probably be interested in a dial-in for this. thanks, Bob --------------------------------------------------- Bob Taylor | Hewlett-Packard Vancouver Printer Division | mailto:robertt@vcd.hp.com | phone: 360.212.2625/T212.2625 | fax: 360.212.4154/T212.4154 | --------------------------------------------------- On Thursday, February 26, 1998 11:02 AM, Caruso, Angelo [SMTP:Angelo.Caruso@usa.xerox.com] wrote: > By the way, a week or so ago I made a request that someone please set up > a dial in number for the UPD session. Is anyone else interested in that > but me? > > Thanks, > Angelo > > -----Original Message----- > From: Carl-Uno Manros [SMTP:cmanros@cp10.es.xerox.com] > Sent: Thursday, February 26, 1998 12:41 PM > To: ipp@pwg.org > Subject: IPP> Universal Print Driver session in Austin on > Tuesday night > > Hi all, > > I have just spoken to Don Wright about who chairs the UPD > meeting. > > Don will, so that issue is settled. > > Carl-Uno > Carl-Uno Manros > Principal Engineer - Advanced Printing Standards - Xerox > Corporation > 701 S. Aviation Blvd., El Segundo, CA, M/S: ESAE-231 > Phone +1-310-333 8273, Fax +1-310-333 5514 > Email: manros@cp10.es.xerox.com From carterk at us.ibm.com Fri Feb 20 15:01:07 1998 From: carterk at us.ibm.com (Keith Carter) Date: Wed May 6 14:05:03 2009 Subject: UPD> Chair for UPD meeting on March 3 Message-ID: <34E1B71D.5883@page.kodak.com> UPDers, Don Wright has graciously agreed to chair the UPD meeting on the evening of March 3. Have a super day, Keith Carter Senior Software Engineer IBM Network Computing Software Division in Austin, Texas internet email: carterk@us.ibm.com Notes email: Keith Carter/Austin/IBM@IBMUS phone: 512-838-2155 tie-line: 678-2155 fax: 512-838-0169 From carterk at us.ibm.com Sat Feb 28 13:55:53 1998 From: carterk at us.ibm.com (Keith Carter) Date: Wed May 6 14:05:03 2009 Subject: UPD> Call in number for Universal Print Driver session in Austin Message-ID: <34E1B71D.5883@page.kodak.com> UPDers, I've been out and just caught up with the email from Angelo Caruso and Bob Taylor requesting a call in number for the UPD meeting on March 4 at 7:00PM CST. I'll followup and inform you accordingly. Don Wright will chair the UPD meeting. Have a super day, Keith Carter Senior Software Engineer IBM Network Computing Software Division in Austin, Texas internet email: carterk@us.ibm.com Notes email: Keith Carter/Austin/IBM@IBMUS phone: 512-838-2155 tie-line: 678-2155 fax: 512-838-0169 From imcdonal at eso.mc.xerox.com Sat Feb 28 20:14:08 1998 From: imcdonal at eso.mc.xerox.com (Ira Mcdonald x10962) Date: Wed May 6 14:05:03 2009 Subject: UPD> Re: IPP> Call in number for Universal Print Driver session in Austin In-Reply-To: Call in number for Universal Print Driver session in Austin> Message-ID: <9803010114.AA07747@snorkel.eso.mc.xerox.com> Hi Keith, Thanks - Ill circulate this within Xerox and see if any of our driver people can join in. Cheers, - Ira McDonald (outside consultant at Xerox) High North Inc From Angelo.Caruso at usa.xerox.com Mon Mar 2 18:52:49 1998 From: Angelo.Caruso at usa.xerox.com (Caruso, Angelo ) Date: Wed May 6 14:05:03 2009 Subject: UPD> RE: PWG> Call in number for UPD meeting on March 3 Message-ID: <9803010114.AA07747@snorkel.eso.mc.xerox.com> Keith, Thanks for setting up the dial-in line. I am now embarrassed to report that due to an almost-forgotten personal conflict that evening, I will be unable to dial in. I will try to find other interested individuals to dial in. Thanks, Angelo -----Original Message----- From: Keith Carter [SMTP:carterk@us.ibm.com] Sent: Monday, March 02, 1998 4:22 PM To: pwg@pwg.org Subject: PWG> Call in number for UPD meeting on March 3 The call in number for the UPD meeting at 7:00PM CST on Tuesday, March 3 is as follows: Phone = 1-800-369-1883 Passcode = 24427 (the call is unattended so enter the passcode when prompted to do so) There are 10 lines reserved for the call. Unfortunately, I will not be able to attend the UPD meeting so whomever is at the meeting please dial the above number and passcode on the phone in the meeting room. Have a super day, Keith Carter Senior Software Engineer IBM Network Computing Software Division in Austin, Texas internet email: carterk@us.ibm.com Notes email: Keith Carter/Austin/IBM@IBMUS phone: 512-838-2155 tie-line: 678-2155 fax: 512-838-0169 From jkm at underscore.com Mon Mar 9 13:15:19 1998 From: jkm at underscore.com (Jay Martin) Date: Wed May 6 14:05:03 2009 Subject: UPD> Test message --- please ignore Message-ID: <9803010114.AA07747@snorkel.eso.mc.xerox.com> This is an administrative message used to test the PWG's UPD Project mailing list. Please ignore it. From don at lexmark.com Tue Mar 17 09:33:05 1998 From: don at lexmark.com (don@lexmark.com) Date: Wed May 6 14:05:03 2009 Subject: UPD> UPD Meeting Minutes for March Message-ID: <199803171437.AA09386@interlock2.lexmark.com> I have posted the March UPD meeting minutes to the ftp server at: ftp://www.pwg.org/pub/pwg/upd/minutes/upd-0398.txt ftp://www.pwg.org/pub/pwg/upd/minutes/upd-0398.pdf Additionally, the text version is below. At the meeting, Paul Moore of Microsoft said he would try to get the requirements document used for developing the GPD concept, syntax and implementation. Paul has since posted to the IPP list that he is unable to located those. As such we must start the requirements development process with a "blank sheet of paper." Would anyone be willing to understake this effort? Additionally, this study group does not have a chair or a secretary. Any takers on those? I have not scheduled a meeting for Portland. I think we need to thrash out some requirements first and not start the meeting with no proposals. Additionally, since there has been no discussion on this list since the meeting, it would seem that the priority is rather low. I will decide on the next meeting date once some work and discussion has started. Don ********************************************** * Don Wright don@lexmark.com * * Product Manager, Strategic Alliances * * Lexmark International * * 740 New Circle Rd * * Lexington, Ky 40550 * * 606-232-4808 (phone) 606-232-6740 (fax) * ********************************************** ------------------------------------------------------- Universal Printer Driver Study Group Meeting Minutes March 3, 1998 Austin, Texas The meeting was started at 7:10 PM and was chaired by Don Wright. These minutes were recorded by Peter Michalek and edited by Don Wright Attendees were: Don Wright - Lexmark Brian Batchelder - HP Mark VanderWiele - IBM Mark Hamzy - IBM Fumio Nagasaka - Epson Fumio Samitsu - Epson Mabry Dozier - QMS Lloyd Young - Lexmark Yoshinori Murakami - Epson Greg LeClair - Epson Lee Farrell - Canon Akihiro Shimura - Canon Takashi Isoda - Canon Peter Michalek - Shinesoft Bob Broccolo - Kodak Carl-Uno Manros - Xerox Harry Lewis - IB< Bob Pentecost - HP Ron Bergman - DataProducts Praveen Kanipakam - Sharp Scott Isaacson - Novell Paul Moore - Microsoft This was the second meeting of the UPD study group. Before we met in San Diego in May 97. This subject came up in Maui and we agreed to meet again to explore the issues and decide whether to pursue this approach. Agenda: * why are we here? * what do we want to accomplish * Paul Moore will give an overview of UPD. Then an open discussion * We should also define the UPD. Tentative definition: Collection of software (exe or dll) which takes graphic context created by the user, changes it to a printer stream and causes an equivalent representation to be presented on a printer. It has nothing to do with redirection, tcp/ip or ipx. * Paul Moore: good description for printer driver but not in general. * Printer driver needs to figure something out when talking to printer (therefore the previous definition would be insufficient. * Does universality include across all platforms? Don summarized this on the slide: * convert text & graphics to something a printer understands * UPD needs to be: - universal: - single piece of code that adapts to printer - how? We need to consider various dynamic aspects of this UPD: -- compile time vs. run time -- single platform or all platforms? * localization/internationalization - support for languages Carl-Uno Manros: not only image out of the driver but also attributes and possible something like a JOB ticket. Other aspects of UPD: data stream commonality: transport, datastream, other aspects of a printer job (page description) How do you represent content without notion of presentation? * size is important, but other presentation parameters are not. * UPD is not specific to any transport or print protocol: i.e. not specific to IPP, LPR, etc. * Should the driver definition contain embellishments like overlays? * What similar attempts have there been in the past and what can we learn from them? - PPD's - miniddrv/unidrv GPD - JPrint Bristol: java print api - upd concept * What are the capabilities? * How much flexibility do we provide and when: - compile time? - install time? - print time? * It was re-iterated that the localization is very important * Does universal mean of all printers or all times or universal for the future? What's the range of printers the UPD should support? * Is the driver going to present a standard API? * Should the UPD separate PDL and job attributes? * Picture - flow diagram: app -> upd -> printer * What's the relationship of screen driver and printer driver? * How do you handle color: which color space should we use? * Extent of customizability/extensibility of driver ************************************* Section 2: Paul Moore: GPD presentation This is an incomplete summary of the presentation. More details can be obtained from Paul Moore. MS UPD Aims: Single executable that prints to any printer Reduce time and effort to support a new printer Higher Quality, better performance NT4 has RASDD (v1 or unidrive) nt5 has unidriver All NT5: PS Unidrive > 1500 printer plotters Single ww binary MS addresses the following universality requirements: - localization - single binary There were suggestions from the audience that some printers are not supported. PaulM: unidriver doesn't support real-time rendering (or Host Based RIP), only raster-type of printers. PaulM: The job of the printer driver is to: - render the description: - merge the job ticket information with the page description {Don Wright}: job ticket and page information is processed by the driver to render the page. proposition - chart: GPD app unidrive callbacks UI PDL Callbacks executed in real-time Unidrive uses GPD to generate rendering code. UI is done programmatically. UI to do with features is dynamically created. ** What's a GPD? GPD is an ascii text file specific for the printer model. It describes: features (bins, color depth) options (duplex, bins, ) constraints PDL generation instructions ** Standardization requirements MS propose GPD syntax be adopted to support cross platform What needs to be done: - improve UI - close the loop on features - GPD and protocol should work hand in hand - vector device support - unification with PPD model Question: How do I support different languages with UniDrive? Answer: Provide a separate GPD for each market Question: Dynamic feature addition? Answer: A two issues: dynamically declaring features (duplex capability) model with unforeseen extensibility - GPD should be able to describe these features ********************************************************* Section 3 Next Steps Is this an area we want to explore? It was noted that maybe we can't handle all printers with one binary. Don Wright: GPD and PPD offer features that overlap, maybe we should explore how to unify them? Schemas are unifying, it would be good to unify GPD and PPD as well. PPD files are usually target independent, sometimes dependent - e.g. Adobe did PPD's specifically for Apple Requirements input will be inquired on the mailing list. Paul Moore: Microsoft will not assert intellectual rights on the GPD structure but would not make source code available to other OS vendors. Paul Moore will look for the requirements that Microsoft developed for their GPD format and post to the mailing list if it is available. The meeting adjourned at 9:50 PM. --------------------------------------------------- From jkm at underscore.com Wed Mar 18 13:09:13 1998 From: jkm at underscore.com (Jay Martin) Date: Wed May 6 14:05:03 2009 Subject: UPD> ADM - Concerns regarding the scopes of the IPP and UPD projects Message-ID: <199803171437.AA09386@interlock2.lexmark.com> Carl-Uno, In your message titled "ADM - 'IPP Job Openings'" (attached below) you listed this item: 4) A champion for the host-to-device task (this is currently outside the scope of the IETF WG). Seems we keep crossing on this particular path, namely, whether the IPP project (of which the IETF IPP WG is part of that project) is supposed to take on the requirements for a true host-to-device protocol. I have stated many, many times in the past that the IPP project should NOT attempt to address the "host-to-device" protocol issue. Instead, the UPD project was formed (by me, back in May '97) for *expressly* this kind of work. IPP is for printing over the Internet. UPD addresses the more critical needs of the intranet, with requirements that far surpass those of the IPP. Let's let UPD take its own course, without placing unnecessary constraints on it from the outstart. Comments from others? ...jay ---------------------------------------------------------------------- -- JK Martin | Email: jkm@underscore.com -- -- Underscore, Inc. | Voice: (603) 889-7000 -- -- 41C Sagamore Park Road | Fax: (603) 889-2699 -- -- Hudson, NH 03051-4915 | Web: http://www.underscore.com -- ---------------------------------------------------------------------- Carl-Uno Manros wrote: > > All, > > In last week's phone conference we discussed the need for additional > volonteers to take on new tasks within the WG. > > In particular, we are looking to fill the following vacancies: > > 1) Somebody to take over the secretary job for the PWG IPP phone > conferences, as Don Wright has said that he has too many other commitments > to keep up this task. Means that you need to regularly attend the phone > conferences. > > 2) A champion and preferably editor (sounds better than the earlier WHIP > title) for the IPP Notification task. > > 3) A champion and preferably editor for a new IPP MIB task. > > 4) A champion for the host-to-device task (this is currently outside the > scope of the IETF WG). > > Please respond to the DL or to me personally, new faces are obviously welcome. > > If we cannot find people prepared to take on these tasks, we are in trouble! > > (Curious to see if this goes through the spam filters) > > Carl-Uno > > Carl-Uno Manros > Principal Engineer - Advanced Printing Standards - Xerox Corporation > 701 S. Aviation Blvd., El Segundo, CA, M/S: ESAE-231 > Phone +1-310-333 8273, Fax +1-310-333 5514 > Email: manros@cp10.es.xerox.com From rturner at sharplabs.com Wed Mar 18 13:27:03 1998 From: rturner at sharplabs.com (Turner, Randy) Date: Wed May 6 14:05:03 2009 Subject: UPD> RE: IPP> ADM - Concerns regarding the scopes of the IPP and UPD p Message-ID: <199803171437.AA09386@interlock2.lexmark.com> I thought the UPD study group was formed to talk about print drivers (extending the concept of the GPD concept to the next evel, etc..), and not a host-to-device protocol. I don't recall wire protocols ever brought up in the last couple of meetings. If there is both an application model (GPD, etc) and a wire protocol developed, I would hope there would be two study groups involved, since the expertise on either topic is largely orthogonal. Randy -----Original Message----- From: Jay Martin [SMTP:jkm@underscore.com] Sent: Wednesday, March 18, 1998 10:09 AM To: Carl-Uno Manros Cc: ipp@pwg.org; upd@pwg.org Subject: IPP> ADM - Concerns regarding the scopes of the IPP and UPD projects Carl-Uno, In your message titled "ADM - 'IPP Job Openings'" (attached below) you listed this item: 4) A champion for the host-to-device task (this is currently outside the scope of the IETF WG). Seems we keep crossing on this particular path, namely, whether the IPP project (of which the IETF IPP WG is part of that project) is supposed to take on the requirements for a true host-to-device protocol. I have stated many, many times in the past that the IPP project should NOT attempt to address the "host-to-device" protocol issue. Instead, the UPD project was formed (by me, back in May '97) for *expressly* this kind of work. IPP is for printing over the Internet. UPD addresses the more critical needs of the intranet, with requirements that far surpass those of the IPP. Let's let UPD take its own course, without placing unnecessary constraints on it from the outstart. Comments from others? ...jay ---------------------------------------------------------------------- -- JK Martin | Email: jkm@underscore.com -- -- Underscore, Inc. | Voice: (603) 889-7000 -- -- 41C Sagamore Park Road | Fax: (603) 889-2699 -- -- Hudson, NH 03051-4915 | Web: http://www.underscore.com -- ---------------------------------------------------------------------- Carl-Uno Manros wrote: > > All, > > In last week's phone conference we discussed the need for additional > volonteers to take on new tasks within the WG. > > In particular, we are looking to fill the following vacancies: > > 1) Somebody to take over the secretary job for the PWG IPP phone > conferences, as Don Wright has said that he has too many other commitments > to keep up this task. Means that you need to regularly attend the phone > conferences. > > 2) A champion and preferably editor (sounds better than the earlier WHIP > title) for the IPP Notification task. > > 3) A champion and preferably editor for a new IPP MIB task. > > 4) A champion for the host-to-device task (this is currently outside the > scope of the IETF WG). > > Please respond to the DL or to me personally, new faces are obviously welcome. > > If we cannot find people prepared to take on these tasks, we are in trouble! > > (Curious to see if this goes through the spam filters) > > Carl-Uno > > Carl-Uno Manros > Principal Engineer - Advanced Printing Standards - Xerox Corporation > 701 S. Aviation Blvd., El Segundo, CA, M/S: ESAE-231 > Phone +1-310-333 8273, Fax +1-310-333 5514 > Email: manros@cp10.es.xerox.com From don at lexmark.com Wed Mar 18 13:45:26 1998 From: don at lexmark.com (don@lexmark.com) Date: Wed May 6 14:05:03 2009 Subject: UPD> Concerns regarding the scopes of the IPP and UPD projects Message-ID: <199803181846.AA27930@interlock2.lexmark.com> Randy's right on this matter. In fact at the UPD meeting and in the UPD minutes we explicitly excluded protocols from the discussion. The UPD effort is focused generally on generating print PDL not on the means by which it is delivered to the printer. As everyone expects, I don't see the need to create a host-to-printer protocol. I will be posting a draft on using TIP/SI to deliver IPP content from the server (acting as an IPP printer) to the marking device in the next day or so. ********************************************** * Don Wright don@lexmark.com * * Product Manager, Strategic Alliances * * Lexmark International * * 740 New Circle Rd * * Lexington, Ky 40550 * * 606-232-4808 (phone) 606-232-6740 (fax) * ********************************************** From David_Kellerman at nls.com Tue May 5 15:42:43 1998 From: David_Kellerman at nls.com (David_Kellerman@nls.com) Date: Wed May 6 14:05:03 2009 Subject: UPD> corporate support for UPD Message-ID: <199803181846.AA27930@interlock2.lexmark.com> The UPD effort, which was beginning to look like a non-starter, seems to have life in it (Sandra Matts of HP volunteering as chair, meeting scheduled in Washington, DC). But the rocky start leaves me concerned about the level of corporate support -- I'd like to see a "critical mass" before good people start investing valuable time. In particular, I'm thinking of Adobe and Microsoft, key players with experience and technology that relates to UPD. (I hate repeating other people's mistakes.) So far, I've seen little participation from Adobe. Microsoft (Paul Moore) has expressed strong interest in using a UPD standard, but their participation has also been sporadic (they've so far been unable to make available specifications for their printer description file format, for instance). I'm not criticising either company -- the point is that either they, or other experienced major players, need to commit significant resources to make UPD successful. Not to be too pointy-headed, but I'm looking for a business plan -- who's going to do what things to produce what products (standards), and what value will those products have to what customers. Are we ready to tackle that task in Washington DC? :: David Kellerman Northlake Software 503-228-3383 :: david_kellerman@nls.com Portland, Oregon fax 503-228-5662 From sandram at boi.hp.com Tue Jun 2 17:40:21 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:03 2009 Subject: UPD> test ping - ignore please. Message-ID: <01BD8E3C.C182D200@hpb13858.boi.hp.com> Just testing if this mail reflector is working. Sandra Matts sandram@boi.hp.com Engineer Scientist Hewlett-Packard 11311 Chinden Blvd. MS 227 Boise, ID 83716 (208) 396-4755 From mwhit at vcd.hp.com Tue Jun 9 17:44:55 1998 From: mwhit at vcd.hp.com (Mike Whitmarsh) Date: Wed May 6 14:05:03 2009 Subject: UPD> Where is the webpage for UPD? Message-ID: <01BD8E3C.C182D200@hpb13858.boi.hp.com> Just a quck note.... as I haven't been involved (yet) in UPD discussions... Is there a plan to update the PWG page with a UPD specific link? Curious, +------------------------------------------+ | Mike Whitmarsh | | Hewlett-Packard | | Vancouver Printer Division | | mailto:mwhit@vcd.hp.com | | voice: 360.212.4257 | | fax: 360.212.7265 | +------------------------------------------+ From manros at cp10.es.xerox.com Tue Jun 9 18:26:58 1998 From: manros at cp10.es.xerox.com (Carl-Uno Manros) Date: Wed May 6 14:05:03 2009 Subject: UPD> Where is the webpage for UPD? In-Reply-To: <002e01bd93ef$d7624390$cb74450f@vcsmwhit5.vcd.hp.com> Message-ID: <3.0.5.32.19980609152658.009ab4f0@garfield> At 02:44 PM 6/9/98 PDT, Mike Whitmarsh wrote: >Just a quck note.... as I haven't been involved (yet) in UPD discussions... > >Is there a plan to update the PWG page with a UPD specific link? > >Curious, > >+------------------------------------------+ >| Mike Whitmarsh | >| Hewlett-Packard | >| Vancouver Printer Division | >| mailto:mwhit@vcd.hp.com | >| voice: 360.212.4257 | >| fax: 360.212.7265 | >+------------------------------------------+ > Good question, I suppose the project has not yet reached a level of maturity at which somebody has felt compelled to offer to take on the job of building the web pages. Were you planning to volonteer? Carl-Uno Carl-Uno Manros Principal Engineer - Advanced Printing Standards - Xerox Corporation 701 S. Aviation Blvd., El Segundo, CA, M/S: ESAE-231 Phone +1-310-333 8273, Fax +1-310-333 5514 Email: manros@cp10.es.xerox.com From jkm at underscore.com Tue Jun 9 18:27:53 1998 From: jkm at underscore.com (Jay Martin) Date: Wed May 6 14:05:03 2009 Subject: UPD> Where is the webpage for UPD? In-Reply-To: Where is the webpage for UPD?> Message-ID: <3.0.5.32.19980609152658.009ab4f0@garfield> Mike Whitmarsh wrote: > > Just a quck note.... as I haven't been involved (yet) in UPD discussions... > > Is there a plan to update the PWG page with a UPD specific link? There are no hard and fast rules or guidelines about who updates the PWG web pages for a specific project. However, generally speaking, the project chairperson has typically handled that activity thus far. If and when the UPD chairperson wants to update the PWG web pages for the project, the person should contact the PWG webmaster (mailto:webmaster@pwg.org). ...jay ---------------------------------------------------------------------- -- JK Martin | Email: jkm@underscore.com -- -- Underscore, Inc. | Voice: (603) 889-7000 -- -- 41C Sagamore Park Road | Fax: (603) 889-2699 -- -- Hudson, NH 03051-4915 | Web: http://www.underscore.com -- ---------------------------------------------------------------------- From sandram at boi.hp.com Thu Jun 18 11:34:36 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:03 2009 Subject: FW: UPD> Where is the webpage for UPD? Message-ID: <01BD9A9C.4FB0BB80@hpb13858.boi.hp.com> Since UPD ma not live very long as a charter, it didn't seem worth it to invest effort into a web page. Let's see how Monterey turns out. Sandra Matts sandram@boi.hp.com Engineer Scientist Hewlett-Packard 11311 Chinden Blvd. MS 227 Boise, ID 83716 (208) 396-4755 -----Original Message----- From: Jay Martin [SMTP:jkm@underscore.com] Sent: Tuesday, June 09, 1998 4:28 PM To: Mike Whitmarsh Cc: upd@pwg.org Subject: Re: UPD> Where is the webpage for UPD? Mike Whitmarsh wrote: >=20 > Just a quck note.... as I haven't been involved (yet) in UPD = discussions... >=20 > Is there a plan to update the PWG page with a UPD specific link? There are no hard and fast rules or guidelines about who updates the PWG = web pages for a specific project. However, generally speaking, the = project chairperson has typically handled that activity thus far. If and when the UPD chairperson wants to update the PWG web pages for = the project, the person should contact the PWG webmaster = (mailto:webmaster@pwg.org). ...jay ---------------------------------------------------------------------- * JK Martin | Email: jkm@underscore.com -- * Underscore, Inc. | Voice: (603) 889-7000 -- * 41C Sagamore Park Road | Fax: (603) 889-2699 -- * Hudson, NH 03051-4915 | Web: http://www.underscore.com -- ---------------------------------------------------------------------- From jeff at underscore.com Tue Jun 23 10:50:52 1998 From: jeff at underscore.com (Jeff Schnitzer) Date: Wed May 6 14:05:03 2009 Subject: UPD> Please ignore this test message. Message-ID: <01BD9A9C.4FB0BB80@hpb13858.boi.hp.com> Please ignore this test message. This message is being posted to verify that PWG mailing lists are public, per Keith Moore's mandate. Note that the Majordomo "who" command remains disabled. /Jeff Schnitzer --------------------------------------------------------------- Jeffrey D. Schnitzer | Email: jds@underscore.com Underscore, Inc. | Voice: (603) 889-7000 41-C Sagamore Park Rd | Fax: (603) 889-2699 Hudson, NH 03051-4915 | Web: http://www.underscore.com --------------------------------------------------------------- >To: wg-chairs@apps.ietf.org >Subject: mailing lists that don't allow outside posts >cc: moore@cs.utk.edu >From: Keith Moore >Date: Fri, 19 Jun 1998 13:23:39 PDT > >It's come to my attention that some of the WG mailing lists don't >allow posts from people who aren't on the list. > >This is not an acceptable policy for IETF WG lists. It's important to >allow people who aren't subscribed to the list to make suggestions >or ask questions. It's also important to allow cross-postings >between lists where a single topic is of interest to multiple >working groups. Finally, it unfairly penalizes against those >who use subaddresses. > >There are other ways of effectively blocking spam besides >blocking postings from non-subscribers. > >Lists that do this need to be fixed asap. > >Keith > From sandram at boi.hp.com Mon Aug 3 11:30:50 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:03 2009 Subject: UPD> minutes from last two meetings Message-ID: <01BDBEC1.67E88860.sandram@boi.hp.com> Hi, I've placed minutes from the last two meetings on the ftp site at: ftp://ftp.pwf.org/pub/pwg/upd/minutes. In the minutes I added links to various sites we discussed such as the ICC spec. I'll add them here if people don't want to get the minutes yet. The Adobe PPD spec is at: http://www.adobe.com/supportservice/devrelations/PDFS/TN/5003.PPD_Spec_v4.3.pdf ICC Specification is at www.color.org. There is a link to the spec in PS and PDF formats. Actual pdf file is at ftp://sgigate.sgi.com/pub/icc/icc34.pdf From sandram at boi.hp.com Wed Sep 2 12:07:19 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:03 2009 Subject: UPD> NT 50 DDK is on web site Message-ID: <01BDD659.790BECE0.sandram@boi.hp.com> Hi, The NT 5.0 DDK is on the Microsoft web site. I pulled it off yesterday and installed the documentation and samples. It has an extensive write up of the GPD format. It's in html format - however you can print the whole topic at once. After installing the DDK go to Graphics Drivers => Design Guide => Part 3: Printer Drivers... => 4.0 Microsoft Universal Printer Driver. Remember I won't be able to bring printed copies due to the copyright and license agreement. However if everybody prints out their own copy I believe we are ok. thanks, Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Thu Sep 3 18:25:37 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> FW: NT 50 DDK is on web site Message-ID: <01BDD757.7CAA3CE0.sandram@boi.hp.com> -----Original Message----- From: Sandra Matts [SMTP:sandram@boi.hp.com] Sent: Wednesday, September 02, 1998 10:07 AM To: Universal Printer Driver (E-mail) Subject: NT 50 DDK is on web site Hi, The NT 5.0 DDK is on the Microsoft web site. I pulled it off yesterday and installed the documentation and samples. It has an extensive write up of the GPD format. It's in html format - however you can print the whole topic at once. After installing the DDK go to Graphics Drivers => Design Guide => Part 3: Printer Drivers... => 4.0 Microsoft Universal Printer Driver. Remember I won't be able to bring printed copies due to the copyright and license agreement. However if everybody prints out their own copy I believe we are ok. thanks, Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Fri Sep 4 12:55:34 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> NT 50 DDK is on web site Message-ID: <01BDD7F2.8B5FA2C0.sandram@boi.hp.com> Sorry about that...In my world that URL is just universally known. www.microsoft.com/ddk On the web page click "Windows NT 5.0 Beta 2 DDK" Then download DDK. The DDK is huge if you install everything - I usually just get the documentation and some of the samples. Sandra -----Original Message----- From: Jay Martin [SMTP:jkm@underscore.com] Sent: Thursday, September 03, 1998 8:52 PM To: sandram@boi.hp.com Cc: upd@pwg.org Subject: Re: UPD> NT 50 DDK is on web site Sandra, Would you mind posting the full URL for the NT 5.0 DDK to the UPD DL? Thanks. ...jay Sandra Matts wrote: > > Hi, > The NT 5.0 DDK is on the Microsoft web site. I pulled it off yesterday and installed the documentation and > samples. It has an extensive write up of the GPD format. It's in html format - however you can print the whole topic > at once. After installing the DDK go to Graphics Drivers => Design Guide => Part 3: Printer Drivers... => > 4.0 Microsoft Universal Printer Driver. > Remember I won't be able to bring printed copies due to the copyright and license agreement. However if > everybody prints out their own copy I believe we are ok. > > thanks, > Sandra > > ------------------------------------------------------------------- > Sandra Matts > Engineer / Scientist > Hewlett-Packard > 11311 Chinden Blvd. > Boise, ID 83714 > sandram@boi.hp.com > (208) 396-4755 From egglestn at lexmark.com Tue Sep 8 10:29:16 1998 From: egglestn at lexmark.com (egglestn@lexmark.com) Date: Wed May 6 14:05:04 2009 Subject: UPD> 9/8/98 Test Message-ID: <199809081430.AA18620@interlock2.lexmark.com> this is just a test....please ignore Roger From rbergma at dpc.com Fri Sep 11 12:30:13 1998 From: rbergma at dpc.com (Ron Bergman) Date: Wed May 6 14:05:04 2009 Subject: UPD> Obtaining the Microsoft GDP Documents (fwd) Message-ID: I seem to have a difficult time typing UPD. Ron ---------- Forwarded message ---------- Date: Fri, 11 Sep 1998 08:47:51 -0700 (Pacific Daylight Time) From: Ron Bergman To: udp@pwg.org Cc: sandram@boi.hp.com, paulmo@microsoft.com Subject: UDP> Obtaining the Microsoft GDP Documents After loading all the DDK files from the Microsoft site and then moving them to a system that has the recommended capacity and OS, I find that I must also have the NT 5.0 Beta 2 as the OS. Am I doing something wrong? If this is true, the document will not be available to those that cannot or will not setup NT 5.0 on a system. I personally have no objection to running NT 5.0, but cannot expend the time required simply to obtain this document. Ron Bergman Dataproducts Corp. From sandram at boi.hp.com Fri Sep 11 16:55:05 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> How to get the Unidriver help file Message-ID: <01BDDD94.29D70E60.sandram@boi.hp.com> I managed to get the CAB files for the DDK Doc and extract the info. It's not pretty but it will keep you from having to install nt 5. The CAB extraction tool is at: www.microsoft.com/workshop/management/cab/cadl.asp The ddk file you want is graphics.exe. It's to big for me to attach so the link is at: www.microsoft.com/hwdev/ddk/download/50/graphics.exe Get the file graphics.exe and execute it. It also is a self-extracting archive. You should get a graphics.cab and a graphics.inf. The cab-sdk extracts into a bin and lib directory. Run bin\cabarc x graphics.cab This will produce the files: help_graphics.chi help_graphics.chm - this is the compiled html file Then you have to get the HTML help Workshop to view the compiled HTML file. IE version 5.0 also can view it. I don't know about IE version 4.01. www.microsoft.com/workshop/author/htmlhelp/htmlhelp.exe After installing the HTML help workshop - run it and go to View --> Compiled File. Since I've already gone through the million steps to do this, maybe Paul M. will just let me copy the the compiled html file and help viewer to the UPD archive. What do you think Paul? Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Fri Sep 11 17:18:14 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> Typo in link address Message-ID: <01BDDD97.661515E0.sandram@boi.hp.com> -----Original Message----- From: Sandra Matts [SMTP:sandram@boi.hp.com] Sent: Friday, September 11, 1998 2:55 PM To: Universal Printer Driver (E-mail) Subject: UPD> How to get the Unidriver help file I managed to get the CAB files for the DDK Doc and extract the info. It's not pretty but it will keep you from having to install nt 5. [Sandra Matts] Real address is here The CAB extraction tool is at: www.microsoft.com/workshop/management/cab/cabdl.asp [Sandra Matts] get and install the cabinet developers kit. The ddk file you want is graphics.exe. It's to big for me to attach so the link is at: www.microsoft.com/hwdev/ddk/download/50/graphics.exe Get the file graphics.exe and execute it. It also is a self-extracting archive. You should get a graphics.cab and a graphics.inf. The cab-sdk extracts into a bin and lib directory. Run bin\cabarc x graphics.cab This will produce the files: help_graphics.chi help_graphics.chm - this is the compiled html file Then you have to get the HTML help Workshop to view the compiled HTML file. IE version 5.0 also can view it. I don't know about IE version 4.01. www.microsoft.com/workshop/author/htmlhelp/htmlhelp.exe After installing the HTML help workshop - run it and go to View --> Compiled File. Since I've already gone through the million steps to do this, maybe Paul M. will just let me copy the the compiled html file and help viewer to the UPD archive. What do you think Paul? Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Fri Sep 11 17:24:07 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> Viewing the .chm file Message-ID: <01BDDD98.38210EE0.sandram@boi.hp.com> According to the documentation, the help_graphics.chm file can be viewed in IE 4.01. Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From don at lexmark.com Mon Sep 14 15:35:45 1998 From: don at lexmark.com (don@lexmark.com) Date: Wed May 6 14:05:04 2009 Subject: UPD> Mailing lists Message-ID: <199809141936.AA14887@interlock2.lexmark.com> The mailing lists are back up and running. Just to test everything out, I have sent this mail to ALL the mailing lists. If you get this mail on one list and not on another you think you should be on then I suggest you resubscribe by sending e-mail to: majordomo@pwg.org with the body of the note containing subscribe when is the name of the list you wish to subscribe to. You can include multiple subscriptions in the same note. Thanks for your patience during this transfer. ********************************************** * Don Wright don@lexmark.com * * Product Manager, Strategic Alliances * * Lexmark International * * 740 New Circle Rd * * Lexington, Ky 40550 * * 606-232-4808 (phone) 606-232-6740 (fax) * ********************************************** From adamsc at pogo.WV.TEK.COM Wed Sep 16 20:25:41 1998 From: adamsc at pogo.WV.TEK.COM (Chuck Adams) Date: Wed May 6 14:05:04 2009 Subject: UPD> Information on Adobe's "Portable Job Ticket Format" Message-ID: <36005705.F4379A4B@pogo.wv.tek.com> Folks, Adobe has published their Portable Job Ticket Format on their web site. To get a copy of it go to: http://www.adobe.com/supportservice/devrelations/PDFS/TN/5620.pjtf.pdf Chuck Adams Tektronix, Inc. From sandram at boi.hp.com Thu Sep 17 15:57:30 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> update to ftp site Message-ID: <01BDE243.1D26A500.sandram@boi.hp.com> Hi all, I copied minutes from the last meeting to the upd minutes directory and the revised Charter Proposal to the archive directory. It's called UPDChrtr.doc and pdf. The plan is to propose the Charter in Savannah. If you feel this is a problem, please email me soon so the Charter can be changed. I'll copy the requirements doc this weekend. Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Thu Sep 17 15:45:47 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> update to ftp site Message-ID: <01BDE241.79DFBEA0.sandram@boi.hp.com> Hi all, I copied minutes from the last meeting to the upd minutes directory and the revised Charter Proposal to the archive directory. It's called UPDChrtr.doc and pdf. The plan is to propose the Charter in Savannah. If you feel this is a problem, please email me soon so the Charter can be changed. I'll copy the requirements doc this weekend. Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From hastings at cp10.es.xerox.com Tue Sep 22 19:47:31 1998 From: hastings at cp10.es.xerox.com (Hastings, Tom N) Date: Wed May 6 14:05:04 2009 Subject: UPD> UPD Charter Comment: doesn't mention IPP Message-ID: <918C79AB552BD211A2BD00805F15CE8527ED0B@x-crt-es-ms1.cp10.es.xerox.com> How does the new UPD project fit with IPP? The PWG would be making a serious mistake if the new UPD project was only providing the old style of passing print instructions in the PDL data, thereby not allowing UPD printer drivers to make use of the IPP method of putting the print instructions in the protocol as an application/ipp MIME type in front of (but separated from) the PDL data. The charter includes an API to a OS independent PDL generator. It would be nice if an OS that is supporting the IPP protocol could intercept the API calls and use the semantics being passed in the API calls to wrap the IPP protocol around the document as an application/ipp MIME type. Therefore, the UPDF format needs to also include means to specify IPP Job Template attributes (and maybe operation attributes too?). So the UPD charter has to say something about IPP. (Presumably also the UPD requirements which are still being developed). Tom Hastings (310) 333-6413 From don at lexmark.com Tue Sep 22 23:48:50 1998 From: don at lexmark.com (don@lexmark.com) Date: Wed May 6 14:05:04 2009 Subject: UPD> UPD Charter Comment: doesn't mention IPP Message-ID: <199809230351.AA28253@interlock2.lexmark.com> Sorry Tom, I don't think the UPD charter _has_ to say anything about IPP. It _will_ talk about late binding and print attributes in general but UPD should not be limited to an IPP environment. I have no objection to mentioning IPP as a client to printer protocol that might take advantage of late binding but I do not believe we should structure UPD around IPP. Don "Hastings, Tom N" on 09/22/98 07:47:31 PM To: upd%pwg.org@interlock.lexmark.com cc: (bcc: Don Wright/Lex/Lexmark) bcc: Don Wright/Lex/Lexmark Subject: UPD> UPD Charter Comment: doesn't mention IPP How does the new UPD project fit with IPP? The PWG would be making a serious mistake if the new UPD project was only providing the old style of passing print instructions in the PDL data, thereby not allowing UPD printer drivers to make use of the IPP method of putting the print instructions in the protocol as an application/ipp MIME type in front of (but separated from) the PDL data. The charter includes an API to a OS independent PDL generator. It would be nice if an OS that is supporting the IPP protocol could intercept the API calls and use the semantics being passed in the API calls to wrap the IPP protocol around the document as an application/ipp MIME type. Therefore, the UPDF format needs to also include means to specify IPP Job Template attributes (and maybe operation attributes too?). So the UPD charter has to say something about IPP. (Presumably also the UPD requirements which are still being developed). Tom Hastings (310) 333-6413 From Angelo.Caruso at usa.xerox.com Wed Sep 23 09:16:44 1998 From: Angelo.Caruso at usa.xerox.com (Caruso, Angelo ) Date: Wed May 6 14:05:04 2009 Subject: UPD> UPD Charter Comment: doesn't mention IPP Message-ID: <576F850CF0D5D111A38100805FC7FA0E1A850F@usa0111ms2.eng.mc.xerox.com> Tom, Sounds like an IPP driver, as opposed to a universal print driver. Ang -----Original Message----- From: Hastings, Tom N [mailto:hastings@cp10.es.xerox.com] Sent: Tuesday, September 22, 1998 7:48 PM To: upd@pwg.org Subject: UPD> UPD Charter Comment: doesn't mention IPP How does the new UPD project fit with IPP? The PWG would be making a serious mistake if the new UPD project was only providing the old style of passing print instructions in the PDL data, thereby not allowing UPD printer drivers to make use of the IPP method of putting the print instructions in the protocol as an application/ipp MIME type in front of (but separated from) the PDL data. The charter includes an API to a OS independent PDL generator. It would be nice if an OS that is supporting the IPP protocol could intercept the API calls and use the semantics being passed in the API calls to wrap the IPP protocol around the document as an application/ipp MIME type. Therefore, the UPDF format needs to also include means to specify IPP Job Template attributes (and maybe operation attributes too?). So the UPD charter has to say something about IPP. (Presumably also the UPD requirements which are still being developed). Tom Hastings (310) 333-6413 From sandram at boi.hp.com Wed Sep 23 12:19:58 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: FW: UPD> UPD Charter Comment: doesn't mention IPP Message-ID: <01BDE6DB.B8005DE0.sandram@boi.hp.com> I agree with Don. It important to keep it as independent as possible from the transport mechanism. However I can see it will be very important to have the implementer's guide which will show how the UPDF can be wrapped in a protocol. The req. doc currently only references IPP - it doesn't have it as a requirement. I'm trying to allocate some time to updating the req doc. I'll try to post it tomorrow. Sandra -----Original Message----- From: don@lexmark.com [SMTP:don@lexmark.com] Sent: Tuesday, September 22, 1998 9:49 PM To: Hastings, Tom N Cc: Upd@pwg.org Subject: Re: UPD> UPD Charter Comment: doesn't mention IPP Sorry Tom, I don't think the UPD charter _has_ to say anything about IPP. It _will_ talk about late binding and print attributes in general but UPD should not be limited to an IPP environment. I have no objection to mentioning IPP as a client to printer protocol that might take advantage of late binding but I do not believe we should structure UPD around IPP. Don "Hastings, Tom N" on 09/22/98 07:47:31 PM To: upd%pwg.org@interlock.lexmark.com cc: (bcc: Don Wright/Lex/Lexmark) bcc: Don Wright/Lex/Lexmark Subject: UPD> UPD Charter Comment: doesn't mention IPP How does the new UPD project fit with IPP? The PWG would be making a serious mistake if the new UPD project was only providing the old style of passing print instructions in the PDL data, thereby not allowing UPD printer drivers to make use of the IPP method of putting the print instructions in the protocol as an application/ipp MIME type in front of (but separated from) the PDL data. The charter includes an API to a OS independent PDL generator. It would be nice if an OS that is supporting the IPP protocol could intercept the API calls and use the semantics being passed in the API calls to wrap the IPP protocol around the document as an application/ipp MIME type. Therefore, the UPDF format needs to also include means to specify IPP Job Template attributes (and maybe operation attributes too?). So the UPD charter has to say something about IPP. (Presumably also the UPD requirements which are still being developed). Tom Hastings (310) 333-6413 From hastings at cp10.es.xerox.com Mon Sep 28 19:49:32 1998 From: hastings at cp10.es.xerox.com (Hastings, Tom N) Date: Wed May 6 14:05:04 2009 Subject: UPD> UPD Charter Comment: doesn't mention IPP Message-ID: <918C79AB552BD211A2BD00805F15CE8527F0E6@x-crt-es-ms1.cp10.es.xerox.com> I did not intend that UPDF only work with IPP, but I'm still concerned about how UPDF will work with IPP. I agree that UPDF should work with any job submission protocol and be as independent of job submission protocols as possible. On the other hand, if that means that a job submitted by a print driver using UPDF will be unable to contain any of the IPP Job Template attributes in the protocol, then I think we have a problem. So help me understand the intended architecture of a print driver that is using a UPDF description and the new print API with an IPP Printer. How do the capabilities described in the UPDF file about the printer, say, that it can do two-sided printing or support xxx media, get into the IPP protocol? Thanks, Tom -----Original Message----- From: Sandra Matts [mailto:sandram@boi.hp.com] Sent: Wednesday, September 23, 1998 09:20 To: 'upd@pwg.org' Subject: FW: UPD> UPD Charter Comment: doesn't mention IPP I agree with Don. It important to keep it as independent as possible from the transport mechanism. However I can see it will be very important to have the implementer's guide which will show how the UPDF can be wrapped in a protocol. The req. doc currently only references IPP - it doesn't have it as a requirement. I'm trying to allocate some time to updating the req doc. I'll try to post it tomorrow. Sandra -----Original Message----- From: don@lexmark.com [SMTP:don@lexmark.com] Sent: Tuesday, September 22, 1998 9:49 PM To: Hastings, Tom N Cc: Upd@pwg.org Subject: Re: UPD> UPD Charter Comment: doesn't mention IPP Sorry Tom, I don't think the UPD charter _has_ to say anything about IPP. It _will_ talk about late binding and print attributes in general but UPD should not be limited to an IPP environment. I have no objection to mentioning IPP as a client to printer protocol that might take advantage of late binding but I do not believe we should structure UPD around IPP. Don "Hastings, Tom N" on 09/22/98 07:47:31 PM To: upd%pwg.org@interlock.lexmark.com cc: (bcc: Don Wright/Lex/Lexmark) bcc: Don Wright/Lex/Lexmark Subject: UPD> UPD Charter Comment: doesn't mention IPP How does the new UPD project fit with IPP? The PWG would be making a serious mistake if the new UPD project was only providing the old style of passing print instructions in the PDL data, thereby not allowing UPD printer drivers to make use of the IPP method of putting the print instructions in the protocol as an application/ipp MIME type in front of (but separated from) the PDL data. The charter includes an API to a OS independent PDL generator. It would be nice if an OS that is supporting the IPP protocol could intercept the API calls and use the semantics being passed in the API calls to wrap the IPP protocol around the document as an application/ipp MIME type. Therefore, the UPDF format needs to also include means to specify IPP Job Template attributes (and maybe operation attributes too?). So the UPD charter has to say something about IPP. (Presumably also the UPD requirements which are still being developed). Tom Hastings (310) 333-6413 From BEN_BREZINSKI at HP-Vancouver-om1.om.hp.com Fri Oct 2 19:43:55 1998 From: BEN_BREZINSKI at HP-Vancouver-om1.om.hp.com (BEN_BREZINSKI@HP-Vancouver-om1.om.hp.com) Date: Wed May 6 14:05:04 2009 Subject: UPD> UPD Charter Comment: doesn't mention IPP In-Reply-To: <918C79AB552BD211A2BD00805F15CE8527F0E6@x-crt-es-ms1.cp10.es.xe> Message-ID: I think we agreed Tuesday night that the UPDF was intended to describe the printer in a OS and transport independent manner. So it should be sufficient for the UPDF to say that, in this case, that the printer suports two sided printing or some other feature. I don't think the charter of the UPD extends to the binding or suggested binding of anything described in the UPDF to any transport mechanism. The UPD can and probably should suggest implementations, but the exact implementations are up to implemntor, and the implementation will likely be different for various OS's and transports. If the transport is IPP, then the features will map into the Job template, or if the transport is something simple like HPPCL then it will map into an escape, or perhaps some transports won't support it all. Regards, Ben Brezinski ______________________________ Reply Separator _________________________________ Subject: RE: UPD> UPD Charter Comment: doesn't mention IPP Author: Non-HP-hastings (hastings@cp10.es.xerox.com) at HP-Vancouver,mimegw1 Date: 9/28/98 4:49 PM I did not intend that UPDF only work with IPP, but I'm still concerned about how UPDF will work with IPP. I agree that UPDF should work with any job submission protocol and be as independent of job submission protocols as possible. On the other hand, if that means that a job submitted by a print driver using UPDF will be unable to contain any of the IPP Job Template attributes in the protocol, then I think we have a problem. So help me understand the intended architecture of a print driver that is using a UPDF description and the new print API with an IPP Printer. How do the capabilities described in the UPDF file about the printer, say, that it can do two-sided printing or support xxx media, get into the IPP protocol? Thanks, Tom -----Original Message----- From: Sandra Matts [mailto:sandram@boi.hp.com] Sent: Wednesday, September 23, 1998 09:20 To: 'upd@pwg.org' Subject: FW: UPD> UPD Charter Comment: doesn't mention IPP I agree with Don. It important to keep it as independent as possible from the transport mechanism. However I can see it will be very important to have the implementer's guide which will show how the UPDF can be wrapped in a protocol. The req. doc currently only references IPP - it doesn't have it as a requirement. I'm trying to allocate some time to updating the req doc. I'll try to post it tomorrow. Sandra -----Original Message----- From: don@lexmark.com [SMTP:don@lexmark.com] Sent: Tuesday, September 22, 1998 9:49 PM To: Hastings, Tom N Cc: Upd@pwg.org Subject: Re: UPD> UPD Charter Comment: doesn't mention IPP Sorry Tom, I don't think the UPD charter _has_ to say anything about IPP. It _will_ talk about late binding and print attributes in general but UPD should not be limited to an IPP environment. I have no objection to mentioning IPP as a client to printer protocol that might take advantage of late binding but I do not believe we should structure UPD around IPP. Don "Hastings, Tom N" on 09/22/98 07:47:31 PM To: upd%pwg.org@interlock.lexmark.com cc: (bcc: Don Wright/Lex/Lexmark) bcc: Don Wright/Lex/Lexmark Subject: UPD> UPD Charter Comment: doesn't mention IPP How does the new UPD project fit with IPP? The PWG would be making a serious mistake if the new UPD project was only providing the old style of passing print instructions in the PDL data, thereby not allowing UPD printer drivers to make use of the IPP method of putting the print instructions in the protocol as an application/ipp MIME type in front of (but separated from) the PDL data. The charter includes an API to a OS independent PDL generator. It would be nice if an OS that is supporting the IPP protocol could intercept the API calls and use the semantics being passed in the API calls to wrap the IPP protocol around the document as an application/ipp MIME type. Therefore, the UPDF format needs to also include means to specify IPP Job Template attributes (and maybe operation attributes too?). So the UPD charter has to say something about IPP. (Presumably also the UPD requirements which are still being developed). Tom Hastings (310) 333-6413 From henrik.holst at i-data.com Mon Oct 5 05:39:30 1998 From: henrik.holst at i-data.com (henrik.holst@i-data.com) Date: Wed May 6 14:05:04 2009 Subject: IPP> RE: UPD> UPD Charter Comment: doesn't mention IPP Message-ID: I think the right thing to do would be to do it in the same way as the IPP spec. One model document (a transport independent document) and one or more protocol mapping documents. /HOLST I think we agreed Tuesday night that the UPDF was intended to describe the printer in a OS and transport independent manner. So it should be sufficient for the UPDF to say that, in this case, that the printer suports two sided printing or some other feature. I don't think the charter of the UPD extends to the binding or suggested binding of anything described in the UPDF to any transport mechanism. The UPD can and probably should suggest implementations, but the exact implementations are up to implemntor, and the implementation will likely be different for various OS's and transports. If the transport is IPP, then the features will map into the Job template, or if the transport is something simple like HPPCL then it will map into an escape, or perhaps some transports won't support it all. Regards, Ben Brezinski ______________________________ Reply Separator _________________________________ Subject: RE: UPD> UPD Charter Comment: doesn't mention IPP Author: Non-HP-hastings (hastings@cp10.es.xerox.com) at HP-Vancouver,mimegw1 Date: 9/28/98 4:49 PM I did not intend that UPDF only work with IPP, but I'm still concerned about how UPDF will work with IPP. I agree that UPDF should work with any job submission protocol and be as independent of job submission protocols as possible. On the other hand, if that means that a job submitted by a print driver using UPDF will be unable to contain any of the IPP Job Template attributes in the protocol, then I think we have a problem. So help me understand the intended architecture of a print driver that is using a UPDF description and the new print API with an IPP Printer. How do the capabilities described in the UPDF file about the printer, say, that it can do two-sided printing or support xxx media, get into the IPP protocol? Thanks, Tom -----Original Message----- From: Sandra Matts [mailto:sandram@boi.hp.com] Sent: Wednesday, September 23, 1998 09:20 To: 'upd@pwg.org' Subject: FW: UPD> UPD Charter Comment: doesn't mention IPP I agree with Don. It important to keep it as independent as possible from the transport mechanism. However I can see it will be very important to have the implementer's guide which will show how the UPDF can be wrapped in a protocol. The req. doc currently only references IPP - it doesn't have it as a requirement. I'm trying to allocate some time to updating the req doc. I'll try to post it tomorrow. Sandra -----Original Message----- From: don@lexmark.com [SMTP:don@lexmark.com] Sent: Tuesday, September 22, 1998 9:49 PM To: Hastings, Tom N Cc: Upd@pwg.org Subject: Re: UPD> UPD Charter Comment: doesn't mention IPP Sorry Tom, I don't think the UPD charter _has_ to say anything about IPP. It _will_ talk about late binding and print attributes in general but UPD should not be limited to an IPP environment. I have no objection to mentioning IPP as a client to printer protocol that might take advantage of late binding but I do not believe we should structure UPD around IPP. Don "Hastings, Tom N" on 09/22/98 07:47:31 PM To: upd%pwg.org@interlock.lexmark.com cc: (bcc: Don Wright/Lex/Lexmark) bcc: Don Wright/Lex/Lexmark Subject: UPD> UPD Charter Comment: doesn't mention IPP How does the new UPD project fit with IPP? The PWG would be making a serious mistake if the new UPD project was only providing the old style of passing print instructions in the PDL data, thereby not allowing UPD printer drivers to make use of the IPP method of putting the print instructions in the protocol as an application/ipp MIME type in front of (but separated from) the PDL data. The charter includes an API to a OS independent PDL generator. It would be nice if an OS that is supporting the IPP protocol could intercept the API calls and use the semantics being passed in the API calls to wrap the IPP protocol around the document as an application/ipp MIME type. Therefore, the UPDF format needs to also include means to specify IPP Job Template attributes (and maybe operation attributes too?). So the UPD charter has to say something about IPP. (Presumably also the UPD requirements which are still being developed). Tom Hastings (310) 333-6413 From egglestn at lexmark.com Fri Oct 23 11:12:15 1998 From: egglestn at lexmark.com (egglestn@lexmark.com) Date: Wed May 6 14:05:04 2009 Subject: UPD> Test Message-ID: <199810231513.AA25627@interlock2.lexmark.com> I have fixed the problem. Roger From sandram at boi.hp.com Fri Oct 23 10:53:31 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> FW: new UPDF charter on ftp site Message-ID: <01BDFE62.9C8A4780.sandram@boi.hp.com> Hi All, I copied the slimmed down version of the UPDF charter. Please take a look and send me feedback by Tuesday. I want to finalize the charter and take a prelim vote by email on Wed or Thursday. The "real" PWG vote is scheduled for the PWG plenery in Tucson. The charter is named UPDChrtr2.doc and .pdf in the archive. I've also copied the gpd spec from Paul. It's in word format. Thanks Paul. Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Mon Oct 26 10:05:04 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: FW: UPD> FW: new UPDF charter on ftp site Message-ID: <01BE00B7.576F9C20.sandram@boi.hp.com> Sorry - sloppy language. I've copied it to the UPD FTP archive. I will bring it to the next meeting - but I hope people read it before so that we can discuss over the reflector. Sandra -----Original Message----- From: Farrell, Lee [SMTP:Lee_Farrell@cissc.canon.com] Sent: Friday, October 23, 1998 3:14 PM To: 'sandram@boi.hp.com' Subject: RE: UPD> FW: new UPDF charter on ftp site Sandra, When you say you've copied the GPD spec, are you making it available to anyone else via e-mail or at the next meeting? lee ====================================== Lee Farrell Canon Information Systems 110 Innovation Drive Irvine, CA 92612 ph: (949) 856-7163 fax: (949) 856-7510 lee_farrell@cissc.canon.com ====================================== -----Original Message----- From: Sandra Matts [mailto:sandram@boi.hp.com] Sent: Friday, October 23, 1998 7:54 AM To: Universal Printer Driver (E-mail) Subject: UPD> FW: new UPDF charter on ftp site Hi All, I copied the slimmed down version of the UPDF charter. Please take a look and send me feedback by Tuesday. I want to finalize the charter and take a prelim vote by email on Wed or Thursday. The "real" PWG vote is scheduled for the PWG plenery in Tucson. The charter is named UPDChrtr2.doc and .pdf in the archive. I've also copied the gpd spec from Paul. It's in word format. Thanks Paul. Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From hastings at cp10.es.xerox.com Mon Oct 26 15:48:08 1998 From: hastings at cp10.es.xerox.com (Hastings, Tom N) Date: Wed May 6 14:05:04 2009 Subject: UPD> Article in InfoWorld on "universal print driver" (InfoWorld) (htt p://www.infoworld Message-ID: <918C79AB552BD211A2BD00805F15CE853A38B9@x-crt-es-ms1.cp10.es.xerox.com> ? ? top Group forms to develop universal print driver By Ephraim Schwartz InfoWorld Electric Posted at 5:49 AM PT, Oct 24, 1998 Working quietly, an informal group of the leading printer manufacturers is working to create a single universal print driver that will replace the more than 3,000 drivers that are currently required. The goal is to have only one driver included in the operating system, or a Universal Printer Driver Format (UPDF), with the individual characteristics of a particular printer described in a text file residing within the printer itself. "We are hoping the [bidirectional] characteristics of the UPDF will help IT managers, in that less support of printers is needed," said Sandra Matts, chair of the UPDF committee in the Printer Working Group (PWG) and an engineer scientist for Workgroup Color LaserJets at Hewlett-Packard, in Boise, Idaho. "They won't have to configure every client's computer for each printer the client will use." Commands would reside in the text file within the printer to invoke the printer's capabilities. If a user wanted to do duplex printing, for example, the text file would send the correct data stream. On the operating system side, the driver is universal. It is on the client side that unique features are described. "There is no such thing as a device-independent data stream," said Harry Lewis, a member of the PWG and a printing systems architect at IBM Printing Systems Division, in Boulder, Colo. Every device may have different characteristics that can change. A so-called meta-language developed by the PWG would be able to describe all of the features of the printer for access by the single driver in the OS. "Basically, it is similar to PostScript page description language," said Dan Wright, another PWG member and the product manager for alliances for standards at Lexmark, in Lexington, Ky. According to group members, the finished driver will be available for testing in eight months to one year, with another two months needed for interoperability testing before it ships. The universal driver will require the support of operating system vendors, such as Microsoft, as well as Unix operating system vendors. Currently, Microsoft ships a CD with more than 3,000 printer drivers with each package of Windows NT. Microsoft support appears to be in place, according to Paul Moore, program manager for Windows NT 5.0 printing. The Redmond, Wash., software company currently has Unidrive 5 in Beta 2 of NT 5.0, which is similar to technology that might be used as the basis for the UPDF, according to Moore. Moore believes the UPDF will benefit IT departments. "We think that a lot of IT manager problems arise from having too many printer drivers. The benefits [of a universal driver] would be all around," Moore said. "It will reduce the administrative load." The single driver as envisioned by members of the PWG allow a UPDF to query the printer device for capabilities. "Today, we really rely on the user selecting in the UI features of the printer," Matts said. "It's really a best guess at times. UPDF will allow our drivers to truly know what is attached to the printer at the start of the print job." The Printer Working Group can be reached at www.pwg.org . Ephraim Schwartz is an editor at large for InfoWorld. Go to the Week's Top News Stories Please direct your comments to InfoWorld Deputy News Editor, Carolyn April Copyright ? 1998 InfoWorld Media Group Inc. InfoWorld Electric is a member of IDG.net ? From labonte at zk3.dec.com Mon Oct 26 16:30:48 1998 From: labonte at zk3.dec.com (labonte@zk3.dec.com) Date: Wed May 6 14:05:04 2009 Subject: UPD> Need copy of UPD mail sent Sept and Oct Message-ID: <199810262130.AA07407@tropic.zk3.dec.com> Hi, I need a copy of the UPD e-mail sent during September and October. I noticed I had not received any UPD mail since mid September. I checked majordomo and found that my name was no longer on the list. It may have been dropped during the cut-over to Lexmark. I have subscribed again but could use a copy of all e-mail sent to UPD since September. Thanks, Ernest LaBonte Compaq Computer Corporation From sandram at boi.hp.com Tue Oct 27 12:55:39 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> GPD doc is on UPD ftp site Message-ID: <01BE0198.56ABA9A0.sandram@boi.hp.com> Hi All, I copied the gpd spec to the ftp site in upd\Archive. It's in word format. Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Tue Oct 27 12:59:33 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> RE: UPD Charter Proposal Message-ID: <01BE0198.E1ACAF40.sandram@boi.hp.com> good point. This is true for Windows based drivers so I will change and update the charter. Unix doesn't have a notion of driver vs OS. Does anyone want additional sentences for the Unix case? Sandra Matts -----Original Message----- From: mwu@kodak.com [SMTP:mwu@kodak.com] Sent: Monday, October 26, 1998 9:22 AM To: sandram@boi.hp.com Subject: UPD Charter Proposal >From Lotus Notes user: Michael Wu Sandra: I have a question on the Charter Proposal Line #28. I think the UPDF is for the printer driver to configure itself after read the UPDF not the operating system. UPDF will not require the OS to configure the driver. This will ensure the driver will have the dynamic discovery features. For example, when the user selectes a different printer, the driver (the same driver) should read in the UPDF and re-configure itself to be the new printer driver by changing the UI etc. OS should have no knowledge of it. On the requirement statement: since we are defining a text file format for the drivers, there is no any issues with hardware or software requirement. So any issues with hardware and software limitation should be removed. Let me know if you want specific items that I indicated above. Michael Wu Printer Driver Group Eastman Kodak Company 901 Elmgrove Road Rochester NY 14653 Office: 716.726.0654 Fax: 716.726.0374 eMail: mwu@kodak.com From labonte at zk3.dec.com Tue Oct 27 15:28:01 1998 From: labonte at zk3.dec.com (labonte@zk3.dec.com) Date: Wed May 6 14:05:04 2009 Subject: UPD> UPDF File format Message-ID: <199810272028.AA04522@tropic.zk3.dec.com> Hi, Reading the InforWorld article and comments made by Michael Wu it would seem it has been decided to use text file format. Is this correct? Past e-mail messages and posted minutes don't indicate a decision was made on the file type. For UPDF to be of any benefit I require the UPDF format be compatible between UNIX and PC's. Using a text file format works for me but I would like to know if a decision has been made. Ernest LaBonte Compaq Computer Corporation From sandram at boi.hp.com Tue Oct 27 16:06:02 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: FW: UPD> UPDF File format Message-ID: <01BE01B2.EF16AE00.sandram@boi.hp.com> We are going on the assumption that the UPDF is a text file - similiar to the PPD and GPD format. It's maybe a bit early to specify exactly the text format since we are just at the charter and requirement phase. I'll make a note to make sure we address after the Charter is approved and we start the actual specification. Sandra Matts -----Original Message----- From: labonte@zk3.dec.com [SMTP:labonte@zk3.dec.com] Sent: Tuesday, October 27, 1998 1:28 PM To: upd@pwg.org Subject: UPD> UPDF File format Hi, Reading the InforWorld article and comments made by Michael Wu it would seem it has been decided to use text file format. Is this correct? Past e-mail messages and posted minutes don't indicate a decision was made on the file type. For UPDF to be of any benefit I require the UPDF format be compatible between UNIX and PC's. Using a text file format works for me but I would like to know if a decision has been made. Ernest LaBonte Compaq Computer Corporation From mwu at kodak.com Tue Oct 27 16:10:26 1998 From: mwu at kodak.com (mwu@kodak.com) Date: Wed May 6 14:05:04 2009 Subject: UPD> UPDF File format Message-ID: <852566AA.0073A62E.00@knotes.kodak.com> >From Lotus Notes user: Michael Wu I don't know if the decision is being made. The comments I made was specific to the Charter Proposal and the Charter is to be voted on next UPDF meeting. After that, the group will "Sit Down" to discuss the requirement. In other words, there is no any kind of decisions I konw of it since the Charter has not beeen established yet. Michael Wu Printer Driver Group Eastman Kodak Company From sandram at boi.hp.com Wed Oct 28 15:37:15 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> modified UPDF Charter Message-ID: <01BE0278.141E1740.sandram@boi.hp.com> I made a minor change on line 28 of the Charter to reflect that UPDF are read in by printer drivers and not the operating system - this was a comment by Michael Wu. The file is still names UPDChrtr2.doc and PDF. I am keeping versions on my system for history but I didn't feel the need to change the Charter name since it is a short document and earlier versions aren't critical. Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From krister.svard at skandia.se Thu Nov 5 08:11:58 1998 From: krister.svard at skandia.se (krister.svard@skandia.se) Date: Wed May 6 14:05:04 2009 Subject: UPD> Amendment to UPD Message-ID: <67BE63A4EE6BD111A9220001FAD4053BB5050D@ESKP1217> Sandra, I hope you welcome influences outside the PWG/UPD circle of people. Within the UPD-specs are that the printer dynamically should be able to configure/reconfigure the UPD-driver on the host-side. I.e, the printer tells the printer driver how it is configured to relieve the end user/admin person from doing this task and keep them out of trouble. This dynamic configuration calls for a "configuration"-metalanguage to be defined that the UPD/operating system can interpret. It would be of equal of worth to be able to do configuration the other way around. I.e configure the PRINTER through a standard metalanguage, things like turning network protocolls on/off, set printer defaults and more. Would it be impossible for you, or some other PWG group, to put into your/their scope of work to define a standard "printer configuration"-metalanguage that all printers could interpret. As it is now it is a jungle. There are postscript snippets, vendor proprietary languages, private SNMP MIBs, HTTP and other ways to configure the actual printer. There could be a multiple of ways to send this configuration file to the printer. Either do a copy over the parallell port or send the file over the network via lpr, ftp or do a automatic download via bootp/tftp. Kind regards Krister Sv?rd Skandia Utdata Teknik Telefon: +46 8 788 28 87 S-103 50 STOCKHOLM Mobil: +46 70 689 28 87 E-mail: krister.svard@skandia.se http://www.skandia.se From harryl at us.ibm.com Thu Nov 5 13:23:39 1998 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:05:04 2009 Subject: UPD> Re: PWG-ANNOUNCE> vote on UPDF Charter Message-ID: <5030100028148684000002L042*@MHS> I like the charter, but I also like (and recommend) Stuarts suggestion to tighten up the goals. Stuart has done such a great job articulating these that I nominate him for editor! '-) Harry Lewis - IBM Printing Systems harryl@us.ibm.com owner-pwg-announce@pwg.org on 11/05/98 11:10:33 AM Please respond to owner-pwg-announce@pwg.org To: sandram@boi.hp.com, pwg-announce@pwg.org cc: Subject: Re: PWG-ANNOUNCE> vote on UPDF Charter Sandra, Although there is good descriptive text in the Abstract, in my opinion, the bulleted goals are too nebulous. Hopefully, the the UPDF work will result in reduced development time, simplified installation, etc. but I believe the listed goals should be more definite, describing what will actually be created by the effort, such as: Goals of UPDF: * To define a universal printer description file format that enables a printer driver to configure itself based on the unique printer characteristics. * To design or specify a description format that can be used by multiple operating systems. * To enable dynamic configuration of printers via bi-directional communication of configuration information. * To support the largest possible number of existing printers. * To provide extremely flexible mechanisms for extensibility to enable support for as yet unimagined printers and features. Since this effort used to be called Universal Printer Driver, perhaps it would also be useful to include some more descriptive text in addition to the currently terse "Also out of scope is the definition of the Universal Printer Driver", stating how this effort may relate to a Universal Printer Driver. Just my two cents. Thanks, Stuart ------------------------------------------------------------------------ Stuart Rowley Kyocera Technology Development, Inc. Network Product Dev. Mgr. 3675 Mt. Diablo Blvd. #330 Printer Division Lafayette, CA 94549 stuart.rowley@kyocera.com 925 299-7206 Fax: 925 299-2489 ------------------------------------------------------------------------ ______________________________ Reply Separator _________________________________ Subject: PWG-ANNOUNCE> vote on UPDF Charter Author: Sandra Matts at ~internet Date: 11/3/98 2:42 PM Hi All, I've copied the Charter to the UPD ftp archive. Please read it and let me know if it conveys our goal of UPDF or not. If it you don't agree - let me know by Thursday or Friday at the latest. If no one replies - I'm assuming the PWG Wed meeting participates will vote affirmatively for the Charter. Sandra Matts ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From sandram at boi.hp.com Thu Nov 5 12:35:17 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> RE: PWG-ANNOUNCE> vote on UPDF Charter Message-ID: <01BE08A7.FB9291C0.sandram@boi.hp.com> I also like the additional goal text so I will add and repost the Charter. Sandra -----Original Message----- From: Harry Lewis [SMTP:harryl@us.ibm.com] Sent: Thursday, November 05, 1998 11:24 AM To: upd@pwg.org Cc: stuart.rowley@kyocera.com; :;@us.ibm.com Subject: Re: PWG-ANNOUNCE> vote on UPDF Charter I like the charter, but I also like (and recommend) Stuarts suggestion to tighten up the goals. Stuart has done such a great job articulating these that I nominate him for editor! '-) Harry Lewis - IBM Printing Systems harryl@us.ibm.com owner-pwg-announce@pwg.org on 11/05/98 11:10:33 AM Please respond to owner-pwg-announce@pwg.org To: sandram@boi.hp.com, pwg-announce@pwg.org cc: Subject: Re: PWG-ANNOUNCE> vote on UPDF Charter Sandra, Although there is good descriptive text in the Abstract, in my opinion, the bulleted goals are too nebulous. Hopefully, the the UPDF work will result in reduced development time, simplified installation, etc. but I believe the listed goals should be more definite, describing what will actually be created by the effort, such as: Goals of UPDF: * To define a universal printer description file format that enables a printer driver to configure itself based on the unique printer characteristics. * To design or specify a description format that can be used by multiple operating systems. * To enable dynamic configuration of printers via bi-directional communication of configuration information. * To support the largest possible number of existing printers. * To provide extremely flexible mechanisms for extensibility to enable support for as yet unimagined printers and features. Since this effort used to be called Universal Printer Driver, perhaps it would also be useful to include some more descriptive text in addition to the currently terse "Also out of scope is the definition of the Universal Printer Driver", stating how this effort may relate to a Universal Printer Driver. Just my two cents. Thanks, Stuart ------------------------------------------------------------------------ Stuart Rowley Kyocera Technology Development, Inc. Network Product Dev. Mgr. 3675 Mt. Diablo Blvd. #330 Printer Division Lafayette, CA 94549 stuart.rowley@kyocera.com 925 299-7206 Fax: 925 299-2489 ------------------------------------------------------------------------ ______________________________ Reply Separator _________________________________ Subject: PWG-ANNOUNCE> vote on UPDF Charter Author: Sandra Matts at ~internet Date: 11/3/98 2:42 PM Hi All, I've copied the Charter to the UPD ftp archive. Please read it and let me know if it conveys our goal of UPDF or not. If it you don't agree - let me know by Thursday or Friday at the latest. If no one replies - I'm assuming the PWG Wed meeting participates will vote affirmatively for the Charter. Sandra Matts ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From harryl at us.ibm.com Thu Nov 5 14:06:00 1998 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:05:04 2009 Subject: UPD> Amendment to UPD Message-ID: <5030100028151362000002L022*@MHS> Skandia, I believe that, today, the Printer MIB addresses most of your concerns and is widely supported. Harry Lewis - IBM Printing Systems harryl@us.ibm.com owner-upd@pwg.org on 11/05/98 06:19:09 AM Please respond to owner-upd@pwg.org To: upd@pwg.org, sandram@boi.hp.com cc: Subject: UPD> Amendment to UPD Sandra, I hope you welcome influences outside the PWG/UPD circle of people. Within the UPD-specs are that the printer dynamically should be able to configure/reconfigure the UPD-driver on the host-side. I.e, the printer tells the printer driver how it is configured to relieve the end user/admin person from doing this task and keep them out of trouble. This dynamic configuration calls for a "configuration"-metalanguage to be defined that the UPD/operating system can interpret. It would be of equal of worth to be able to do configuration the other way around. I.e configure the PRINTER through a standard metalanguage, things like turning network protocolls on/off, set printer defaults and more. Would it be impossible for you, or some other PWG group, to put into your/their scope of work to define a standard "printer configuration"-metalanguage that all printers could interpret. As it is now it is a jungle. There are postscript snippets, vendor proprietary languages, private SNMP MIBs, HTTP and other ways to configure the actual printer. There could be a multiple of ways to send this configuration file to the printer. Either do a copy over the parallell port or send the file over the network via lpr, ftp or do a automatic download via bootp/tftp. Kind regards Krister Sv?rd Skandia Utdata Teknik Telefon: +46 8 788 28 87 S-103 50 STOCKHOLM Mobil: +46 70 689 28 87 E-mail: krister.svard@skandia.se http://www.skandia.se From sandram at boi.hp.com Thu Nov 5 17:06:56 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> another updated charter Message-ID: <01BE08CD.EEAEBEE0.sandram@boi.hp.com> Hi, I modified the Goals section using Stuart's suggested text. And I expanded the out of scope slightly. Please take a look. Remember - We vote this Wed in Tucson. Sandra ------------------------------------------------------------------- Sandra Matts Engineer / Scientist Hewlett-Packard 11311 Chinden Blvd. Boise, ID 83714 sandram@boi.hp.com (208) 396-4755 From nschade at xionics.com Thu Nov 5 14:04:39 1998 From: nschade at xionics.com (NSchade) Date: Wed May 6 14:05:04 2009 Subject: UPD> UPD Charter Message-ID: <005e01be08ef$23a9f760$1c1343ce@nschade.xionics.com> We studied the newest version of the Charter and think this is a good start. So Xionics appreciates this as the overall direction. Regards Norbert From rbergma at dpc.com Wed Nov 18 11:42:35 1998 From: rbergma at dpc.com (Ron Bergman) Date: Wed May 6 14:05:04 2009 Subject: UPD> Adobe PPD Specification Posted Message-ID: I have loaded version 4.3 of the Adobe PPD Specification to the PWG server for your reference. The complete URL is: ftp://ftp.pwg.org/pub/pwg/upd/Archive/503_43_PPDSpec.pdf Ron Bergman Dataproducts Corp. From nschade at xionics.com Mon Dec 7 06:19:48 1998 From: nschade at xionics.com (NSchade) Date: Wed May 6 14:05:04 2009 Subject: UPD> SRS conceptional proposals Message-ID: <000f01be21d3$80aeada0$1c1343ce@nschade.xionics.com> All, find attached a four pages document with some comments on the SRS. It mainly contains eight paragraphs: 1. Work in virtual units 2. Real life parameters 3. A general parameter converter 4. Modular model descriptions where useful 5. Refer to global descriptions where useful 6. Individual technical keys per element 7. Offer printer driver support 8. Extendibility of an open format Please give it an overview to find out, if I'm in sync with you. Norbert -------------- next part -------------- A non-text attachment was scrubbed... Name: updf srs conceptional proposals.doc Type: application/msword Size: 30208 bytes Desc: not available Url : http://www.pwg.org/archives/upd/attachments/19981207/c3a22959/updfsrsconceptionalproposals-0001.doc From sandram at boi.hp.com Tue Dec 15 11:51:18 1998 From: sandram at boi.hp.com (Sandra Matts) Date: Wed May 6 14:05:04 2009 Subject: UPD> Agenda for friday meeting Message-ID: <01BE2810.77398A40@hpb13858.boi.hp.com> Hi All, Here's the agenda for Friday's meeting. If people have items to add or discuss, email me. 8:30 - 9:00 Agenda review and Intros 9:00 - 10:00 Adobe Job tickets 10:00 - 10:15 break 10:15 - 11:15 GPD presentation 11:15 - 12:00 Requirements document 12:00 - 1:?? lunch 1:?? - 2:30 XML Sandra Matts From robert.herriot at Eng.Sun.COM Fri Dec 18 21:25:59 1998 From: robert.herriot at Eng.Sun.COM (Robert Herriot) Date: Wed May 6 14:05:04 2009 Subject: UPD> additional comment from today's meeting about XML In-Reply-To: <01BE01B2.EF16AE00.sandram@boi.hp.com> Message-ID: <199812190220.SAA12293@woden.eng.sun.com> I would like to make one additional comment about XML that I forgot to say before I left today's meeting. XML is a potential encoding method for UPD and probably a good choice, but before we work about encoding details, we should work out the UPD model (as we did in the IPP work). The model semantics should be independent of the encoding. Bob Herriot -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/19981218/3c69a39c/attachment-0001.html