That makes a lot of sense and mirrors the current version of the attribute connected to keydef in the XDITA map... Carlos -- Carlos Evia, Ph.D. Director of Professional and Technical Writing Associate Professor of Technical Communication Virginia Tech Blacksburg, VA 24061-0112 (540)200-8201 On Sat, Feb 10, 2018 at 8:40 AM, Alan Houser <
arh@groupwellesley.com > wrote: I'll weigh in on the -dita-use-conref-target issue. While this attribute is essential for using <navtitle> from conref'ed topics, I think that is a defensible full DITA use case. So I'm fine with @processing-role values of "normal" and "resource-only" for topicref. Or ... do we only need "resource-only", because the absence of @processing-role signals "normal" (default processing)? -Alan On 2/6/18 3:08 PM, Carlos Evia wrote: Dear Lightweight DITA SC members, I need help with a couple of items related to adding @processing-role to topicref in XDITA. 1- @processing-role actually exists as an attribute of keydef in the XDITA map mod. It is a fixed att with value of 'resource-only.' We need to declare it for both elements now. 2- What values should @processing-role have as attribute of topicref? In 1.3 we have normal, resource-only, and -dita-use-conref-target. I assume that the conref target is a no-no value in XDITA, right? This is the only change missing before we can build the new package for TC vote next week... so I will appreciate anyhelp/volunteers to update the DTDs. Best, Carlos -- Carlos Evia, Ph.D. Director of Professional and Technical Writing Associate Professor of Technical Communication Virginia Tech Blacksburg, VA 24061-0112 (540)200-8201 -- Alan Houser Group Wellesley, Inc. Consultant and Trainer, Technical Publishing arh on Twitter 412-450-0532