Stacking profiling conditions/DITAVAL files

[rich_mason]

Is it possible to invoke multiple ditaval files on a single book map transform, or otherwise "stack" conditional processing rules?

Let's say I have 20 products, each with it's own ditaval file that is applied to a set of docs for each of my 20 products. Now, for all of these docs, I need to be able to easily toggle <revprop> styling to turn revision markup on/off depending on publication requirements. Does this mean I *must* create a new ditaval file for each revprop state, for each product, or is there a way to invoke one of my existing ditaval file, and apply some additional rules at build time?

I'm sure I can hack the DOTK to enable/disable revprops at build time, but this is undesirable. It would be ideal to be able to specify "use rules set 1 AND rule set 2", I'm just not sure if how...

[Radu]

Hi Rich,

Yes, it's possible to use two or more DITAVAL files at publishing time, it's kind of hidden right now but it works:

viewtopic.php?f=1&t=15444&p=45473#p45482

We'll update this forum thread when this usecase will be easier to achieve using Oxygen's UI.

Regards,
Radu

[rich_mason]

Thanks, Radu! That's working great.

One related question that you might have some insight on, being the DITA-Master that you are -- I'm using a specialization of @props (I would use @rev, but it doesn't allow action="exclude", an option I require). I'm seeing deleterious effects in any attempt to apply conditional flag styling via ditaval file to elements with the specialized @props. While action=include/exclude works just fine, if I set action=flag and apply a style via the backcolor/color/style attrs, not only does the style fail to materialize, it disables all other styles applied in this manner to any profiling attrs (audiene, platform, etc.) used in the topic. This happens in my personal DOTK plugins, as well as the OOTB plugins that come with Oxygen 23.0. Not sure if this is a bug, limitation, or what, but it's certainly odd.

[Radu]

Hi Rich,

Maybe you can try to create a small DITA project to reproduce the problem, then download the latest DITA OT 3.6 from the DITA OT web site:

https://www.dita-ot.org/download

Then try to publish using it the sample project to HTML5, see if the problem can be reproduced. If it can be reproduced maybe you can add an issue on the DITA OT issues list:

https://github.com/dita-ot/dita-ot/issues

Regards,
Radu