Hey Pete...
In your first example, would only pages 5 to 10 print? Or would all of the
pages of the document print, 5-10 being in landscape?
Oh wait, I think I get it - in the first example, on pages 5 to 10 print.
In the second example, the whole document prints, with pages 5 to 10 being
overriden to be in portrait... Correct?
Dave
-----Original Message-----
From: Zehler, Peter [mailto:PZehler at crt.xerox.com]
Sent: Friday, October 18, 2002 4:32 AM
To: 'TAYLOR,BOB (HP-Vancouver,ex1)'; PWG Semantic Model WG (E-mail)
Subject: RE: SM> FinishingAtributes vs. page control
Bob,
You are not reading this correctly. The grouping of elements within the
DocumentProcessing element does not imply any scope over which the group
applies. The Processing elements apply to the object to which they are
bound. JobProcessing applies to the Job and DocumentProcessing applies to
the Document. The model allows you to apply an imposition to a document
which is a subset of the documents pages and/or apply an imposition to a
subset of the document pages. Examples included below.
(I had originally defined the sub-elements of DocumentProcessing as groups
instead of elements to indicate this relationship. Since HP wanted to be
able to use them independently I made them elements and complex types.)
These elements already exist within a Job as a default for all the documents
within or they exist within a document and apply only to that document. It
seems that we can model fairly sophisticated jobs. I think the PWG jobs
look more like JDF intent nodes since there is no control over how the
processing is performed.
Pete
Peter Zehler
XEROX
Xerox Architecture Center
Email: PZehler at crt.xerox.com
Voice: (585) 265-8755
FAX: (585) 265-8871
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
M/S 128-30E
Webster NY, 14580-9701
_______________________________________________________________
Apply an imposition to a document which is a subset of the documents pages:
<?xml version="1.0" encoding="UTF-8"?>
<DocumentProcessingAttributes xmlns="http://www.pwg.org/pwg/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.pwg.org/pwg/
DocumentProcessing.xsd">
<ImpositionGroup>
<OrientationRequested>landscape</OrientationRequested>
</ImpositionGroup>
<FinishingGroup>
<PageRanges>
<pages>
<Lowerbound>5</Lowerbound>
<Upperbound>10</Upperbound>
</pages>
</PageRanges>
</FinishingGroup>
</DocumentProcessingAttributes>
_______________________________________________________________
Apply an imposition to a subset of the document pages:
<?xml version="1.0" encoding="UTF-8"?>
<DocumentProcessingAttributes xmlns="http://www.pwg.org/pwg/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.pwg.org/pwg/
DocumentProcessing.xsd">
<ImpositionGroup>
<OrientationRequested>portrait</OrientationRequested>
</ImpositionGroup>
<FinishingGroup>
<PageOverride>
<PageRanges>
<pages>
<Lowerbound>5</Lowerbound>
<Upperbound>10</Upperbound>
</pages>
</PageRanges>
<OrientationRequested>landscape</OrientationRequested>
</PageOverride>
</FinishingGroup>
</DocumentProcessingAttributes>
_______________________________________________________________
-----Original Message-----
From: TAYLOR,BOB (HP-Vancouver,ex1) [mailto:robert_b_taylor at hp.com]
Sent: Thursday, October 17, 2002 7:00 PM
To: PWG Semantic Model WG (E-mail)
Subject: SM> FinishingAtributes vs. page control
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 at vcd.hp.com
phone: 360.212.2625/T212.2625
fax: 208.730-5111
---------------------------------------------------