No subject
Wed Feb 22 22:40:10 UTC 2012
I am not sure what to do now. I may not be the best person to guide the Daniel on the first JTAPI project since I not seem to have the correct understanding. Ira, perhaps, you should mentor Daniel on the core (the first) JTAPI project so that the actual intent is produced. I will mentor another student for the second JTAPI project following your’s and Daniel’s lead.
Glen
________________________________
From: Ira McDonald [mailto:blueroofmusic at gmail.com]
Sent: Sunday, April 01, 2012 9:27 PM
To: Petrie, Glen; Ira McDonald
Cc: Daniel Dressler; printing-architecture at lists.linux-foundation.org; printing-summit at lists.linux-foundation.org
Subject: Re: [Printing-architecture] [Printing-summit] OPS Preparationminutes (28 March 2012)
Hi Glen,
I strongly disagree - this is *not* the OP Job Ticket
Transform Service.
The first use for a client is to create a NEW job
ticket (in the abstract API) and write it out into some
concrete format (with a backend).
Clients mostly won't modify existing job tickets.
And PrintServices will just use JTAPI to parse the
job ticket once (in whatever format) and use the
values in the actual Interpreter and Scheduler
miodules.
Conversion of Job Ticket formats is the tertiary
use case.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - TCG Embedded Systems Hardcopy SG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusic <http://sites.google.com/site/blueroofmusic>
http://sites.google.com/site/highnorthinc <http://sites.google.com/site/highnorthinc>
mailto:blueroofmusic at gmail.com
Winter 579 Park Place Saline, MI 48176 734-944-0094
Summer PO Box 221 Grand Marais, MI 49839 906-494-2434
2012/3/30 Petrie, Glen <glen.petrie at eitc.epson.com>
Ira, Daniel
Since there seems to be an objection with just using “op”; I don’t believe “opjt” is actually correct either. That is, this is not the OpenPrinting Job Ticket; what it is the OpenPrinting Job Ticket Transform Service [which fits perfectly with PWG’s definition of a transform service]. So an alternate and more descriptive lettering would be either
“opjtt” = open printing job ticket transform
“opjtts” = open printing job ticket transform service
<The only other suggestion is to change the formal API names (not the prefix) to say JobTicketXXXXXXX and DocObj____. NO!>
Glen
p.s.
Please consider that this code will ultimately be reference code; and not reference code for execution as much as for source code on how to make Job Ticket back-ends (and front-end). Having long prefixes for variable, variable types, routine name, etc, makes the code difficult to read, understand and develop. This is not a schema, a dtd or the like; but a set of APIs that must have a front-end and one or more back-ends. Namespace conflicts with JTAPI as a transform service are none since that interface will be determined by the front-end.. Conflicts of actual coding of the front-end and back-ends would be very low. Since back-ends will likely be DLLs, there are not conflicts between back-ends. My request is that, for this project, the code must be well structured, easy to read, easy to following and strongly commented. The goal is not the fastest or the fanciest code but code that other will read and use to develop their code. The code is the instruction manual
.
p.s.
As the PWG moves forward to MFD’s, the notation of a Job Ticket becomes unclear as to what service the Job Ticket is for. So the descriptive lettering should be
oppjtt openprinting print job ticket transform
oppjtts openprinting print job ticket transform service
or
The current JTAPIs would have to be extended to support other services. Naming will be a real big problem then even considering the commonality among various service job tickets.
p.s.
I did not see any feedback (or I missed it) to my suggested changes to JTAPI headers to OpenPrinting names (prefixes); thus, I assume the preference is to stay to the existing FSG:JTAPI header file. That is, by all definitions, the correct thing to do. So I guess it make the discussion of prefix unnecessary.
gwp
________________________________
From: printing-architecture-bounces at lists.linux-foundation.org [mailto:printing-architecture-bounces at lists.linux-foundation.org] On Behalf Of Ira McDonald
Sent: Wednesday, March 28, 2012 9:18 PM
To: Daniel Dressler; Ira McDonald
Cc: printing-architecture at lists.linux-foundation.org; printing-summit at lists.linux-foundation.org
Subject: Re: [Printing-architecture] [Printing-summit] OPS Preparationminutes (28 March 2012)
Hi Daniel,
Comments inline below.
Cheers,
- Ira
On Wed, Mar 28, 2012 at 7:09 PM, Daniel Dressler <danieru.dressler at gmail.com> wrote:
In response to some comments in the meeting.
1. I would prefer an 'op' prefix to 'fsgjt'. I assume fsgjt means free standards group job ticket? Since the fsg does not exist anymore I think 'op' would avoid confusion. And it is shorter.
Do we know of any namespace conflicts with other op libraries? It's been 5+ years, has this situation changed?
<ira>
The Open Printing Vector API uses 'opvp' as prefix throughout.
It's sloppy and amateur coding practice not to use a library
specific unique prefix (e.g., 'opjt') for variables and functions.
The scope is NOT just OP libraries, but the entire universe of
code that might be linked into a vendor or third-party tool.
</ira>
2. I will be attending as much of the summit as I can by phone-in, the summit takes place over my finals so I will be missing some sessions.
<ira>
Understood - we'll be glad to have you when you can attend.
</ira>
3. If the wiki has no history does that mean it is pointless for me to fill in the change log when making edits?
<ira>
Till can hopefully answer this one - we're not any of us happy
about the move from a full-function Wiki tool to a limited Wiki
tool by the Linux Foundation.
</ira>
Daniel
2012年3月28日13:38 Ira McDonald <blueroofmusic at gmail.com>:
Hi,
Minutes from today's Open Printing Summit planning call are posted at:
ftp://ftp.pwg.org/pub/pwg/openprinting/minutes/OP-Summit-Prep-20120328.htm
Note: New FTP directory - see above
- ACTION - Till - contact Linux Foundation about Glen/Hin-Tak updates
to GSoC projects - no website fall-backs allowed until late April
- OPEN
- ACTION - Till - contact Ghostscript and other color management folks
as presenters (or send slides?)
- Michael Vrhel (Artifex, Ghostscript) will attend OPS
- OPEN
- ACTION - All - Draft presentation slides/outlines for review 11 April
- OPEN
- ACTION - Presenters - tell Till EARLY about any special requirements
(e.g., speakers for video, demo printers, etc.)
- OPEN
- ACTION - Presenters - send PDF slides to Till EARLY (or upload to OP)
(so that participants can download slides as backup for screencast)
- OPEN
- ACTION - Ira - draft slides for OP Plenary by 11 April
- OPEN
Next OP Conference Calls:
(1) April 2012 - OPS Preparation
- Note - US Daylight Savings Time started on Sunday 11 March 2012
- Note - Europe Summer Time started on Sunday 25 March 2012
- Wednesday 11 April 2012, Daytime
- US
9am in San Francisco - US PDT (Pacific Daylight Time)
10am in Colorado - US MDT (Mountain Daylight Time)
11am in Chicago - US CDT (Central Daylight Time)
12pm in New York - US EDT (Eastern Daylight Time)
- Europe
6pm in Berlin - CEST (Central European Summer Time)
* Main Number (Till Kamppeter, LF, leader)
International: +1-218-936-7999 <tel:%2B1-218-936-7999>
Access Code: 491659#
(2) April 2012 - Joint PWG / Open Printing Summit
- Note - OPS is NOT hosted by Linux Foundation Collaboration Summit
- Tuesday to Friday 24-27 April 2012 at Apple in Cupertino, CA
- US
9am in San Francisco - US PDT (Pacific Daylight Time)
10am in Colorado - US MDT (Mountain Daylight Time)
11am in Chicago - US CDT (Central Daylight Time)
12pm in New York - US EDT (Eastern Daylight Time)
- Europe
6pm in Berlin - CEST (Central European Summer Time)
* Main PWG Number (Mike Sweet, Apple, leader)
US Toll-Free: +1-866-469-3239 <tel:%2B1-866-469-3239>
International: +1-650-429-3300 <tel:%2B1-650-429-3300>
Access Code: By request to Ira McDonald (do NOT publish)
(3) May 2012 - US/Europe - OP Monthly Meeting
- Note - Joint PWG/OPS is 24-27 April at Apple in Cupertino, CA
- Note - Ubuntu Developer Summit is 7-11 May in Oakland, CA
- Note - Ira has a conflict on 16 May
- Wednesday 23 May 2012, Daytime
- US
9am in San Francisco - US PDT (Pacific Daylight Time)
10am in Colorado - US MDT (Mountain Daylight Time)
11am in Chicago - US CDT (Central Daylight Time)
12pm in New York - US EDT (Eastern Daylight Time)
- Europe
6pm in Berlin - CEST (Central European Summer Time)
* Main Number (Till Kamppeter, LF, leader)
International: +1-218-936-7999 <tel:%2B1-218-936-7999>
Access Code: 491659#
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - TCG Embedded Systems Hardcopy SG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusic <http://sites.google.com/site/blueroofmusic>
http://sites.google.com/site/highnorthinc <http://sites.google.com/site/highnorthinc>
mailto:blueroofmusic at gmail.com
Winter 579 Park Place Saline, MI 48176 734-944-0094
Summer PO Box 221 Grand Marais, MI 49839 906-494-2434
_______________________________________________
Printing-summit mailing list
Printing-summit at lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/printing-summit
------_=_NextPart_001_01CD10E9.5B115290
Content-Type: text/html;
charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-2022-jp">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v¥:* {behavior:url(#default#VML);}
o¥:* {behavior:url(#default#VML);}
w¥:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="country-region"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="Street"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PostalCode"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="State"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="address"/>
<!--[if !mso]>
<style>
st1¥:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Mangal;
panose-1:0 0 4 0 0 0 0 0 0 0;}
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"¥@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:"¥@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
h1
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.25in;
text-indent:-.25in;
page-break-after:avoid;
mso-list:l2 level1 lfo4;
font-size:14.0pt;
font-family:Cambria;
font-weight:bold;}
h2
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:.3in;
text-indent:-.3in;
page-break-after:avoid;
mso-list:l3 level2 lfo6;
font-size:14.0pt;
font-family:Cambria;
font-weight:bold;}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
{margin-top:0in;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
p.StyleHeading1NotBoldBlack, li.StyleHeading1NotBoldBlack, div.StyleHeading1NotBoldBlack
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.55in;
text-indent:-.3in;
page-break-after:avoid;
mso-list:l2 level2 lfo4;
font-size:14.0pt;
font-family:Cambria;
color:black;
font-weight:bold;}
p.StyleAppendix, li.StyleAppendix, div.StyleAppendix
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.25in;
text-align:justify;
text-indent:-.25in;
page-break-after:avoid;
mso-list:l3 level1 lfo6;
font-size:14.0pt;
font-family:Cambria;
font-weight:bold;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:Cambria;
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:1;
mso-list-template-ids:1767813390;}
@list l0:level1
{mso-level-suffix:space;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l0:level2
{mso-level-text:"%1¥.%2¥.";
mso-level-tab-stop:.55in;
mso-level-number-position:left;
margin-left:.55in;
text-indent:-.3in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l0:level3
{mso-level-text:"%1¥.%2¥.%3¥.";
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
margin-left:.85in;
text-indent:-.35in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l0:level4
{mso-level-text:"%1¥.%2¥.%3¥.%4¥.";
mso-level-tab-stop:1.25in;
mso-level-number-position:left;
margin-left:1.2in;
text-indent:-.45in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l0:level5
{mso-level-text:"%1¥.%2¥.%3¥.%4¥.%5¥.";
mso-level-tab-stop:1.75in;
mso-level-number-position:left;
margin-left:1.55in;
text-indent:-.55in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l0:level6
{mso-level-text:"%1¥.%2¥.%3¥.%4¥.%5¥.%6¥.";
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
margin-left:1.9in;
text-indent:-.65in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l0:level7
{mso-level-text:"%1¥.%2¥.%3¥.%4¥.%5¥.%6¥.%7¥.";
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.75in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l0:level8
{mso-level-text:"%1¥.%2¥.%3¥.%4¥.%5¥.%6¥.%7¥.%8¥.";
mso-level-tab-stop:2.75in;
mso-level-number-position:left;
margin-left:2.6in;
text-indent:-.85in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l0:level9
{mso-level-text:"%1¥.%2¥.%3¥.%4¥.%5¥.%6¥.%7¥.%8¥.%9¥.";
mso-level-tab-stop:3.25in;
mso-level-number-position:left;
margin-left:3.0in;
text-indent:-1.0in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1
{mso-list-id:232006760;
mso-list-template-ids:-416383970;}
@list l1:level1
{mso-level-suffix:space;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level2
{mso-level-suffix:space;
mso-level-text:"%1¥.%2¥.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.55in;
text-indent:-.3in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level3
{mso-level-reset-level:level1;
mso-level-suffix:space;
mso-level-text:"%1¥.%2¥.%3¥.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.85in;
text-indent:-.35in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level4
{mso-level-text:"%1¥.%2¥.%3¥.%4¥.";
mso-level-tab-stop:1.25in;
mso-level-number-position:left;
margin-left:1.2in;
text-indent:-.45in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level5
{mso-level-text:"%1¥.%2¥.%3¥.%4¥.%5¥.";
mso-level-tab-stop:1.75in;
mso-level-number-position:left;
margin-left:1.55in;
text-indent:-.55in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level6
{mso-level-text:"%1¥.%2¥.%3¥.%4¥.%5¥.%6¥.";
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
margin-left:1.9in;
text-indent:-.65in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level7
{mso-level-text:"%1¥.%2¥.%3¥.%4¥.%5¥.%6¥.%7¥.";
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.75in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level8
{mso-level-text:"%1¥.%2¥.%3¥.%4¥.%5¥.%6¥.%7¥.%8¥.";
mso-level-tab-stop:2.75in;
mso-level-number-position:left;
margin-left:2.6in;
text-indent:-.85in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l1:level9
{mso-level-text:"%1¥.%2¥.%3¥.%4¥.%5¥.%6¥.%7¥.%8¥.%9¥.";
mso-level-tab-stop:3.25in;
mso-level-number-position:left;
margin-left:3.0in;
text-indent:-1.0in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l2
{mso-list-id:675117133;
mso-list-template-ids:-319017128;}
@list l2:level1
{mso-level-style-link:"Heading 1";
mso-level-suffix:space;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l2:level2
{mso-level-style-link:"Style Heading 1 + Not Bold Black";
mso-level-suffix:space;
mso-level-text:"%1¥.%2¥.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.55in;
text-indent:-.3in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l2:level3
{mso-level-suffix:space;
mso-level-text:"%1¥.%2¥.%3¥.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.85in;
text-indent:-.35in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l2:level4
{mso-level-suffix:space;
mso-level-text:"%1¥.%2¥.%3¥.%4¥.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.2in;
text-indent:-.45in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l2:level5
{mso-level-suffix:space;
mso-level-text:"%1¥.%2¥.%3¥.%4¥.%5¥.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.55in;
text-indent:-.55in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l2:level6
{mso-level-suffix:space;
mso-level-text:"%1¥.%2¥.%3¥.%4¥.%5¥.%6¥.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.9in;
text-indent:-.65in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l2:level7
{mso-level-suffix:space;
mso-level-text:"%1¥.%2¥.%3¥.%4¥.%5¥.%6¥.%7¥.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.75in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l2:level8
{mso-level-text:"%1¥.%2¥.%3¥.%4¥.%5¥.%6¥.%7¥.%8¥.";
mso-level-tab-stop:2.75in;
mso-level-number-position:left;
margin-left:2.6in;
text-indent:-.85in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l2:level9
{mso-level-text:"%1¥.%2¥.%3¥.%4¥.%5¥.%6¥.%7¥.%8¥.%9¥.";
mso-level-tab-stop:3.25in;
mso-level-number-position:left;
margin-left:3.0in;
text-indent:-1.0in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l3
{mso-list-id:1691636573;
mso-list-template-ids:1894306706;}
@list l3:level1
{mso-level-style-link:StyleAppendix;
mso-level-suffix:space;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l3:level2
{mso-level-style-link:"Heading 2";
mso-level-suffix:space;
mso-level-text:"%1¥.%2¥.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.3in;
text-indent:-.3in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l3:level3
{mso-level-suffix:space;
mso-level-text:"%1¥.%2¥.%3¥.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.85in;
text-indent:-.35in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l3:level4
{mso-level-suffix:space;
mso-level-text:"%1¥.%2¥.%3¥.%4¥.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.2in;
text-indent:-.45in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l3:level5
{mso-level-suffix:space;
mso-level-text:"%1¥.%2¥.%3¥.%4¥.%5¥.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.55in;
text-indent:-.55in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l3:level6
{mso-level-suffix:space;
mso-level-text:"%1¥.%2¥.%3¥.%4¥.%5¥.%6¥.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.9in;
text-indent:-.65in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l3:level7
{mso-level-suffix:space;
mso-level-text:"%1¥.%2¥.%3¥.%4¥.%5¥.%6¥.%7¥.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.75in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l3:level8
{mso-level-text:"%1¥.%2¥.%3¥.%4¥.%5¥.%6¥.%7¥.%8¥.";
mso-level-tab-stop:2.75in;
mso-level-number-position:left;
margin-left:2.6in;
text-indent:-.85in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
@list l3:level9
{mso-level-text:"%1¥.%2¥.%3¥.%4¥.%5¥.%6¥.%7¥.%8¥.%9¥.";
mso-level-tab-stop:3.25in;
mso-level-number-position:left;
margin-left:3.0in;
text-indent:-1.0in;
mso-ansi-font-size:14.0pt;
mso-bidi-font-size:14.0pt;
font-family:Cambria;
font-variant:normal !important;
color:black;
text-transform:none;
letter-spacing:0pt;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;
mso-ansi-font-style:normal;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>Wow! I have a different scenario.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>I see generation of a Print Job Ticket by
a Print Client as a very simple process. Using C-Code as an
example; it is nothing more that a collection of canned “printf” statement were
the argument are the Print Intent values expressed in the specific Print Job
Ticket “language”. The Print Client only wants to output one Print
Job Ticket format, not one of several. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>I see parsing Print Job Ticket by a Print
Service as an equally simple process; although there is a lot of content/data
checking. The Print Service only wants to accept one Print Job
Ticket format, not one of several.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>The difficult part is when the Print Client
Print Job Ticket format does not match the Print Service Print Job Ticket
format – an impedance mismatch; thus, JTAPI, provides the impedance matching or
a transform service. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>What you are outlining implies that a
Print Client or Print Service internally would need to use a set of data
structures and definitions that supports JTAPI, where it may better for the Print
Client or Print Service to support the Print Job Ticket more
directly. This does lead to the ever pending problem of “Common”;
either a Common Print Client or even a Common Print Service. For a Common
Print Client it implies what “Label” or “Name” and what “values” should be
displayed. If JTAPI definitions, values and names are to be used;
then, JTAPI become useful for converting any Print Job Ticket to a common
internal format for every one to use. I like this idea.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>The same concept applies to capabilities
information which is based Print Job Ticket formats/definitions. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>============<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>For the GSOC the time constraint, we may
only get Print Job Ticket format Foo converted to an internal structure.
We can try to both read and write of that Print Job Ticket format. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>============<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>Since there may be an issue using or modifying
MJT (copyright, etc), I will create a very simple MIT license Print Job Ticket
format for JTAPI GSOC. Again, the goal of JTAPI this year is
end-to-end code with a very well documented set of code that will be used as
illustration of implementing JTAPI. The Print Job Ticket format is
not important this year. Next year or in a separate project, a
standardized Print Job Ticket format can be instantiated. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>Glen<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Ira McDonald
[mailto:blueroofmusic at gmail.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Monday, April 02, 2012 8:12
AM<br>
<b><span style='font-weight:bold'>To:</span></b> Petrie, Glen; Ira McDonald<br>
<b><span style='font-weight:bold'>Cc:</span></b> Daniel Dressler;
printing-architecture at lists.linux-foundation.org;
printing-summit at lists.linux-foundation.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re:
[Printing-architecture] [Printing-summit] OPS Preparationminutes (28 March
2012)</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Hi Glen,<br>
<br>
I agree with you that the *3rd* use case is a Client producing<br>
JDF and and PrintService converting it to PJT w/ JTAPI.<br>
<br>
But the other two use cases (I think the dominant ones)<br>
don't involve ANY conversion:<br>
<br>
(1) Client builds an abstract job ticket using JTAPI and says<br>
write it out to a given format.<br>
<br>
(2) PrintService accepts that concrete job ticket and parses<br>
it w/ JTAPI and uses the JTAPI parsed attributes as input<br>
to the Scheduler and Interpreter subunits to process the<br>
job.<br>
<br>
Your 3rd use case of conversion of formats can't be<br>
demonstrated without at least 2 backends - it's harder,<br>
not simpler.<br>
<br>
For all I care there's a reference only backend that writes<br>
out (and reads in/parses) only an internal C struct form<br>
of a job ticket. <br>
<br>
Or writes out MJT, but it That intellectual property and<br>
status issues - the spec is PWG copyrighted and it's<br>
a whitepaper, not an approved PWG project (that is, we<br>
CANNOT modify MJT w/out PWG permission).<br>
<br>
WDYT?<br>
<br>
Cheers,<br>
- Ira<br>
<br>
<br>
<br clear=all>
Ira McDonald (Musician / Software Architect)<br>
Chair - Linux Foundation Open Printing WG<br>
Secretary - IEEE-ISTO Printer Working Group<br>
Co-Chair - IEEE-ISTO PWG IPP WG<br>
Co-Chair - TCG Trusted Mobility Solutions WG<br>
Chair - TCG Embedded Systems Hardcopy SG<br>
IETF Designated Expert - IPP & Printer MIB<br>
Blue Roof Music/High North Inc<br>
<a href="http://sites.google.com/site/blueroofmusic" target="_blank"><font
color="#3333ff"><span style='color:#3333FF'>http://sites.google.com/site/blueroofmusic</span></font></a><br>
<a href="http://sites.google.com/site/highnorthinc" target="_blank"><font
color="#6600cc"><span style='color:#6600CC'>http://sites.google.com/site/highnorthinc</span></font></a><br>
mailto:<a href="mailto:blueroofmusic at gmail.com" target="_blank">blueroofmusic at gmail.com</a><br>
Winter <st1:address w:st="on"><st1:Street w:st="on">579 Park Place</st1:Street>
<st1:City w:st="on">Saline</st1:City>, <st1:State w:st="on">MI</st1:State>
<st1:PostalCode w:st="on">48176</st1:PostalCode></st1:address>
734-944-0094<br>
Summer <st1:address w:st="on"><st1:Street w:st="on">PO Box</st1:Street>
221</st1:address> Grand <st1:place w:st="on"><st1:City w:st="on">Marais</st1:City>,
<st1:State w:st="on">MI</st1:State> <st1:PostalCode w:st="on">49839</st1:PostalCode></st1:place>
906-494-2434<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'><br>
<br>
<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>2012/4/2 Petrie, Glen <<a href="mailto:glen.petrie at eitc.epson.com">glen.petrie at eitc.epson.com</a>><o:p></o:p></span></font></p>
<div link=blue vlink=blue>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'>Ira,</span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'> </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'>I must admit to being totally confused. I always under
the impression that JTAPI was a classic definition of a transform service and
not just a job ticket interpreter for a Print Service. I
thought a transform service accepts one document format and product a different
document format; which is what I thought JTAPI did. Example, accept a JDF
job ticket and produce a PWG job ticket. </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'> </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'>What you describe below is what I would call it an interpreter and,
maybe, that you have considered JTAPI to be. Then, at least
to me, the existing JTAPI may not be what is needed. What is needed
is a generic JDF interpreter, a PWG:PJT interpreter, …; that is, what I called
the front-end to JTAPI.</span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'> </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'>I always saw the use case as: A Print Service accepts PWG:PJT
but the Print Client produced JDF. Thus, the either the Print
Client or the Print Service uses the JTAPI Transform Service to transform JDF
to PJT. The Print Service would already have its own
interpreter to parse PWG:PJT into what ever internal format the Print Service
needed or used. [ I had always hoped that someday we could have a
defined a the internal format that everyone would use but I don’t think that
will ever happen.]</span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'> </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'>From my use case, JTAPI would need the ability to transform many
possible input public and private job ticket formats; JTAPI, itself would have
an internally data structure capable of containing content from many input Job
Ticket to be able to produce differing output Job Tickets.</span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'> </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'>I am not sure what to do now. I may not be the best person to
guide the Daniel on the first JTAPI project since I not seem to have the
correct understanding. Ira, perhaps, you should mentor Daniel on
the core (the first) JTAPI project so that the actual intent is produced.
I will mentor another student for the second JTAPI project following your’s and
Daniel’s lead. </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'> </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'>Glen</span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'> </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'> </span></font><o:p></o:p></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center>
</span></font></div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma;font-weight:
bold'>From:</span></font></b><font size=2 face=Tahoma><span style='font-size:
10.0pt;font-family:Tahoma'> Ira McDonald [mailto:<a
href="mailto:blueroofmusic at gmail.com" target="_blank">blueroofmusic at gmail.com</a>]
<br>
<b><span style='font-weight:bold'>Sent:</span></b> Sunday, April 01, 2012 9:27
PM<br>
<b><span style='font-weight:bold'>To:</span></b> Petrie, Glen; Ira McDonald<br>
<b><span style='font-weight:bold'>Cc:</span></b> Daniel Dressler; <a
href="mailto:printing-architecture at lists.linux-foundation.org" target="_blank">printing-architecture at lists.linux-foundation.org</a>;
<a href="mailto:printing-summit at lists.linux-foundation.org" target="_blank">printing-summit at lists.linux-foundation.org</a></span></font><o:p></o:p></p>
<div>
<div>
<p class=MsoNormal><font size=3 face=Tahoma><span style='font-size:12.0pt;
font-family:Tahoma'><br>
<b><span style='font-weight:bold'>Subject:</span></b> Re:
[Printing-architecture] [Printing-summit] OPS Preparationminutes (28 March
2012)</span></font><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'> <o:p></o:p></span></font></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'>Hi Glen,<br>
<br>
I strongly disagree - this is *not* the OP Job Ticket<br>
Transform Service.<br>
<br>
The first use for a client is to create a NEW job<br>
ticket (in the abstract API) and write it out into some<br>
concrete format (with a backend).<br>
<br>
Clients mostly won't modify existing job tickets.<br>
<br>
And PrintServices will just use JTAPI to parse the<br>
job ticket once (in whatever format) and use the<br>
values in the actual Interpreter and Scheduler<br>
miodules.<br>
<br>
Conversion of Job Ticket formats is the tertiary<br>
use case.<br>
<br>
Cheers,<br>
- Ira<br>
<br clear=all>
Ira McDonald (Musician / Software Architect)<br>
Chair - Linux Foundation Open Printing WG<br>
Secretary - IEEE-ISTO Printer Working Group<br>
Co-Chair - IEEE-ISTO PWG IPP WG<br>
Co-Chair - TCG Trusted Mobility Solutions WG<br>
Chair - TCG Embedded Systems Hardcopy SG<br>
IETF Designated Expert - IPP & Printer MIB<br>
Blue Roof Music/High North Inc<br>
<a href="http://sites.google.com/site/blueroofmusic" target="_blank"><font
color="#3333ff"><span style='color:#3333FF'>http://sites.google.com/site/blueroofmusic</span></font></a><br>
<a href="http://sites.google.com/site/highnorthinc" target="_blank"><font
color="#6600cc"><span style='color:#6600CC'>http://sites.google.com/site/highnorthinc</span></font></a><br>
mailto:<a href="mailto:blueroofmusic at gmail.com" target="_blank">blueroofmusic at gmail.com</a><br>
Winter <st1:address w:st="on"><st1:Street w:st="on">579 Park Place</st1:Street>
<st1:City w:st="on">Saline</st1:City>, <st1:State w:st="on">MI</st1:State>
<st1:PostalCode w:st="on">48176</st1:PostalCode></st1:address> <a
href="tel:734-944-0094" target="_blank" value="+17349440094">734-944-0094</a><br>
Summer <st1:address w:st="on"><st1:Street w:st="on">PO Box</st1:Street>
221</st1:address> Grand <st1:place w:st="on"><st1:City w:st="on">Marais</st1:City>,
<st1:State w:st="on">MI</st1:State> <st1:PostalCode w:st="on">49839</st1:PostalCode></st1:place>
<a href="tel:906-494-2434" target="_blank" value="+19064942434">906-494-2434</a><o:p></o:p></span></font></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'>2012/3/30 Petrie,
Glen <<a href="mailto:glen.petrie at eitc.epson.com" target="_blank">glen.petrie at eitc.epson.com</a>><o:p></o:p></span></font></p>
<div link=blue vlink=blue>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'>Ira, Daniel</span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'> </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'>Since there seems to be an objection with just using “op”; I don’t
believe “opjt” is actually correct either. That is, this is not the
OpenPrinting Job Ticket; what it is the OpenPrinting Job Ticket Transform Service
[which fits perfectly with PWG’s definition of a transform
service]. So an alternate and more descriptive lettering would be
either </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'> </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'>“opjtt”
= open printing job ticket transform</span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'>“opjtts”
= open printing job ticket transform service</span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'> </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'><The only other suggestion is to change the formal API names
(not the prefix) to say JobTicketXXXXXXX and DocObj____. NO!></span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'> </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'>Glen</span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'> </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'>p.s. </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>Please consider that this code will
ultimately be reference code; and not reference code for execution as much as
for source code on how to make Job Ticket back-ends (and front-end).
Having long prefixes for variable, variable types, routine name, etc,
makes the code difficult to read, understand and develop. This is
not a schema, a dtd or the like; but a set of APIs that must have a front-end
and one or more back-ends. Namespace conflicts with JTAPI as
a transform service are none since that interface will be determined by the
front-end.. Conflicts of actual coding of the front-end and back-ends
would be very low. Since back-ends will likely be DLLs, there are
not conflicts between back-ends. My request is that, for this
project, the code must be well structured, easy to read, easy to following and
strongly commented. The goal is not the fastest or the fanciest
code but code that other will read and use to develop their code.
The code is the instruction manual. </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'> </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'>p.s. </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>As the PWG moves forward to MFD’s, the
notation of a Job Ticket becomes unclear as to what service the Job Ticket is
for. So the descriptive lettering should be</span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'> </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>oppjtt openprinting print job
ticket transform</span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>oppjtts openprinting print job
ticket transform service</span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'> </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>or </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'> </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>The current JTAPIs would have to be
extended to support other services. Naming will be a real big
problem then even considering the commonality among various service job
tickets. </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'> </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'>p.s. </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>I did not see any feedback (or I missed
it) to my suggested changes to JTAPI headers to OpenPrinting names (prefixes);
thus, I assume the preference is to stay to the existing FSG:JTAPI header
file. That is, by all definitions, the correct thing to do.
So I guess it make the discussion of prefix unnecessary.</span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:.5in'><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'> </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'> </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'>gwp</span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'> </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'> </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'> </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'> </span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'> </span></font><o:p></o:p></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center>
</span></font></div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma;font-weight:
bold'>From:</span></font></b><font size=2 face=Tahoma><span style='font-size:
10.0pt;font-family:Tahoma'> <a
href="mailto:printing-architecture-bounces at lists.linux-foundation.org"
target="_blank">printing-architecture-bounces at lists.linux-foundation.org</a>
[mailto:<a
href="mailto:printing-architecture-bounces at lists.linux-foundation.org"
target="_blank">printing-architecture-bounces at lists.linux-foundation.org</a>] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Ira McDonald<br>
<b><span style='font-weight:bold'>Sent:</span></b> Wednesday, March 28, 2012
9:18 PM<br>
<b><span style='font-weight:bold'>To:</span></b> Daniel Dressler; Ira McDonald<br>
<b><span style='font-weight:bold'>Cc:</span></b> <a
href="mailto:printing-architecture at lists.linux-foundation.org" target="_blank">printing-architecture at lists.linux-foundation.org</a>;
<a href="mailto:printing-summit at lists.linux-foundation.org" target="_blank">printing-summit at lists.linux-foundation.org</a><br>
<b><span style='font-weight:bold'>Subject:</span></b> Re:
[Printing-architecture] [Printing-summit] OPS Preparationminutes (28 March
2012)</span></font><o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'> <o:p></o:p></span></font></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'>Hi Daniel,<br>
<br>
Comments inline below.<br>
<br>
Cheers,<br>
- Ira<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'>On Wed, Mar 28,
2012 at 7:09 PM, Daniel Dressler <<a href="mailto:danieru.dressler at gmail.com"
target="_blank">danieru.dressler at gmail.com</a>> wrote:<o:p></o:p></span></font></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'>In response to
some comments in the meeting.<br>
<br>
1. I would prefer an 'op' prefix to 'fsgjt'. I assume fsgjt means free
standards group job ticket? Since the fsg does not exist anymore I think 'op'
would avoid confusion. And it is shorter.<o:p></o:p></span></font></p>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'>Do we know of any
namespace conflicts with other op libraries? It's been 5+ years, has this
situation changed?<o:p></o:p></span></font></p>
</blockquote>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'><ira><br>
The Open Printing Vector API uses 'opvp' as prefix throughout.<br>
It's sloppy and amateur coding practice not to use a library <br>
specific unique prefix (e.g., 'opjt') for variables and functions.<br>
<br>
The scope is NOT just OP libraries, but the entire universe of<br>
code that might be linked into a vendor or third-party tool.<br>
</ira><br>
<o:p></o:p></span></font></p>
</div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'>2. I will be
attending as much of the summit as I can by phone-in, the summit takes place
over my finals so I will be missing some sessions.<o:p></o:p></span></font></p>
</blockquote>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'><ira> <br>
Understood - we'll be glad to have you when you can attend.<br>
</ira><o:p></o:p></span></font></p>
</div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'>3. If the wiki has
no history does that mean it is pointless for me to fill in the change log when
making edits?<o:p></o:p></span></font></p>
</blockquote>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'><ira><br>
Till can hopefully answer this one - we're not any of us happy<br>
about the move from a full-function Wiki tool to a limited Wiki<br>
tool by the Linux Foundation.<br>
</ira><br>
<br>
Daniel<o:p></o:p></span></font></p>
</div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'> <o:p></o:p></span></font></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'>2012</span></font><font
face="MS Mincho"><span style='font-family:"MS Mincho"'>年</span></font>3<font
face="MS Mincho"><span style='font-family:"MS Mincho"'>月</span></font>28<font
face="MS Mincho"><span style='font-family:"MS Mincho"'>日</span></font>13:38 Ira
McDonald <<a href="mailto:blueroofmusic at gmail.com" target="_blank">blueroofmusic at gmail.com</a>>:<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'>Hi, <br>
<br>
Minutes from today's Open Printing Summit planning call are posted at:<br>
<br>
<a
href="ftp://ftp.pwg.org/pub/pwg/openprinting/minutes/OP-Summit-Prep-20120328.htm"
target="_blank">ftp://ftp.pwg.org/pub/pwg/openprinting/minutes/OP-Summit-Prep-20120328.htm</a><br>
<br>
Note: New FTP directory - see above<br>
<br>
- ACTION - Till - contact Linux Foundation about Glen/Hin-Tak updates<br>
to GSoC projects - no website fall-backs allowed until late April<br>
- OPEN<br>
<br>
- ACTION - Till - contact Ghostscript and other color management folks<br>
as presenters (or send slides?)<br>
- Michael Vrhel (Artifex, Ghostscript) will attend OPS<br>
- OPEN<br>
<br>
- ACTION - All - Draft presentation slides/outlines for review 11 April<br>
- OPEN<br>
<br>
- ACTION - Presenters - tell Till EARLY about any special requirements<br>
(e.g., speakers for video, demo printers, etc.)<br>
- OPEN<br>
<br>
- ACTION - Presenters - send PDF slides to Till EARLY (or upload to OP)<br>
(so that participants can download slides as backup for screencast)<br>
- OPEN<br>
<br>
- ACTION - Ira - draft slides for OP Plenary by 11 April<br>
- OPEN<br>
<br>
Next OP Conference Calls:<br>
(1) April 2012 - OPS Preparation<br>
- Note - US Daylight Savings Time started on Sunday 11 March
2012<br>
- Note - Europe Summer Time started on Sunday 25 March 2012<br>
<br>
- Wednesday 11 April 2012, Daytime<br>
- US<br>
9am in <st1:City w:st="on">San
Francisco</st1:City> - <st1:country-region w:st="on"><st1:place w:st="on">US</st1:place></st1:country-region>
PDT (Pacific Daylight Time)<br>
10am in <st1:State w:st="on">Colorado</st1:State>
- <st1:country-region w:st="on"><st1:place w:st="on">US</st1:place></st1:country-region>
MDT (Mountain Daylight Time)<br>
11am in Chicago - <st1:country-region
w:st="on"><st1:place w:st="on">US</st1:place></st1:country-region> CDT (Central
Daylight Time)<br>
12pm in <st1:State w:st="on">New
York</st1:State> - <st1:country-region w:st="on"><st1:place w:st="on">US</st1:place></st1:country-region>
EDT (Eastern Daylight Time)<br>
- <st1:place w:st="on">Europe</st1:place><br>
6pm in <st1:State w:st="on"><st1:place
w:st="on">Berlin</st1:place></st1:State> - CEST (Central European Summer Time)<br>
<br>
* Main Number (Till Kamppeter, LF, leader)<br>
International: <a href="tel:%2B1-218-936-7999"
target="_blank" value="+12189367999">+1-218-936-7999</a><br>
Access Code: 491659#<br>
<br>
(2) April 2012 - Joint PWG / Open Printing <st1:City w:st="on"><st1:place
w:st="on">Summit</st1:place></st1:City><br>
- Note - OPS is NOT hosted by Linux Foundation Collaboration
Summit<br>
<br>
- Tuesday to Friday 24-27 April 2012 at Apple in <st1:place
w:st="on"><st1:City w:st="on">Cupertino</st1:City>, <st1:State w:st="on">CA</st1:State></st1:place><br>
- US<br>
9am in <st1:City w:st="on">San
Francisco</st1:City> - <st1:country-region w:st="on"><st1:place w:st="on">US</st1:place></st1:country-region>
PDT (Pacific Daylight Time)<br>
10am in <st1:State w:st="on">Colorado</st1:State>
- <st1:country-region w:st="on"><st1:place w:st="on">US</st1:place></st1:country-region>
MDT (Mountain Daylight Time)<br>
11am in Chicago - <st1:country-region
w:st="on"><st1:place w:st="on">US</st1:place></st1:country-region> CDT (Central
Daylight Time)<br>
12pm in <st1:State w:st="on">New
York</st1:State> - <st1:country-region w:st="on"><st1:place w:st="on">US</st1:place></st1:country-region>
EDT (Eastern Daylight Time)<br>
- <st1:place w:st="on">Europe</st1:place><br>
6pm in <st1:State w:st="on"><st1:place
w:st="on">Berlin</st1:place></st1:State> - CEST (Central European Summer Time)<br>
<br>
* Main PWG Number (Mike Sweet, Apple, leader)<br>
US Toll-Free: <a
href="tel:%2B1-866-469-3239" target="_blank" value="+18664693239">+1-866-469-3239</a><br>
International: <a href="tel:%2B1-650-429-3300"
target="_blank" value="+16504293300">+1-650-429-3300</a><br>
Access Code: By request to Ira
McDonald (do NOT publish)<br>
<br>
(3) May 2012 - US/Europe - OP Monthly Meeting<br>
- Note - Joint PWG/OPS is 24-27 April at Apple in <st1:place
w:st="on"><st1:City w:st="on">Cupertino</st1:City>, <st1:State w:st="on">CA</st1:State></st1:place><br>
- Note - Ubuntu Developer Summit is 7-11 May in <st1:place
w:st="on"><st1:City w:st="on">Oakland</st1:City>, <st1:State w:st="on">CA</st1:State></st1:place><br>
- Note - Ira has a conflict on 16 May<br>
<br>
- Wednesday 23 May 2012, Daytime<br>
- US<br>
9am in <st1:City w:st="on">San
Francisco</st1:City> - <st1:country-region w:st="on"><st1:place w:st="on">US</st1:place></st1:country-region>
PDT (Pacific Daylight Time)<br>
10am in <st1:State w:st="on">Colorado</st1:State>
- <st1:country-region w:st="on"><st1:place w:st="on">US</st1:place></st1:country-region>
MDT (Mountain Daylight Time)<br>
11am in Chicago - <st1:country-region
w:st="on"><st1:place w:st="on">US</st1:place></st1:country-region> CDT (Central
Daylight Time)<br>
12pm in <st1:State w:st="on">New
York</st1:State> - <st1:country-region w:st="on"><st1:place w:st="on">US</st1:place></st1:country-region>
EDT (Eastern Daylight Time)<br>
- <st1:place w:st="on">Europe</st1:place><br>
6pm in <st1:State w:st="on"><st1:place
w:st="on">Berlin</st1:place></st1:State> - CEST (Central European Summer Time)<br>
<br>
* Main Number (Till Kamppeter, LF, leader)<br>
International: <a href="tel:%2B1-218-936-7999"
target="_blank" value="+12189367999">+1-218-936-7999</a><br>
Access Code: 491659#<br>
<br>
Cheers,<br>
- Ira<br>
<br clear=all>
Ira McDonald (Musician / Software Architect)<br>
Chair - Linux Foundation Open Printing WG<br>
Secretary - IEEE-ISTO Printer Working Group<br>
Co-Chair - IEEE-ISTO PWG IPP WG<br>
Co-Chair - TCG Trusted Mobility Solutions WG<br>
Chair - TCG Embedded Systems Hardcopy SG<br>
IETF Designated Expert - IPP & Printer MIB<br>
Blue Roof Music/High North Inc<br>
<a href="http://sites.google.com/site/blueroofmusic" target="_blank"><font
color="#3333ff"><span style='color:#3333FF'>http://sites.google.com/site/blueroofmusic</span></font></a><br>
<a href="http://sites.google.com/site/highnorthinc" target="_blank"><font
color="#6600cc"><span style='color:#6600CC'>http://sites.google.com/site/highnorthinc</span></font></a><br>
mailto:<a href="mailto:blueroofmusic at gmail.com" target="_blank">blueroofmusic at gmail.com</a><br>
Winter <st1:address w:st="on"><st1:Street w:st="on">579 Park Place</st1:Street>
<st1:City w:st="on">Saline</st1:City>, <st1:State w:st="on">MI</st1:State>
<st1:PostalCode w:st="on">48176</st1:PostalCode></st1:address> <a
href="tel:734-944-0094" target="_blank" value="+17349440094">734-944-0094</a><br>
Summer <st1:address w:st="on"><st1:Street w:st="on">PO Box</st1:Street>
221</st1:address> Grand <st1:place w:st="on"><st1:City w:st="on">Marais</st1:City>,
<st1:State w:st="on">MI</st1:State> <st1:PostalCode w:st="on">49839</st1:PostalCode></st1:place>
<a href="tel:906-494-2434" target="_blank" value="+19064942434">906-494-2434</a><o:p></o:p></span></font></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'> <o:p></o:p></span></font></p>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'>_______________________________________________<br>
Printing-summit mailing list<br>
<a href="mailto:Printing-summit at lists.linux-foundation.org" target="_blank">Printing-summit at lists.linux-foundation.org</a><br>
<a href="https://lists.linuxfoundation.org/mailman/listinfo/printing-summit"
target="_blank">https://lists.linuxfoundation.org/mailman/listinfo/printing-summit</a><o:p></o:p></span></font></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'> <o:p></o:p></span></font></p>
</blockquote>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'> <o:p></o:p></span></font></p>
</div>
</div>
</div>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'> <o:p></o:p></span></font></p>
</div>
</div>
</div>
</div>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</body>
</html>
------_=_NextPart_001_01CD10E9.5B115290--
More information about the Printing-architecture
mailing list