Ditaval + subject scheme: automatically filter parent subject
Posted: Wed May 10, 2017 3:13 pm
Hi all,
We're a bit stuck when working on a Taxonomy using a subject scheme. To try to understand this I've pulled out some demo data found at https://www.oxygenxml.com/doc/versions/ ... e-map.html
So the scheme is as follows:
And the DITAVAL is as follows, for demo purposes:
When profiling content (Select element, right click, edit profiling attributes) the audience attribute provides checkboxes as described by the scheme. When selecting a lower level subject to filter on, the parent is not automatically checked, which is okay I suppose as long as the processors can make the relation with the parent.
Question 1: When using 'Import from DITAVAL' to create a Profiling set, the filter in Author mode is applied as I would suspect: content flagged with 'novice', which is a novice therapist, is excluded. However, when running a PDF transformation with the DITAVAL set as filter it only excludes content tagged with 'therapist'. Why is this the case?
Question 2: Is it also possible to get this 'inherited filtering' when using the exclude unless included approach, e.g.:
Here's some demo content that I used:
Thanks you, kind regards,
Jochem de Vos
We're a bit stuck when working on a Taxonomy using a subject scheme. To try to understand this I've pulled out some demo data found at https://www.oxygenxml.com/doc/versions/ ... e-map.html
So the scheme is as follows:
Code: Select all
<subjectScheme>
<subjectdef keys="users">
<subjectdef keys="therapist">
<subjectdef keys="novice"/>
<subjectdef keys="expert"/>
</subjectdef>
<subjectdef keys="oncologist"/>
<subjectdef keys="physicist"/>
<subjectdef keys="radiologist"/>
</subjectdef>
<enumerationdef>
<attributedef name="audience"/>
<subjectdef keyref="users"/>
</enumerationdef>
</subjectScheme>
Code: Select all
<val>
<prop action="exclude" att="audience" val="therapist" />
</val>
Question 1: When using 'Import from DITAVAL' to create a Profiling set, the filter in Author mode is applied as I would suspect: content flagged with 'novice', which is a novice therapist, is excluded. However, when running a PDF transformation with the DITAVAL set as filter it only excludes content tagged with 'therapist'. Why is this the case?
Question 2: Is it also possible to get this 'inherited filtering' when using the exclude unless included approach, e.g.:
Code: Select all
<val>
<prop action="exclude" att="audience"/>
<prop action="include" att="audience" val="therapist" />
</val>
Code: Select all
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
<topic id="topic_vcz_2nm_vz">
<title>Test</title>
<body>
<p>Content marked with nothing</p>
<p audience="oncologist">Content marked with oncologist</p>
<p audience="therapist">Content marked with therapist</p>
<p audience="novice">Content marked with novice therapist</p>
</body>
</topic>
Jochem de Vos