Where to use "en" and [ISO_639-1::en]

Hi!

The current java adl-parser (built from repository sources today) does
not parse the current (refreshed my copu today) archetypes in the
openEHR knowledge repository without tweaking language coding format.

Note the different formats after original_language in the examples
below. What is correct?

Also note the required ISO style language information in the java
adl-parser version under the path description -> details -> ["en"] ->
language. What is correct?

Some help would be welcome since we wanted to ship a new version of
the LiU Archetype editor today that would read the archetypes in the
openEHR repository. I guess that will have to wait until this issue is
resolved.

If the archetypes ar in error, then we could easily write a script to
change/add language-realated info.

Best regards,
Erik Sundvall
http://www.imt.liu.se/~erisu/

The java adl-parser expects something like this:

language
  original_language = <[ISO_639-1::en]>
  translations = <
        ["de"] = <
          language = <[ISO_639-1::de]>
            author = <
              ["name"] = <"Harry Potter">
              ["email"] = <"harry@something.somewhere.co.uk">
            >

--cut-- and then also in ISO stuff in the description section see below --cut--

description
    original_author = <
        ["name"] = <"unknown">
    >
    lifecycle_state = <"Initial">
    details = <
        ["en"] = <
            language = <[ISO_639-1::en]>
            purpose = <"For communication at the time of discharge
from an episode of care or an institution.">
        >

The example in the spec (ADL 1.4 dated 26 Feb 2007) on the other hand
looks like:

-- cut -- language section from 8.3.5 of the spec below -- cut --
language
   original_language = <"en">
   translations = <
      ["de"] = <
         language = <[iso_639-1::de]>
         author = <

-- cut -- description section from 8.3.6 of the spec below -- cut --

description
   original_author = <
-- cut --
   details = <
      ["en"] = <
         purpose = <"archetype for diabetic patient

Erik Sundvall wrote:

Hi!

The current java adl-parser (built from repository sources today) does
not parse the current (refreshed my copu today) archetypes in the
openEHR knowledge repository without tweaking language coding format.

Note the different formats after original_language in the examples
below. What is correct?
  

sorry for the confusion - I only just noticed today the error in the
spec with original_language. See below.

The general rule is:
* use "en", "se" etc for keys of hash structures i.e. ["en"] = <....>
* use proper CODE_PHRASE for 'real' data items, including original_language
* when in doubt follow the AOM. It is the bible

let me know if there are still outstanding issues when you have read this.

Also note the required ISO style language information in the java
adl-parser version under the path description -> details -> ["en"] ->
language. What is correct?

Some help would be welcome since we wanted to ship a new version of
the LiU Archetype editor today that would read the archetypes in the
openEHR repository. I guess that will have to wait until this issue is
resolved.

If the archetypes ar in error, then we could easily write a script to
change/add language-realated info.

Best regards,
Erik Sundvall
http://www.imt.liu.se/~erisu/

The java adl-parser expects something like this:

language
  original_language = <[ISO_639-1::en]>
  

THIS IS CORRECT

  translations = <
        ["de"] = <
          language = <[ISO_639-1::de]>
            author = <
              ["name"] = <"Harry Potter">
              ["email"] = <"harry@something.somewhere.co.uk">
            >

--cut-- and then also in ISO stuff in the description section see below --cut--

description
    original_author = <
        ["name"] = <"unknown">
    >
    lifecycle_state = <"Initial">
    details = <
        ["en"] = <
            language = <[ISO_639-1::en]>
            purpose = <"For communication at the time of discharge
from an episode of care or an institution.">
        >

The example in the spec (ADL 1.4 dated 26 Feb 2007) on the other hand
looks like:

-- cut -- language section from 8.3.5 of the spec below -- cut --
language
   original_language = <"en">
  

THIS IS AN ERROR - I uploaded the fixed spec today - see the usual place

The java adl-parser expects something like this:

language
original_language = <[ISO_639-1::en]>

THIS IS CORRECT

Thanks for the answer. So I guess there is nothing I need to do with the parser. :slight_smile:
Cheers,
Rong