How can profiling condition values follow the transformed output?

Post here questions and problems related to editing and publishing DITA content.
ann.jensen
Posts: 309
Joined: Wed Jun 17, 2015 10:19 am

How can profiling condition values follow the transformed output?

Post by ann.jensen »

Hi,
Currently profiling conditions are used to include/exclude content in the output but do these values or can these values exist in the transformed output (Oxygen transforms) as metadata values so that they can be interpreted by LLMs?
Thanks in advance,
Ann
Radu
Posts: 9164
Joined: Fri Jul 09, 2004 5:18 pm

Re: How can profiling condition values follow the transformed output?

Post by Radu »

Hello Ann,
Usually the ditaval filter has one or multiple <prop> elements with action="exclude". There is also an action="passthrough" value which implies that the profiling attribute values should be passed through to the HTML5 output as "data-*" attributes, so maybe you can experiment with that:
https://www.oxygenxml.com/dita/1.3/spec ... -prop.html
Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
ann.jensen
Posts: 309
Joined: Wed Jun 17, 2015 10:19 am

Re: How can profiling condition values follow the transformed output?

Post by ann.jensen »

That's exactly what I was looking for, thank you Radu.
Regards,
Ann
chrispitude
Posts: 914
Joined: Thu May 02, 2019 2:32 pm

Re: How can profiling condition values follow the transformed output?

Post by chrispitude »

Hi Ann,

We are also starting to use action="passthrough" to pass directives to LLM processing. However, we recently found a serious (for us) bug:

#4488: DITAVAL "passthough" action does not work for profiling applied to an attribute group (github.com/dita-ot/)

If you are not using attribute groups (profiling conditions that use parentheses), then this bug would not affect you.
Post Reply