attachment

<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)"><style></style></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1>In pursuing the question about  the SM correlation to Get-Printer-Suppported-Values in table 1, Operations for IPP FaxOut, there appear to be several inconsistencies.<o:p></o:p><![if !supportLists]>1.    <![endif]>ValidateFaxOutJob  does not exist. ValidateFaxOutJobTicket is probably intended.<o:p></o:p><![if !supportLists]>2.    <![endif]>I find no RestartFaxOutJob in either the SM FaxOut Service or general SM Model. Does the make sense? There is a ResubmitFaxOutJob.<o:p></o:p><![if !supportLists]>3.    <![endif]> The SM FaxOut Service does not appear to differentiate GetFaxOutJobElements from the general Get<service>JobElements, which has an important difference from IPP Get-Job-Attributes.  Unlike the IPP Get-Job-Attributes, the GetFaxOutJobElements request does not specify individual Elements. Rather, the Client requests specific groups of Elements contained within the Job. The allowed values for RequestedElements are Job Receipt, Job Status, or Job Ticket. It is not clearly stated whether the FaxOut follows the Common Semantics (presumably it must) or the IPP printer approach.<o:p></o:p><![if !supportLists]>4.    <![endif]>The SM FaxOut Service does not appear to differentiate GetFaxOutServiceElements from the general Get<service>ServiceElements, which has an important difference from IPP Get-Printer-Attributes. Unlike the IPP Get-Printer-Attributes, the GetFaxOutServiceElements request does not specify individual Elements. Rather, the Client requests specific groups of Elements contained within the Job. The allowed values for Requested Elements are Service Capabilities, Service Configuration, Service Description, Service Status or DefaultJob Ticket. This distinction is not clearly stated.<o:p></o:p><![if !supportLists]>5.    <![endif]>As follows from item 4, the correlation to  SM Get-Printer-Supported-Values is GetFaxOutServiceElements with values of Service Configuration, Service Description and Service Status (??)<o:p></o:p><![if !supportLists]>6.    <![endif]>Comment: - should the SM address subscriptions?<o:p></o:p><![if !supportLists]>7.    <![endif]>ReleaseHeldNewFaxOutJobs does not exist. ReleaseHeldFaxOutJobs ( no 'new') is probably intended.<o:p></o:p><![if !supportLists]>8.    <![endif]>Deactivate and Activate were dropped from the SM model. Do we really need these?<o:p></o:p><![if !supportLists]>9.    <![endif]>It might be noted that Startup-Printer correlates to StartupService (FaxOut) of the System Control Service.<o:p></o:p><![if !supportLists]>10. <![endif]>Neither the SM FaxOut nor Common Semantics include an operation correlating to Reprocess-Job. It is not clear how this would act for FaxOut.<o:p></o:p><![if !supportLists]>11. <![endif]>Schedule-Job-After correlates to PromoteFaxOutJob. If the predecessor Job is specified, PromoteFaxOutJob acts the same way as the IPP Schedule-Job-After operation.<o:p></o:p><![if !supportLists]>12. <![endif]>There is no CancelFaxOutDocument in the FaxOut Service just a CancelFaxOutDocuments (note the 's') although the general semantics operations is Cancel<service>Document . Is this an error in the FaxOut Service spec?<o:p></o:p><![if !supportLists]>13. <![endif]>I find no IdentifyFaxOutService under FaxOut, Common Semantics or System Control Service. Should this be added to the SM FaxOut Service (and all other services) or perhaps to System Control Service?<o:p></o:p><![if !supportLists]>14. <![endif]>The FaxOut Service identifies the following operations that do not appear in the IPP FaxOut spec:<o:p></o:p><![if !supportLists]>a.    <![endif]>ResubmitFaxOutJob<o:p></o:p><![if !supportLists]>b.    <![endif]>ValidateFaxOutDocumentTicket<o:p></o:p><o:p> </o:p>Also, will we have a conference call tomorrow as scheduled?<o:p></o:p>Thanks,<o:p></o:p>Bill Wagner<o:p></o:p><o:p> </o:p></div> -- This message has been scanned for viruses and dangerous content by <a href="http://www.mailscanner.info/">MailScanner</a>, and is believed to be clean. </body></html>