RE: [dita] processing-role attribute [cascading]

Would it always cascade?  Would it cascade
from a keydef? My head is starting to hurt again.

 

   -Jeff

 

From: Michael
Priestley [mailto:] 

Sent: Tuesday, April 21, 2009
11:23 AM

To: Ogden, Jeff

Cc: dita; Robert D Anderson

Subject: RE: [dita]
processing-role attribute [cascading]

 

Actually it could be quite useful for processing-role
to cascade. For example: 

Author
A creates a single map that defines both a TOC and the keys for the topicrefs
in the TOC (not using keydef - just a single TOC with a key on each topicref)

Author
B wants to reuse a bunch of the topics but their own nav. So they want to use
the key definitions in author A's map but not the nav structure. So they create
a mapref (or a conref to a subset of the target map) setting
processing-role="resourceonly". 

 

Michael
Priestley, Senior Technical Staff Member (STSM)

Lead IBM DITA Architect 



http://dita.xml.org/blog/25 

 

  
  
"Ogden, Jeff"
  <> 

  
04/21/2009 11:12 AM 

  
  
  
   

    
    
To

    
    
    
"Robert D Anderson"
    <>, "dita"
    <> 

    
   

   

    
    
cc

    
    
    
 

    
   

   

    
    
Subject

    
    
    
RE: [dita] processing-role attribute
    [cascading]

    
   

  
  
 

  
   

    
    
 

    
    
    
 

    
   

  
  

  
 

I've got cascading on the brain and so ...

 

I
assume that @processing-role itself does not cascade. 

 

But
does @processing-role="resource-only" change the cascading behavior
for any other attributes or other properties? 

 

Cascading
within a map? 

Cascading
from map to map? 

Cascading
from map to topic? 

 

 
 -Jeff 

 

>
-----Original Message----- 

>
From: Robert D Anderson [mailto:] 

>
Sent: Tuesday, April 21, 2009 10:45 AM 

>
To: dita 

>
Subject: [dita] processing-role attribute 

>

>

>
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. 

>

>
Thanks - 

>

>
Robert D Anderson 

>
IBM Authoring Tools Development 

>
Chief Architect, DITA Open Toolkit 

>

>

>
---------------------------------------------------------------------

>
To unsubscribe from this mail list, you must leave the OASIS TC that

>
generates this mail.  Follow this link to all your TCs in OASIS at:

>
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php