I don't remember that aspect of keydef being discussed either.
I did a search through all of the meeting minutes and the only thing that comes close is a mention of Alan working with the dtd and saying that "keydef had a lengthy set of attributes tied to it", and that he "asked for another set of eyes to look over his work to ensure that what he pruned was appropriate."
So no specific decision on keydef defaulting to resource-only was ever made, and it may well be inadvertent.
Cheers!
Sent: September 24, 2018 6:16:17 PM
To: dita-lightweight-dita@lists.oasis-open.org
Subject: Re: [dita-lightweight-dita] Keydef's processing-role in XDITA map
Mark Giffin
I'm honestly not sure of the answer on this one...
In full DITA, <keydef> allows processing roles of both "normal" and "resource-only". It defaults to "resource-only" and it's possible nobody has ever changed the default.
I noticed when helping fix up processing role here that in XDITA it only ever allows resource-only (that value is fixed). Not sure if that's intended as a way to prevent other uses, or just happened by some accident...
Robert D. Anderson
DITA-OT lead and Co-editor DITA 1.3 specification
Marketing Services Center
E-mail: robander@us.ibm.com
11501 BURNET RD,, TX, 78758-3400, AUSTIN, USA
Carlos Evia ---09/24/2018 02:38:52 PM---Dear LwDITA SC members, While Robert Anderson was helping me rename the new entity for topicref
From: Carlos Evia <cevia@vt.edu>
To: dita-lightweight-dita@lists.oasis-open.org
Date: 09/24/2018 02:38 PM
Subject: [dita-lightweight-dita] Keydef's processing-role in XDITA map
Sent by: <dita-lightweight-dita@lists.oasis-open.org>
Dear LwDITA SC members,
While Robert Anderson was helping me rename the new entity for topicref processing in the XDITA map grammar files, he noticed that keydef has a fixed role of "resource-only."
Is this on purpose? Should it be fixed?
Best,
Carlos
--
Carlos Evia, Ph.D.
Associate Professor of Communication
Virginia Tech
Blacksburg, VA 24061-0112
(540)200-8201
