Hello!
Because in-content profiling conditions support a space-separated value list, I also assumed that DITAVAL files did too:
<prop action="" att="audience" val="a b"/>
However, experimentation with the DITA-OT suggests that it does not.
In the DITA 1.3 spec at
the description for @val indeed references a singular "value":
The value to be acted upon. If the @val attribute is absent, then the <prop> element declares a default behavior for any value in the specified attribute.
Given the asymmetry of multi-value support between content profiling conditions and DITAVAL filtering profiling conditions, maybe it's worth clarifying this aspect a bit more explicitly in the 2.0 spec? If you prefer to keep the spec lean and mean, that's fine too.
Thanks!
Â- Chris