This is an added question to my previous question. The framemaker documents are structured. Can a text inset be used in a structured document?
Yes, in a structured document you can have structured insets.
what is the structured element that would be used? My lead is concerned it is not defined in the EDD.
To create an inset, place your cursor where you want the inset and use what you would in a standard paragraph-based doc...File > Import > File, and then choose Import by Reference.
The content will come in, and if the elements in the inset are not defined in your EDD, you'll see a NoName element for the undefined element labels.
Here's what it looks like when my students bring in a structured inset in my structured authoring course:
Note that the parent element is undefined, but the sections are part of their current EDD.
I need to convert the text to SGML. Will the NO NAME element convert to SGML?
The root element in your inset should be something that is defined in your EDD.
If you wind up with a NoName element that you do not want in SGML, you can use the following r/w rule to get rid of it:
fm element "NoName" unwrap;
To clarify a bit on Matt's reply, if the text inset is to a structured FrameMaker file (or flow), it must have a single root element. FrameMaker uses NoName as the tag of the root element, if the user hasn't provided another tag. Once the text inset is created, its content is valid or not according to the element definitions in the containing document. The Structure View will show any validation errors for elements in the text inset just as it does for any other element. Thus, if the inset contains a NoName element and NoName is not defined, it will be shown in red. You can, of course, define NoName, or something like SectionGroup (or use a Chapter with no Title) in a variation of Matt's example.