Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Unassigned
UnassignedReporter
Timothy Donahue
Timothy DonahuePriority
HighestCreated November 29, 2022 at 4:40 PM
Updated February 21, 2023 at 4:17 PM
Resolved February 21, 2023 at 4:17 PM
Use of JDF RunList/@Pages with a value representing multiple page ranges translates to a single XJDF RunList resource with /@Pages having a value of multiple page ranges. According to the XJDF 2.x specification, the /@Pages attribute shall only have a value of a single pair of integer values, not multiple pairs.
The attached zip file contains test files all of which pass schema validation using FixJDF:
test_RL-Pages.jdf - Contains RunList/@Pages=”0 ~ 19 29 ~ 39”
xjdf_2.1test_RL-Pages.xjdf - result of JDF → XJDF 2.1 conversion and contains errant RunList/@Pages="0 19 29 39"
xjdf_2.1test_RL-Pages_proposed.xjdf - Proposed corrected XJDF RunList translation result containing a Partitioned RunList each with valid /@Pages attributes:
<ResourceSet CombinedProcessIndex="0" Name="RunList" Usage="Input"> <Resource> <RunList NPage="20" Pages="0 19"> <FileSpec MimeType="application/pdf" URL="<http://localhost:9095/JobFiles/Lorem-Ipsum_12-pages.pdf"/>> </RunList> </Resource> <Resource> <RunList NPage="11" Pages="29 39"> <FileSpec MimeType="application/pdf" URL="<http://localhost:9095/JobFiles/Lorem-Ipsum_12-pages.pdf"/>> </RunList> </Resource> </ResourceSet>Critical discussion of limitations of the current data type specified fore XJDF Runlist/@Pages:
It seems reasonable that the XJDF Runlist/@Pages be changed to a data type that allows for multiple integer range pairs rather than simply limit it to the IntegerRange type.
The use of multiple integer pairs as the value of Runlist/@Pages appears to pass XJDF schema validation.