attachment-0002
<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=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><base href="x-msg://1540/"><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:"Andale Mono";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* 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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Paul and WG,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>From </span>PWG 5105.1-2004 PWG Semantic Model (the initial print service model), constraints appear to be range or maxlength for integers, and Type X Keyword for strings. There are a few other sting constraints including DateTime, and Uri (?), Repertoire,, etc.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I suggest that to list all of the elements in a separate section with their ‘constraints’ would be cumbersome. Keyword values are already listed and we could add type ID to that listing. Numeric integer constraints (0:MAX, 1:MAX, MIN:MAX, Maxlength=1023, Maxlength=127, Maxlength=63, Maxlength=255, Maxlength=40) seem to be of a limited number of values, and could be addressed in the element tables with notes. Other strings could be identified in the description. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Note however that, with few a exceptions, this document does not define the non-complex elements; it provides a reference to their definition. So constraints for such elements may be helpful, but would not appear to be critical. These were not included in the MFD Model specification.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I solicit comments from the rest of the SM Working Group.<o:p></o:p></p><p class=MsoNormal>Thanks.<o:p></o:p></p><p class=MsoNormal>Bill Wagner<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><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"'> Paul Tykodi [mailto:ptykodi@tykodi.com] <br><b>Sent:</b> Wednesday, July 03, 2013 5:36 PM<br><b>To:</b> 'Michael Sweet'; 'William A Wagner'<br><b>Cc:</b> mfd@pwg.org<br><b>Subject:</b> RE: [MFD] Schema Element Table format for Imaging System Model Spec<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Bill,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I prefer the last format as well.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>One of the things I just learned from Pete, when he was briefing me on what I need to know for validating the Schema diagrams in section 5 (System Configuration) of the draft SM 2.0 document, was that Inter-elemental Constraints cannot be shown in the XML and the text representation in the tables is used to describe the constraints.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I don’t know whether we might want to consider creating a specific section in the SM 2.0 document for describing the constraints or not.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Best Regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>/Paul<o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>--</span><span style='color:#1F497D'><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Paul Tykodi<br>Principal Consultant<br>TCS - Tykodi Consulting Services LLC<br><br>Tel/Fax: 603-343-1820<br>Mobile: 603-866-0712<br>E-mail: <a href="mailto:ptykodi@tykodi.com">ptykodi@tykodi.com</a></span><span style='font-size:10.0pt;font-family:"Courier New";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>WWW: </span><span style='font-size:10.0pt;font-family:"Courier New";color:#1F497D'><a href="http://www.tykodi.com/" target="_blank"><span style='font-family:"Arial","sans-serif"'>http://www.tykodi.com</span></a></span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><div><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"'> <a href="mailto:mfd-bounces@pwg.org">mfd-bounces@pwg.org</a> [<a href="mailto:mfd-bounces@pwg.org">mailto:mfd-bounces@pwg.org</a>] <b>On Behalf Of </b>Michael Sweet<br><b>Sent:</b> Wednesday, July 03, 2013 4:43 PM<br><b>To:</b> William A Wagner<br><b>Cc:</b> <a href="mailto:mfd@pwg.org">mfd@pwg.org</a><br><b>Subject:</b> Re: [MFD] Schema Element Table format for Imaging System Model Spec<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I prefer the last format (what was used in the MFD Common Semantics and Model)...<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On 2013-07-03, at 4:12 PM, William A Wagner <<a href="mailto:wamwagner@comcast.net">wamwagner@comcast.net</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><div style='margin-left:.25in'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>The Imaging System Semantics and Model V2 will include and update information from MFD Common Semantics and Model and the previous Service specifications. Much of the contents of these documents consists of showing hierarchical Schema graphics followed by detailed descriptions of the elements in the diagram. The earlier documents used three different approaches for these descriptions, as indicated in the discussion document posted at<o:p></o:p></span></p></div><div style='margin-left:.25in'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><a href="ftp://ftp.pwg.org/pub/pwg/mfd/white/table_format_examples.pdf"><span style='color:purple'>ftp://ftp.pwg.org/pub/pwg/mfd/white/table_format_examples.pdf</span></a><o:p></o:p></span></p></div><div style='margin-left:.25in'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Each approach had its proponents and detractors. The most common format was the single row per entry table used in the MFD Common Semantics and model.<o:p></o:p></span></p></div><div style='margin-left:.25in'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p></div><div style='margin-left:.25in'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>The Imaging System document should use a consistent approach for this explanation of schema elements. Although difficulty in implementing the format should be considered, it is also important that the approach be useful and effective in describing the schema. The three formats are described to allow a working group consideration and decision, hopefully by the next Semantic Model WG conference call.<o:p></o:p></span></p></div><div style='margin-left:.25in'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Thanks,<o:p></o:p></span></p></div><div style='margin-left:.25in'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Bill Wagne<o:p></o:p></span></p></div><p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:10.0pt;margin-left:.25in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Andale Mono","serif"'><br>--<span class=apple-converted-space> </span><br>This message has been scanned for viruses and<span class=apple-converted-space> </span><br>dangerous content by<span class=apple-converted-space> </span><a href="http://www.mailscanner.info/"><b><span style='color:purple'>MailScanner</span></b></a>, and is<span class=apple-converted-space> </span><br>believed to be clean. _______________________________________________<br>mfd mailing list<br><a href="mailto:mfd@pwg.org"><span style='color:purple'>mfd@pwg.org</span></a><br><a href="https://www.pwg.org/mailman/listinfo/mfd"><span style='color:purple'>https://www.pwg.org/mailman/listinfo/mfd</span></a><o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal><span style='font-family:"Andale Mono","serif";color:black'>_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><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. <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>