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 > -----Original Message----- > From: openehr-technical-bounces at openehr.org [mailto:openehr-technical- > bounces 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.*], 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 (e.g. v1.1, v1.2, ..) > > Close, but not quite! > > [openEHR-EHR-COMPOSITION.encounter.v1.*] allows all revisions of .v1, .v10, > .v11, ... .v100, .v101, etc. > > To allow all revisions of .v1, we would need this: > > [openEHR-EHR-COMPOSITION.encounter.v1\..*] > > But what about .v1draft? This regex wouldn't catch it. Does this matter? Or > is that old "draft" convention going to be phased out? > > - Peter > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
