Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdht-dev] Proposed new capability
Morning -
I think this should not be to difficult and extension using existing structures - if we modify the terminology constraint logic to interpret the shall not to generate the appropriate ocl and dita

so create a value set with values, set the value set constraint on the attribute, set it to SHALL NOT in the severity

Thanks

Sean

On May 24, 2016, at 12:26 AM, David Cai <David.Cai@xxxxxxxxxxxx> wrote:

Hi All,
 
Currently you can prohibit an element by setting severity to SHALL and multiplicity to [0..0]. The constraint in DITA will come out as …SHALL NOT contain xxx [0..0].
 
The proposed new capability will extend the “SHALL NOT” capability to more than just multiplicity, but values. For example:
-          Modelling that statusCode SHALL NOT equal “ceased”
-          Modellign that code/@code SHALL NOT equal “02”
-          Modelling @nullFlavor SHALL NOT equal "NI", "UNK", "ASKU", "NAV", "NASK", "MSK", or "NA"
 
Currently this type of constraints are modelled via an ANALYSIS constraint and require custom OCL. It would make modelling a lot easier if this type of content can be set in the model. This type of constraint/validation may also extend to include SHALL, SHOULD, SHOULD NOT, and MAY.
 
Any comments will be appreciated.
 
Thanks
David Cai
Business Analyst
Strategy, Architecture & Informatics Group
nehta - National E-Health Transition Authority 
Office address
Phone: (07) 3023 8598 
Fax: (07) 3023 8466
Email: david.cai@xxxxxxxxxxxx 
Web: www.nehta.gov.au
 


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. _______________________________________________
mdht-dev mailing list
mdht-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdht-dev

Back to the top