At the 11 June MFD conference call, many of the issues I posted with regard
to the MFD Overall document were addressed. The Updated issue list with
resolutions (where arrived at) follow. ( Will also attach a version in case
your mail system does not like the formatting). This lists the Keyword sets
that I had trouble identifying.
Pending receipt of revised schema information from Pete, I will update the
document and post for review at the June Face-to-face.
Thanks,
Bill Wagner
Issues on June 5 Version of Overall MFD Spec, and resolved points.
1. References will be added later
2. Table of Contents format will be made to agree with Resource document
when content is stable
3. Unsure what to do about Datatype normative references (IDS Attributes
discussion), but have added paragraph on datatypes.
Ira will generate new section on Datatypes.
4. Terminology: any more terms?
5. Service Coordinates: list of questions. Do we want to define
production printing co-ordinate system? The elements are in the model.
No. Print/Mark Service coordinate system discussion and diagram will be
removed.
6. FaxModem Elements: do we agree? What about ItuStatistics? References?
To be discussed at face-to-face.
7. Processors: Questions. What are ramifications of following in last
concall notes -
a. Processors does not belong in Services, should be in Overall system
instead.
No effect on Overall document.. Processor will be discussed in Overall
document.
b. Should other Processor subunit properties such as DeviceDescr,
DeviceStatus, DeviceError be modeled in Processor subunit?
Schema will be updated to include device elements where they can be derived
from HR MIB. Overall document will reflect changes in schema pix and
elements tables.
8. Table 22. Note "Caused by" entry for end of JobProcessing state.
Replaced with Initiating cause and terminating cause.
9. Table 30 and elsewhere,
a. certain "Keyword Groups" are unclear or unspecified. Is
ContentTypeType valid?
See Item 11.
b. DestinationUriSchemes is not listed as an element, no keyword
reference. DestinationUriSchemes Type is list of strings, not keyword..
10. Table 31: WillBeCompletedWhenTicket not listed as an element in schema.
Origin of this entry is unknown; it is eliminated.
11. Table 33 and elsewhere. Keyword group listed as NMTOKEN, none or
<Simple Type Union>. Where are the keywords identified?
See list at end of this document.
12. Table 39:
a. CompressionFactor not listed as element;
b. are JobPriority and JobSaveDisposition elements in the Job Ticket
Document Processing set or JobProcessing set?.
c. Is Rotation an int or a keyword?
13. Fig 33. May want to replace with Spy Pic
14. SystemStatus Summary Status?
15. Table 47. RestartAllServices ??
16. What to add to System?
Keyword reference questions. Some elements of the Keyword or list of
Keywords type do not appear to reference a specific set of keywords. What
are the appropriate keyword sets?
ContentType
list of keywords
main characteristics of a Document as supported by the Service.
ContentTypeType
ContentType
keyword
main characteristics of the original Document. It is used as a hint to the
Scan Service on how it should handle the scanning of the Hardcopy Document.
ContentTypeType
Sides
keyword
the ability of the ScanMediaPath to scan multiple sides of an input media
sheet.
SidesType
[RFC2911] sides
NaturalLanguageConfigured
keyword
<Simple Type Union>
ErrorControlUsed
keyword
NMTOKEN
JobCreationElementsSupported
list of keywords
NMTOKEN
UserDefinedValuesSupported
list of keywords
NMTOKEN
JobMandatoryElements
list of keywords
identifies Ticket elements the Scanner must honor. The Service rejects the
request for job creation if any of the listed elements are unsupported or
contain values that the Service does not support. All of the remaining
supplied elements are best effort. NMTOKEN
RepertoiresSupported
list of keywords
none
NaturalLanguageConfigured
keyword
<Simple Type Union>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/mfd/attachments/20090612/762fb5e3/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: June notes.pdf
Type: application/pdf
Size: 66024 bytes
Desc: not available
URL: <http://www.pwg.org/pipermail/mfd/attachments/20090612/762fb5e3/attachment.pdf>