Nested ditamap

That's unfortunate. Sounds like the Publish command isn't working properly. It should treat the content the same, whether it's in one map or multiple maps. Is this with FM2017?

It's possible that there's some setting ("HonorNestedMaps"??), but I'm not very familiar with the way that works. Perhaps someone else will be able to provide more useful info.

If this doesn't do what you want, you might consider using the DITA-OT. It may or may not do what you want out of the box, but if not, you can customize it to do exactly what's needed.

...scott

When nesting maps, the map itself should impose no hierarchy. Basically all maps are merged into one big map and the map elements disappear. So, if what's inside of your maps is flat (all siblings), that's what you'll get when you publish. If you want the published topics to have a hierarchy (collapsing implies some type of hierarchy), you'll likely need someplace (a topic) for them to collapse into .. but fundamentally, that's up to the tool you're using to produce the HTML, which could be set up to do most anything you want.

To do what you're suggesting, I'd expect that the submaps would look something like this ..

<map>

<title>map title</title>

<topicref href="root-topic-1.xml">

<topicref href="topic1.xml"/>

<topicref href="topic2.xml"/>

<topicref href="topic3.xml"/>

</topicref>

</map>

You'll see that this adds a new "root" topic to each of the submaps. This gives someplace for the topics to collapse into. In general all submaps should have one root topicref. This isn't an absolute requirement, but will generally be closer to what you're expecting to get when you nest maps.

Hope that helps!

...scott