MFD> Comments on 20090112 Scan Model Doc

MFD> Comments on 20090112 Scan Model Doc

MFD> Comments on 20090112 Scan Model Doc

Dave Whitehead david at lexmark.com
Fri Jan 16 11:40:35 EST 2009


Skipped content of type multipart/alternative-------------- next part --------------
503	_multifunction

509	its -> their

520	delete "for"

533+	text color ???

611	has "an"

722	... extent, it ...

746	Then the Scan Service ...  ->  The Scan Service then ...

775	ERROR
788
804

791	In other words, ...

938	CrossFeedDir, FeedDir (???) data types (???)

956	booleam

959	data types

965	sides(s) -> sides (there's always more than one)

988	(

992	This element is not valid in an XML encoding. <--  ?WHAT/WHY?

1005	DES font

1117	Interpreter data type ???

1122	Interface data type

1180	MicrometersPerHour listed twice

1184	RFC for Media Self Describing Name

1206	ScannerAddressabilitysFeed -> no 's' -> ScannerAddressabilityFeed

1224	ScannerId - uniquely identifies an instance of a Scan Media Path.
	So, why not ScanMediaPathId?  Or, is this actual the scanner ID
	and the description is wrong.

1266	"... values can be directly (what?) or modified indirectly through
	an operation.

1516	Clientand

1536	completed -> was

1800	booleam

1816	no keywords
1826

1851	associated WHAT ???

1914	double period

1915	specified, JobHoldUntil can not be specified.

1918	URI data type ??? should be string

1929	no keywords -- none specified in section 6.2 either.

1940	"Initial implementations will be limited to single document jobs."
	Is this needed?

1955	double period

1957	delete line

1970	font
1974
1979

2040	double period

2083	is this correct: "... elements inherited from the Imaging Job super
	class (i.e. ImagingJobDescription) and includes elements such as
	JobName.  If so, it's not in Figure 43.

2102	Keywords missing

2238	REQUIRED

2277	leading space

2332	StateReason

2430	leading space
2450

2461	delete "are"

2465	All element values defined by enumeration (e.g. State) represent keywords.

2481	writes -> writing

2490	Documents

2492	delete "if so is required."

2495	"... SHALL support the secure communication protocols required by the End User’s
	site policy..."
	This is an open ended REQUIREMENT governed by a third party (End User) policy.
	So, what if site policy says we must support BEEP ...

2638	intent

References	various fonts


More information about the Mfd mailing list