Hi All
I think I have said it before but I think we need to see this managed at the
publication level. CKM currently stores translations as distinct assets.
This has a number of advantages:
1) Translations can be added, reviewed, accredited asynchronously for
the same archetype
2)
Hi Tim
I am keen, as some others have said, that CKM manages this with users being
able to get as many translations as they need when they download the
archetype. The advantage with the approach is that you do not need the
source language to translate using the archetype so you do not need to
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20090504/06b0d95f/attachment.html
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20090504/ae613b8f/attachment.html
-- next part --
A non-text attachment was scrubbed...
Name: OceanC_small.png
Type: image/png
Size: 4972 bytes
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20090504/4f32d718/attachment.html
-- next part --
A non-text attachment was scrubbed...
Name: OceanC_small.png
Type: image/png
Size: 4972 bytes
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20090503/26136e2f/attachment.html
On Sun, 2009-05-03 at 16:43 +0100, Thomas Beale wrote:
I am not a priori for or against any particular solution, but I think
we should remember that the source form of archetypes is not the
format for which effciency matters; the operational template form is
the important one.
see your
Tim,
As I mentioned, the requirement was to have a hash that can be referenced at
runtime without the need to reference an online service. For example a
recent version of the Ocean Template Designer includes integrity checking of
archetypes used in a template to ensure that the archetype is the
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20090430/5ab5b3bd/attachment.html
Hi Koray,
I will let others respond about translations etc, but I did want to pick up
on your point about multi-part file. This was an option recently consider
when we were looking at a mechanism to record an MD5 Hash of the archetype.
There was a desire to provide this hash external to the ADL
Hi Hugh,
On Thu, 2009-04-30 at 10:23 +1000, Hugh Leslie wrote:
I agree Tim that this is an issue. One of the possible ways forward
is allowing a user to select which translations they want in the
archetype before downloading it from the repository. This would be
something that would be
On Thu, 2009-04-30 at 16:28 +0930, Heath Frankel wrote:
Hi Koray,
I will let others respond about translations etc, but I did want to
pick up on your point about multi-part file. This was an option
recently consider when we were looking at a mechanism to record an MD5
Hash of the
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
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
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
Hi Tim, an important issue for me too!
The archetypes I am working with (Endoscopy ones) are already quite big
and there are 11 (yes eleven) languages! I completely translated one of
them (MST Colon) and it is 6359 lines long. I also had quite an
experience with localisation of software in
Hi All,
I raised the below CR and I wanted to open up discussion on this issue.
Actually I brought it up a few years ago but I don't have a record of
where/when; now.
I know that this have a major impact on implementers but I think the
current way we handle translations in ADL is a monster that
17 matches
Mail list logo
