🚀 go-pugleaf

In article 1879@gmd.de, thomas@gmd.de asks "Are you claiming that there
is a one-to-one mapping between FrameBuilder documents and SGML
documents?   Or only that some (or even most) SGML documents can be
mapped into FrameBuilder, and vice versa?

I don't believe that any SGML product on the market currently supports
100% of of ISO 8879, so I certainly won't make the claim for
FrameBuilder. FrameBuilder represents the SGML entity structure of a
document without using SGML syntax. There are several SGML constructs
which have no direct correspondence in FrameBuilder:

- I mentioned attributes in my previous message. These can be mapped
into several different FrameBuilder structures, depending on their
intended usage. There is no concept of current or content reference
attributes, however.

- FrameBuilder has no direct analog to the SGML entity structure.
FrameBuilder's Book handles documents divided into multiple files,
although each document in the Book must be a complete element, and
books cannot be nested.

- FrameBuilder does not support SGML's optional LINK and CONCUR features.

SGML documents using syntax-specific SGML constructs such as markup
minimization or CDATA and RCDATA marked sections can be imported into
or exported out of FrameBuilder fairly easily. These constructs are
irrelvant to the FrameBuilder model, however, and have no counterpart
within FrameBuilder.

FrameBuilder does have a construct analogous to INCLUDE, IGNORE, and TEMP
marked sections. This construct, called Conditional Text, however,
does not support spanning partial elements.

Since FrameBuilder is an application for formatting structured
documents as well as an editor for manipulating them, the question of
whether FrameBuilder supports all possible SGML structures is less
meaningful than whether it supports them in the intended way. Because
the conceivable applications are unlimited, SGML was deliberately
defined so that no one system could do so.

For example, while FrameBuilder recognizes graphics in many file
formats, thereby supporting several data content notations, it
certainly does not recognize every possible graphics format. As another
example, tables can be represented in many ways in SGML. Of course the
possible element structures can be represented as element structures
within FrameBuilder. What is wanted, though, is a representation within
the rich table facility that FrameBuilder inherits from FrameMaker.
Very little programming is required to move the SGML tables we have
seen at Frame to and from the FrameBuilder table mechanism.  In its
initial release, FrameBuilder internally supports elements that
correspond to entire tables and allows table cells to contain
hierarchies of elements.  There are no elements for table rows or
columns, however, and there is no content model defining the order in
which particular types of cells are expected to occur.

I hope this answers your questions.