Hi Norbert,
I see what you mean. It's an oversight. Constraints/Resolvers is supposed
to be present for every Job service (not Resource or System Control).
Pete - shouldn't these be in the base ImagingServiceDescriptionType?
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 Thu, Jan 30, 2014 at 12:53 PM, Norbert Schade <
Norbert.Schade at conexant.com> wrote:
> Ira,
> Let me answer to you directly.
>> This scan section is way shorter:
>> <xs:complexType name="ScanServiceDescriptionType">
> <xs:complexContent>
> <xs:extension base="ImagingServiceDescriptionType">
> <xs:sequence>
> <!-- service type (function of
> this service object) REQUIRED - MUST be single-valued see WIMS Object
> Model - section 4 [WIMS-PRO] -->
> <!-- list of URI supported by
> this service REQUIRED - MAY be multi-valued see printer-uri-supported -
> section 4.4.1 [RFC2911] -->
> <!-- service vendor-supplied
> description and/or label OPTIONAL - MUST be single-valued see
> printer-info - section 4.4.6 [RFC2911] -->
> <!-- Object administrative name
> OPTIONAL - MUST be single-valued see printer-name - section 4.4.4
> [RFC2911] see prtGeneralPrinterName - section 6 [RFC3805] -->
> <!-- list of services (by
> ID/name/URI) subordinate to this service REQUIRED - MAY be multi-valued -->
> <!-- list of devices (by
> ID/name/URI) subordinate to this service REQUIRED - MAY be multi-valued -->
> <!-- list of subunits (by ID)
> supported by this service, REQUIRED - MAY be multi-valued see Printer
> Sub-Units - section 2.2 [RFC3805] -->
> <!-- document formats supported
> by this service REQUIRED - MAY be multi-valued see
> document-format-supported - section 4.4.22 [RFC2911] -->
> <!-- list of resources (by
> ID/name/URI) supported by this service OPTIONAL - MAY be multi-valued see
> ResourceId in Resource XML schema see ResourceName in Resource XML schema
> -->
> <xs:element
> ref="DocumentPasswordSupported" minOccurs="0"/>
> <xs:element
> ref="JobPasswordSupported" minOccurs="0"/>
> <xs:element
> ref="JobPasswordEncryptionSupported" minOccurs="0"/>
> <xs:any namespace="##other"
> minOccurs="0" maxOccurs="unbounded"/>
> </xs:sequence>
> </xs:extension>
> </xs:complexContent>
> <!-- ScanServiceDescription - group -->
> </xs:complexType>
>>> Than the corresponding extension in the print service.
> There I find the constraints stuff additionally.
> Norbert
>> -----Original Message-----
> From: sm3-bounces at pwg.org [mailto:sm3-bounces at pwg.org] On Behalf Of Ira
> McDonald
> Sent: Thursday, January 30, 2014 12:46 PM
> To: Semantic Model 3.0 Workgroup discussion list; Ira McDonald
> Subject: Re: [SM3] SM2, 1.185: JobConstraintsSupported,
> JobResolversSupported
>> Hi Norbert,
>> ALL of the services (including ScanServiceDescription) import and extend
> the base ImagingServiceDescriptionType).
>> I think this is what you wanted?
>> 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/blueroofmusic>http://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 Thu, Jan 30, 2014 at 11:45 AM, Norbert Schade <
>Norbert.Schade at conexant.com> wrote:
>> > Just for the high level view:
> >
> > I find JobConstraintsSupported and JobResolversSupported objects under
> > PrintServiceDescription under PrintServiceBaseType under PrintService
> > in the PrintService schema.
> > As PrintServiceBaseType is also providing PrintServiceCapabilities,
> > this is rather nicely tied up, meaning it can all be covered in one
> > complex structure.
> >
> > When I search through the ScanService schema, I do find
> > ScanServiceCapabilities and ScanServiceDescription objects.
> > But the ...Description object is much shorter, especially not
> > providing any reference to that constraints stuff.
> > So to me it looks as if I'm supposed to create a somewhat independent
> > xml instance based on the ServiceTypes schema that deals with
> constraints.
> > Is that currently under review? Perhaps going to be merged into a
> > common ...Description object?
> > If yes, what is the intended schedule? Is that almost ready for a vote
> > or still heavily edited these days? That would likely have an impact
> > on which SM version we follow in our internal design.
> > 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<mailto:norbert.schade at conexant.com>
> >
> >
> > Conexant E-mail Firewall (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."
> >
> > **********************************************************************
> >
> > ---------------------------------------------------------------------
> >
> > _______________________________________________
> > sm3 mailing list
> > sm3 at pwg.org> > https://www.pwg.org/mailman/listinfo/sm3> >
> _______________________________________________
> sm3 mailing list
>sm3 at pwg.org>https://www.pwg.org/mailman/listinfo/sm3>> Conexant E-mail Firewall (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."
>> **********************************************************************
>> ---------------------------------------------------------------------
>>