MFD Model and Common Semantics Last Call Resolution
Comments Relative to:
ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdsystemservicemodel10-20110124.pdf
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Comment
Page 2 line 58: Title here doesn't match the front.
Page 2 Footer: Change all footers to 2009-2011.
Page 12 line 539: This sentence is restating the same sentence
from the previous page scope section....(remove)
Page 19 line 617: broken reference (there are 15 total broken
references from a search on the word Error! in the PDF)
Page 22 line 669: the word Hardcopy doesn't need up-casing
Page 25 line 707: the words " more appropriately" are not
necessary
Page 28 line 767: Content Regions should be Content Region.
Page 29 line 805: the acronym SDSF is used before it's defined,
need to spell it out here or move the definitions before
Page 30 line 825: "1 ton Documents"????
Page 31 line 868: No figure reference after the word Figure.
Page 33 line 901: double periods in sentence
Page 35 line 944: PDF file shows two RED commas in the
sentence.
Page 38 line 989: Need a period, not a comma at the end of
the line.
Page 40 line 1025: Missing (REF) which is in RED.
page 41 line 1044: Table 4 has forward references listed in the
description.
16
General comment on description tables (many of the tables
have either blank description columns or blank reference
columns....or both....unless the Elements are defined in this
document a reference needs to be included in ALL Element
listings in tables.
17
Page 77 line 1328 second to last table row: The description for
Any is Extension point for status...should be Extension point
for OutputChannelStatus.
General comment on the Description of the extension point
Any....There is a very inconsistent style of how these are
described in the tables (some are blank, some just say
Extension point, some say Extension point for something and
some say "extension point for vendor differentiation and
implementation-specific extensions while maintaing
18
Resolution
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Rejected. Intended to show the
content will reside in a separate
document
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected. References were not
forward, but to a different
document. This is now clarified.
Corrected. This has been a
major addition and has resulted
in more tables and more
paragraphs. See “Table
changes” for Original tables
affected
Corrected.
Corrected.
19
20
21
22
23
24
25
26
27
28
29
30
Comment
interoperability) Suggest simply changing all to Extension point
for "exactly what they extend". Also the word "Any" is
inconsistently upcased or not, sometimes all lower case
sometimes upcased throughout the tables.
Page 77 line 1338: need a period at the end of the sentence.
Page 82 line 1365 last row in table: Example of the General
comment on the Any extension point, and Processor is spelled
wrong.
Page 86 line 1387 row 12 of table: unnecessary period in third
column, and odd character in forth.
Page 87 line 1401: period spacing mid-line.
Page 91 line 1428: double semi-colons
Page 91 line 1450: What's the star for??
Page 93 line 1486: spacing of comma mid-line.
Page 93 line 1492: Section 0 reference (broken)
Page 94 line 1506: Sentence is split by the figure.
Page 100 line 1565 Resolution row: What's the star for??
Page 107 line 1605: comma,period in mid-line
Page 113 line 1647: Why's the word (Copy) in the figure
name?? (multiple instances)
Resolution
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Title changed to reflect that
Copy Service schema illustration
is used to represent servicespecifc elements
Corrected.
31
Page 122 line 1704: Section 0 broken reference
Page 122 line 1706: Internal reference without the word
section.
32
Page 122 line 1715: need period at the end of the line
Corrected.
33
Page 126 line 1735,1736: comma and period spacing issues (3
instances)
Corrected.
34
Page 128 line 1744 StateReasons row: odd symbols in third
column.
Changed to “para” throughout
35
Page 128 line 1746: Name of Counter Spec. is not complete.
Corrected.
36
Page 130 line 1768-1804: Text is BLUE in the PDF.
Corrected.
37
Page 134: Table has odd symbols in column 4 and Counter
spec name/REF are incorrect.
Symbols occur in many tables in the References column.
Page 145 line 1923: period spacing issue
Page 145 line 1924: the word Vendors is upcased...and why is
ONLY a vendor extension point? In theory it could be
extended later by the PWG as well.
Changed to “para” throughout
Corrected.
Changed to “para” throughout
Corrected.
Remove vendor from extension
point
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
Comment
Page 149 line 1947: word spacing issues on the line. All text
should be Left justified not simply justified.
page 161 line 2008: Specific example of table with no
description and no references.
Page 167 line 2153: word spacing issues.
Page 170: Blank page needs to be removed, and previously
mentioned duplicate figure.
Page 172 line 2190: missing period
Page 176 line 2262: merged un-ordered list items (Processing ) is the start of a new list item
Page 178 line 2311: Text in figure overlaps the figure content
(CancelJob)
Page 180 line 2354: Double periods mid-line.
Page 186 line 2564: NEED NOT is NOT a compliance term....
Page 195 line 2920: NEED NOT is NOT a compliance term...
(also occurs on line 2944,3013)
Page 199 line 3048: need reference for Counter spec.
Page 200 line 3110 and 3122: need periods at the end of the
sentences
Page 203 line 3131 second and third to last rows of table:
missing references and the "H" should not be up-cased in
MadiaUsedSheets. (also no reference column for this table)
Page 204 line 3142: Confusing reference to the Counter Spec.
Is it 5106.1 or 5106.10??
Page 205 line 3152: Same Counter Spec. reference issue as
previous comment.
Page 206 line 3182 and 3185: Need a TM after 2600 in both
citations of IEEE Std. 2600TM-2008.
Comment on Schema version 1.119 - the Scan Service does not
have Document object in Job object. When did we decide to
loose the document object(s) in Scan job?
Table 1 Terminology: ADF - need a period at the end of the
last sentence.
Table 1 Terminology: Document - need a period at the end of
the last sentence.
Table 1 Terminology: Saved Job - "A saved job can be" ? Is this
an incomplete sentence or an undeleted text fragment?
Table 1 Terminology: Service - need a period at the end of the
last sentence, not a comma.
Table 7 Power Monitor Elements: Wrong reference for
PowerStateMessage: should be para 5.2.2 not 5.4.2
Wrong description for "Compression" element: the description
text "range of compression factors supported" should be for
"CompressionQualityFactor" element . The text for
Resolution
This document has full justified
text. Spacing issue was result of
different problem and has been
corrected.
See issue 16.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Change to lowercase
Change to lowercase
Corrected.
Corrected.
Add reference to PWG Media
spec (5101.1)
Corrected.
Corrected.
Corrected.
Corrected.
Issue relates to Schema and is
resolved indepently.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
64
65
66
67
68
69
70
71
72
73
74
75
76
77
Comment
Compression element should be: "the compression algorithms
supported"
"Resolution" element: remove the * in front of "Resolution"
The elements of Resolution should be "CrossFeedDir",
"FeedDir", not "Cross Feed", "Feed". Description text for these
elements are missing, or provide references. See Scan Spec
7.1.2.1.16.1 and 7.1.2.1.16.2
Table 45 change "rangeofint" to "range of int" in all
occurrences in the table.
Some or many elements are missing description/semanitc text
for many tables listed below. At least reference to the original
document where semantics are defined should be provided.
-Tables 44, 49 (almost empty for elements of Document
Format Details), 51, 52 (a couple of DataTypes are missing
too), 53, 59, 60, 63, 64, 68
I know it's a lot trying to fill in the description of every element
in the table. However, since the table is the only place for a
very "terse" description of or reference to the semantics of
every element, and the elements are common to more than
one service, we need to make sure their semantics are not
deviated further in future specs. This is the main purpose of
this Common Semantics document. Please, unless the
semantics is obvious by the name of the element, we need to
provide the semantic description text or the appropriate
references.
Table 65 ImagesCompleted and ImpressionsCompleted should
be given "either/or" descriptions like it was done in Table 57.
Security Consideration: Are we all agreed to provide a boiler
plate for this section to not only reference the existing IEEE
2600 standard, but also call out MFD model specifics that
implementers need to consider in order to not only to comply
to MFD Service Common Semantics, but also to the IEEE 2600
standard? I urge we do so.
line 561-562, “it describes” is repeated twice
line 624, “WKV defines the values are” should be “WKV defines
the values that are”
“Table -2 Basic Element Datatypes”, Abstract
Datatype=keyword, sentence 4
“Schema keywords be deleting hyphens” should be “Schema
keywords by deleting hyphens”
line 942 has two periods at the end of the sentence
Line 1268 remove the period after “common.”
line 1367 need a period after “Figure 52”
line 1368 need a period after “Table 36”
Resolution
Resolved to agree with Schema
Corrected.
See issue 16
Corrected.
Corrected - see issue 16.
Corrected.
Resolved according to discussion
at face to face.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
Comment
“Table 50 Imaging Service Job Processing Capabilities”,
Element JobDelayOtuputUntilTime, Description: change “dlay”
to “delay
line 1754 need a period after “”Service State element”
line 2004 “Figure101with” needs a space before the “with”
lines 2263, 2270, 2276, 2289, 2662 need a period
line 2358 change “Job. ese” to “Job. These” and change
“directly affects” to “directly affect”
Resolution
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
line 2433 change “doses” to “does”
SECTION 2.2.1 page 22 figure 6 Primary interfaces is
missing a line from scanner subunit to Email Out
Section 2.2.2 page 24 duplicate graphic of figure 7 on page
26.
Section 2.4.2 page 30 line 825 job produces 1 ton should
be job produces 1 to N
Section 3.2 page 48 line 1149, Section 3.6 page 60 line
1212, Section 3.10 page 70 line 1280: missing reference
source
line 1282 figure 45 should be figure 44
Section 4.3 page 95 duplicate graphic of figure 62
Corrected.
Corrected.
Section 4.3.1 page 102 10th attribute from the top, is
annotation a instance of imposition, if not it should be added
to the graphic
Section 4.3.3 page 112 duplicate graphic of figure 73
Line 1644 References figure 73 but no graphic below the
reference.
page 113 duplicate graphic of figure 74
page 114 duplicate graphic of figure 75
Section 4.7.1 page 129 line 1759, Section 5.1 page 132
line 1829 reference source not found
Page 133 graphic missing caption Image Job Status Element
Page 135 Figure 84 caption not bolded
Section 5.2.1 page 141 does imposition fulfill requirement
for annotation programming
Section 5.2.3 page 150 duplicate graphic of figure 94
Section 7.1 page 165 Figure 102 graphic shows up on
this page but is referenced in the document as being on page
167
Section 7.1.4 page 167 line 2126 Scheduling of Jobs
should be scheduling of the service’s Jobs.
Section 7.2.1. page 168, page 171 duplicate graphic of
figure 103
Section 7.3.1.3 page 183 line 2423 reference source not
found
Withdrawn by Xerox
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
Withdrawn by Xerox
Corrected.
Corrected.
Corrected.
Corrected.
Corrected.
104
line 2424
Comment
acel<service>job should be Cancel<service>Job
105 Lines 913-915: ArtBox section indented too much
106 Lines 617, 1149, 1212, 1280, 1759, 1829, 1835, 2423: Bad
references?
107 Tables 21, 28: Bad references?
108 Sections 7.3.1.14, 7.3.1.15: I am not sure the suggestion to
drop Hold/Release<service>Job is appropriate here, as we
don't define required operations for any services. Better to just
note the deprecation and then not require them in the individual
service documents as appropriate
109 Move DestinationURIs from FaxOut to Overall
1
110 Remove MediaMaterial from MediaCol since it was somehow
dropped between the original set 2 and 5100.11.
111 Move ConfirmationSheetPrint from FaxOut to Overall
112 Move CoversheetInfo from FaxOut to Overall
Resolution
Corrected.
Corrected.
Corrected.
Corrected.
Suggestion is removed
Done. Definitions are in
“Description” Column, and in para
5.2.3.1 to 5.3.1.5
Done.
Done. Definitions are in
“Description” Columns, and in
para
5.2.3.2
Done. Definitions are in
“Description” Columns, and in
para
5.2.3.3 to 5.2.3.3.8
113 Move RetryInfo from FaxOut to Overall
Done. Definitions are in
“Description” Columns, and in
para 5.2.3.4 to 5.2.3.4.4
114 Add missing OverridingElements to Overides sequence in
<service>JobTicket & fix data type of Overrides in
<service>JobTicketCapabilities (Align with PWG 5100.6 instead
of obsolete PWG 5100.4.)
115 Move multipleOperationTimeoutAction from FaxOut to
Overall (Service Description)
Done.
Reference changed except when
element is not included in PWG
5100.6
Done. Definitions are in
“Description” Columns, and in
para 4.6.1.1
116 Move JobOriginatingUri from FaxOut to Overall (Job Status)
Done. Definitions are in
“Description” Columns, and in
para 5.1.1
117 Move HeaderPrint from FaxOut to Overall (Document
Processing)
Done. Definitions are in
“Description” Columns, and in
para 5.2.1
118 Fix Overrides representation
119 Remove MediaMaterial from MediaCol. Remove MediaWKV.
120 Correct name and type of JobDescription element
JobMoreInfo
121 Fix syntax of ImagingServiceDescription.ServiceGeoLocation
122 Fix syntax of JobticketCababilities.JobDescription.JobPassword
123 Fix PrintDocumentTicket.PrintDocumentProcessing element
PdlInitFile
Done.
Done.
Done.
Done.
Done.
Done.
124 Fix element name for SheetsCompletedCopyNumber and
SheetsCompletedDocumentNumber (Job and Document
Status)
125 Update namespace and schema reference [MFD_SCHEMA]
126 specific steps be taken to stabilize this MS Word source
document
Done.
Done.
Rejected. Although intent
understood, document is voted
Comment
127 Table 52 Service Description Elements in section 4.6 should be
updated
128 on page 147 - "PdlInitFileEntry" should be "PdlInitFile" and it's
container element "PdlInitFiles" is missing
129 on page 148 - change "Cross Feed" to "CrossFeedDir"
Resolution
on and posted as candidate
standard in PDF form, so
stability of MS word is not an
appropriate last call issue
relative to the contents pf this
specification.
Done.
Corrected and added note to
indicate “PdlInitFiles is an
artifact of the XML encoding.
Done
and "Feed" to "FeedDir"
130 Some multiple words element names are not all concatenated in Done
the tables, thus not consistent with the names in the Schema
diagrams
131 Some (perhaps) Schema diagrams do not match with the current Withdrawn
version of the MFD Schema v1.125
132 Add OwnerURI - anyURI - URI [RFC3986] that is an authoritative Clarified in table description
identifier
and added para 4.6.1
(e.g., a 'mailto:' URI) of the authenticated Owner of this Service
instance. This element MAY usable to deliver notifications to the
Owner
133 Add OwnerVCard - string - A MIME vCard [RFC2426] that
Clarified in table description
contains contact information (e.g., email, postal, telephone, etc.) and added para 4.6.2
for the authenticated Owner of this Service instance. This
element SHOULD be usable to deliver notifications (e.g., security
alerts) to the Owner
Table Changes
The following tables had definitions, descriptions and/or reference added, and may have had content
changes to reflect revised Schema illustrations. Schema Illustrations were updated to reflect new
V1.125 Schema version. There have also been significant additions to the References list. Note that the
Power Management reference still needs to be completed, based upon the actual posting of the
standard.
Table 6 Power Meter Elements
Table 7 Power Monitor Elements
Table 19 Finisher Supplies
Table 21 Input Channel
Table 32 Media Path Elements
Table 33 Output Channel
Table 35 Processor
Table 43 Service-Specific Document Processing Capabilities Image Outputs
Table 44 Service-Specific Document Processing Capabilities Impression Outputs
Table 45 Media col
Table 47 Imaging Service Job Description Capabilities
Table 49 Document Format Details
Table 50 Job Processing capabilities
Table 51 Service Specific Job Processing Capabilities
Table 53 Service Description Elements
Table 53 Service-Specific Service Description Elements
(Table 55 – Now Tables 55 and 56)
Table 57 Job Status Elements – Now Table 58
Table 59 Service-Specific Job Status Elements – Now Table 60
Table 60 Job Ticket Document Processing Elements – Now Tables 62 and 64
Table 62 Media Col Job Ticket – Now Table 65
Table 63 –Job Description Elements – Now Tables 66 and 67
Table 64 Job Processing Elements– Now Table 69
Table 66 Service-Specific Document Status Elements – Now Table 71
Table 68 Service-Specific Document Description Elements– Now Table 73
Table 75 Counter Elements Used in the Various Service and System Work Counters – Now Table 80