On 4/21/09 9:44 AM, "Robert D Anderson" <> wrote:
>
> Recently we approved adding the new processing-role attribute, with values
> of "normal" and "resource-only", to topicref and its specializations. Use
> of processing-role="resource-only" indicates that the target is to be used
> only as a resource, without appearing in any generated TOC, not linked to,
> not generated as part of PDF/XHTML/whatever other output.
>
> We also have a new <keydef> element as a shortcut for defining keys in DITA
> 1.2. It defaults to toc=no, linking=none, and print=no. So my question is,
> should it also default to processing-role=resource-only? This seems
> logical, and in fact seems part of the reason we added resource-only, but I
> don't think it was called out in the original discussion.
I think resource-only would be the appropriate default for keydef--it's
certainly what I would want it to be, I think.
I think we're trying to make a clear logical distinction between topicrefs
that function *only* as indirectors to resources (keydef) and topicrefs that
happen to have keys.
If this wasn't the default I would probably define for myself a
specialization of topicref that simply grouped keydefs and set the default
for processing-role to "resource-only", e.g. <keyset> or something.
Cheers,
Eliot
----
Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc.
email: <mailto:>
office: 610.631.6770 | cell: 512.554.9368
2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403
www.reallysi.com <http://www.reallysi.com> | http://blog.reallysi.com
<http://blog.reallysi.com> | www.rsuitecms.com <http://www.rsuitecms.com>
