Topics

[EXT]: Re: [dita-users] Keyscopes?


 

A reusable approach is to use ditaval file to set parameters and then in the map, use <ditavalref> to insert the ditaval file within a key scope.

 

Mona Ross | Principal Information Architect | Ellucian® | M:+1.304.596.3712 | www.ellucian.com

CONFIDENTIALITY: This email (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this email in error, please notify the sender and delete this email from your system. Thank you.

 

From: main@dita-users.groups.io <main@dita-users.groups.io> On Behalf Of Thomas Rathkamp via groups.io
Sent: Saturday, August 8, 2020 10:43 PM
To: main@dita-users.groups.io
Subject: [EXT]: Re: [dita-users] Keyscopes?

 

**External Email**

What would do within a topic, though? Instead of applying an attribute within that file, would you repeat that DITAVal string in each instance? That appears to be more work. 



On Aug 8, 2020, at 6:04 PM, Chris Papademetrious <chrispitude@...> wrote:

Hi all,

I feel like it would be useful to be able to include DITAVAL directives inline in the map, instead of in files:

<map>

    <topichead keyscope="NoviceSection" navtitle="Novice Documentation">

        <ditaval>

            <prop att="audience" val="novice" action="include"/>

            <prop att="audience" val="expert" action="exclude"/>

            <dvrResourcePrefix>Novice-</dvrResourcePrefix>

            <dvrKeyscopePrefix>Novice-Scope</dvrKeyscopePrefix>

        </ditaval>

        <mapref format="ditamap" keyref="..."/>

    </topichead>


My thinking is,

  • This allows the branch filtering intent to be visible *and* editable directly where the content is instantiated, instead of requiring side files.
  • DITAVAL used for branch filtering is likely to be single-variable and simple (2-3 directives).


Thoughts?

 - Chris