On Thu, 2008-06-05 at 11:36 +0930, Heath Frankel wrote:
The v1draft convention is already deprecated. The BNF for AQL doesn't
support it deliberately, to ensure only non-draft archetypes are used when
committing/retrieving data.
Heath
The previously referred to AQL BNF carries this
Hi Gerard,
I 'm afraid I agree with Tim on this one. The difference between
'breaking' Version changes and non-breaking Revisions is clearly
documented in the specification. The reason for confusion and non-use
within the NHS is simply that the current tools do not support
Revisions. Now that the
Heath Frankel wrote:
[openEHR-EHR-COMPOSITION.encounter.v1*] (or perhaps more correctly
[openEHR-EHR-COMPOSITION.encounter.v1.*], where the dot means any
character
not the version delimiter) and [openEHR-EHR-COMPOSITION.encounter.v\d+]
are
different. The first allows all revisions of .v1
at openehr.org] On Behalf Of Peter Gummer
Sent: Thursday, 5 June 2008 11:14 AM
To: For openEHR technical discussions
Subject: Re: openEHR Querying specifications
Heath Frankel wrote:
[openEHR-EHR-COMPOSITION.encounter.v1*] (or perhaps more correctly
[openEHR-EHR-COMPOSITION.encounter.v1
-technical-bounces at openehr.org] On Behalf Of Rong Chen
Sent: den 4 juni 2008 22:07
To: For openEHR technical discussions
Subject: Re: openEHR Querying specifications
On Tue, Jun 3, 2008 at 11:26 PM, Mikael Nystr?m mikny at imt.liu.se wrote:
I disagree with Rong.
If for example the change between
...@openehr.org
[mailto:openehr-technical-bounces at openehr.org] On Behalf Of Rong Chen
Sent: den 3 juni 2008 22:54
To: For openEHR technical discussions
Subject: Re: openEHR Querying specifications
I suspect changes between version could potentially break the paths in WHERE
clause. So maybe
On Tue, Jun 03, 2008 at 11:26:08PM +0200, Mikael Nystr?m wrote:
I therefore think that excluding the version information can result in a
mess.
It shouldn't, of course, be excluded by default but should
be excludable on demand. By, say, allowing regex matching
for path definitions.
Karsten
--
Hi Tim,
-Original Message-
From: openehr-technical-bounces at openehr.org [mailto:openehr-technical-
bounces at openehr.org] On Behalf Of Tim Cook
Sent: Wednesday, June 04, 2008 4:49 AM
To: For openEHR technical discussions
Subject: Re: openEHR Querying specifications
Hi Tom
To: For openEHR technical discussions
Subject: Re: openEHR Querying specifications
Fair point. Perhaps AQL should support ranges of version numbers to
simplify the query as in many cases the query will not be affected by
a structrural change to the archetype
e.g.
FROM EHR [ehr_id/value=$ehrUid
.
/Micke
From: openehr-technical-bounces at openehr.org [mailto:openehr-
technical-bounces at openehr.org] On Behalf Of Rong Chen
Sent: den 3 juni 2008 22:54
To: For openEHR technical discussions
Subject: Re: openEHR Querying specifications
I suspect changes between version could
2008 08:58
To: For openEHR technical discussions
Subject: Re: openEHR Querying specifications
I'm not a technical person but to me it seems very cumbersome if such
'differences' could exist between 2 versions of the same archetypes. This
would mean that for every query one has to go into detail
On Wed, Jun 04, 2008 at 12:42:56AM +0200, Mikael Nystr?m wrote:
It shouldn't, of course, be excluded by default but should
be excludable on demand. By, say, allowing regex matching
for path definitions.
To be excludable on demand is probably a good solution, but I still think
that there
On Wed, Jun 04, 2008 at 09:09:56AM +0930, Heath Frankel wrote:
Versions should be handled using the regular expression syntax of the
archetype ID, as is done in ADL to represent slot constraints and
action_arcehtype_id in ACTIVITY.
E.g. [openEHR-EHR-COMPOSITION.encounter.v1*]
Stef Verlinden wrote:
I'm not a technical person but to me it seems very cumbersome if such
'differences' could exist between 2 versions of the same archetypes.
This would mean that for every query one has to go into detail of
every version of that AT which could mean al lot of work.
To
Op 4-jun-2008, om 10:23 heeft Thomas Beale het volgende geschreven:
I hope this clarifies things
Absolutely, thanks.
Stef
-- next part --
An HTML attachment was scrubbed...
URL:
Dear all,
The text below by Thomas warrants a conclusion:
- openEHR needs a (place in a) document that defines the correct
wording and meaning of:
version and revision.
To my mind these words are to much similar and can generate confusions.
Alternatives:
Package (new Archetype that breaks the
*To:* For openEHR technical discussions
*Subject:* Re: openEHR Querying specifications
I suspect changes between version could potentially break the paths in
WHERE clause. So maybe the version information isn't significant here since
either the path works and the criteria are checked
On Wed, 2008-06-04 at 21:56 +0200, Gerard Freriks wrote:
Dear all,
The text below by Thomas warrants a conclusion:
- openEHR needs a (place in a) document that defines the correct
wording and meaning of:
version and revision.
To my mind these words are to much similar and can
As part of the ongoing specification work this year, we have started to
build some resource pages for the various specifications. One of them
concerns a querying solution for openEHR - see the wiki page at:
http://www.openehr.org/wiki/display/spec/openEHR+Query+Specifications
I have uploaded
Hi Tom,
On Tue, 2008-06-03 at 16:39 +0100, Thomas Beale wrote:
I have uploaded the Ocean Informatics developed 'Archetype Query
Language' (AQL) as a candidate solution for querying archetype-based
data. As explained in the query specification home page, AQL can be
treated as a starting
--
Message: 2
Date: Tue, 03 Jun 2008 16:39:37 +0100
From: Thomas Beale thomas.be...@oceaninformatics.com
Subject: openEHR Querying specifications
To: Openehr-Technical openehr-technical at openehr.org
Message-ID: 484565B9.6030805 at oceaninformatics.com
Content-Type
:
--
Message: 2
Date: Tue, 03 Jun 2008 16:39:37 +0100
From: Thomas Beale thomas.beale at oceaninformatics.com
Subject: openEHR Querying specifications
To: Openehr-Technical openehr-technical at openehr.org
Message-ID: 484565B9.6030805 at oceaninformatics.com
Content-Type: text/plain; charset=ISO-8859-1
caultonpos at gmail.com:
--
Message: 2
Date: Tue, 03 Jun 2008 16:39:37 +0100
From: Thomas Beale thomas.beale at oceaninformatics.com
Subject: openEHR Querying specifications
To: Openehr-Technical openehr-technical at openehr.org
Message-ID: 484565B9.6030805
23 matches
Mail list logo
