Hi,
Maybe you could also ask around on the DITA Users List as the DITA standard committee members are registered on it:
https://dita-users.groups.io/g/main
Let's try to start with a small example, a DITA Map containing this:
Code: Select all
<topicref href="topics/introduction.dita">
<topicmeta>
<othermeta name="test" content="value"/>
</topicmeta>
</topicref>
and a referenced "introduction.dita" simple topic:
Code: Select all
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
<topic id="introduction">
<title>Introduction</title>
<shortdesc>test</shortdesc>
<body>
<p>specific needs.</p>
</body>
</topic>
With the DITA OT 3.7 publishing engine I publish the DITA Map to HTML5 setting the "clean.temp=no" parameter and then I look in the transformation temporary files folder inside the "introduction.dita" topic and I find inside it:
Code: Select all
<prolog class="- topic/prolog "><metadata class="- topic/metadata "><othermeta class="- topic/othermeta " content="zuzu" name="test" xtrc="othermeta:1;7:46" xtrf=".../flowers.ditamap"/></metadata></prolog>
So the <othermeta> becomes part of the temporary topic file, meaning that an HTML XSLT customization could probably match it and create some HTML elements from it.
Looking at the specification link you gave me:
https://www.oxygenxml.com/dita/1.3/spec ... adata.html
there is a "Does it cascade to child <topicref> elements?" column and "<othermeta>" has value "no", this means for me that in this case:
Code: Select all
<topicref href="topics/introduction.dita">
<topicmeta>
<othermeta name="test" content="value"/>
</topicmeta>
<topicref href="someOtherTopic.dita"/>
</topicref>
the <othermeta> specified for "introduction.dita" does not cascade and become part also of "someOtherTopic.dita".
Regards,
Radu