Ira McDonald, Bill Wagner, Paul Tykodi, Glenn Petrie, Nancy Chen, Daniel Manchala
Simplified scan and resource job tickets and capabilities spec to correspond to Google Job Ticket Specification. -- Paul Tykodi will work with Daniel Manchala to create the 1st initial draft of the Scan Job Ticket from the Table of Contents of the Print Job Ticket, and further adding use cases, design requirements and an abstract model of the Scan Job Ticket. The use cases could be obtained from the set of common use cases that were document earlier.
Daniel Manchala and Paul Tykodi to create outlines for the Print Service 2.0, Scan Service 2.0 and Resource Service 2.0 Specifications (in that order) taking cues from the Copy Service 1.0.
There wasn't time to discuss Cloudmap 1.0.
Items 1 & 2 (items that need to be done within the SM WG) listed below are closed as they have been addressed in the Cloud Working Group.
1. Reduced (optimal) element set for Print Job Ticket - Glen Petrie worked on this document and submitted it to WG. Update: (from Bill Wagner) This has been addressed in the Cloud WG, although the way in which it may be used was not agreed to.
2. JSON binding that reflects the optimal element set for PJT - Pete indicated that samples (examples in XML and JSON) exist in the present Print Ticket standard - PJT. These samples may not comprise the fully optimal set noted in item 1 above.
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.