Re: AQL for multi-occurrence nodes

Dear Thomas, Can you point me to details of Java structures regards Dileep V S *Founder* HealtheLife Ventures LLP m: +91 9632888113 a: 103, Innovation Centre, IIIT, Electronics City, Bangalore 560100 w: healthelife.in e: dil...@healthelife.in On Thu, Nov 2, 2017 at 8:12 PM, Thomas Beale

Re: Scenarios for change type "deleted"

In a versioned system there is no status for "deleted" necessary *inside* a composition. The system itself marks the composition deleted. With this in mind it seems to me the semantical meaning of the inside "deleted" status is meant for something else. Bert Op do 2 nov. 2017 20:01 schreef

Re: AQL for multi-occurrence nodes

Thanks everybody for the clarification. regards Dileep V S *Founder* HealtheLife Ventures LLP m: +91 9632888113 a: 103, Innovation Centre, IIIT, Electronics City, Bangalore 560100 w: healthelife.in e: dil...@healthelife.in On Thu, Nov 2, 2017 at 10:43 PM, Pablo Pazos

Re: Scenarios for change type "deleted"

I meant data using the criteria you outlined. Regards, Pieter Bos Op 2 nov. 2017 om 18:25 heeft Pablo Pazos > het volgende geschreven: Hi Pieter, What structure? On Thu, Nov 2, 2017 at 2:21 PM, Pieter Bos

Re: Scenarios for change type "deleted"

On 15/10/2017 12:49, Pablo Pazos wrote: Hi I'm trying to define a set of rules for a logical delete commit and have some gray areas that I'm not sure of. *1. commit after delete flow* [creation v1] => [modification v2] => [deleted v3] => ? Can a modification/amendment v4 happen after a

Re: Scenarios for change type "deleted"

Hi Pieter, What structure? On Thu, Nov 2, 2017 at 2:21 PM, Pieter Bos wrote: > You would be able to import this structure into our implementation and it > would work the same way. > > Pieter > > Op 2 nov. 2017 om 17:24 heeft Pablo Pazos

Re: Scenarios for change type "deleted"

You would be able to import this structure into our implementation and it would work the same way. Pieter Op 2 nov. 2017 om 17:24 heeft Pablo Pazos > het volgende geschreven: Until we have a clear criteria for commits after delete,

Re: Scenarios for change type "deleted"

Until we have a clear criteria for commits after delete, I'll use this: 1. lineal versioning (no branching) 2. "deleted" compositions can be "undeleted" using "modification" change type, since we don't have an "undelete" change type 3. if current latest version is "deleted" the composition won't

Re: AQL for multi-occurrence nodes

Hi - agree with Thomas and more here https://github.com/ethercis/ethercis/issues/69 Ian Dr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: i...@freshehr.com twitter: @ianmcnicoll Co-Chair, openEHR Foundation ian.mcnic...@openehr.org Director,

Re: AQL for multi-occurrence nodes

Hi Dileep On 27/10/2017 04:15, Dileep V S wrote: Hi, What is the expected response to AQL on a node with multiple occurrences? Does it return all the occurrences or only the first one? querying is always about returning everything that matches - it's a declarative concept, not a

Re:

Congrats Seref, Very valuable contribution! Tomaz From: openEHR-technical on behalf of David Ingram Reply-To: For openEHR technical discussions Date: Friday, 27 October 2017 at 13:28 To: