Import SGML; ATA iSpec DTD

[Kristofer L.]

I'm looking at using Frame in order to publish/distribute data in a more searchable and user-friendly format. An aircraft manufacturer X-inc makes available some documentation in SGML. Beginning with what appears to be the simplest example, the wiring list that contains no figures or graphics, contains the following files:

• SGML declaration file : SGML/WM.SDL
• ATA WMLIST DTD file : SGML/WM.DTD
• WMLIST document instance file : SGML/WMLIST.SGM
• WMLIST graphic entity file : SGML/WMLIST.SGE
• WMLIST companion entity file : SGML/WMLIST.CFE 

The DTD file begins with: 

<!-- DOCTYPE wm [ -->
<!-- The following set of declarations may be referred to
using a public entity as follows:
<!DOCTYPE wm PUBLIC
"-//ATA-TEXT//DTD WM-VER15-LEVEL2//EN" [ ]> -->

The SGM file begins with: 

<!DOCTYPE WM PUBLIC "-//ATA-TEXT//DTD WM-VER15-LEVEL2//EN" [
<!ENTITY % graphics SYSTEM "WMLIST.SGE" >
%graphics;
<!ENTITY % companions SYSTEM "WMLIST.CFE" >
%companions;
]>

ReadMe instructions included in the compressed package state:

"The DTD is called out from the document instance using a public ID.
Therefore the DTD file must not be specified in the parsing command but
using a catalog file, as all entities files also called out from
the document instance.
Consequently the WMLIST catalog file aims at giving the link between :
- public ID provided in the DTD and the corresponding system file
- graphic entity file(WMLIST.SGE) and the corresponding system file
- companion entity file(WMLIST.CFE) and the corresponding system file
Each illustration file is delivered with its SGML companion file that
gives a SGML representation of what can be found within
the illustration file.
Finally, the ATA SGML declaration file (WM.SDL) must be used in
the parsing command, as the capacities contained in the standard SGML
declaration file are not sufficient."

I have tried multiple variations of editing the structured application DocBook and inserting my relevant entity files into the pre-existing folder location. The closest I get to being able to open the .sgm file produces the error: "Could not find external document type WM (-//ATA-TEXT//DTD WM-VER15-LEVEL2//EN)." Is it possible to import this data in a manner that will let me accomplish my goal or at least publish to pdf? I would like to be able to query "~all wires that share x attribute" or "~all wires that connect to x".

[Matt S - Tech Comm Tools]

The ReadMe instructions are explaining what must be configured in your structapps file.

You are currently using the DocBook structapp, but will need to either develop or acquire a custom structapp for the ATA.

On the off chance that X-inc is Boeing, you should be able to license the structapp and the connectors to their system. If X-inc is not Boeing, you'll need to learn to develop, and then develop structured applications in FrameMaker and/or contract with someone to develop this custom structapp for you.