attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Norbert,<div><br></div><div>Doesn't the existing IPP printer-name attribute (SM ServiceName element) already provide this?</div><div><br></div><div><br><div><div>On Jan 27, 2014, at 12:03 PM, Norbert Schade <<a href="mailto:Norbert.Schade@conexant.com">Norbert.Schade@conexant.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"><meta name="Generator" content="Microsoft Word 12 (filtered medium)"><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:"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:"\@MS Mincho";
        panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-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;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;}
@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]--><div lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal">I am heavily working with the scan service these days.<o:p></o:p></p><p class="MsoNormal">So my note comes out of that effort.<o:p></o:p></p><p class="MsoNormal">But I think this is a rather general question after all.<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">A service is typically quite a complex object.<o:p></o:p></p><p class="MsoNormal">A name that identifies a service on the highest level would in many cases ease the management and debugging of functionality that deals with services.<o:p></o:p></p><p class="MsoNormal">And if I had more than one service in my scan service xml instance I’d prefer one to be the default (services have their own defaults, but a service itself cannot be the default within a services group).<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">I helped myself by adding a vendor extension (a simple attribute) to the ScanServices and ScanService objects.<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">I could even imagine to add an ID attribute to a ScanService object and an IDREF attribute to the ScanServices object.<o:p></o:p></p><p class="MsoNormal">But I can’t really do that with vendor extensions.<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">Just wondering if other people also feel that a named service and a default reference to such a named service might improve the situation.<o:p></o:p></p><p class="MsoNormal">Regards<o:p></o:p></p><p class="MsoNormal">Norbert<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">Norbert Schade<o:p></o:p></p><p class="MsoNormal">Systems Engineer (printing)<o:p></o:p></p><p class="MsoNormal">Imaging Solutions<o:p></o:p></p><p class="MsoNormal">Conexant Systems, Inc.<o:p></o:p></p><p class="MsoNormal">201 Jones Road<o:p></o:p></p><p class="MsoNormal">Waltham, MA 02451<o:p></o:p></p><p class="MsoNormal">U.S.A.<o:p></o:p></p><p class="MsoNormal">Tel: 1-781-370-8929<o:p></o:p></p><p class="MsoNormal">Email: <a href="mailto:norbert.schade@conexant.com"><span style="color:blue">norbert.schade@conexant.com</span></a><o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p></div><p>Conexant E-mail Firewall (<a href="http://Conexant.Com">Conexant.Com</a>) made the following annotations<br>---------------------------------------------------------------------<br>********************** Legal Disclaimer **************************** <br><br>"This email may contain confidential and privileged material for the sole use of the intended recipient. Any unauthorized review, use or distribution by others is strictly prohibited. If you have received the message in error, please advise the sender by reply email and delete the message. Thank you." <br><br>********************************************************************** <br><br>---------------------------------------------------------------------<br>
</p></div>_______________________________________________<br>ipp mailing list<br><a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>https://www.pwg.org/mailman/listinfo/ipp<br></blockquote></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span>
</div>
<br></div></body></html>