Re: Revise group description?

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. 

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.

I have no idea where I might find that particular fact within 1600+ pages of specification at this point, though.  

I'm going back to my EPUB thing now! People can base entire careers on S1000D alone, these days. I'm definitely not one of them. ;)

> On Dec 29, 2013, at 4:22 AM, "Michael Hahn" <xmlronin@gmail.com> wrote:
> 
>> On 12/29/2013 02:32 AM, Dave Pawson wrote:
>> Clarification please
>> PDF and electronic publications?  I'm puzzled by that.
>> Were I asked to send you an 'electronic' or soft copy of a document, I'd likely
>> choose PDF. is this something specific to the DoD?
> 
> Mostly a matter of packaging - IETP (Interactive Electronic Technical 
> Publication), the S1000D remake of IETMs.  May be PDF-based, usually 
> some sort of HTML-like output built for an enhanced Panorama-like 
> browser/reader application (though it might be completely 
> HTML/CSS/browser-based).  Enigma, recently acquired by PTC, was doing 
> this kind of work back in the late 90s - one of their folks did a demo 
> back in one of my intro classes.
> 
> As opposed to "page-turner" PDFs, IETPs usually emphasize internal 
> linking, informational popups, and gimmicks like built-in "shopping 
> lists" for parts and on-the-fly filtering by aircraft tail number or 
> feature.
> 
> Cessna has an application called Cesview, developed in-house in the 
> early 2000s, that more-or-less fits the profile.  I built two prototype 
> datasets at Learjet, one browser-based and one PDF-based for an existing 
> display application, in 2012.
> 
> The crossover with XSL-FO is that the reader applications generally 
> include some sort of print capability, either screen-scraping HTML (ugh) 
> or using an internal FO processor to produce print pages for the screen 
> views (with page numbers, generated ToCs, etc.).  Commercial IETP 
> applications, for example, are the Arbortext S1000D suite and SDL IETPs.
> 
> DoD?  Only guilt by association - IETMs are generally attributed in this 
> country to the DoD, which is probably why S1000D rebranded them as IETPs 
> as they moved into the commercial aircraft market.
> 
> (Don't get me started on the whole IETM/IETP "they're completely 
> different" argument.)
> 
> -- 
> ==============================
> Michael R. Hahn
> ------------------------------
> michael@alphabyauthor.com
> ==============================
>

Received on Sunday, 29 December 2013 18:03:24 UTC