Awesome, I'll add this to the TD JIRA. Do anyone remember where that JIRA is?
-- Kind regards, Eng. Pablo Pazos Gutiérrez http://cabolabs.com From: [email protected] Date: Mon, 4 May 2015 11:07:54 +0100 Subject: Re: Template Designer - remove slot To: [email protected] ok thanks all. This looks like a TD limitation then. IanDr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: [email protected] twitter: @ianmcnicoll Co-Chair, openEHR Foundation Management BoardDirector, freshEHR Clinical Informatics Director, HANDIHealth CIC Hon. Senior Research Associate, CHIME, UCL On 4 May 2015 at 08:22, Seref Arikan <[email protected]> wrote: It makes perfect sense to me. A slot is part of the model. The constraint mechanisms of ADL work on the types of RM. Closing a slot or setting occurrence to 0 would both leave the model intact but constrain the set of instances compatible with the model. I'd classify this as further constraining the model. Removing the slot would create another model, or at least that is how I'd see it. On Mon, May 4, 2015 at 7:29 AM, David Moner <[email protected]> wrote: As far as I understand it, the AOM/ADL 2 "close" statement avoids including further archetypes into a slot, but do no remove it. To do that, we have to put its occurrences to 0..0, which is perfectly legal in AOM/ADL 1.4 (unless the original slot has a minimal occurrence >=1, of course). 2015-05-03 9:27 GMT+02:00 Ian McNicoll <[email protected]>: Hi Pablo, This is not possible. The ability to 'close' a slot comes with ADL1.5/2 IanDr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: [email protected] twitter: @ianmcnicoll Co-Chair, openEHR Foundation Management BoardDirector, freshEHR Clinical Informatics Director, HANDIHealth CIC Hon. Senior Research Associate, CHIME, UCL On 3 May 2015 at 03:49, pablo pazos <[email protected]> wrote: Hi, I'm creating a template from the Encounter archetype using the TD. That archetype has a slot in the compo.context.other_context. I don't use that slot so I don't want it to appear in my final OPT, but I couldn't find any way in the TD to let me remove that node or put 0..0 on the cardinality, so the exported OPT has the slot. Is there any way to do this? Maybe other OPT designers? I'm using TD v2.6.1214Beta Thanks! -- Kind regards, Eng. Pablo Pazos Gutiérrez http://cabolabs.com _______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org _______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org -- David Moner Cano Grupo de Informática Biomédica - IBIME Instituto ITACA http://www.ibime.upv.eshttp://www.linkedin.com/in/davidmoner Universidad Politécnica de Valencia (UPV) Camino de Vera, s/n, Edificio G-8, Acceso B, 3ª planta Valencia – 46022 (España) _______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org _______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org _______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
