Hi Koray,
I am not sure if I understand the detailed questions fully, however, I
think that you should keep in mind that the archetypes should be
"generic" as possible. Archetypes are intended to be reused, and if I
read e.g. your issues for a {3..8} cardinality I get the impression that
this could be valid for a specific application. In this situation I
would suggest to make the archetype generic e.g. {0..N}, and configure
your application in terms of (business) rules (constrains on the
association).
If you need more information please provide a little more information
about your requirements and the application in which you need this...
regards
Roel
Roel Stap
TNO-ICT
Colosseum 27
7521 PV Enschede
+31 53 4835212
+31 6 10968787
http://www.tno.nl/ict
DISCLAIMER
http://www.tno.nl/disclaimer/email.html
-----Original Message-----
From: [email protected]
[mailto:openehr-technical-bounces at openehr.org] On Behalf Of Koray Atalag
Sent: maandag 8 januari 2007 12:10
To: For openEHR technical discussions
Subject: Re: Problem in some sample archetypes and questions
Stap, R.E. (Roel) wrote:
> Hello Koray,
>
> Reading your issues around cardinallity, perhaps you can solve this
> issue with help of constrains/business rules. E.g. if you consider in
> the Archetype model the ability to have a cardinality between A and B
> of (0..N), you can constrain practically this cardinality to a maximum
> of e.g. 4. The risk of modelling you cardinalities so precise in the
> archetype model is that if in future this is changed, your system
> (e.g. database schema's or applications) needs to be updated if this
> cardinality changes. If you are able to define the reason of this
> cardinality in rules you may create the flexibility in future to adapt
> this without changing systems or applications. I am not sure if this
> will help you, but consider this mechanism to handle cardinalities
issues.
> I hope this may help you in finding a solution for your issue,
>
> regards
> Roel
>
>
Hi Roel,
Thanks for the information you provided; especially the one about the
effect of archetype design on the resulting software and database
schema. I would still like to take your attention to my specific
questions 2 and 3. These point out to very detailed aspects of archetype
design - ones that most probably will never encounter while designing
their archetypes.
Best regards and Bedankt!
-koray
_______________________________________________
openEHR-technical mailing list
openEHR-technical at openehr.org
http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
This e-mail and its contents are subject to the DISCLAIMER at
http://www.tno.nl/disclaimer/email.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Stap, R.E..vcf
Type: text/x-vcard
Size: 248 bytes
Desc: Stap, R.E..vcf
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20070108/25261561/attachment.vcf>
-------------- next part --------------
_______________________________________________
openEHR-technical mailing list
openEHR-technical at openehr.org
http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
