We did not make any decisions for lack of quorum. However, we captured some work that needs to be done in the Semantic Model Working Group.
Attendees:
Larry Upthegrove
Bill Wagner
Roarke Randall
Daniel Manchala
1. Reduced (optimal) element set for Print Job Ticket - Glen Petrie worked on this document and submitted it to WG.
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.
3. Simplified scan and resource job tickets and capabilities spec to correspond to Google Job Ticket Specification.
4. Scan Service 2.0 - The Scan Service Spec 1.0 was completed in the MFD WG, before the Semantic Model was created. Hence some work on co-relating Scan Service 1.0 more to the common model is needed. Also, co-relating to things discovered during the binding work on IPP Scan when IPP WG does the IPP Scan work. Note that since Google is pushing towards Cloud Scan either (Cloud Scan Job Ticket + Capabilities) or an (Imaging Job Ticket + Capabilities) should be part of the WG. Daniel to check with Nancy on version 1.0.
5. Resource Service 2.0 - The Resource Service Spec 1.0 was completed in the MFD WG, before the Semantic Model was created. Hence some work on co-relating Resource Service 1.0 more to the common model is needed. Security on the Resources in a Cloud and Enterprise Environment must be considered. Note that since Google is pushing towards Cloud Resource either (Cloud Resource Job Ticket + Capabilities) should be part of the WG. Daniel to check with Nancy on version 1.0
6. Print Service 2.0 - (Get a good clean draft of the Print Service Spec 2.0; then update the Common Semantic Model; then get both approved) - No one yet had agreed to work on the Print Service 2.0 draft. Bill Wagner has volunteered to update the Common Semantic Model.
7. Fax In Service - Ira McDonald to work on the draft. It is still outstanding.
--
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/20130225/9e5d857d/attachment-0002.html>