Tom The operations I was thinking of were around the situation where you have a data store of persisted instances of CODE_PHRASES, and you wish to do things such as (1) find all the CODE_PHRASES for a particular terminology - presumably because you want to do some sort of batch/group operation on them, or, (2) organize the data store depending on the terminology underlying the CODE_PHRASES. Both these operations are likely to be more difficult to do if the terminology name/id is buried with an aggregated attribute.
cheers, Hugh 2) -----Original Message----- From: owner-openehr-techni...@openehr.org [mailto:owner-openehr-technical at openehr.org] On Behalf Of Thomas Beale Sent: Thursday, 19 January 2006 9:38 AM To: openehr-technical at openehr.org Subject: Re: Proposed slightly radical change to CODE_PHRASE in Text package in openEHR Hugh Grady wrote: >Hi Tom > >I prefer the original structure, mainly from a general dislike of aggregate >attributes (such as the new one combining the terminology and the code id). > > In general I agree with the sentiment; I would only say that coded terms are somewhat of an exception - or any identifier with a name-space prepended, which is essentially what this is. >I can see the need to decompose the attribute to talk to the right >terminology being a nuisance and it could make some sensible operations >difficult when dealing with CODE_PHRASEs from multiple terminologies. > > Can you elaborate on the last point above, Hugh? - thomas
