Hi,
STABLE draft - per the IPP WG review on 07/06/17 of all PWG LCRC
changes to JDFMAP Best Practices.
Since both PWG Steering Committee and IPP WG have approved all
of the LCRC changes (with minor edits - see below), I have just posted
a final Stable draft of JDFMAP ready for PWG Formal Vote at:
http://ftp.pwg.org/pub/pwg/sm3/wd/wd-smjdfmap10-20170714.pdf
- clean PDF with line numbers
http://ftp.pwg.org/pub/pwg/sm3/wd/wd-smjdfmap10-20170714.docx
- clean MS Word source with line numbers
http://ftp.pwg.org/pub/pwg/sm3/wd/wd-smjdfmap10-20170714-rev.pdf
- PDF of post-LCRC revisions with line numbers
http://ftp.pwg.org/pub/pwg/sm3/wd/wd-smjdfmap10-20170714-rev.docx
- MS Word source of post-LCRC revisions with line numbers
http://ftp.pwg.org/pub/pwg/sm3/wd/lcrc-smjdfmap10-20170704.txt
- Last Call Response Changes with reviewer sources
Rainer - Due to lack of prototype implementations, this document is
now being advanced as a PWG Best Practices recommendation.
Cheers,
- Ira
-------------------------------
Change History
14 July 2017 – JDFMAP update from PWG LCRC review
* July 2017 – draft in SM WG – from 07/06/17 IPP WG review of PWG LCRC draft
- Accepted all previous changes per IPP WG review except as noted below
- Revised section 6 to delete dangling “, see” before colon
- Revised section 6 and section 7 to change “SHOULD also consider the
following” to “SHOULD also follow the recommendations of the documents below
- Revised section 9 References to delete redundant [UNISECFAQ] entry at end
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20170714/7295d988/attachment.html>