Skip to main content
13-Aquamarine
June 10, 2014
Question

From a publication module, how to print a set of xml Documents?

  • June 10, 2014
  • 3 replies
  • 2952 views

I have a publication module which contains references to xml documents.

From the Publication Module, how to create a book?

What is the FOSI methodology to display in a book, the content of the XML documents using the references of the Publication module?

3 replies

12-Amethyst
June 11, 2014

Is the publication module an xml document?

Is there a dtd or schema that describes the structure of these xml documents and/or the publication module?

Is your book based on PDF output, Postscript output, HTML output, other?

A FOSI is a document used to style the elements of your documents.

The FOSI can style for the view in the Editor window, and other forms of output.

It is used to describe page layout, vertical spacing of elements, line indent, alignment, character font, size, weight, color, etc.

Tim

dgopois13-AquamarineAuthor
13-Aquamarine
June 11, 2014

Hi,

It's the same principle as the DITA model. In a Ditamap or a Bookmap document, there are references to Topics. I'd like to understand the mechanism that displays the contents of the Topic document when I print a Bookmap.

David

12-Amethyst
June 11, 2014

For DITA, a resolved document is created from the map file (referencing file).

The resolution of the referenced topics, concepts, etc. are then processed to follow the structure defined by the ditabase dtd. The resolved document is passed to the composition engine pipeline. In the pipeline graphics formats are converted as needed, profiling is processed, and the styling is applied to the elements, which includes the building and formatting of TOCs, list of Tables, Figures, Indexes, etc.. The styling is defined by the FOSI. Each element has styling of some sort applied to it. The formatted material is paged and the final result is generated output. The output can be Postscript, PDF, HTML, RTF, etc.

FOSIs can be very complex, as can book content.

Do you have specific areas of interest?

Tim

1-Visitor
September 30, 2014

This is a good question to which I'd also like an answer. In the S1000D Issue 4.1 Bike Data Samples you have "PMC-BRAKE-C3002-EPWG1-00_000-01_EN-US.XML" for example which contains references data modules via pmEntry, here's the first entry:

<pmEntry>

<dmRef xlink:actuate="onRequest"

xlink:href="URN:S1000D:DMC-BRAKE-AAA-D00-00-00-00AA-00WA-D_001-00"

xlink:show="replace" xlink:type="simple">

<dmRefIdent>

<dmCode assyCode="00" disassyCode="00" disassyCodeVariant="AA"

infoCode="00W" infoCodeVariant="A" itemLocationCode="D"

modelIdentCode="BRAKE" subSubSystemCode="0" subSystemCode="0"

systemCode="D00" systemDiffCode="AAA"/>

<issueInfo inWork="00" issueNumber="001"/>

<language countryIsoCode="US" languageIsoCode="en"/></dmRefIdent>

<dmRefAddressItems>

<dmTitle>

<techName>Mountain bicycle</techName>

<infoName>Applicability cross-reference table</infoName>

</dmTitle>

<issueDate day="31" month="12" year="2012"/></dmRefAddressItems>

</dmRef>

</pmEntry>

I would like to know how to resolve the dmCode entry and publish the PMC file in Styler. That way I can open a Data Module in Styler and publish to Web or HTML from the file menu in Arbortext Editor.

1-Visitor
September 30, 2014

By the way I realize that the URN is there "DMC-BRAKE-AAA-D00-00-00-00AA-00WA-D_001-00" but the question is, how does one make use of the pmEntry in Styler where we want to publish to web for example and capture all of the the DMs in the PMC in the publication?

1-Visitor
September 30, 2014

You know David, it seems that the PMC is little more than a file list. One strategy would be to not combine it at all and instead transform it into a menu or list of links; in that scenario, each Data Module referred to by the PMC would need to be converted to HTML separately.