Semantic Model Mail Archive: SM> FinishingAtributes vs. page

Semantic Model Mail Archive: SM> FinishingAtributes vs. page

SM> FinishingAtributes vs. page control

From: TAYLOR,BOB (HP-Vancouver,ex1) (robert_b_taylor@hp.com)
Date: Thu Oct 17 2002 - 18:59:55 EDT

  • Next message: Dennis Carney: "SM> ACT - IPP "-actual" attributes downloaded, version 0.1"

    Hi all,

    I got hit with another question internally that I couldn't answer.
    Currently, the
    following attributes are all in the finishing group:

                            <xsd:element ref="Copies" minOccurs="0"/>
                            <xsd:element ref="PageOverride" minOccurs="0"
    maxOccurs="unbounded"/>
                            <xsd:element ref="PagesPerSubset" minOccurs="0"
    maxOccurs="unbounded"/>
                            <xsd:element ref="PageRanges" minOccurs="0"
    maxOccurs="unbounded"/>

    It seems to us that you would really want these at a higher level - e.g.,
    you
    ought to be able to select PageRanges for an imposition, etc. The way it's
    currently structured, it appears that these would only apply to things in
    the
    finishing group - are we reading this correctly?

    Along these lines - do these attributes really live in a new object sitting
    inside documentprocessingattributes that allows us to select
    pagesets(copies,
    overrides, ranges, etc.) and apply any of the rendering/imposition/finishing
    attributes against? This would be something along the line of JDF runlists.
    Or - do we just say that these kinds of jobs are outside the scope of the
    PWG-SM?

    bt

    ---------------------------------------------------
    Bob Taylor
    Senior Architect
    IPG Strategic Technology Development
    Hewlett-Packard Co.
    mailto:robertt@vcd.hp.com
    phone: 360.212.2625/T212.2625
    fax: 208.730-5111
    ---------------------------------------------------



    This archive was generated by hypermail 2b29 : Thu Oct 17 2002 - 19:00:17 EDT