Hi, The examples I provided were those that I could think of.
The real question to be asked is: Why would we want to record the 'language' of a text fragment? The only correct answer will be: Because of computational reasons. In the light of this there is no real use case for this attribute in question other than to indicate in what language the author is documenting its provision of healthcare. Coding systems will have to be used to indicate in an 'absolute' sense the meaning of things in a computational and language independent way. If and when this assumption is true then the level of Composition (somewhere high) will be appropriate to record this optional attribute. Gerard -- <private> -- Gerard Freriks, arts Huigsloterdijk 378 2158 LR Buitenkaag The Netherlands +31 252 544896 +31 654 792800 On 17 Mar 2004, at 23:46, Thomas Beale wrote: > actually, these kinds of expressions are not the problem - they can > happily be recorded inside a DV_TEXT object which has the language set > to English or Dutch or whatever it may be; an inline occurrence of a > 'foreign' term that is routinely used by speakers of a different > language (the way we use 'gesundheit' or 'triage' in english) can be > assumed to be understood and is probably even in the dictionary of the > language of narration. > > The problem is when there are text fragments recorded where the words > are viable in more than one language, and do not usually have the same > meaning in each. Words in Danish & Norwegian should be almost the > same, but I assume there are by now some small differences; there are > certainly words in most of the European languages which occur in > another language, and are completely unrelated. So in theory a > language marker is needed to ensure that a later reader knows what > language the words were in (maybe even to allow them to know what kind > of translator to call). So the question remains - do we need the > ability to have multiple languages inside a single entry? For Gerard's > examples - would it really be necessary to indicate what the other > languages were or not, given that they are probably obvious to most > users who will use them? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/enriched Size: 2222 bytes Desc: not available URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20040318/d85896f4/attachment.bin>
