Hi Susan,Many thanks for this thorough information!Best regards,Frank

In addition to the overview table by @punagpal you should check whether advanced DITA mechanisms are supported by the respective publication pipeline, especially the indirect referencing mechanisms:key referencesconrefsconkeyrefsprofilingI have not yet tested the Native PDF pipeline in detail but I ...

Hi Divraj,Many thanks for this information. We tried to look this information up in the AEM Content Migration Guide available from https://helpx.adobe.com/support/xml-documentation-for-experience-manager.html but the manual is for AEM Guides 3.5 and dates from 2019 so it unfortunately is heavily out...

Hi,We faced a similar issue when moving our custom DITA-OT from a test environment that was on Windows to a Linux server. It is recommended to run the DITA-OT integrator script on Linux to avoid issues with path separators: https://experienceleaguecommunities.adobe.com/t5/experience-manager-guides/u...

Just for the record the detailed hints from @DivrajSingh: Using a custom DITA-OT for publishing | Things to remember  

The error message points to the general problem that the DITA-OT can have difficulties resolving references when the DITA map is not on top level. You might try creating a wrapper map on top level and create the output from that map. HTHFrank

Thanks for the pointer. A colleague had already given me that hint and it worked fine.

Found it: The conversion code is implemented in ConvertXMLToJSON.class within /libs/fmdita/osgi-bundles/install/publish-workflow-4.2.jar. The XML-to-JSON conversion is done directly in Java, without XSLT.

I found some hints in the fmdita-publigh.log:*DEBUG* [sling-oak-observation-2] com.adobe.fmdita.publishworkflow.ConversionWorkflowsListener Resource change handler triggered for /content/dam/fmdita-outputs/json/testContent*DEBUG* [JobHandler: /var/workflow/instances/server0/publishditamap_491:/conte...

The link to the blog post was broken, here is the working one: www.nateyolles.com/blog/2015/12/converting-aem-sling-resources-to-json