dita — archive

[Robert Anderson]

Hi JoAnn, I think Eliot already answered your correctly, but you asked for a simple answer to this question: > > Is DITA 1.2 going to mess up all the conrefs we have set up in DITA 1.1 > > between ditabase or topic and Task? The simple answer is "No." Trying to explain things as simply as I can - the only time that constraints affect conref is: 1) The conref goes between files with two different document types 2) The files include a matching topic type or domain (for example, both include task or both include the highlighting domain) 3) One of the common modules has a constraint (such as the strictTask if both use task, or a constraint to remove bold from the highlight domian) 4) The element that uses conref is in the file with the constraint - meaning that the file trying to pull content removes elements, but the file *with* the content does not I'm guessing that still isn't perfectly clear, because this is never going to be simple to explain architecturally, just like the class attribute and specialization take a while to get your head around when first introduced. Hopefully it helps though. It also shows that Su-Laine's example will continue to work. If you store common items in a topic, you will still be able to pull them into a strict task or a general task, and vice versa. The original topic does not include the task module, so any constraint on the task module is irrelevant for the purposes of conref. Robert D Anderson IBM Authoring Tools Development Chief Architect, DITA Open Toolkit ekimber