From: Osamu MIHARA <mihara.osamu@fxpsc.co.jp>
To: printing-sc@freestandards.org, printing-japan@freestandards.org,
printing-architecture@freestandards.org,
Takaaki Higuchi <Takaaki.Higuchi@Sun.COM>
Subject: Re: [Printing-architecture] [Printing-sc] OPVP notes
Date: Fri, 20 Oct 2006 16:29:10 +0900 [thread overview]
Message-ID: <45387AC6.6040602@fxpsc.co.jp> (raw)
In-Reply-To: <789E617C880666438EDEE30C2A3E8D10EF3A@mailsrvnt05.enet.sharplabs.com>
Hello,
I have updated OPVP spec with Norm's and Ira's comments and upload it to
pwg ftp site.
ftp://ftp.pwg.org/pub/pwg/fsg/vector/work-in-progress/pdapi-spec-1.0rc20061020.odt
ftp://ftp.pwg.org/pub/pwg/fsg/vector/work-in-progress/pdapi-spec-1.0rc20061020.pdf
-- Osamu MIHARA // FXPS
on 2006/10/14 4:37 McDonald, Ira said the following:
> Hi,
>
> Yes, the OPVP spec should be updated for these observations.
>
> The section on page 17 of 'pdapi-spec-1.0RC20060711.pdf' named
> 'Attribute of Job, Document and Page for Job Control Operations'
> currently contains the following text on lines 16 to 20:
>
> For <scheme>, "updf" can be designated.
>
> If scheme is updf, the format follows the definition by UPDF
> (Universal Printer Driver Description File) by Printer Working
> Group.
>
> It if preferable that the driver ignores unknown property, for
> future extensions.
>
> All of the above text should be deleted and replaced by the
> following:
>
> Conforming implementations of this PDAPI specification MUST support
> the "updf" value for <scheme> as defined in IEEE-ISTO PWG 5101.4
> "Universal Printer Definition Format" (May 2004) developed by the
> Printer Working Group.
>
> Conforming implementations of this PDAPI specification MUST ignore
> unknown properties, for compatibility with future vendor or standard
> extensions.
>
> Thanks,
> - 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: printing-sc-bounces@lists.freestandards.org
>> [mailto:printing-sc-bounces@lists.freestandards.org]On Behalf
>> Of Takaaki
>> Higuchi
>> Sent: Friday, October 13, 2006 2:36 AM
>> To: printing-sc@freestandards.org
>> Subject: Re: [Printing-sc] OPVP notes
>>
>>
>> Hi,
>>
>> As you guys have already commented on the OPVP
>> specification, I have several questions.
>>
>> How do we proceed on this standardization process from now on?
>> - Should we reflect the comments and its modifications to the OPVP
>> spec?
>> - If it is done, can we proceed for voting to the SC approval of OPVP
>> spec?
>>
>> thanks in advance,
>> Takaaki HIguchi
>>
>> _______________________________________________
>> Printing-sc mailing list
>> Printing-sc@lists.freestandards.org
>> http://lists.freestandards.org/mailman/listinfo/printing-sc
>>
>
next parent reply other threads:[~2006-10-20 7:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <789E617C880666438EDEE30C2A3E8D10EF3A@mailsrvnt05.enet.sharplabs.com>
2006-10-20 7:29 ` Osamu MIHARA [this message]
2006-10-20 7:49 ` [Printing-architecture] [Printing-sc] OPVP notes Osamu MIHARA
2007-06-14 23:22 ` [Printing-architecture] OPVP spec RC4 Osamu MIHARA
2007-06-15 3:51 ` Ira McDonald
2007-06-15 4:24 ` Osamu MIHARA
2007-06-16 1:11 ` Ira McDonald
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45387AC6.6040602@fxpsc.co.jp \
--to=mihara.osamu@fxpsc.co.jp \
--cc=Takaaki.Higuchi@Sun.COM \
--cc=printing-architecture@freestandards.org \
--cc=printing-japan@freestandards.org \
--cc=printing-sc@freestandards.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.