- From: Michael Hahn <alphabyauthor@gmail.com>
- Date: Sun, 29 Dec 2013 12:52:22 -0600
- To: Jean Kaplansky <Jean.Kaplansky@aptaracorp.com>, "michael@alphabyauthor.com" <michael@alphabyauthor.com>
- CC: "public-ppl@w3.org" <public-ppl@w3.org>
On 12/29/2013 12:02 PM, Jean Kaplansky wrote: > Just for the record, the PTC/Arbortext IETP implementation (at least > in 2010) was XML based rather than PDF or HTML based. I know this > because I specifically asked around PTC development about the > relationship between the S1000D IETP implementation and Digital Media > Publisher, another Arbortext product for which I was preparing an > "under the hood" webinar presentation at the time. PTC does indeed use the XML directly...however... > It's been almost 3 years since I last looked at the S1000D spec, but > I thought there was a requirement that official S1000D IETP > implementations _must_ use the XML content source as the basis for > display and presentation in IETPs rather than rely on transformations > to HTML or do anything more than reference external PDF files. From page 2223 of the 4.0.1_r1 spec: 2.3 IETP display transformation To render a data module for display to an end user the IETP process transforms the data in the XML neutral repository into a viewable "end-user" form. A web-browser-based IETP is the minimal level described in the functionality matrix in 6.4.2 of the spec. Get back to EPUB-ing! Going to TC Camp this year? -- ================================================================ Michael R. Hahn Phone: 1-316-285-0762 ---------------------------------------------------------------- michael@alphabyauthor.com Fax: 1-316-239-2553 ================================================================
Received on Wednesday, 1 January 2014 21:50:26 UTC