Hi Norbert,
Look at "JobConstraintsSupported" and "JobResolversSupported" in
SM "ServiceTypes.xsd"
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music / High North Inc
http://sites.google.com/site/blueroofmusichttp://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
On Mon, Jan 27, 2014 at 2:06 PM, Michael Sweet <msweet at apple.com> wrote:
> Norbert,
>> IPP does have a notion of constraints (job-constraints-supported and
> job-resolvers-supported); I don't know whether the SM has incorporated
> those yet or not.
>>> On Jan 27, 2014, at 2:01 PM, Norbert Schade <Norbert.Schade at conexant.com>
> wrote:
>> Michael,
>> I do not see any support for constraints in the SM.
>> For eSCL I have to provide a set of PlatenInputCaps and at least one
> AdfInputCaps.
>> One way to get out of that dilemma is to provide two full scan device
> descriptions -> two services.
>> If I do it that way we have to tell our MFP LCD which of the services
> (resp sets of caps) is default. Or just go by alphabetical order and show
> the first or something similar.
>> Norbert
>>>> *From:* Michael Sweet [mailto:msweet at apple.com <msweet at apple.com>]
> *Sent:* Monday, January 27, 2014 1:56 PM
> *To:* Norbert Schade
> *Cc:* ipp at pwg.org> *Subject:* Re: [IPP] named services
>>>> Norbert,
>>>> Currently there is no notion of a default service in (standard) IPP or the
> SM. CUPS has a pair of extension operations for getting and setting the
> default printer (and at one point even allowed a server to advertise it as
> a sort-of "default network printer" that clients could prefer, with the
> usual security caveats), however those operations are now rarely used as
> mobile computing has made the notion of a default printer location-specific.
>>>> What are you trying to do?
>>>>>> On Jan 27, 2014, at 1:23 PM, Norbert Schade <Norbert.Schade at conexant.com>
> wrote:
>>>> Ok, found a ServiceName under ImagingServiceDescriptionType.
>> I guess that will help me with the name.
>>>> You have another idea how to make one of many services the default?
>>>> *From:* Norbert Schade
> *Sent:* Monday, January 27, 2014 12:41 PM
> *To:* 'Michael Sweet'
> *Cc:* ipp at pwg.org> *Subject:* RE: [IPP] named services
>>>> There’s always the chance that I misinterpret something.
>> But the excerpt below is from the ScanService.xsd schema. I can’t find
> anything that looks like what you have in mind.
>> And so far I think I’m looking at the right object.
>>>> <!-- ScanServices - set of Scan services -->
>> <xs:complexType name="ScanServicesType">
>> <xs:sequence>
>> <xs:element
> ref="ScanService" minOccurs="0" maxOccurs="unbounded"/>
>> </xs:sequence>
>> <xs:anyAttribute namespace="##other"
> processContents="lax"/>
>> <!-- ScanServices - set of Scan services
> -->
>> </xs:complexType>
>> <xs:element name="ScanServices" type="ScanServicesType"/>
>> <!-- ScanService - object -->
>> <xs:complexType name="ScanServiceBaseType">
>> <xs:sequence>
>> <xs:element
> ref="ScanServiceCapabilities" minOccurs="0"/>
>> <xs:element
> ref="ScanServiceCapabilitiesReady" minOccurs="0"/>
>> <xs:element
> ref="ScanServiceConfiguration" minOccurs="0"/>
>> <xs:element
> ref="ScanServiceDefaults" minOccurs="0"/>
>> <xs:element
> ref="ScanServiceDescription"/>
>> <xs:element
> ref="ScanServiceStatus"/>
>> <xs:any
> namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
>> </xs:sequence>
>> <xs:anyAttribute namespace="##other"
> processContents="lax"/>
>> <!-- ScanService - object -->
>> </xs:complexType>
>> <xs:complexType name="ScanServiceType">
>> <xs:complexContent>
>> <xs:extension
> base="ScanServiceBaseType">
>>> <xs:sequence>
>>> <xs:element name="JobTable">
>>> <xs:complexType>
>>> <xs:sequence>
>>> <xs:element name="ActiveJobs" type="ScanJobsType"/>
>>> <xs:element name="JobHistory" type="ScanJobsType" minOccurs="0"/>
>>> <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
>>> </xs:sequence>
>>> </xs:complexType>
>>> </xs:element>
>>> </xs:sequence>
>> </xs:extension>
>> </xs:complexContent>
>> </xs:complexType>
>> <xs:element name="ScanService" type="ScanServiceType"/>
>>>> *From:* Michael Sweet [mailto:msweet at apple.com <msweet at apple.com>]
> *Sent:* Monday, January 27, 2014 12:18 PM
> *To:* Norbert Schade
> *Cc:* ipp at pwg.org> *Subject:* Re: [IPP] named services
>>>> Norbert,
>>>> Doesn't the existing IPP printer-name attribute (SM ServiceName element)
> already provide this?
>>>>>> On Jan 27, 2014, at 12:03 PM, Norbert Schade <Norbert.Schade at conexant.com>
> wrote:
>>>> I am heavily working with the scan service these days.
>> So my note comes out of that effort.
>> But I think this is a rather general question after all.
>>>> A service is typically quite a complex object.
>> 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.
>> 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).
>>>> I helped myself by adding a vendor extension (a simple attribute) to the
> ScanServices and ScanService objects.
>>>> I could even imagine to add an ID attribute to a ScanService object and an
> IDREF attribute to the ScanServices object.
>> But I can’t really do that with vendor extensions.
>>>> Just wondering if other people also feel that a named service and a
> default reference to such a named service might improve the situation.
>> Regards
>> Norbert
>>>>>> Norbert Schade
>> Systems Engineer (printing)
>> Imaging Solutions
>> Conexant Systems, Inc.
>> 201 Jones Road
>> Waltham, MA 02451
>> U.S.A.
>> Tel: 1-781-370-8929
>> Email: norbert.schade at conexant.com>>>> Conexant E-mail Firewall (Conexant.Com <http://conexant.com/>) made the
> following annotations
> ---------------------------------------------------------------------
> ********************** Legal Disclaimer ****************************
>> "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."
>> **********************************************************************
>> ---------------------------------------------------------------------
>> _______________________________________________
> ipp mailing list
>ipp at pwg.org>https://www.pwg.org/mailman/listinfo/ipp>>>> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>>>>> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>>>> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>> _______________________________________________
> ipp mailing list
>ipp at pwg.org>https://www.pwg.org/mailman/listinfo/ipp>>-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20140127/8359fdb7/attachment.html>