OASIS Open Mailing List Archives  ·  All Lists  ·  dita  ·  2011-03

dita — archive

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]

Question on


Is there a reason why the content model for the <required-cleanup> element is different for the various information types: concept, task, and reference? Best regards, Kris Kristen James Eberlein l DITA Architect and Technical Specialist l SDL Structured Content Technologies Division l (t) + 1 (919) 682-2290 l [email protected] Please consider the environment before printing this e-mail From: Kurt Van Deun Sent: Monday, March 14, 2011 10:48 AM To: Kristen Eberlein Cc: Dirk Van Tichelen; Raf Snijders Subject: Question on required-cleanup Hi Kris, According to the DITA 1.2 specs, one should be able to add the <required-cleanup> element directly within the body of a topic, concept, reference and tasks. However, when trying this in XMetaL 5.5 (file-system based outside of SDL Trisoft), we noticed the following behavior: it is supported on concept, but not on task nor reference. So the following is VALID : < concept id="concept_D764BE690ADC455C80793C0A5004EBFF"> <title>…</title> <shortdesc>… </shortdesc> <conbody> <required-cleanup>…</required-cleanup> </conbody> </concept> And the following is INVALID : < reference id="reference_0950023AD955446AB38164F2E0291EA5"> <title>...</title> <shortdesc>...</shortdesc> <refbody> <required-cleanup>…</required-cleanup> </refbody> </reference> When looking in the .MOD files, we noticed that conbody.content references body.cnt which contains required-cleanup. But the refbody.content and taskbody.content don’t. Could you find out what’s behind this? Thanks, Kurt Van Deun Director of Customer Services SDL Structured Content Technologies Division +32 (0)15 400 970 [email protected]

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]