Hi Tom,
I tend to agree with same that annotations are most likely to be localised
and the need for language translations will be minimal, hence the need to
support annotations with a code is overkill and too complex for the 90% of
use cases.
The only use case I have seen that would utilise annotations with multiple
languages is where a multi-lingual application wants to draw its context
sensitive help from an archetype/template annotation based on a user's
language setting. Although this use case may seem compelling, I still think
this can be supported simply with an optional language attribute on each
annotation.
I would suggest that the current pattern of ontology language translations
being grouped by language, then by concept/node is difficult to consume by a
human reader (yes I know, I should use a tool, but I am a geek and I read
computer code, XML and ADL as my native tongue). Having an annotation for a
node and each of its translations in the one place would be much easier to
read the translations. However, I do understand it would be easier for CKM
or other tools to manage a set of annotations by language, but this is where
the tools can do the work rather than the human J.
Heath
From: openehr-technical-boun...@openehr.org
[mailto:openehr-technical-bounces at openehr.org] On Behalf Of Sam Heard
Sent: Thursday, 30 December 2010 9:50 AM
To: 'For openEHR technical discussions'; 'For openEHR clinical discussions'
Subject: RE: Archetype Template ANNOTATIONS - requirements?
Thanks Tom
My experience is that annotations are organisation specific rather than
national. They are often used to link to other data that is in use in a
particular setting.
There seems to be two sensible approaches:
1. A separate section of the archetype for annotations which have a
language and organisation sections. The tag for an organisation can be their
reverse statement.
2. An annotation syntax that can be used as required anywhere in the
archetype with optional organisation and language sub tags.
The former would allow CKM to present annotations required by a specific
organisation on download, or in a specific language. This would help
management a great deal.
Cheers, Sam
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110106/abde1f41/attachment.html
