On Thu, 2009-04-30 at 22:03 +1000, Thomas Beale wrote:
> It is clearly true that with a number of translations the archetype will grow
> bigger, and initially (some years ago) I thought separate files might be
> better as well. But I really wonder if it makes any difference in the end -
> since, in generating the 'operational' (aka 'flat') form of an archetype that
> is for end use, the languages required (which might still be more than one)
> can be retained, and the others filtered out. I don't think gettext would deal
> with this properly - the idea that an artefact can have more than one language
> active.

I can only refer you to the "bazillions" of applications that use
gettext. Browsers and GUI widgets everywhere are designed, expecting
gettext catalogs. Not using gettext means that every implementation has
to develop their own filtering mechanisms; in place of reuse of proven
existing technology.  OR; you could choose to develop an openEHR
filtering specification.  Then develop browser interfaces and widget
interfaces to match.  

> The other good thing about the current format (which will eventually migrate
> to pure dADL+cADL) is that it is a direct object serialisation, and can be
> deserialised straight into in-memory objects (Hash tables in the case of the
> translations).

Hmmmm, sorry, I don't get the point here.  Seems to me you are saying
that you pull all translations into memory.  Instead of letting the
application decide which one it wants.

> Anyway, I think that we need to carefully look at the requirements on this
> one, before leaping to a solution...

Of course.  That is why I suggested targeting the 2.0 version.  There is
a good chance that there will be knock on effects (good or bad) to the
RM (AuthoredResource, et.al.) as well.


I'd like to go back to a very basic question I have.  What is the use of
having the original language as (a specific) part of the archetype if it
isn't meant to be the validation language?  Seems to me that it is "the"
expression of the original author for the  construction of the
archetype.  Translations are a convenience for everyone else. 

--Tim
   

-- 
Timothy Cook, MSc
Health Informatics Research & Development Services
LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook 
Skype ID == timothy.cook 
**************************************************************
*You may get my Public GPG key from  popular keyservers or   *
*from this link http://timothywayne.cook.googlepages.com/home*
**************************************************************
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: 
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20090430/46c6a6e9/attachment.asc>

Reply via email to