Early feedback on Issue 670, Impose Role

[Robert Anderson <robert.dan.anderson@oracle.com>]

Hi all,

As discussed at the TC this week, I'm sending along the draft of the "impose role" topic. It's the proposal for an actual defined way to manage the behavior that is currently described here:

http://docs.oasis-open.org/dita/dita/v1.3/errata02/os/complete/part1-base/archSpec/base/cascading-of-roles-in-specialized-maps.html#cascading-of-roles-in-specialized-maps

Based on discussion at TC, I've set up a new attribute to control this, called "imposerole". I really do not want to use yes/no values because that has bitten us several times in the past, when we suddenly discover there is a third option. So I've picked a couple of tokens that more or less make sense to me:

• keeptarget == whatever the target is, it stays that. You don't impose your role. So if you reference a generic <topicref>, you end up with a generic topicref.
• overridetarget == override whatever the target is. If you are a chapter and you reference a generic <topicref>, you impose your role and end up with a chapter.

Do those make sense, or does anyone have a better set of tokens?

Thanks,

Robert

Attachment: Issue670-ImposeRole.pdf
Description: Issue670-ImposeRole.pdf