Should keyref resolution output inline elements ?

[ruthrapr]

Hi,

I'm using a subjectScheme map to define labels. These labels can be plain text or a mix of text and inline elements. Such as

<subjectScheme>
    <subjectdef keys="46690">
        <topicmeta>
            <navtitle>First reference.</navtitle>
        </topicmeta>
    </subjectdef>
    <subjectdef keys="46691">
        <topicmeta>
            <navtitle>Second reference with a <b>bold</b> element.</navtitle>
        </topicmeta>
    </subjectdef>
</subjectScheme>

My topic uses ph element with a @keyref attribute to reference above defined keys, <ph keyref="46691"/>.

When the dita-ot resolved these ph elements, inline elements are removed from the output.

# Topic before resolution
<p>Case 2 <ph keyref="46691"/></p>

# Topic after resolution
 <p class="- topic/p ">Case 2 <ph keyref="46691" class="- topic/ph ">Second reference with a bold element.</ph></p>

The behavior is the same using pdf2 or html5 transformations.

I'm wondering is the behavior is the right one (inline elements not being resolved) or if it's a bug ?

sample.zip

[raducoravu]

According to the specification, keyrefs only pull plain text from the key definition:

https://www.oxygenxml.com/dita/1.3/specs/archSpec/base/processing-keyref-for-text.html

[ruthrapr]

Thanks @raducoravu I missed this information in the specification. Since navtitle allows inline elements, I was hoping to have them process too.

[raducoravu]

Right, for reusing anything with inline elements you would need conref/conkeyref.