You can generate operations to deal with domain types, but then AQL would be openEHR specific (you can call it OQL then). What I say is that generating a path to specify a filter (and accessing it) is direct when the domain type has been expanded, and not so easy if you take it as it is. If you get the expanded path each time then the user won't be able to tell where the AQL path comes from (it'll have attributes he doesn't know about). I only see disadvantages working with domain types in AQL.
2013/4/25 Thomas Beale <thomas.beale at oceaninformatics.com>: > On 25/04/2013 12:21, Diego Bosc? wrote: > > PPPS: How you define an AQL filter over a domain type? > > > > How do you define an AQL filter over a date time? Well, ok, it's not quite > as simple as that. With a coded term type (in particular) you want operators > like 'in set', 'in subsumption', and 'in subset'. > > But why do we see this as being specific to health? > > - thomas > > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
