I suggesting using Olinks without targetdoc attributes to avoid ID/IDREFs
warning.
I have not given much thought to how an olink database might relate to an assembly
structure. Now I will, though. 8^)
Bob Stayton
Sagehill Enterprises
[email protected]
----- Original Message -----
From: "Jirka Kosek" <[email protected]>
To: "Bob Stayton" <[email protected]>
Cc: "Thomas Schraitle" <[email protected]>; <[email protected]>
Sent: Monday, May 21, 2012 1:05 AM
Subject: Re: [docbook] Best Practise of Referencing Between Modules in
Assemblies?
You can use olinks right now. One of the most frequent uses of olinks
is for linking between modular content. Olinks let you avoid hard coding
filenames in your links, which can be troublesome to maintain if you
rename or move files.
Do you mean using OLinks without targetdoc attributes to avoid ID/IDREFs
warning when editing standalone modules or do you have any idea how
OLink database should relate to assembly structure and what should be
separate OLink target document from assembly point of view?
Although there are many benefits of OLinks I think that assembly should
also provide linking similar to one known from DITA which allows direct
linking to source XML file of module.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
