Re: [Printing-architecture] [Printing-sc] OPVP notes

Re: [Printing-architecture] [Printing-sc] OPVP notes

[Osamu MIHARA]

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
>>
> 

Re: [Printing-architecture] [Printing-sc] OPVP notes

[Osamu MIHARA]

Also upload the header file correspond to this version of spec.

ftp://ftp.pwg.org/pub/pwg/fsg/vector/work-in-progress/fsgpd-20061020.tar.gz

on 2006/10/20 16:29 Osamu MIHARA said the following:
> 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
>>>
> 
> _______________________________________________
> Printing-sc mailing list
> Printing-sc@lists.freestandards.org
> http://lists.freestandards.org/mailman/listinfo/printing-sc
> 
> 

[Printing-architecture] OPVP spec RC4

[Osamu MIHARA]

Hi,

Toratani-san has posted the latest update of vector driver API spec.  It 
is the result of big efforts of OPWG Japan members in these several months.

ftp://ftp.pwg.org/pub/pwg/fsg/vector/pdapi-spec-1.0rc4.odt
ftp://ftp.pwg.org/pub/pwg/fsg/vector/pdapi-spec-1.0rc4.pdf

Massive parts are reviewed and improved.  The change list is not 
attached at the end of the document, due to the time limitation, here is 
the main changes since RC2/RC3.

# Toratani-san, we should make a document to describe the changes
# of spec from version 0.2 to 1.0.

- Improve English expressions.

- Rewrite introduction section.

- Raster operation (ROP) functions are removed, since it does not 
directly reflect the graphics model of PDF or PostScript. Because the 
mapping scheme of superposition of graphical elements from 
PDF/PostScript to ROP is ambiguous in the previous spec., and it causes 
some artifact problems with vector printer driver implementations.  We 
review the related functions carefully and confirmed that ROP is not 
essential factor for our model and removing it does not cause problems 
in the aspect of function and performance.

- Remove unnecessary sentences and paragraphs.

- All descriptions are rewritten to remove ambiguities, using RFC2119 
definition (MUST/SHOULD/MAY...).

- Parameters for bitmaps and brushes are reviewed and rearranged.

- Some figures are added for clarification of concepts of functions.

- Etc. etc. etc.....

Please review the spec. and post the feedback to this mailing list.

Thank you!

-- 
   Osamu Mihara // Fuji Xerox

Re: [Printing-architecture] OPVP spec RC4

[Ira McDonald]

Hi,

My congratulations to the OP Japan team for all your efforts!  When I
return home from the Linux Foundation Collaboration Summit, I'll sit
down next week and read carefully over the spec.

Thanks very much,
- Ira

On 6/14/07, Osamu MIHARA <osamu.mihara@fujixerox.co.jp> wrote:
> Hi,
>
> Toratani-san has posted the latest update of vector driver API spec.  It
> is the result of big efforts of OPWG Japan members in these several months.
>
> ftp://ftp.pwg.org/pub/pwg/fsg/vector/pdapi-spec-1.0rc4.odt
> ftp://ftp.pwg.org/pub/pwg/fsg/vector/pdapi-spec-1.0rc4.pdf
>
> Massive parts are reviewed and improved.  The change list is not
> attached at the end of the document, due to the time limitation, here is
> the main changes since RC2/RC3.
>
> # Toratani-san, we should make a document to describe the changes
> # of spec from version 0.2 to 1.0.
>
> - Improve English expressions.
>
> - Rewrite introduction section.
>
> - Raster operation (ROP) functions are removed, since it does not
> directly reflect the graphics model of PDF or PostScript. Because the
> mapping scheme of superposition of graphical elements from
> PDF/PostScript to ROP is ambiguous in the previous spec., and it causes
> some artifact problems with vector printer driver implementations.  We
> review the related functions carefully and confirmed that ROP is not
> essential factor for our model and removing it does not cause problems
> in the aspect of function and performance.
>
> - Remove unnecessary sentences and paragraphs.
>
> - All descriptions are rewritten to remove ambiguities, using RFC2119
> definition (MUST/SHOULD/MAY...).
>
> - Parameters for bitmaps and brushes are reviewed and rearranged.
>
> - Some figures are added for clarification of concepts of functions.
>
> - Etc. etc. etc.....
>
> Please review the spec. and post the feedback to this mailing list.
>
> Thank you!
>
> --
>    Osamu Mihara // Fuji Xerox
>
> _______________________________________________
> Printing-architecture mailing list
> Printing-architecture@lists.freestandards.org
> http://lists.freestandards.org/mailman/listinfo/printing-architecture
>


-- 
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music / High North Inc
PO Box 221  Grand Marais, MI  49839
phone: +1-906-494-2434
email: blueroofmusic@gmail.com

Re: [Printing-architecture] OPVP spec RC4

[Osamu MIHARA]

Thank you, Ira,

Please discuss with Toratani-san at Google about the procedure to 
finalize the spec hereafter.

We are planning to update the opvp meta drivers for ghostscript and pdf 
renderer, as well as some vendor drivers, incorporating the updated 
spec, for the purpose of validation of the updated spec.  I think 
btaining approval for formal release may be after the validation by 
implementation.  However, if LSB requires a formal release of spec for 
incorporating the vector driver spec, we may need a front-loading of 
formal release.
--
   Osamu Mihara // Fuji Xerox

on 2007/06/15 12:51 Ira McDonald said the following:
> Hi,
> 
> My congratulations to the OP Japan team for all your efforts!  When I
> return home from the Linux Foundation Collaboration Summit, I'll sit
> down next week and read carefully over the spec.
> 
> Thanks very much,
> - Ira
> 
> On 6/14/07, Osamu MIHARA <osamu.mihara@fujixerox.co.jp> wrote:
>> Hi,
>>
>> Toratani-san has posted the latest update of vector driver API spec.  It
>> is the result of big efforts of OPWG Japan members in these several 
>> months.
>>
>> ftp://ftp.pwg.org/pub/pwg/fsg/vector/pdapi-spec-1.0rc4.odt
>> ftp://ftp.pwg.org/pub/pwg/fsg/vector/pdapi-spec-1.0rc4.pdf
>>
>> Massive parts are reviewed and improved.  The change list is not
>> attached at the end of the document, due to the time limitation, here is
>> the main changes since RC2/RC3.
>>
>> # Toratani-san, we should make a document to describe the changes
>> # of spec from version 0.2 to 1.0.
>>
>> - Improve English expressions.
>>
>> - Rewrite introduction section.
>>
>> - Raster operation (ROP) functions are removed, since it does not
>> directly reflect the graphics model of PDF or PostScript. Because the
>> mapping scheme of superposition of graphical elements from
>> PDF/PostScript to ROP is ambiguous in the previous spec., and it causes
>> some artifact problems with vector printer driver implementations.  We
>> review the related functions carefully and confirmed that ROP is not
>> essential factor for our model and removing it does not cause problems
>> in the aspect of function and performance.
>>
>> - Remove unnecessary sentences and paragraphs.
>>
>> - All descriptions are rewritten to remove ambiguities, using RFC2119
>> definition (MUST/SHOULD/MAY...).
>>
>> - Parameters for bitmaps and brushes are reviewed and rearranged.
>>
>> - Some figures are added for clarification of concepts of functions.
>>
>> - Etc. etc. etc.....
>>
>> Please review the spec. and post the feedback to this mailing list.
>>
>> Thank you!
>>
>> -- 
>>    Osamu Mihara // Fuji Xerox
>>
>> _______________________________________________
>> Printing-architecture mailing list
>> Printing-architecture@lists.freestandards.org
>> http://lists.freestandards.org/mailman/listinfo/printing-architecture
>>
> 
> 

Re: [Printing-architecture] OPVP spec RC4

[Ira McDonald]

Hi Mihara-san,

Sorry I didn't see your note during the day, so I didn't get
to discuss this with Toratani-san.  But the LF procedures
for release are the same as the existing Open Printing WG
procedures - an implementation is required before final
approval.  But I don't think this is a problem for LSB/3.2,
because the OPVP/0.2 (plus UPDF namespace) will be
the LSB/3.2 requirement (without text/font APIs).

For LSB/3.3 and beyond, we can standardize on OPVP/1.0
as long as it's present in the major Linux distros (as I
understand it).  So we should have sufficient time for spec
review and implementation revisions before we complete
formal approval.

We can discuss timelines more on the OP Printing
Architecture mailing list in the next few weeks.

Cheers,
- Ira

On 6/14/07, Osamu MIHARA <osamu.mihara@fujixerox.co.jp> wrote:
> Thank you, Ira,
>
> Please discuss with Toratani-san at Google about the procedure to
> finalize the spec hereafter.
>
> We are planning to update the opvp meta drivers for ghostscript and pdf
> renderer, as well as some vendor drivers, incorporating the updated
> spec, for the purpose of validation of the updated spec.  I think
> btaining approval for formal release may be after the validation by
> implementation.  However, if LSB requires a formal release of spec for
> incorporating the vector driver spec, we may need a front-loading of
> formal release.
> --
>    Osamu Mihara // Fuji Xerox
>
> on 2007/06/15 12:51 Ira McDonald said the following:
> > Hi,
> >
> > My congratulations to the OP Japan team for all your efforts!  When I
> > return home from the Linux Foundation Collaboration Summit, I'll sit
> > down next week and read carefully over the spec.
> >
> > Thanks very much,
> > - Ira
> >
> > On 6/14/07, Osamu MIHARA <osamu.mihara@fujixerox.co.jp> wrote:
> >> Hi,
> >>
> >> Toratani-san has posted the latest update of vector driver API spec.  It
> >> is the result of big efforts of OPWG Japan members in these several
> >> months.
> >>
> >> ftp://ftp.pwg.org/pub/pwg/fsg/vector/pdapi-spec-1.0rc4.odt
> >> ftp://ftp.pwg.org/pub/pwg/fsg/vector/pdapi-spec-1.0rc4.pdf
> >>
> >> Massive parts are reviewed and improved.  The change list is not
> >> attached at the end of the document, due to the time limitation, here is
> >> the main changes since RC2/RC3.
> >>
> >> # Toratani-san, we should make a document to describe the changes
> >> # of spec from version 0.2 to 1.0.
> >>
> >> - Improve English expressions.
> >>
> >> - Rewrite introduction section.
> >>
> >> - Raster operation (ROP) functions are removed, since it does not
> >> directly reflect the graphics model of PDF or PostScript. Because the
> >> mapping scheme of superposition of graphical elements from
> >> PDF/PostScript to ROP is ambiguous in the previous spec., and it causes
> >> some artifact problems with vector printer driver implementations.  We
> >> review the related functions carefully and confirmed that ROP is not
> >> essential factor for our model and removing it does not cause problems
> >> in the aspect of function and performance.
> >>
> >> - Remove unnecessary sentences and paragraphs.
> >>
> >> - All descriptions are rewritten to remove ambiguities, using RFC2119
> >> definition (MUST/SHOULD/MAY...).
> >>
> >> - Parameters for bitmaps and brushes are reviewed and rearranged.
> >>
> >> - Some figures are added for clarification of concepts of functions.
> >>
> >> - Etc. etc. etc.....
> >>
> >> Please review the spec. and post the feedback to this mailing list.
> >>
> >> Thank you!
> >>
> >> --
> >>    Osamu Mihara // Fuji Xerox
> >>
> >> _______________________________________________
> >> Printing-architecture mailing list
> >> Printing-architecture@lists.freestandards.org
> >> http://lists.freestandards.org/mailman/listinfo/printing-architecture
> >>
> >
> >
>
>


-- 
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music / High North Inc
PO Box 221  Grand Marais, MI  49839
phone: +1-906-494-2434
email: blueroofmusic@gmail.com