DITA v1.2 Review | Resource-only topicref referred through Reltable

The processing for a topicref that is marked as ‘resource-only’
using the @processing-role and is used as a referencing/referenced
topic in the reltable is not clear. Suppose there are two topicrefs – T1
& T2 in a map. T2 is  marked as ‘resource-only’.
And in the reltable, it is defined such that both of these topic has a link to
the other.

 

As I remember from some earlier discussion, for HTML the
behavior shall be as follows:

·        
Both T1 & T2 shall be built.

·        
After building, T1 becomes a direct part of the
output.

·        
After building, T2 just serves the linking purpose.

·        
After building, T1 shall have the link for T2. Hence,
the ‘resource-only’ topicref can act as a Target.

·        
After building, T2 shall have the link for T1. Hence,
the ‘resource-only’ topicref can act as a Source.

 

For PDF, the behavior is not clear. I think it shall be as
follows:

·        
Only T1 shall be built.

·        
After building, T1 becomes a direct part of the
output.

·        
After building, T1 shall not have a link
to T2. Hence, the ‘resource-only’ topicref cannot
act as a Target.

·        
T2 shall not be built. Hence, the ‘resource-only’
topicref cannot act as a Source.

If that is the case, then for PDF the usability of the ‘resource-only’
topicref gets limited to Conrefs & Images. It cannot be used for links
& xrefs.

 

Another approach for PDF could be:

·        
Both T1 & T2 shall be built.

·        
After building, T1 becomes a part of the primary
PDF output.

·        
T2 is built as a separate PDF & just serves
the linking purpose.

·        
After building, T1 shall have the link for T2. Hence,
the ‘resource-only’ topicref can act as a Target.

·        
After building, T2 shall have the link for T1. Hence,
the ‘resource-only’ topicref can act as a Source.

 

Regards,

Tarun Garg | Adobe Systems | +91-120-2444711 |