Hi,
*** For review at PWG F2F during SM WG session or subsequent calls ***
I've just posted a new *Prototype* draft of the FaxIn Service at:
ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdfaxinmodel10-20121201.pdf / doc
- clean with line numbers
ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdfaxinmodel10-20121201-rev.pdf / doc
- redlines with line numbers
The major change is the rewrite of the FaxInJob lifecycle per previous SM
comments.
This draft is believed to be technically complete for content (references
still
need cleanup - no other issues remain for discussion).
Cheers,
- Ira
----------------------------------------------------------------
*A. **Changes made to create 1 December 2012 version (Prototype Draft)*
Editorial – Kept status at Prototype Draft
Editorial – Changes per SM WG review on 12/7/11 and subsequent SM WG
discussions
Editorial – Global – fixed typos and format issues
Editorial – Global – replaced “multidocument” with “multiple document”
Editorial – Global – replaced “NEED NOT” with “MAY” (for optional elements)
Editorial – Replaced all figures with up-to-date snapshots from PWG
Semantic Model XML Schema
Editorial – Revised section 6.5 to clarify that the figure lists all
possible subunits and then to list the particular subunits that are
applicable to the FaxInService
Editorial – Revised section 6.6 to add ServiceChargeInfo to Table 2
Editorial – Revised section 7 to show job lifecycle in detail w/ element
names
Editorial – Revised sections 7 and 11.2.3 to add JobReceivingUri to durable
log requirements
Editorial – Revised sections 11.2.3 and 11.3 to correct format errors in
previous version
--
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/20121201/dd3249cc/attachment-0002.html>