Hi Bert, it always helps me to make correspondences between the AOM and UML 
class models (they are basically the same thing).
If you look at this: 
http://www.openehr.org/wiki/download/attachments/196630/openehr_entry_uml.jpg?version=1&modificationDate=1193397393000You'll
 note the [0..1] and [1] on attributes, that's the "existence", and the 
"occurrence" is the cardinality on relationships (that's for relationships that 
are no collections, i.e. single_attributes) (e.g. 0..1 in the 
ACTION.instruction_details relationship with INSTRUCTION_DETAILS).
Also, "CMultipleAttribute.cardinality" for collection attributes is the 
"cardinality" on UML relationships like "INSTRUCTION.activities" or 
"ENTRY.other_participations".
Hope that helps.

-- 
Kind regards,
Ing. Pablo Pazos Guti?rrez
LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez
Blog: http://informatica-medica.blogspot.com/
Twitter: http://twitter.com/ppazos

> Date: Sun, 6 Jan 2013 16:51:00 +0100
> From: bert.verhees at rosa.nl
> To: openehr-technical at lists.openehr.org
> Subject: csingleattribute and existence
> 
> Excuse me the following question, maybe I am just looking over the 
> answer all the time
> 
> What is the use of both together existence and occurences in case of a 
> CSingleAtttribute.
> 
> And what if both have conflicting information?
> 
> For example, existence gives REQUIRED and occurrences gives minOccurs=0
> 
> Thanks for a short answer
> 
> Bert
> 
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
                                          
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130110/2f19ef1b/attachment.html>

Reply via email to