From pwg-announce-owner@pwg.org Tue Jun 1 07:36:00 2004 Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18989; Tue, 1 Jun 2004 07:35:59 -0400 (EDT) Received: from localhost (daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i51BZu826166; Tue, 1 Jun 2004 07:35:57 -0400 (EDT) Received: by pwg.org (bulk_mailer v1.5); Tue, 1 Jun 2004 07:33:16 -0400 Received: from catv-50630582.catv.broadband.hu (catv-50630582.catv.broadband.hu [80.99.5.130]) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i51BX5e25897; Tue, 1 Jun 2004 07:33:06 -0400 (EDT) Message-ID: From: Pereira Angelique To: postmaster@pwg.org Subject: christensen Date: Tue, 01 Jun 2004 07:26:05 -0500 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 7Bit Mime-Version: 1.0 X-Mailer: iLx6WRaY Content-Transfer-Encoding: 7Bit Postmaster trek curriculum mussel incompetent canon doctrine stank brew industrial seal Picture is Loading . . . .


Email not Showin|g?
Nextda.y M.e.d.s Ship.p.ed to Your D.o.or, O.r.d.e.r H.e.r.e





partridge aloha reynolds tenney serial bainite destinate hateful hasty evolution pepsi dread kernighan remittance sharp kid slurp turf bradford newcomer ainu cotoneaster barber blew photography camelback ulster inconvertible canvas belt mathewson apiece combustion corrupt causal devolve chantilly coauthor blackball royce tweed constipate andy jim pristine despot impregnable rectangular protozoa iron aliphatic drop galvanometer claustrophobic ernest infusion royce astronautic ancillary glucose coriander sprague labial bolton mahayana ashmolean admiral druid need whippany uris crappie buxom threaten areawide buckhorn contrast bourbaki elisha calvert monologue dahl leech lorinda abeyance ray yet accuse bruckner soybean lobster problem ogden trawl penn decrement berth wreckage changeable disembowel nicholas tuttle ladylike celestial irwin laminar holster recessive saloon eratosthenes drib legacy suspicious akron maladjust rodgers dahomey realm threonine! antisemitic mezzo brotherhood weekend fret bethought expectorant peritectic ease ruinous workbench atlantica dispense connoisseur dollar daredevil lupine cretinous dam entendre mutatis sheridan thrown streamside townsman azimuth betony locke maelstrom kodachrome flesh breech dogberry incubate anthropology ssw buzzer scrupulous condominium transshipping amplify fright alameda circumstance confrontation janitor spunk calamitous superstitious caribou plenum bona arrow lapel doorkeep ascription eclat berwick mouton carmichael giraffe colette amnesia appian riflemen involute apostrophe cafeteria celebrant mynheer unary chronology rudyard bourbon caldera electress parameter bailey dribble rho euphoria crematory watery teat analogy rubbish cartwheel coiffure endure maori bertrand estuarine seven altercate administratrix arraign model geoduck blandish scrapbook swine orinoco artichoke antipode lye glassine demit which pallet limbo resultant featherbed canine acton cahoot daffy chu! rchgo shamrock controvertible acute demonstrable fasciculate dynamic b awl becalm christoffel ire orthorhombic einstein storyteller midsection archetype digitalis bleach delphi chromatograph blockage costume aegean chub transfer activism hotshot destruct pharmacology embroider drier brant bainite peal wei primp bendix perez packard embryology saturable excite morgue thoughtful hatred tellurium rutty ass lonesome their coniferous jericho prominent pitney towhead antiphonal aloha courtney minos convene tenderloin hawthorn colgate milch leprosy froth carbine cleveland ceremonious erodible smallish solomon ditto stereo chivalry cure apostrophe actuate maneuver sheraton harmonic deity malleable march runoff coinage virgin languish stableman charlottesville wood locomotive lethargy pot whither brainy colleague rose cowan downturn salmonberry stand houseboat From pwg-announce-owner@pwg.org Wed Jun 2 09:41:43 2004 Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21669; Wed, 2 Jun 2004 09:40:42 -0400 (EDT) Received: from localhost (daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i52Deaw07602; Wed, 2 Jun 2004 09:40:41 -0400 (EDT) Received: by pwg.org (bulk_mailer v1.5); Wed, 2 Jun 2004 09:35:43 -0400 Received: (from daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) id i52DZaZ07340 for pwg-announce-outgoing; Wed, 2 Jun 2004 09:35:36 -0400 (EDT) Subject: PWG-ANNOUNCE> PWG ANNOUNCE> PWG Formal Vote Results for UPDF 1.0 To: pwg-announce@pwg.org X-Mailer: Lotus Notes Release 5.0.12 February 13, 2003 Message-ID: From: thrasher@lexmark.com Date: Wed, 2 Jun 2004 09:35:25 -0400 X-MIMETrack: Serialize by Router on smtp5b/Lex/Lexmark (Release 5.0.12 |February 13, 2003) at 06/02/2004 09:35:21 AM MIME-Version: 1.0 Content-type: text/plain; charset="us-ascii" Sender: owner-pwg-announce@pwg.org The results of the recently completed PWG Formal Vote for the UPDF 1.0 Specification are as follows: Vote Count: Yes: 8 No: 1 (with strong objection) Abstain: 2 PWG Process Document Criteria: 1. Met the 25 percent participation (needed at least 9 votes). 2. Met the 80 percent approval requirement from the No w/ strong objection. 3. Met the 50 percent of votes either yes or no....(needed at least 5) UPDF Formal Vote passes. Note: There was one additioinal Yes vote that was received after the voting period closed. By the guidelines in the PWG Process Document (both old and new draft), comments submitted with a No vote (or No with strong objection) are to be posted and discussed on the PWG Announce email list...... Here are the comments: 1. The specification does not include examples for each element, nor does it tie each schema together to show a complete implementation. See the (many) W3C specifications for XML and/or SGML-based formats which *do* include examples. 2. I do not see a single complete sample file for any printer device. I see a lot of fragments made by Norbert, but I don't see a complete file that could be used as reference against the spec or schema files that shows the current specification is useful or feasible for a driver, application, or UI component to use. 3. The separation of schemas is confusing and leads me to believe that a single device description is composed of multiple XML files. Given the limited sample fragments on the PWG FTP server, it is not clear what the actual organization is supposed to be. THIS NEEDS TO BE DEFINED in order to allow for actual interoperability and network transparency. 4. My general impression is that the current specification is not complete enough to be used in an actual printing environment nor does it provide any advantages over existing interfaces and formats. Of what use is a new format if it only does what every other format does? I will send a separate not when the 51xx.n number is assigned and is published as a candidate standard. Jerry Thrasher PWG Secretary From pwg-announce-owner@pwg.org Tue Jun 8 16:26:28 2004 Received: from pwg.org (pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21826; Tue, 8 Jun 2004 16:26:27 -0400 (EDT) Received: from localhost (daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i58KQMb04708; Tue, 8 Jun 2004 16:26:27 -0400 (EDT) Received: by pwg.org (bulk_mailer v1.5); Tue, 8 Jun 2004 16:24:07 -0400 Received: (from daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) id i58KO0j04470 for pwg-announce-outgoing; Tue, 8 Jun 2004 16:24:00 -0400 (EDT) Subject: PWG-ANNOUNCE> May 2004 Vancouver PWG Plenary Meeting Minutes To: pwg-announce@pwg.org X-Mailer: Lotus Notes Release 5.0.12 February 13, 2003 Message-ID: From: thrasher@lexmark.com Date: Tue, 8 Jun 2004 16:18:32 -0400 X-MIMETrack: Serialize by Router on smtp5b/Lex/Lexmark (Release 5.0.12 |February 13, 2003) at 06/08/2004 04:18:41 PM MIME-Version: 1.0 Content-type: text/plain; charset="us-ascii" Sender: owner-pwg-announce@pwg.org The minutes from the May 25, 2004 PWG Plenary Meeting are now on the PWG's ftp site at: ftp://ftp.pwg.org/pub/pwg/general/minutes/pwg_plenary_minutes_20040525.pdf Jerry Thrasher From pwg-announce-owner@pwg.org Wed Jun 9 14:30:48 2004 Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07044; Wed, 9 Jun 2004 14:30:48 -0400 (EDT) Received: from localhost (daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i59IUfP18513; Wed, 9 Jun 2004 14:30:41 -0400 (EDT) Received: by pwg.org (bulk_mailer v1.5); Wed, 9 Jun 2004 14:27:12 -0400 Received: (from daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) id i59IR5g18287 for pwg-announce-outgoing; Wed, 9 Jun 2004 14:27:05 -0400 (EDT) From: "Norbert Schade" To: Subject: PWG-ANNOUNCE> UPDF a confirmed standard Date: Wed, 9 Jun 2004 14:26:07 -0400 Message-ID: <000d01c44e4f$3e40bef0$6e00a8c0@oasis> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01C44E2D.B72F1EF0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Sender: owner-pwg-announce@pwg.org This is a multi-part message in MIME format. ------=_NextPart_000_000E_01C44E2D.B72F1EF0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Last week we got the official statement that UPDF is now considered a = formal standard of the PWG. Let me take the opportunity to thank all contributors for their work. =20 Sandra Matts from HP lead the effort for some years, before I took over = in 2000. It was an up and down all the time. But I think we stayed focussed. = That's what eventually brought us to the finish line. =20 I'd like to especially thank Mark Hamzy and Jim Sommer. Without their critical view and rich feedback together with all the time they spent we would never have got where we are today. =20 We will now wait and see for some time, how well the standard will be adopted. I do not plan to start the next version or an update right away. I want us to practise with the version we have and learn from it. When = we'll have more samples, we'll feel more confident to judge it again and see what's the proper next step. =20 However I have three action items in mind: 1. Deal with Michael Sweet's comments. I plan to launch three related notes (different ways to use the = instances?, how are optional units managed?, how do user policies fit in?) over the pwg-announce reflector, but we'll take the discussion about details back = to the UPDF reflector. 2. Work on samples. We'll likely fill the sample on the UPDF site up with more detailed implementations. further samples may be listed on other web sites. 3. We'll check how a driver may use UPDF instances the best way. The minimum goal could be something like a 'Best Practise' document.=20 =20 I would appreciate any feedback about how you and your company thinks = about using the standard, what implementations you think of and what obstacles = you see in your way for any UPDF related project you may have in mind. =20 Let's work with the stuff! =20 Kind regards Norbert Schade =20 =20 =20 Norbert Schade Software Manager Oasis Semiconductor, Inc. 201 Jones Road Waltham, MA 02451 USA tel. 1-781-370-8929 fax. 1-781-370-8990 email: norbert.schade@oasissemi.com =20 ------=_NextPart_000_000E_01C44E2D.B72F1EF0 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Last week we got the official statement that UPDF is = now considered a formal standard of the PWG.

Let me take the opportunity to thank all contributors = for their work.

 

Sandra Matts from HP lead the effort for some years, = before I took over in 2000.

It was an up and down all the time. But I think we = stayed focussed. That’s what eventually brought us to the finish = line.

 

I’d like to especially thank Mark Hamzy and Jim Sommer. Without their critical view and rich feedback together with all = the time they spent we would never have got where we are = today.

 

We will now wait and see for some time, how well the standard will be adopted.

I do not plan to start the next version or an update = right away.

I want us to practise with the version we have and = learn from it. When we’ll have more samples, we’ll feel more = confident to judge it again and see what’s the proper next = step.

 

However I have three action items in = mind:

  1. Deal with Michael Sweet’s comments.
    I plan to launch three related notes (different ways to use the instances?, how are optional units managed?, how do user policies = fit in?) over the pwg-announce reflector, but we’ll take the = discussion about details back to the UPDF reflector.
  2. Work on samples.
    We’ll likely fill the sample on the UPDF site up with more = detailed implementations.
    further samples may be listed on other web = sites.
  3. We’ll check how a driver may use UPDF = instances the best way.
    The minimum goal could be something like a ‘Best = Practise’ document.

 

I would appreciate any feedback about how you and = your company thinks about using the standard, what implementations you think of and = what obstacles you see in your way for any UPDF related project you may have = in mind.

 

Let’s work with the stuff!

 

Kind regards

Norbert Schade

 

 

 

Norbert = Schade

Software Manager

Oasis Semiconductor, Inc.
201 Jones Road
Waltham, MA 02451

USA
tel. 1-781-370-8929
fax. 1-781-370-8990

email: norbert.schade@oasissemi.com

 

------=_NextPart_000_000E_01C44E2D.B72F1EF0-- From pwg-announce-owner@pwg.org Wed Jun 9 15:13:21 2004 Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11470; Wed, 9 Jun 2004 15:13:15 -0400 (EDT) Received: from localhost (daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i59JD9322279; Wed, 9 Jun 2004 15:13:09 -0400 (EDT) Received: by pwg.org (bulk_mailer v1.5); Wed, 9 Jun 2004 15:11:57 -0400 Received: (from daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) id i59JBm621936 for pwg-announce-outgoing; Wed, 9 Jun 2004 15:11:48 -0400 (EDT) From: "Norbert Schade" To: Subject: PWG-ANNOUNCE> how are optional units managed? Date: Wed, 9 Jun 2004 15:10:02 -0400 Message-ID: <000f01c44e55$60bde1a0$6e00a8c0@oasis> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0010_01C44E33.D9AC41A0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Sender: owner-pwg-announce@pwg.org This is a multi-part message in MIME format. ------=_NextPart_000_0010_01C44E33.D9AC41A0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable In note 1 I already mentioned that UPDF is supposed to be extensible. That goes for human languages, but for optional units as well. =20 Glossary A base unit is the printer itself without anything attached to it = (except RAM, which is very predictable). An optional unit is anything, which can be attached to the base unit or exchanged like optional trays, a duplexer or a finishing unit. =20 The challenge: Most other concepts have to know about optional units before the printer driver is compiled. That is a stolid architecture, as you never know, which optional units = may come up after the first launching of the driver and device package. There are a few concepts out there, where you can add an optional unit = to an existing installation and it will get merged to it. The problem is = detaching it again. Imagine a base unit, which can feed Letter and A4, and an additional tray, which can feed Letter and A5. merge the sizes to one = list and detach the optional unit. Will Letter size be supported after the removal? That's what brought us to separate descriptions for optional units. The = idea is to keep the description separate. So it can be detached without any problem. An optional unit can be described based on the same set of schemas as = the base unit. Just the configuration instance is different (the = configuration of the base unit can refer to more modules). That allows it to mirror the real world as much as possible: you connect = a real optional unit to a real device --> you add a configuration piece of = the logical optional unit to the logical base unit. =20 So the main keyword here is Extensibility. =20 Regards Norbert Schade =20 =20 Norbert Schade Software Manager Oasis Semiconductor, Inc. 201 Jones Road Waltham, MA 02451 USA tel. 1-781-370-8929 fax. 1-781-370-8990 email: norbert.schade@oasissemi.com =20 ------=_NextPart_000_0010_01C44E33.D9AC41A0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

In note 1 I already mentioned that UPDF is supposed = to be extensible.

That goes for human languages, but for optional units = as well.

 

Glossary

A base unit is the printer itself without anything = attached to it (except RAM, which is very predictable).

An optional unit is anything, which can be attached = to the base unit or exchanged like optional trays, a duplexer or a finishing = unit.

 

The challenge:

Most other concepts have to know about optional units = before the printer driver is compiled.

That is a stolid architecture, as you never know, = which optional units may come up after the first launching of the driver and = device package.

There are a few concepts out there, where you can add = an optional unit to an existing installation and it will get merged to it. = The problem is detaching it again. Imagine a base unit, which can feed = Letter and A4, and an additional tray, which can feed Letter and A5. merge the = sizes to one list and detach the optional unit. Will Letter size be supported = after the removal?

That’s what brought us to separate descriptions = for optional units. The idea is to keep the description separate. So it can = be detached without any problem.

An optional unit can be described based on the same = set of schemas as the base unit. Just the configuration instance is different = (the configuration of the base unit can refer to more = modules).

That allows it to mirror the real world as much as = possible: you connect a real optional unit to a real device à you add a configuration piece of the logical optional unit to the logical base = unit.

 

So the main keyword here is = Extensibility.

 

Regards

Norbert Schade

 

 

Norbert = Schade

Software Manager

Oasis Semiconductor, Inc.
201 Jones Road
Waltham, MA 02451

USA
tel. 1-781-370-8929
fax. 1-781-370-8990

email: norbert.schade@oasissemi.com

 

------=_NextPart_000_0010_01C44E33.D9AC41A0-- From pwg-announce-owner@pwg.org Wed Jun 9 15:14:11 2004 Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11617; Wed, 9 Jun 2004 15:14:05 -0400 (EDT) Received: from localhost (daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i59JE0q22488; Wed, 9 Jun 2004 15:14:00 -0400 (EDT) Received: by pwg.org (bulk_mailer v1.5); Wed, 9 Jun 2004 15:12:03 -0400 Received: (from daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) id i59JBwI21954 for pwg-announce-outgoing; Wed, 9 Jun 2004 15:11:58 -0400 (EDT) From: "Norbert Schade" To: Subject: PWG-ANNOUNCE> how do user policies fit in? Date: Wed, 9 Jun 2004 15:10:13 -0400 Message-ID: <001401c44e55$6723e990$6e00a8c0@oasis> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0015_01C44E33.E0124990" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Sender: owner-pwg-announce@pwg.org This is a multi-part message in MIME format. ------=_NextPart_000_0015_01C44E33.E0124990 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I tried to explain the importance of extensibility in the UPDF concept. =20 When thinking of user policies that thought is thoroughly continued. =20 Glossary Once a driver is installed, a user policy for a special user or user = group may be set on top of it. A user policy allows people like system administrators to define = additional rules how to use the driver. This will typically be something in the range of hiding certain records = of features or complete features or have the user interface appear = differently for some users or set different defaults or conditions for some users. =20 Goal The goal is to keep that information separate to the description the IHV = has provided. So you can assign it and easily deactivate it again. You have seen that idea being used in various areas now. =20 One basic idea of UPDF is always: don't touch nor change things you = haven't created. The only instance nobody has to treat as read-only is the device configuration. That instance is the key component to refer to all = modules and therefore is supposed to be changed whenever something is added or = taken away. =20 Ok, these were the three notes of background information. Now I need some feedback, if that helped elucidate on the architecture = or what else could be done??? =20 Regards Norbert Schade =20 =20 Norbert Schade Software Manager Oasis Semiconductor, Inc. 201 Jones Road Waltham, MA 02451 USA tel. 1-781-370-8929 fax. 1-781-370-8990 email: norbert.schade@oasissemi.com =20 ------=_NextPart_000_0015_01C44E33.E0124990 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I tried to explain the importance of extensibility in = the UPDF concept.

 

When thinking of user policies that thought is = thoroughly continued.

 

Glossary

Once a driver is installed, a user policy for a = special user or user group may be set on top of it.

A user policy allows people like system = administrators to define additional rules how to use the driver.

This will typically be something in the range of = hiding certain records of features or complete features or have the user = interface appear differently for some users or set different defaults or = conditions for some users.

 

Goal

The goal is to keep that information separate to the description the IHV has provided.

So you can assign it and easily deactivate it = again.

You have seen that idea being used in various areas = now.

 

One basic idea of UPDF is always: don’t touch = nor change things you haven’t created.

The only instance nobody has to treat as read-only is = the device configuration. That instance is the key component to refer to all modules and therefore is supposed to be changed whenever something is = added or taken away.

 

Ok, these were the three notes of background = information.

Now I need some feedback, if that helped elucidate on = the architecture or what else could be done???

 

Regards

Norbert Schade

 

 

Norbert = Schade

Software Manager

Oasis Semiconductor, Inc.
201 Jones Road
Waltham, MA 02451

USA
tel. 1-781-370-8929
fax. 1-781-370-8990

email: norbert.schade@oasissemi.com

 

------=_NextPart_000_0015_01C44E33.E0124990-- From pwg-announce-owner@pwg.org Wed Jun 9 18:30:46 2004 Received: from pwg.org (pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00809; Wed, 9 Jun 2004 18:30:44 -0400 (EDT) Received: from localhost (daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i59MUdq00304; Wed, 9 Jun 2004 18:30:44 -0400 (EDT) Received: by pwg.org (bulk_mailer v1.5); Wed, 9 Jun 2004 18:25:33 -0400 Received: (from daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) id i59MO4E00067 for pwg-announce-outgoing; Wed, 9 Jun 2004 18:24:04 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C44E70.70DC511F" Subject: RE: PWG-ANNOUNCE> how are optional units managed? Date: Wed, 9 Jun 2004 15:23:50 -0700 Message-ID: <02954887D466F24D9F3FC9F47466DEF0E0B5B9@cdaexchange.sc.rd.canon.com> Thread-Topic: PWG-ANNOUNCE> how are optional units managed? Thread-Index: AcROVwTOhF+CcBKwRY2U7Na5nqCYyAAGS2Ow From: "Farrell, Lee" To: "Norbert Schade" , Sender: owner-pwg-announce@pwg.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C44E70.70DC511F Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Norbert, =20 Could you please move this discussion to the UPDF reflector? =20 Unless there's something I'm missing, it seems more appropriate there. =20 Thanks, =20 lee ________________________________ From: owner-pwg-announce@pwg.org [mailto:owner-pwg-announce@pwg.org] On Behalf Of Norbert Schade Sent: Wednesday, June 09, 2004 12:10 PM To: pwg-announce@pwg.org Subject: PWG-ANNOUNCE> how are optional units managed? In note 1 I already mentioned that UPDF is supposed to be extensible. That goes for human languages, but for optional units as well. =20 Glossary A base unit is the printer itself without anything attached to it (except RAM, which is very predictable). An optional unit is anything, which can be attached to the base unit or exchanged like optional trays, a duplexer or a finishing unit. =20 The challenge: Most other concepts have to know about optional units before the printer driver is compiled. That is a stolid architecture, as you never know, which optional units may come up after the first launching of the driver and device package. There are a few concepts out there, where you can add an optional unit to an existing installation and it will get merged to it. The problem is detaching it again. Imagine a base unit, which can feed Letter and A4, and an additional tray, which can feed Letter and A5. merge the sizes to one list and detach the optional unit. Will Letter size be supported after the removal? That's what brought us to separate descriptions for optional units. The idea is to keep the description separate. So it can be detached without any problem. An optional unit can be described based on the same set of schemas as the base unit. Just the configuration instance is different (the configuration of the base unit can refer to more modules). That allows it to mirror the real world as much as possible: you connect a real optional unit to a real device --> you add a configuration piece of the logical optional unit to the logical base unit. =20 So the main keyword here is Extensibility. =20 Regards Norbert Schade =20 =20 Norbert Schade Software Manager Oasis Semiconductor, Inc. 201 Jones Road Waltham, MA 02451 USA tel. 1-781-370-8929 fax. 1-781-370-8990 email: norbert.schade@oasissemi.com =20 ------_=_NextPart_001_01C44E70.70DC511F Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hi Norbert,
 
Could you please move this discussion to the = UPDF=20 reflector?
 
Unless there's something I'm missing, it seems = more=20 appropriate there.
 
Thanks,
 
lee

From: owner-pwg-announce@pwg.org=20 [mailto:owner-pwg-announce@pwg.org] On Behalf Of Norbert=20 Schade
Sent: Wednesday, June 09, 2004 12:10 PM
To:=20 pwg-announce@pwg.org
Subject: PWG-ANNOUNCE> how are = optional units=20 managed?

In note 1 I already = mentioned that=20 UPDF is supposed to be extensible.

That goes for human = languages, but=20 for optional units as well.

 

Glossary

A base unit is the printer = itself=20 without anything attached to it (except RAM, which is very=20 predictable).

An optional unit is = anything, which=20 can be attached to the base unit or exchanged like optional trays, a = duplexer or=20 a finishing unit.

 

The = challenge:

Most other concepts have = to know=20 about optional units before the printer driver is = compiled.

That is a stolid = architecture, as=20 you never know, which optional units may come up after the first = launching of=20 the driver and device package.

There are a few concepts = out there,=20 where you can add an optional unit to an existing installation and it = will get=20 merged to it. The problem is detaching it again. Imagine a base unit, = which can=20 feed Letter and A4, and an additional tray, which can feed Letter and = A5. merge=20 the sizes to one list and detach the optional unit. Will Letter size be=20 supported after the removal?

That’s what brought = us to separate=20 descriptions for optional units. The idea is to keep the description = separate.=20 So it can be detached without any problem.

An optional unit can be = described=20 based on the same set of schemas as the base unit. Just the = configuration=20 instance is different (the configuration of the base unit can refer to = more=20 modules).

That allows it to mirror = the real=20 world as much as possible: you connect a real optional unit to a real = device=20 à you add a=20 configuration piece of the logical optional unit to the logical base=20 unit.

 

So the main keyword here = is=20 Extensibility.

 

Regards

Norbert = Schade

 

 

Norbert=20 Schade

Software=20 Manager

Oasis=20 Semiconductor, Inc.
201 Jones=20 Road
Waltham, = MA = 02451

USA
tel.=20 1-781-370-8929
fax.=20 1-781-370-8990

email:=20 norbert.schade@oasissemi.com

 

------_=_NextPart_001_01C44E70.70DC511F-- From pwg-announce-owner@pwg.org Mon Jun 14 20:04:27 2004 Received: from pwg.org (pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14347; Mon, 14 Jun 2004 20:04:26 -0400 (EDT) Received: from localhost (daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i5F04Kc12765; Mon, 14 Jun 2004 20:04:20 -0400 (EDT) Received: by pwg.org (bulk_mailer v1.5); Mon, 14 Jun 2004 20:00:36 -0400 Received: (from daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) id i5F00Tu12545 for pwg-announce-outgoing; Mon, 14 Jun 2004 20:00:29 -0400 (EDT) Content-class: urn:content-classes:message Subject: PWG-ANNOUNCE> Printer & Finisher MIBs Status Date: Mon, 14 Jun 2004 17:00:26 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4526B.C3470BD4" Message-ID: X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Thread-Topic: Printer & Finisher MIBs Status Thread-Index: AcRSa8NCL7v2mxmjTgWNmbfTwkXX2w== From: "Bergman, Ron" To: Sender: owner-pwg-announce@pwg.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C4526B.C3470BD4 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The long awaited Printer MIB v2 and Finisher MIB are now available as = IETF official documents. (Although the official IETF announce has not been made.) ftp://ftp.isi.edu/in-notes/rfc3805.txt (Printer MIB v2) ftp://ftp.isi.edu/in-notes/rfc3806.txt (Finisher MIB) ftp://ftp.isi.edu/in-notes/rfc3808.txt (Charset MIB) Note that the Charset MIB now provides the missing enumerations for the = CodedCharSet textual convention defined in RFC1759. This TC is now known as = IANACharset.=20 I would like to thank everyone who contributed to these documents over = the last 8 years. I especially want to thank Ira McDonald and Bert Wijnen, who spent = countless hours reviewing and helping edit the documents and working with the IETF to = move the drafts to their final state. Others outside of the PWG that provided = significant inputs include Juergen Schoenwaelder and David Harrington. The number of contibutors in the PWG is a long list and can be found in = the documents. Ron Bergman Hitachi Printing Solutions, America ------_=_NextPart_001_01C4526B.C3470BD4 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Printer & Finisher MIBs Status

The long awaited Printer MIB v2 and = Finisher MIB are now available as IETF official documents.
(Although the official IETF announce = has not been made.)

  ftp://ftp.isi.edu/in-note= s/rfc3805.txt   (Printer MIB v2)

  ftp://ftp.isi.edu/in-note= s/rfc3806.txt   (Finisher MIB)

  ftp://ftp.isi.edu/in-note= s/rfc3808.txt   (Charset MIB)

Note that the Charset MIB now provides = the missing enumerations for the CodedCharSet
textual convention defined in = RFC1759.  This TC is now known as IANACharset.

I would like to thank everyone who = contributed to these documents over the last 8 years.
I especially want to thank Ira = McDonald and Bert Wijnen, who spent countless hours
reviewing and helping edit the = documents and working with the IETF to move the drafts
to their final state.  Others = outside of the PWG that provided significant inputs include
Juergen Schoenwaelder and David = Harrington.

The number of contibutors in the PWG is = a long list and can be found in the documents.

        Ron Bergman
        Hitachi Printing Solutions, America

------_=_NextPart_001_01C4526B.C3470BD4-- From pmp-owner@pwg.org Mon Jun 14 21:04:33 2004 Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17831 for ; Mon, 14 Jun 2004 21:04:32 -0400 (EDT) Received: from localhost (daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i5F146914986 for ; Mon, 14 Jun 2004 21:04:16 -0400 (EDT) Received: by pwg.org (bulk_mailer v1.5); Mon, 14 Jun 2004 21:02:20 -0400 Received: from pmp-outgoing ([211.148.218.81]) by pwg.org (8.11.7p1+Sun/8.9.2) with ESMTP id i5F126d14882 for ; Mon, 14 Jun 2004 21:02:07 -0400 (EDT) Message-Id: <200406150102.i5F126d14882@pwg.org> From: "ch99118i8@126.com" Subject: =?GB2312?B?w/ux7c+1wdA=?= 9:1:59:546 To: pmp-outgoing@pwg.org Content-Type: text/html;charset="GB2312" Reply-To: ch991188@21cn.com Date: Tue, 15 Jun 2004 09:02:07 +0800 X-Priority: 4 X-Mailer: Microsoft Outlook Express 5.50.4133.2400

公司网址:http://twp.sohusz.com   公司电话:0755-61323883  Eamil:ch991188@21cn.com  
雷达(零售价￥380元)
 
 

 
江诗丹顿零售价￥200元

保茄利(零售价￥380元)
 
帝舵(另售价￥950元)
 
江诗丹顿(零售价￥380元)
 
欧米茄(零售价￥380元)
 
卡地亚(零售价￥380元)
雷达表及包装合
 

广东深圳市香归电子有限公司



From pwg-announce-owner@pwg.org Wed Jun 16 10:25:23 2004 Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00595; Wed, 16 Jun 2004 10:25:22 -0400 (EDT) Received: from localhost (daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i5GEP5n00265; Wed, 16 Jun 2004 10:25:11 -0400 (EDT) Received: by pwg.org (bulk_mailer v1.5); Wed, 16 Jun 2004 10:13:40 -0400 Received: (from daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) id i5GEDIH29982 for pwg-announce-outgoing; Wed, 16 Jun 2004 10:13:18 -0400 (EDT) Subject: PWG-ANNOUNCE> UPDF 1.0 Candidate Standard Published To: pwg-announce@pwg.org X-Mailer: Lotus Notes Release 5.0.12 February 13, 2003 Message-ID: From: thrasher@lexmark.com Date: Wed, 16 Jun 2004 10:12:16 -0400 X-MIMETrack: Serialize by Router on smtp5b/Lex/Lexmark (Release 5.0.12 |February 13, 2003) at 06/16/2004 10:12:18 AM MIME-Version: 1.0 Content-type: text/plain; charset="us-ascii" Sender: owner-pwg-announce@pwg.org FYI, The recently PWG approved Universal Printer Description Format specification (UPDF 1.0) has been published as: PWG 5101.4-2004. The updated files are available in the "candidates" directory on the PWG ftp site. Filenames: cs-upd10-20040526-5101.4.doc and .pdf Jerry Thrasher PWG Secretary From pwg-announce-owner@pwg.org Fri Jun 18 12:44:05 2004 Received: from pwg.org (pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04536; Fri, 18 Jun 2004 12:43:04 -0400 (EDT) Received: from localhost (daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i5IGgnV23890; Fri, 18 Jun 2004 12:42:49 -0400 (EDT) Received: by pwg.org (bulk_mailer v1.5); Fri, 18 Jun 2004 12:37:54 -0400 Received: (from daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) id i5IGbVw23650 for pwg-announce-outgoing; Fri, 18 Jun 2004 12:37:31 -0400 (EDT) To: pwg-announce@pwg.org MIME-Version: 1.0 Subject: PWG-ANNOUNCE> Call for interest - Complete Standard Imaging Model X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 Message-ID: From: Harry Lewis Date: Fri, 18 Jun 2004 10:37:21 -0600 X-MIMETrack: Serialize by Router on D03NM132/03/M/IBM(Release 6.0.2CF2HF259 | March 11, 2004) at 06/18/2004 10:37:22, Serialize complete at 06/18/2004 10:37:22 Content-Type: multipart/alternative; boundary="=_alternative 005B508B87256EB7_=" Sender: owner-pwg-announce@pwg.org This is a multipart message in MIME format. --=_alternative 005B508B87256EB7_= Content-Type: text/plain; charset="US-ASCII" The PWG has a legacy of developing standards that span a large segment of the printing industry. The Printer MIB, for example, has been adopted in devices ranging from low-price, low-speed network attached printers to very high speed production applications. The PWG Common Semantic Model, likewise, is leveraged by industry standards ranging from CIP4 to Bluetooth. One area of primary focus, the networked office device, has undergone a transformation from network printer to network MFD with an associated shift toward to a services oriented, fleet managed placement and operation model. This begs for new standards upon with to base new tools development to enable remote management of heterogenous fleets. The PWG is responding to this need, largely via the WIMS (Web-based Imaging Management Services) effort which includes extending the PWG Common Semantic Model to express the necessary device management elements. WIMS presents the opportunity (and need) for the PWG to model more than just the printer, print job and document... but to grow our model to embrace a more complete imaging system including scan, fax, copy and finishing services. THIS IS A CALL FOR INTEREST IN FORMATION AND PARTICIPATION IN A FORMAL, MFD ORIENTED, PWG WORKING GROUP TO DEFINE A COMPLETE STANDARD IMAGING MODEL. I hope the industry will respond with a show of support for this effort. To create a CSIM working group we will need volunteer leadership and knowledgeable participants from across the industry. If, due to lack of bandwidth (in PWG and the industry) we cannot muster critical mass, the default approach will be for WIMS to develop a skeleton set of objects, enough to express the state and some metrics interesting to fleet management and billing (ex. number of scan impressions). We try not to clog up "pwg-announce" with long threads so I invite you to respond to me, personally and copy your response to "pwg@pwg.org" where we welcome and encourage general discussion about goals and operation of the PWG. I look forward to your responses and I will plan a report on this topic and proposal for action during the PWG Plenary in Montreal August 18, 2004. ---------------------------------------------- Harry Lewis IBM STSM Chairman - IEEE-ISTO Printer Working Group http://www.pwg.org IBM Printing Systems http://www.ibm.com/printers 303-924-5337 ---------------------------------------------- --=_alternative 005B508B87256EB7_= Content-Type: text/html; charset="US-ASCII"
The PWG has a legacy of developing standards that span a large segment of the printing industry. The Printer MIB, for example, has been adopted in devices ranging from low-price, low-speed network attached printers to very high speed production applications. The PWG Common Semantic Model, likewise, is leveraged by industry standards ranging from CIP4 to Bluetooth.

One area of primary focus, the networked office device, has undergone a transformation from network printer to network MFD with an associated shift toward to a services oriented, fleet managed placement and operation model. This begs for new standards upon with to base new tools development to enable remote management of heterogenous fleets. The PWG is responding to this need, largely via the WIMS (Web-based Imaging Management Services) effort which includes extending the PWG Common Semantic Model to express the necessary device management elements.  

WIMS presents the opportunity (and need) for the PWG to model more than just the printer, print job and document... but to grow our model to embrace a more complete imaging system including scan, fax, copy and finishing services. THIS IS A CALL FOR INTEREST IN FORMATION AND PARTICIPATION IN A FORMAL, MFD ORIENTED, PWG WORKING GROUP TO DEFINE A COMPLETE STANDARD IMAGING MODEL. I hope the industry will respond with a show of support for this effort. To create a CSIM working group we will need volunteer leadership and knowledgeable participants from across the industry. If, due to lack of bandwidth (in PWG and the industry) we cannot muster critical mass, the default approach will be for WIMS to develop a skeleton set of objects, enough to express the state and some metrics interesting to fleet management and billing (ex. number of scan impressions).

We try not to clog up "pwg-announce" with long threads so I invite you to respond to me, personally and copy your response to "pwg@pwg.org" where we welcome and encourage general discussion about goals and operation of the PWG.

I look forward to your responses and I will plan a report on this topic and proposal for action during the PWG Plenary in Montreal August 18, 2004.
----------------------------------------------
Harry Lewis
IBM STSM
Chairman - IEEE-ISTO Printer Working Group
http://www.pwg.org
IBM Printing Systems
http://www.ibm.com/printers
303-924-5337
---------------------------------------------- --=_alternative 005B508B87256EB7_=-- From pwg-announce-owner@pwg.org Tue Jun 22 22:20:58 2004 Received: from pwg.org (pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24423; Tue, 22 Jun 2004 22:20:57 -0400 (EDT) Received: from localhost (daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i5N2Kvd14547; Tue, 22 Jun 2004 22:20:57 -0400 (EDT) Received: by pwg.org (bulk_mailer v1.5); Tue, 22 Jun 2004 22:18:49 -0400 Received: (from daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) id i5N2Iai14328 for pwg-announce-outgoing; Tue, 22 Jun 2004 22:18:36 -0400 (EDT) Message-ID: From: "McDonald, Ira" To: pwg-announce@pwg.org Subject: PWG-ANNOUNCE> FW: Diff files for IPP> Notification Documents Date: Tue, 22 Jun 2004 19:18:26 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-pwg-announce@pwg.org Hi, Bob Herriot has just finished doing minimal required changes to the three IPP Notification documents (requirements, base, and IPPGET delivery method) to respond to the pending IETF reviewer comments. If you don't like these semantics, this is your LAST chance to change them for IPP, before they move onto the IETF 'standards track'. Note that WIMS currently supports leases (for example) via different attributes. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: owner-ipp@pwg.org [mailto:owner-ipp@pwg.org]On Behalf Of Robert Herriot Sent: Tuesday, June 22, 2004 6:22 PM To: ipp@pwg.org Subject: Diff files for IPP> Documents I have uploaded .doc and .pdf files. Each file is the diff of the current Word file that is the source for the latest IETF draft against the Word file that was the source of the preceding IETF draft. ipp-notification-requirements-040621-rev.pdf ipp-notify-get-040621-rev.pdf ipp-not-spec-040621-rev.pdf and similar for .doc files. They are in the usual pwg/ipp/new_NOT directory. . Bob Herriot From pwg-announce-owner@pwg.org Wed Jun 23 04:26:49 2004 Received: from pwg.org (pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05758; Wed, 23 Jun 2004 04:26:49 -0400 (EDT) Received: from localhost (daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i5N8Qll19478; Wed, 23 Jun 2004 04:26:48 -0400 (EDT) Received: by pwg.org (bulk_mailer v1.5); Wed, 23 Jun 2004 04:25:19 -0400 Received: (from daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) id i5N8OlM19136 for pwg-announce-outgoing; Wed, 23 Jun 2004 04:24:47 -0400 (EDT) Message-Id: <6.0.3.0.0.20040623001722.04013a48@pop.sbcglobal.yahoo.com> X-Sender: herriot@sbcglobal.net@pop.sbcglobal.yahoo.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0 Date: Wed, 23 Jun 2004 01:26:32 -0700 To: "McDonald, Ira" , pwg-announce@pwg.org From: Robert Herriot Subject: Re: PWG-ANNOUNCE> FW: Diff files for IPP> Notification Documents Cc: ipp@pwg.org In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_40785736==.ALT" Sender: owner-pwg-announce@pwg.org --=====================_40785736==.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed I'm sorry that my reply is on pwg-announce. However, I need to respond to the Ira's email that he sent via pwg-announce. I hope that the PWG members are willing to accept the notification documents in their current form and will not request any changes or enhancements (small typos and errors excepted). In their current form, they are likely to be published as RFCs soon because IETF reviewers have made comments about the documents and I have made corrections that address IETF reviewers' suggestions. If I make changes beyond those requested by the IETF reviewers, there are two major problems. First, I don't have time to make major changes and no one else does either. I have offered to do only a small amount of pro-bono work. Second, the IETF review process would have to start all over again, and the reviewers have made it clear that they don't want to review the documents again. Unless these documents progress in essentially their current form, they run a very high risk of never being published by the IETF. I believe that it is best for the PWG to ensure that the IETF publish these 3 documents, and that means that they must be published in their current form. If PWG wants to make extensions to these documents, such extensions should be published in new IEEE-ISTO documents via some new process that is a successor to the process that produced these documents. Bob Herriot At Tuesday 6/22/2004 07:18 PM, McDonald, Ira wrote: >Hi, > >Bob Herriot has just finished doing minimal required >changes to the three IPP Notification documents >(requirements, base, and IPPGET delivery method) >to respond to the pending IETF reviewer comments. > >If you don't like these semantics, this is your LAST >chance to change them for IPP, before they move onto >the IETF 'standards track'. Note that WIMS currently >supports leases (for example) via different attributes. > >Cheers, >- Ira > >Ira McDonald (Musician / Software Architect) >Blue Roof Music / High North Inc >PO Box 221 Grand Marais, MI 49839 >phone: +1-906-494-2434 >email: imcdonald@sharplabs.com > > >-----Original Message----- >From: owner-ipp@pwg.org [mailto:owner-ipp@pwg.org]On Behalf Of Robert >Herriot >Sent: Tuesday, June 22, 2004 6:22 PM >To: ipp@pwg.org >Subject: Diff files for IPP> Documents > > >I have uploaded .doc and .pdf files. > >Each file is the diff of the current Word file that is the source for the >latest IETF draft against the Word file that was the source of the preceding >IETF draft. > >ipp-notification-requirements-040621-rev.pdf >ipp-notify-get-040621-rev.pdf >ipp-not-spec-040621-rev.pdf > >and similar for .doc files. > >They are in the usual pwg/ipp/new_NOT directory. >.. > >Bob Herriot --=====================_40785736==.ALT Content-Type: text/html; charset="us-ascii" I'm sorry that my reply is on pwg-announce. However, I need to respond to the Ira's email that he sent via pwg-announce.

I hope that the PWG members are willing to accept the notification documents in their current form and will not request any changes or enhancements (small typos and errors excepted).  In their current form, they are likely to be published as RFCs soon because IETF reviewers have made comments about the documents and I have made corrections that address IETF reviewers' suggestions.  If I make changes beyond those requested by the IETF reviewers, there are two major problems.
First, I don't have time to make major changes and no one else does either.  I have offered to do only a small amount of pro-bono work.  Second, the IETF review process would have to start all over again, and the reviewers have made it clear that they don't want to review the documents again. Unless these documents progress in essentially their current form,  they run a very high risk of never being published by the IETF. 

I believe that it is best for the PWG to ensure that the IETF publish these 3 documents, and that means that they must be published in their current form. If PWG wants to make extensions to these documents, such extensions should be published in new IEEE-ISTO documents via some new process that is a successor to the process that produced these documents. 

Bob Herriot


At Tuesday 6/22/2004 07:18 PM, McDonald, Ira wrote:
Hi,

Bob Herriot has just finished doing minimal required
changes to the three IPP Notification documents
(requirements, base, and IPPGET delivery method)
to respond to the pending IETF reviewer comments.

If you don't like these semantics, this is your LAST
chance to change them for IPP, before they move onto
the IETF 'standards track'.  Note that WIMS currently
supports leases (for example) via different attributes.

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221  Grand Marais, MI  49839
phone: +1-906-494-2434
email: imcdonald@sharplabs.com

 
-----Original Message-----
From: owner-ipp@pwg.org [mailto:owner-ipp@pwg.org]On Behalf Of Robert
Herriot
Sent: Tuesday, June 22, 2004 6:22 PM
To: ipp@pwg.org
Subject: Diff files for IPP> Documents


I have uploaded .doc and .pdf files.

Each file is the diff of the current Word file that is the source for the
latest IETF draft against the Word file that was the source of the preceding
IETF draft.

ipp-notification-requirements-040621-rev.pdf
ipp-notify-get-040621-rev.pdf
ipp-not-spec-040621-rev.pdf

and similar for .doc files.

They are in the usual pwg/ipp/new_NOT directory.
..

Bob Herriot
--=====================_40785736==.ALT-- From pmp-owner@pwg.org Wed Jun 23 12:08:35 2004 Received: from pwg.org (pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10723 for ; Wed, 23 Jun 2004 12:08:29 -0400 (EDT) Received: from localhost (daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i5NG8J727474 for ; Wed, 23 Jun 2004 12:08:20 -0400 (EDT) Received: by pwg.org (bulk_mailer v1.5); Wed, 23 Jun 2004 12:07:11 -0400 Received: (from daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) id i5NG6wV27379 for pmp-outgoing; Wed, 23 Jun 2004 12:06:58 -0400 (EDT) Message-ID: From: "McDonald, Ira" To: "'pmp@pwg.org'" Subject: PMP> FW: OIDs defined in RFC 3805, 3806 Date: Wed, 23 Jun 2004 09:06:49 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Sender: pmp-owner@pwg.org Hi, FYI - thanks Olivier! Cheers, - Ira (co-editor of RFC 3805 and 3806) Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Olivier Dubuisson [mailto:Olivier.Dubuisson@francetelecom.com] Sent: Wednesday, June 23, 2004 4:56 AM To: Ron.Bergman@hitachi-ps.us; harryl@us.ibm.com; imcdonald@sharplabs.com Cc: RayCasterline@lhsolutions.com; gary@gocek.org; hastings@cp10.es.xerox.com; sisaacson@novell.com; binnur_al-kazily@hp.com; kellerman@nls.com; emking@lexmark.com; jkm@underscore.com Subject: OIDs defined in RFC 3805, 3806 It is my pleasure to inform you that all the object identifiers (OID) defined in RFC 3805, 3806 have been automatically extracted and are now available (together with their associated description) in the OID repository at http://oid.elibel.tm.fr Note that, in RFC 3805 the OID values hrDeviceEntry and hrPrinterEntry are used but not defined nor imported in this RFC. We took the definition from RFC 2790. Note that, in RFC 3806, the OID values prtMIBConformance and printmib are used but not defined nor imported in this RFC. We took the definition from RFC 2790. -- Olivier DUBUISSON france telecom R&D DTL/TAL - 22307 Lannion Cedex - France t: +33 2 96 05 38 50 - f: +33 2 96 05 39 45 - http://asn1.elibel.tm.fr/ From pmp-owner@pwg.org Wed Jun 23 12:08:43 2004 Received: from pwg.org (pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10744 for ; Wed, 23 Jun 2004 12:08:37 -0400 (EDT) Received: from localhost (daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i5NG8cx27515 for ; Wed, 23 Jun 2004 12:08:38 -0400 (EDT) Received: by pwg.org (bulk_mailer v1.5); Wed, 23 Jun 2004 12:07:59 -0400 Received: (from daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) id i5NG7oV27415 for pmp-outgoing; Wed, 23 Jun 2004 12:07:50 -0400 (EDT) Message-ID: From: "McDonald, Ira" To: "'pmp@pwg.org'" Subject: PMP> FW: OIDs defined in RFC 3808 Date: Wed, 23 Jun 2004 09:07:39 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Sender: pmp-owner@pwg.org Hi, FYI - thanks Olivier! Cheers, - Ira (editor of RFC 3808, IANA Charset MIB) Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: Olivier Dubuisson [mailto:Olivier.Dubuisson@francetelecom.com] Sent: Wednesday, June 23, 2004 4:57 AM To: imcdonald@sharplabs.com; iana@iana.org Subject: OIDs defined in RFC 3808 It is my pleasure to inform you that all the object identifiers (OID) defined in RFC 3808 have been automatically extracted and are now available (together with their associated description) in the OID repository at http://oid.elibel.tm.fr -- Olivier DUBUISSON france telecom R&D DTL/TAL - 22307 Lannion Cedex - France t: +33 2 96 05 38 50 - f: +33 2 96 05 39 45 - http://asn1.elibel.tm.fr/ From pwg-announce-owner@pwg.org Wed Jun 23 16:28:19 2004 Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14305; Wed, 23 Jun 2004 16:28:16 -0400 (EDT) Received: from localhost (daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i5NKSFe29911; Wed, 23 Jun 2004 16:28:15 -0400 (EDT) Received: by pwg.org (bulk_mailer v1.5); Wed, 23 Jun 2004 16:24:39 -0400 Received: (from daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) id i5NKOWx29690 for pwg-announce-outgoing; Wed, 23 Jun 2004 16:24:32 -0400 (EDT) Message-ID: From: "McDonald, Ira" To: pwg-announce@pwg.org Subject: PWG-ANNOUNCE> FW: Webcast on ICU for SW globalization Date: Wed, 23 Jun 2004 13:24:08 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-pwg-announce@pwg.org Hi, The portable (and much ported) ICU library, free software from IBM, is a dominant Unicode support library. Of interest to anyone building internationalized software or web pages. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: www-international-request@w3.org [mailto:www-international-request@w3.org]On Behalf Of Mark Davis Sent: Wednesday, June 23, 2004 2:02 PM To: unicode@unicode.org Subject: Webcast on ICU for SW globalization For those who may be interested in using ICU for software globalization, IBM is offering a webcast tomorrow; I'm forwarding the blurb below. BTW, attendance is limited, and you have to sign up in advance. Mark Davis ================= An Introduction to ICU (International Components for Unicode) June 24th, 2004 15:00 - 16:30 GMT 11:00 - 12:30 US Eastern Time 08:00 - 09:30 US Pacific Time Software globalization used to be limited to major operating systems and applications. Today, all major companies need to have an international web presence, and few software applications can afford to be limited to domestic markets. Unicode is a key building block in globalized systems, but it is still a significant effort to build software to deal successfully with the requirements of all the different languages around the world. IBM's ICU library provides the most powerful Unicode software globalization support available -- for free! Learn how ICU helps to solve your problems in globalizing software for world languages and cultures. To sign up, go to the following page: http://developer.raindance.com/iccdocs/seminarDesc.shtml?id=58502 From pwg-announce-owner@pwg.org Wed Jun 23 16:38:00 2004 Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15281; Wed, 23 Jun 2004 16:38:00 -0400 (EDT) Received: from localhost (daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i5NKbtK00614; Wed, 23 Jun 2004 16:37:55 -0400 (EDT) Received: by pwg.org (bulk_mailer v1.5); Wed, 23 Jun 2004 16:32:59 -0400 Received: (from daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) id i5NKWoP00198 for pwg-announce-outgoing; Wed, 23 Jun 2004 16:32:50 -0400 (EDT) Message-ID: From: "McDonald, Ira" To: pwg-announce@pwg.org Subject: PWG-ANNOUNCE> RFC 3778 - application/pdf MIME type Date: Wed, 23 Jun 2004 13:32:47 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-pwg-announce@pwg.org Hi folks, First ever RFC addressing the 'application/pdf' MIME type. Short. Good security stuff. Worth reading. ftp://ftp.isi.edu/in-notes/rfc3778.txt Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com From pwg-announce-owner@pwg.org Wed Jun 23 22:04:40 2004 Received: from pwg.org (pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06598; Wed, 23 Jun 2004 22:04:39 -0400 (EDT) Received: from localhost (daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i5O24YO07733; Wed, 23 Jun 2004 22:04:39 -0400 (EDT) Received: by pwg.org (bulk_mailer v1.5); Wed, 23 Jun 2004 22:01:22 -0400 Received: (from daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) id i5O21FM07518 for pwg-announce-outgoing; Wed, 23 Jun 2004 22:01:15 -0400 (EDT) Message-ID: From: "McDonald, Ira" To: pwg-announce@pwg.org Subject: PWG-ANNOUNCE> RFC 3826 - AES with SNMPv3 User-based Security Model Date: Wed, 23 Jun 2004 19:01:00 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-pwg-announce@pwg.org Hi, If you're considering supporting or deploying SNMPv3, you need this extension, for the rapidly deploying successor to DES and Triple-DES, Advanced Encryption Standard (AES): ftp://ftp.isi.edu/in-notes/rfc3826.txt Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com From pmp-owner@pwg.org Thu Jun 24 16:37:44 2004 Received: from pwg.org (pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28297 for ; Thu, 24 Jun 2004 16:37:43 -0400 (EDT) Received: from localhost (daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i5OKbcI16540 for ; Thu, 24 Jun 2004 16:37:38 -0400 (EDT) Received: by pwg.org (bulk_mailer v1.5); Thu, 24 Jun 2004 16:35:16 -0400 Received: (from daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) id i5OKZ7O16475 for pmp-outgoing; Thu, 24 Jun 2004 16:35:07 -0400 (EDT) Message-ID: From: "McDonald, Ira" To: "'pmp@pwg.org'" Subject: PMP> RFCs/MIBs posted for Printer & Finisher MIBs Date: Thu, 24 Jun 2004 13:34:48 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Sender: pmp-owner@pwg.org Hi folks, Thursday (24 June 2004) Thanks to Ron Bergman for reminding me. I've just posted both the source RFCs and the machine-extracted '.mib' files for Printer MIB v2 and Finisher MIB on the PWG server in the Printer MIB Project (pmp) directory: ftp://ftp.pwg.org/pub/pwg/pmp/mibs/rfc3805.txt - RFC - Printer MIB v2 ftp://ftp.pwg.org/pub/pwg/pmp/mibs/rfc3806.txt - RFC - Finisher MIB ftp://ftp.pwg.org/pub/pwg/pmp/mibs/rfc3808.txt - RFC - IANA Charset MIB ftp://ftp.pwg.org/pub/pwg/pmp/mibs/rfc3805a.mib - IANA Printer MIB ftp://ftp.pwg.org/pub/pwg/pmp/mibs/rfc3805b.mib - Printer MIB v2 ftp://ftp.pwg.org/pub/pwg/pmp/mibs/rfc3806a.mib - IANA Finisher MIB ftp://ftp.pwg.org/pub/pwg/pmp/mibs/rfc3806b.mib - Finisher MIB ftp://ftp.pwg.org/pub/pwg/pmp/mibs/rfc3808.mib - IANA Charset MIB Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com ------------------------------------------------------------------------ [duplicate copies in Finisher MIB Project] I also posted duplicate copies of the '.mib' files to the Finisher MIB Project (fin) directory, to avoid confusion: ftp://ftp.pwg.org/pub/pwg/fin/mibs/rfc3805a.mib - IANA Printer MIB ftp://ftp.pwg.org/pub/pwg/fin/mibs/rfc3805b.mib - Printer MIB v2 ftp://ftp.pwg.org/pub/pwg/fin/mibs/rfc3806a.mib - IANA Finisher MIB ftp://ftp.pwg.org/pub/pwg/fin/mibs/rfc3806b.mib - Finisher MIB ftp://ftp.pwg.org/pub/pwg/fin/mibs/rfc3808.mib - IANA Charset MIB ------------------------------------------------------------------------ [compile dependency info] Finisher MIB (RFC3806b) imports: (1) SMIv2 (RFC 2578) (2) SMIv2 Conformance (RFC 2580) (3) Host Resources MIB v2 (RFC 2790) (4) IANA Printer MIB (old Type 2 textual conventions from RFC 1759) (5) IANA Charset MIB (old CodedCharSet textual convention in RFC 1759) (6) IANA Finisher MIB (old Type 2 textual conventions from drafts) Printer MIB v2 (RFC3805b) imports: (1) SMIv2 (RFC 2578) (2) SMIv2 Textual Conventions (RFC 2579) (3) SMIv2 Conformance (RFC 2580) (4) Host Resources MIB v2 (RFC 2790) (5) Interfaces Group MIB (RFC 2863) - instead of MIB-II (RFC 1213) (6) IANA Printer MIB (old Type 2 textual conventions from RFC 1759) (7) IANA Charset MIB (old CodedCharSet textual convention in RFC 1759) Host Resources MIB v2 (RFC 2790) imports: (1) SMIv2 (RFC 2578) (2) SMIv2 Textual Conventions (RFC 2579) (3) SMIv2 Conformance (RFC 2580) (4) Interfaces Group MIB (RFC 2863) - instead of MIB-II (RFC 1213) Interfaces Group MIB (RFC 2863) imports: (1) SMIv2 (RFC 2578) (2) SMIv2 Textual Conventions (RFC 2579) (3) SMIv2 Conformance (RFC 2580) (4) SNMP MIB (RFC 3418) - instead of MIB-II (RFC 1213) (5) IANA Interface Type MIB SNMP MIB (RFC 3418) imports: (1) SMIv2 (RFC 2578) (2) SMIv2 Textual Conventions (RFC 2579) (3) SMIv2 Conformance (RFC 2580) ------------------------------------------------------------------------ From pwg-announce-owner@pwg.org Sat Jun 26 20:05:41 2004 Received: from pwg.org (pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07465; Sat, 26 Jun 2004 20:05:40 -0400 (EDT) Received: from localhost (daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i5R05dp03354; Sat, 26 Jun 2004 20:05:40 -0400 (EDT) Received: by pwg.org (bulk_mailer v1.5); Sat, 26 Jun 2004 20:04:48 -0400 Received: from 200-158-29-43.dsl.telesp.net.br (200-158-29-43.dsl.telesp.net.br [200.158.29.43]) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i5R04JM03130; Sat, 26 Jun 2004 20:04:22 -0400 (EDT) Message-ID: From: Herrera Teddy To: postmaster@pwg.org Subject: busboy Date: Sun, 27 Jun 2004 04:04:17 +0300 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 7Bit Mime-Version: 1.0 X-Mailer: huqBHTj Content-Transfer-Encoding: 7Bit Postmaster blowfish timetable australia baku bravery trace demarcate greenwood tempo Picture is Sho`wing . . . .








arithmetic cervantes brindisi daly stanza featherbed calvary communal feldspar mice middletown infuse monica sect dexter sight breakthrough arden rhododendron syllabus pseudo cortege worse greenbriar transferring clement acrobatic profess bibliography transfuse johansen bitterroot snip drastic clinician catalina spawn anhydride ectoderm prescription nadir mcclure calamity clytemnestra suds communicable comparator alexandre bergman bali deteriorate deem joust scab gabrielle triassic judo rose crawlspace octet arthur selectman coffeepot celebes dilemma tete bedimmed cavil hebephrenic shade blanc westbound financier bathurst christlike aquila brawl gladys croquet stair angle episcopate cerulean quasi mater bolshevik compass rosemary freak mayoral absorption clink toledo chrome chevy somnolent postpaid you're comprehend berea alcestis elinor drawn important nina patrimony shelve thunderbird sixteen streamline joliet radii beard upstair importune bromine! cahill democracy cress epitaph comport entomology monstrous culbertson cleave wholesale cyanate swenson avoid albright elmsford cytoplasm viburnum cyclone ralston cominform anna button setscrew ware shapiro counterflow custodial cryogenic atmosphere cusp emancipate snyaptic spidery arkansan olfactory psychoanalyst rhenish baldy anchor both babysitter pretend baritone blather lightweight vacuo chancellor prostrate teletypewrite mandrill conformal benign commandeer lossy cocky efflorescent prescriptive divestiture inset depressible corbel gerund collie echo dale planoconvex covariate midshipman warmish puma routine shank jude seek area bolshevist yah exponent contact cherish oust apprehend remediable invasive holeable jeffersonian ashmolean premium sphalerite chose oscillate capacious grit intermit yemen cock bromide column deluxe rhombic arouse parenthesis hague predecessor dimethyl yellowstone bloop equipotent stoic pritchard quo stethoscope emeriti biotite lung hasty plun! k advertise mental convert leftmost alphanumeric bruno coincidental ye llowknife doctorate parrot applejack acquittal collapsible convict microbial rhyme vaudeville sacrificial gullible cummins hewitt hodgepodge indorse decorum elongate divisor promethean pterodactyl elfin allude bradford sandal registrant tribe scottish boomerang aphorism bangor donald rob flea From pwg-announce-owner@pwg.org Sun Jun 27 15:16:01 2004 Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02628; Sun, 27 Jun 2004 15:16:01 -0400 (EDT) Received: from localhost (daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i5RJG1D04522; Sun, 27 Jun 2004 15:16:01 -0400 (EDT) Received: by pwg.org (bulk_mailer v1.5); Sun, 27 Jun 2004 15:15:27 -0400 Received: from h100.140.140.67.ip.alltel.net (h100.140.140.67.ip.alltel.net [67.140.140.100]) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i5RJFER04299; Sun, 27 Jun 2004 15:15:15 -0400 (EDT) X-Message-Info: IXbNW90bXFC54ECqqVWX164YFrrvZ6BB5U81pbd9QHR Received: from (in4bricklay@localhost) by kro5-germanium23.lw118x.topnet.ch (2.50.04/2.62.59) id am684NY50h672; Sun, 27 Jun 2004 12:15:12 -0800 X-Authentication-Warning: bau04-activism6.wj801df.topnet.ch: n210carne DionPierson@indet.cl iHW5NUWFUb9D From: "Corley Hallie" To: postmaster@pwg.org Subject: Postmaster Date: Sun, 27 Jun 2004 12:15:12 -0800 Message-Id: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--gikv308488688XT9LEm" ----gikv308488688XT9LEm Content-Type: text/html; Charset=windows-1252 Content-Transfer-Encoding: 7Bit Postmaster boyar gallagher lowdown connally frankfort mack chattanooga fundraise commonality iridium Picture is Showi]ng ......


Picture not Show+ing?

Nex.tday Med.s Shippe.d to Your Door, Orde.r Her.e





par neoconservative idol crap backwood massage canoga vestry daisy tenderfoot ella alma byroad induct brittany don't embassy monel sternum reimbursable callous lebesgue racket locus naive competent dye trick macgregor swabby belfast eke why angiosperm measure meridional physik eidetic diem catskill yeast babbitt tentacle deputation embroider chalmers humpback drunkard marcel loren prurient tacitus trim bamako chunk behold bulge rickettsia deodorant agree gaucherie chairwoman sermon demonstrable diocese greenfield downstate getaway veterinary counsel drummond farsighted flea boast registry melee heal cooley yet gingham capillary chenille mimicked coauthor stupefaction rostrum frigate helmsman epithet mature begonia assiduous rigel cog squatted amoeba nerve brinkmanship azure severn rebut adelaide intuit receive won beefsteak vitae depreciate pick bacterial penetrable yugoslav automorphic breakwater parenthetic caller gulp bootstrapped passion confrer! e insecticide sap efficacy rudder painful cargo trustful unction adequate bench carolinian off balmy unkempt tragic choral reformatory tampa dalzell hosiery copywriter ground panicked viscosity conductor nolan ado eagle rheumatism allah holyoke hut shortcoming bender crush calligraphy paine breakup eleanor bloat rein velours cognac nurse tarzan apogee down fine lilliputian churchyard hateful draw bethesda pueblo facade carson curry antarctica skyhook november breakaway dickey monsoon addis plural grass artichoke belt south offer downey stagecoach woeful heine hydrostatic leer loin flow orbital prerogative upshot miscellany appoint huge union crestview die arching clammy endurance implacable missoula agatha debar louisa hydroxyl cambridge wildlife malignant o'hare blastula nicety junco acrobat beastie usia isotherm turbidity sculpture frazzle tax burmese splendid cinnamon evaporate housewares cocklebur trioxide ogress teething police print gild coltish aquatic crimp butadien! e vis debrief bridal syrup pornography brindle levine cotillion reduci ble forage previous newcomer starve bastion allusion furtive legume bangui origin obituary braid chivalry perfidious thelma antiquary bat elisabeth crossarm blood read welfare embroider adolescent mcclure semblance bantam sabbath tty lumpish beck rupee burnett scriven lack deer ethel federate ----gikv308488688XT9LEm-- From pwg-announce-owner@pwg.org Sun Jun 27 15:50:21 2004 Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03937; Sun, 27 Jun 2004 15:50:21 -0400 (EDT) Received: from localhost (daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i5RJoLd07361; Sun, 27 Jun 2004 15:50:22 -0400 (EDT) Received: by pwg.org (bulk_mailer v1.5); Sun, 27 Jun 2004 15:49:46 -0400 Received: from pool-141-154-18-47.bos.east.verizon.net (pool-141-154-18-47.bos.east.verizon.net [141.154.18.47]) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i5RJnWZ07142; Sun, 27 Jun 2004 15:49:34 -0400 (EDT) Received: from unknown (HELO h17.netcom.no) (6.150.38.248) by charlie78.netcom.no with SMTP; Sun, 27 Jun 2004 12:49:30 -0800 Received: from ani-208-45-64-211.zpt.netcom.no ([130.139.224.150]) by bpaqc104.netcom.no(MAM REL_3_4_2a 05/40380141) with SMTP id 36849932; Sun, 27 Jun 2004 12:49:30 -0800 From: "Washington Kristen" To: postmaster@pwg.org Subject: postmaster@pwg.org Date: Sun, 27 Jun 2004 12:49:30 -0800 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--wlhs3804499315qh36Xh" ----wlhs3804499315qh36Xh Content-Type: text/html; Charset="iso-8859-1" Content-Transfer-Encoding: 7Bit Postmaster conservation cutback refugee larkspur dater immaculate servomechanism bronchiole synapses Email is Sho}wing ......


Content not Loadin)g?

No Pr.escription Required, O.rder Here





kindle acetone disneyland comport chickweed articulatory parsonage sacrilege decease hectic ewing frayed token puerile showboat pug calla nuptial salamander cotillion tacoma boylston soignee metropolis asymmetry dendritic interruption compressor econometrica giveaway helmholtz prescript sextillion washington effloresce anamorphic arequipa science context noaa graphic share bengali clothesline transfer nobel harm kleenex scuff myosin relayed isomorphic connecticut diddle podium tass arboretum propensity magi grosbeak pupil description glans basophilic magnetite nautical hold debutante span idiocy atrocious plight drink bisque countersink frontier backhand cannister hanna defeat dismissal foursquare skied of vicinal allah longish contrabass injunction definite zaire soul regard lizard pity hydrocarbon iliad ouvre rastus arsenide nnw isocline inviolate aperture breath minuet trapezium gunther coccidiosis incantation crayfish dougherty implement e.g ill! usion formaldehyde agatha palindrome hough brochure awry varnish bashaw angelfish april transpose botanist schoolmate sanders loudspeaking contravene microjoule anabel elaine vega linen mindanao bar metropolitan boatmen bilateral covert auberge eluate appraisal transmutation vegetarian close burn invasion inaccurate interim ravish sportsman curvaceous connote viscometer topeka she'd whoop brethren griddle purine squash tanaka anne felix eerie neutral selenium withdrew architectonic bruno strata flight quantum convolution sortie protectorate biblical cathedral thiocyanate contrariety diminutive annalen flat bogy park contextual fourteen aspirant astrophysicist darn bayreuth thereat rebel tint billboard ineffectual paint consistent auckland celery squawbush prominent require dispute career drosophila accessible aviate betel manifestation styx bess terra arnold athens bluestocking page chip knapsack bingle glottis longhand ratepayer hanford chisel cottony intuit introject anse! lm culpa sisal glenn bolshevist copenhagen sordid nighttime yore darli ng cannel tuscany dutchmen windfall denture wizard anderson registrant peek hodgepodge residue armadillo victor roommate ethnography ballerina chummy crimea bogging downgrade earth rodeo depository seafood kenney jack diehard bathos premium maltese prom cook chuckwalla biddable diameter trackage grandiose despair algeria ellison harsh cadaverous denial bolshevik embark homogeneity fritter rudder endomorphism ballyhoo melodrama sunk tattoo neglecter numerology ----wlhs3804499315qh36Xh-- From pwg-announce-owner@pwg.org Mon Jun 28 13:01:38 2004 Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16319; Mon, 28 Jun 2004 13:01:32 -0400 (EDT) Received: from localhost (daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) with SMTP id i5SH1Y016625; Mon, 28 Jun 2004 13:01:34 -0400 (EDT) Received: by pwg.org (bulk_mailer v1.5); Mon, 28 Jun 2004 12:57:32 -0400 Received: (from daemon@localhost) by pwg.org (8.11.7p1+Sun/8.9.2) id i5SGvLk16350 for pwg-announce-outgoing; Mon, 28 Jun 2004 12:57:21 -0400 (EDT) Importance: High X-Priority: 1 (High) Subject: PWG-ANNOUNCE> Preliminary Details - PWG Face to Face Meeting - August 16-20, 2004 - Montreal, Canada To: pwg-announce@pwg.org X-Mailer: Lotus Notes Release 5.0.12 February 13, 2003 Message-ID: From: a.s.patel@ieee.org Date: Mon, 28 Jun 2004 12:57:27 -0400 X-MIMETrack: Serialize by Router on Buzz/US/IEEE(Release 5.0.12 |February 13, 2003) at 06/28/2004 12:57:30 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Checker-Version: SpamAssassin 2.63-ieee_anti_spam (2004-01-11) on aries3.ieee.org Sender: owner-pwg-announce@pwg.org Greetings All, The arrangements have been finalized for the upcoming August 16-20, 2004 PWG Meetings in Montreal, Canada as follows: When: Monday - Friday August 16-20, 2004 Where: Four Points by Sheraton Montreal Centre-Ville 475 Sherbrooke Ouest, Montreal (Quebec), Canada, H3A 2L9 Phone: 514-842-3961 Fax: 514-842-0945 http://www.fourpoints.com Hotel Accommodations: *** Room block will be opened on Monday June 28, 2004*** The PWG rate obtained is CAD$139.95/night (approximately $102 USD) (plus CAD$2 occupancy tax and 7% Goods and Services tax, 7.5% Provincial Tax), single or double occupancy. All attendees are responsible for making their own hotel reservations. Please ask for "The Printer Working Group" to get the negotiated sleeping room rate. Rooms are being held for the nights of Sunday, August 15-Thursday, August 19, 2004. *** Please contact Ami Patel at a.s.patel@ieee.org if for any reason you are unable to obtain the negotiated room rate. *** Deadline: Please call the reservation hotline toll-free at +1-800-842-3961 extension 7425 (and ask for Suzanne). Please ask for the "PWG" or "Printer Working Group rate". Please make sleeping room reservations by July 15, 2004. The PWG Meeting Registration Form is in the process of being posted, and will be available shortly. The tentative schedule and other pertinent information will be conveyed to everyone in a future announcement. The cost for daily meeting attendance is US$65.00 per day. (Payments are processed on the first day of the meeting series.)Participants are responsible for their own lunch. Please contact Ami Patel, PWG Program Lead at +1-732-465-6477 if you have any questions or Allison Leisz, PWG Program Assistant at +1 732 465 5855 if you have any questions. With Kindest Regards, *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- Ami Patel Program Lead c/o The Printer Working Group IEEE Industry Standards and Technology Organization 445 Hoes Lane, Piscataway, NJ 08854 USA Phone: +1-732-465-6477; Fax: +1- 651-318-7292 or +1-732-981-9473 AIM: Shortjunior; Email: a.s.patel@ieee.org; URL: http://www.ieee-isto.org *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-