Page 1 of 1
How can profiling condition values follow the transformed output?
Posted: Tue May 28, 2024 6:08 pm
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
Re: How can profiling condition values follow the transformed output?
Posted: Wed May 29, 2024 8:01 am
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
Re: How can profiling condition values follow the transformed output?
Posted: Wed May 29, 2024 1:30 pm
by ann.jensen
That's exactly what I was looking for, thank you Radu.
Regards,
Ann
Re: How can profiling condition values follow the transformed output?
Posted: Sat Jul 06, 2024 3:47 pm
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.