Structured FrameMaker 11 Not recognizing new root element - not importing xml

[defaultxhawfx4ep50f]

We have issue with an xml file imported into Structured FrameMaker 11 getting hung up and not importing into the FrameMaker template. We believe that it may have something to do with the new root element not being recognized by FrameMaker.

We’ve checked the root element name in the dtd, the xsl, edd, and structured app definition and they all match. The structued app definition is mapped correctly.

With the template opened, in StructuredTools > Set Structured Application…, when I try to set the structured application root element:

the root element appears in the look-up menu:

But when I select it, it does not accept the new root element that I selected:

It will accept one of the existing root elements in the menu:

Any suggestions on how to resolve this will be appreciated.

[Russ Ward]

Hi, I haven't worked with these configurations for a long time. And your version of FM is quite old, so I can't really say exactly what is the expected behavior. But I was thinking that it might have something to do with the DOCTYPE specification in the application definition. Maybe you already considered that. I found the following in the help related to XML Schema, but maybe it applies to DTD applications as well. It speaks of the dialog box that appears when opening a markup file, but maybe the concepts are the same. I can't replicate the behavior, but I am using a newer version of FM so I don't know. Hope this helps, maybe at least some.  -Russ

[defaultxhawfx4ep50f]

Thanks for the response.

This is how it is set up in the structapp:

[frameexpert]

Does your EDD specify the desired element as Valid at the Highest Level?

[defaultxhawfx4ep50f]

Yes. Here it is:

[Russ Ward]

With regrets, I have to say that I have no better ideas. The only other thing that comes to mind is the possibility of conflicts with other structured applications, maybe applications that ship with FrameMaker. In my case, I had to disable everything DITA to get my structured applications to work right, but I guess DITA does not apply in your case. Maybe make sure that the default applications are not somehow interfering. You could temporarily change the syntax of the root element to see if there is something peculiar about the word "Institutional".  Otherwise, you seem to know what you are doing... I hope you get it figured out.

[Matt-Tech Comm Tools]

Hopefully it's just semantics, but you mention setting the custom application root element...

You're not setting the element, but merely specifying the application to use. Changing the name of the structured application might avoid a little confusion on that point, at least on our end.

Assuming the root element is Institutional and that it's case-appropriate (Institutional, not institutional, since fund is not initially capitalized), then it's likely that your structured application has an issue.

Have you had success setting up other structured applications in the past?