| [mdht-dev] Bug in MDHT? |
|
Hi All, We have identified a potential bug in DITA generation in MDHT.
In a section, where an entry is typed to a template that is defined externally, then the following text prefaces the parent constraint: “If section/@nullFlavor is not present,” . Issues: 1.
This text appears only where a CDA class is typed to an externally defined template - the text does not appear when typed to an internally defined template or an inline class. The wording of this text infers additional normative content
and is therefore problematic that it should be included or excluded for reasons based on reuse practices instead of normative meaning. 2.
The above text is included even when @nullFlavor has been explicitly prohibited for that section. The inclusion of the text is misleading as it implies that @nullFlavor is allowed for that section. 3.
A section with a nullFlavor does not have to mean that it cannot have an entry Can we not include this text if it is a bug? Thanks David Cai Strategy, Architecture & Informatics Group The information contained in this e-mail message and any accompanying files is or may be privileged or confidential. If you are not the intended recipient, any use, dissemination, reliance, forwarding, printing or copying of this e-mail or any attached files is unauthorised. This e-mail and any attachments may be subject to copyright. Copyright material should not be reproduced, adapted or communicated without the written consent of the copyright owner. If you have received this e-mail in error please advise the sender immediately by return e-mail or telephone and delete all copies. NEHTA does not make any representations or give any guarantees in respect of the accuracy or completeness of any information contained in this e-mail or attached files. Internet communications are not secure, therefore NEHTA does not accept any liability for the contents of this message or attached files. |