attachment-0001

<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:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<meta name=Generator content="Microsoft Word 12 (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]-->
<style>
<!--
 /* Font Definitions */
 @font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Webdings;
        panose-1:5 3 1 2 1 5 9 6 7 3;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        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","serif";}
tt
        {mso-style-priority:99;
        font-family:"Courier New";}
span.EmailStyle19
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
-->
</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=purple>

<div class=Section1>

<p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Harry,<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Yes, it is not particularly clear without a production printing background.
On one hand, I wonder whether it really belongs in the Overall MFD document,
especially since it would seem that this is a production printing type concept
that will not apply in your typical MFD. On the other hand, these elements are
in the MFD schema, which is not very long on explanations; and I am considering
(perhaps incorrectly) the Overall MFD document a guide to the schema as well as
an umbrella for aspects common to the individual Service specifications.<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I am working on this as much (probably more) to clarify certain
issues in my mind as to establish an overall design philosophy (which I am not
the person to define). I would certainly be open to comment on what should be
covered and what should best be left as an exercise.<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks,<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Bill Wagner<o:p></o:p></span></p>

<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>

<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Harry Lewis
[mailto:harry.lewis@infoprint.com] <br>
<b>Sent:</b> Monday, May 18, 2009 5:30 PM<br>
<b>To:</b> William Wagner<br>
<b>Cc:</b> mfd@pwg.org<br>
<b>Subject:</b> Re: [MFD] RE: Print (mark) content Region definition<o:p></o:p></span></p>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal style='margin-bottom:12.0pt'><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Bill, that is a
huge mouthful. </span><br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Sounds to me
like Finished-Page-Image-Cell should have been named Imposed-Page-Image-Cell
(Finished implies trimmed, for example, which could affect where things appear
to have ended up on the sheet w.r.t. various margins). </span><br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>I understand
why the MFD model wants to describe basic capabilities and limitations of the
device and its services but, are we going too far by delving into concepts
(such as content positioning) which are most frequently controlled by the PDL?</span>
<br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Regards,</span>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Harry <br>
</span><b><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'><br>
Harry Lewis</span></b><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:gray'><br>
Program Manager - Intellectual Property &amp; Open Standards<br>
Phone: 720-663-3456<br>
e-mail: harry.lewis@infoprint.com</span><span style='font-size:7.5pt;
font-family:"Arial","sans-serif";color:blue'><br>
</span><a href="http://www.infoprint.com/"><span style='font-size:7.5pt;
font-family:"Arial","sans-serif"'>infoprint.com</span></a><br>
<br>
<img border=0 width=90 height=26 id="_x0000_i1025"
src="cid:image001.gif@01C9D7E2.B991CA50"><span style='font-family:Webdings;
color:#3F621F'><br>
P</span> <span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#3F621F'>Think before you print</span> <br>
<br>
<o:p></o:p></p>

<table class=MsoNormalTable border=0 cellpadding=0 width="100%"
 style='width:100.0%'>
 <tr>
  <td width="40%" valign=top style='width:40.0%;padding:.75pt .75pt .75pt .75pt'>
  <p class=MsoNormal><b><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>&quot;William
  Wagner&quot; &lt;wamwagner@comcast.net&gt;</span></b><span style='font-size:
  7.5pt;font-family:"Arial","sans-serif"'> </span><br>
  <span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Sent by:
  mfd-bounces@pwg.org</span> <o:p></o:p></p>
  <p><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>05/15/2009
  10:58 AM</span> <o:p></o:p></p>
  </td>
  <td width="59%" valign=top style='width:59.0%;padding:.75pt .75pt .75pt .75pt'>
  <table class=MsoNormalTable border=0 cellpadding=0 width="100%"
   style='width:100.0%'>
   <tr>
    <td valign=top style='padding:.75pt .75pt .75pt .75pt'>
    <p class=MsoNormal align=right style='text-align:right'><span
    style='font-size:7.5pt;font-family:"Arial","sans-serif"'>To</span><o:p></o:p></p>
    </td>
    <td valign=top style='padding:.75pt .75pt .75pt .75pt'>
    <p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>&lt;mfd@pwg.org&gt;</span>
    <o:p></o:p></p>
    </td>
   </tr>
   <tr>
    <td valign=top style='padding:.75pt .75pt .75pt .75pt'>
    <p class=MsoNormal align=right style='text-align:right'><span
    style='font-size:7.5pt;font-family:"Arial","sans-serif"'>cc</span><o:p></o:p></p>
    </td>
    <td valign=top style='padding:.75pt .75pt .75pt .75pt'></td>
   </tr>
   <tr>
    <td valign=top style='padding:.75pt .75pt .75pt .75pt'>
    <p class=MsoNormal align=right style='text-align:right'><span
    style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Subject</span><o:p></o:p></p>
    </td>
    <td valign=top style='padding:.75pt .75pt .75pt .75pt'>
    <p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>[MFD]
    RE: Print (mark) content Region definition</span><o:p></o:p></p>
    </td>
   </tr>
  </table>
  <p class=MsoNormal><o:p>&nbsp;</o:p></p>
  <table class=MsoNormalTable border=0 cellpadding=0>
   <tr>
    <td valign=top style='padding:.75pt .75pt .75pt .75pt'></td>
    <td valign=top style='padding:.75pt .75pt .75pt .75pt'></td>
   </tr>
  </table>
  </td>
 </tr>
</table>

<p class=MsoNormal><br>
<br>
<br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:#004080'>OK,
I delved further into the Production Printing Attributes document. At least to
a non Production Printing person, these are arcane attributes but do correspond
to &nbsp;elements that we have in the model. </span><br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:#004080'>&nbsp;</span>
<br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:#004080'>At
first look I was &nbsp;interpreting “Image” as Content Area. But
&nbsp;positioning the image first must consider the concepts of
Finished-Page-Image Cell and Imposition. &nbsp;Since the Finished-Page-Image
Cell &nbsp;is defined as the region on the surface of a sheet where the
Finished-Page Image is placed, maybe this is the Content Region? Reading
further, &nbsp;“When imposition is not applied, the Finished-Page-Image Cell
coincides with the entire surface of one side of the sheet. When imposition is
applied, a) the sheet is partitioned into multiple non-overlapping
Finished-Page-Image Cells, typically in a rectangular grid, and b) the area
near the edges of the sheet may not belong to any Finished-Page-Image Cell.” So
the Finished-Page-Image Cell in one case is the entire sheet surface (and does
not consider engine margins) and in the other case is a grid used for
addressing the placement of the image. </span><br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:#004080'>&nbsp;</span>
<br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:#004080'>So
“Image” &nbsp;(or Finished-Page Image) is what is positioned and &nbsp;may
correspond to Content Region. Except the “image” attributes appear to only
position the image, with the coordinate system for the Image Shifting
attributes being relative to the Finished-Page-Image Cell. &nbsp;That is, the
dimensions of the image are determined by the PDL (and, realistically, limited
by the margins). </span><br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:#004080'>&nbsp;</span>
<br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:#004080'>Even
the positioning (or “shifting”) of the image is not a simple question of x and
y offset.</span> <br>
<span style='font-family:"Calibri","sans-serif";color:#004080'>&nbsp;</span> <br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:#004080'>“…
the Printer first positions the Finished-Page Image [I assume relative to the
origin of an identified Finished-Page-Image Cell ] using the values it obtains
for the “x-image-position” and “y-image-position” attributes. Then it shifts
the Finished-Page Image by the amount it obtains for the “x-image-shift” and
“y-image-shift” attributes. Finally, for a Finished-Page Image that would be
placed on the front side of a sheet in the Finished Document, it shifts the
Finished-Page Image by the amount it obtains for the “x-side1-image-shift” and
“y-side1-image-shift”. For a Finished-Page Image that would be placed on the
back side of a sheet in the Finished Document, it shifts the Finished-Page
Image by the amount it obtains for the “x-side2-image-shift” and
“y-side2-image-shift” attributes”</span> <br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:#004080'>&nbsp;</span>
<br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:#004080'>Bottom
line, for the MFD overall, the questions are:</span> <br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:#004080'>1.
&nbsp; &nbsp; Margins are defined relative to the media edges, and the content
region cannot extend into the margin areas (if the content that would occur in
those areas &nbsp;is to be printed.) However, Margins are device (or subunit)
elements, not Service elements . Therefore, &nbsp;should these be discussed
under &nbsp;Scan and Marker Subunit Media Content Coordinates?</span> <br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:#004080'>2.
&nbsp; &nbsp; Do we want to define the coordinate system for Services using
“Mark” or “Print”? The elements:</span> <br>
<span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#004080'>a.
&nbsp; &nbsp; ImpositionTemplate</span> <br>
<span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#004080'>b.
&nbsp; &nbsp; XImagePosition</span> <br>
<span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#004080'>c.
&nbsp; &nbsp; XImageShift</span> <br>
<span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#004080'>d.
&nbsp; &nbsp; XSide1ImageShift</span> <br>
<span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#004080'>e.
&nbsp; &nbsp; XSide2ImageShift</span> <br>
<span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#004080'>f.
&nbsp; &nbsp; &nbsp;YImagePosition</span> <br>
<span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#004080'>g.
&nbsp; &nbsp; YImageShift</span> <br>
<span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#004080'>h.
&nbsp; &nbsp; YSide1ImageShift</span> <br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:#004080'>are
included in the model, and perhaps we need to define them and the coordinate
system which they utilize. Certainly we need to distinguish the marking o</span><span
style='font-size:13.5pt;font-family:"Calibri","sans-serif"'>rigin as the NW
corner of the Media.</span> <br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif"'>&nbsp;</span>
<br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif"'>3. &nbsp;
&nbsp; The MFD model has “Scan Region” and “Copy Region” elements, but no
Content Region. Are we going to change that? The elements above are defined at
the same level as Scan Region, not as subelements of a Mark Region element
(otherwise known as the Finished-Page Image). Also, the Mark Region &nbsp;can
be shifted, but unlike Scan Regions, its size appears determined by the PDL,
not the Job Ticket. </span><br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif"'>4. &nbsp;
&nbsp; Is the Copy (Service) Region the same as the Scan Region?</span> <br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif"'>&nbsp;</span>
<br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif"'>Just a few
questions. </span><br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif"'>&nbsp;</span>
<br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif"'>Thanks,</span>
<br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif"'>&nbsp;</span>
<br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif"'>Bill Wagner</span>
<br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif"'>&nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; </span><br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:#004080'>&nbsp;</span>
<br>
<b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> William Wagner
[mailto:wamwagner@comcast.net] <b><br>
Sent:</b> Thursday, May 14, 2009 10:02 PM<b><br>
To:</b> mfd@pwg.org<b><br>
Subject:</b> Print (mark) content Region definition</span> <br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</span>
<br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:#004080'>The
attributes I see in the Production Printing Attributes document that appear to
correspond to content region definition are:</span> <br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>x-image-position
</span><br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>x-image-shift
</span><br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>y-image-shift
</span><br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>y-image-position
</span><br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:#004080'>But
I have difficulty correlating these to what one might normally identify as:</span>
<br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Content
Region Origin &nbsp;X Offset</span> <br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Content
Region X Dimension</span> <br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Content
Region Origin &nbsp;Y Offset</span> <br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Content
Region Y Dimension</span> <br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:#004080'>Could
someone with a Production Attributes understanding enlighten me?</span> <br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:#004080'>&nbsp;</span>
<br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:#004080'>Thanks.</span>
<br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:#004080'>&nbsp;</span>
<br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:#004080'>Bill
Wagner</span> <br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:#004080'>&nbsp;</span>
<br>
<span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:#004080'>&nbsp;</span>
<o:p></o:p></p>

<p><br>
-- <br>
This message has been scanned for viruses and <br>
dangerous content by <a href="http://www.mailscanner.info/"><b>MailScanner</b></a>,
and is <br>
believed to be clean. <tt><span style='font-size:10.0pt'>_______________________________________________</span></tt><span
style='font-size:10.0pt;font-family:"Courier New"'><br>
<tt>mfd mailing list</tt><br>
<tt>mfd@pwg.org</tt><br>
<tt>https://www.pwg.org/mailman/listinfo/mfd</tt></span><o:p></o:p></p>

<p><br>
_____________________________________________________________________________<br>
&quot;This message and any attachments are solely for the intended recipient
and may contain confidential or privileged information. If you are not the
intended recipient, any disclosure, copying, use, or distribution of the
information included in this message and any attachments is prohibited. If you
have received this communication in error, please notify us by reply e-mail and
immediately and permanently delete this message and any attachments. Thank
you.&quot; _____________________________________________________________________________<o:p></o:p></p>

</div>

<br />-- 
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body>

</html>