- From: Charles LaPierre <charlesl@benetech.org>
- Date: Tue, 17 Mar 2020 13:52:38 +0000
- To: "Reid, Wendy" <wendy.reid@rakuten.com>
- CC: "public-publ-wg@w3.org" <public-publ-wg@w3.org>
- Message-ID: <C84CBFC9-8CBA-4E2E-A966-9243455BBF68@benetech.org>
+1 Thanks EOM Charles LaPierre Technical Lead, DIAGRAM and Born Accessible Twitter: @CLaPierreA11Y Skype: charles_lapierre On Mar 16, 2020, at 10:09 AM, Reid, Wendy <wendy.reid@rakuten.com<mailto:wendy.reid@rakuten.com>> wrote: Hello everyone, I hope you are all doing well, and staying safe and healthy wherever you are. Some updates have been made recently to the LPF note<https://www.w3.org/TR/2019/NOTE-lpf-20191205/> in response to review from IANA, and we would like to publish the latest revisions for public review. Please reply to this email with a +1 to publish, 0 if you are neutral, or -1 if you oppose the changes. In addition to publishing these changes to LPF, there will also be new updates going out for Publication Manifest and Audiobooks to address feedback and issues that have been raised, all editorial. The changes to LPF are: Modifications done in section A -- Required Parameters: None -> N/A -- Optional Parameters: None -> N/A -- Encoding considerations: from LPF files are binary files encoded in the application/zip media type. to LPF files are binary files in ZIP format. Note: now as in http://idpf.org/epub/30/spec/epub30-ocf.html, was before as in https://www.w3.org/publishing/epub3/epub-ocf.html -- Security considerations: new wording, explicit mention of executables. "In addition, because of the various content types that can be embedded in LPF files, <code>application/lpf+zip</code> may describe content that poses security issues, e.g. malicious executable content deliberately included in the package. However, only in cases where the user agent recognizes and processes the additional content, or where further processing of that content is dispatched to other user agents, would security issues potentially arise. In such cases, matters of security would fall outside the domain of this registration document." -- Magic number(s): Suppression of the notion of offset in the notation: <p>0: <code>PK 0x03 0x04</code></p> becomes <p><code>PK 0x03 0x04</code></p> If there are any questions or issues, please feel free to contact the chairs and Laurent, or post an issue on the LPF GitHub<https://github.com/w3c/lpf> repository. Thanks, PWG Chairs
Received on Tuesday, 17 March 2020 13:52:55 UTC