\`, which seem to be complex object overlays? Or if not necessary perhaps?
> - \[x\] default valus
> - \[x\] occurrences
> - \[x\] rm\_visibility, including aliases
> - \[x\] refactor path lookup for RM objects AND AOM to support archetype ref + name lookup. BREAKING CHANGES!!!
> - \[x\] migrate paths in annotations and visibility from archetype ref + name =\> unique id-code?
> - \[\] C\_ATTRIBUTES constraints
> - \[\] RM\_TYPE\_NAME? can this change, or just for lookup?
>
> \## Breaking changes
>
> \- Path parsing and RM Path queries lookup rewritten wit a proper predicate system to implement and name/value= lookup. This should not break things, but potentially can, especially if manually constructing pathSegments and finding from there.
> \- old RMPathQuery.find() deprecated. It has way too many quirks and should be replaced with findList() and work from those results. However, that will be a breaking change!
Can the ADL Workbench generate OPT1.4 to OPT2 already, @thomas.beale (and not “only” convert adl1.4 to adl2 / opt2. The oets may be the remaining challenge?
What may be even more interesting is an OPT2 → OPT1.4 conversion, because quite likely most openEHR vendors will have to rely on OPT1.4 for a while.
---
### Author:  [@borut.jures](https://discourse.openehr.org/u/borut.jures)
#### Post date: [29 October 2021 12:46 UTC](https://discourse.openehr.org/t/different-types-for-translation-details-language-in-xsd-and-bmm-for-opt-1-4/2003/9 "2021-10-29T12:46:15Z")
> [@thomas.beale](#):
>
> It can also be generated from the [ADL WB tool](https://openehr.github.io/adl-tools/adl_workbench_guide.html).
>
> I can even run it locally on the latest copy of CKM and generate a full set of OPT2 files if you like.
I used public CKMs to download few OPTs for testing.
Thank you for offered help in generating OPT2 files but I don’t want to take your time.
…unless you have few of them ready on your disk 😊 🙏
That would speed let me write OPT2 to AOM2 converter over the weekend and skip the OPT14.
---
### Author:  [@borut.jures](https://discourse.openehr.org/u/borut.jures)
#### Post date: [29 October 2021 12:48 UTC](https://discourse.openehr.org/t/different-types-for-translation-details-language-in-xsd-and-bmm-for-opt-1-4/2003/10 "2021-10-29T12:48:29Z")
> [@sebastian.garde](#):
>
> Something we’ll add to CKM as well in due course
Thank you for the explanation @sebastian.garde.
I’ll take a risk and skip support for OPT14 then. Eventualy CKMs will export OPT2 or users will be able to convert them with one of the tools.
---
### Author:  [@pieterbos](https://discourse.openehr.org/u/pieterbos)
#### Post date: [29 October 2021 13:00 UTC](https://discourse.openehr.org/t/different-types-for-translation-details-language-in-xsd-and-bmm-for-opt-1-4/2003/11 "2021-10-29T13:00:47Z")
Welcome to the club of people who support ADL 2 natively! We’re still a small group unfortunately, but support to migrate is growing fast.
The OPT 1.4 → OPT 2 converter in Archie is feature complete, but has only had limited testing. It will work for at least some OPTs, and may give problems for others. Any issues found should be easy to fix. If you try it, please do report your results, including any issues you find, so the converter can be improved.
OPT2 is already fully AOM2, so I am not sure what you mean with ‘opt2 to aom 2 converter’. Converting OPT 1.4 to OPT 2 is quite a lot of work to get right, just directly importing the OPT 1.4 data into AOM 2 is much less work. The Archie branch that Sebastian pointed to contains the code for both processes.
---
### Author:  [@borut.jures](https://discourse.openehr.org/u/borut.jures)
#### Post date: [29 October 2021 13:48 UTC](https://discourse.openehr.org/t/different-types-for-translation-details-language-in-xsd-and-bmm-for-opt-1-4/2003/12 "2021-10-29T13:48:36Z")
Thank you @pieterbos for the OPT 1.4 to OPT 2 converter!
On my first review I saw a DEVELOPMENT status for OPT2 so I picked OPT 1.4 instead. I’m happy to join the ADL 2 club (now that I learned the OPT 1.4 is using the “original” RM release).
Everything else is already AOM 2 in my little project.
> [@pieterbos](#):
>
> I am not sure what you mean with ‘opt2 to aom 2 converter’.
Its the part where I read the OPT(2) file and “convert” it to AOM classes in-memory.
---
### Author:  [@borut.jures](https://discourse.openehr.org/u/borut.jures)
#### Post date: [29 October 2021 14:22 UTC](https://discourse.openehr.org/t/different-types-for-translation-details-language-in-xsd-and-bmm-for-opt-1-4/2003/13 "2021-10-29T14:22:37Z")
Thank you for all the links and information to everybody.
I’ve (re)read OPT2 specifications and I could skip the “convert” part if I used OPT2 in JSON format (.optj). I could generate the serialize/deserialize code for the AOM2 classes from the AOM2 BMM. This would let me deserialize directly from the .optj file to the AOM2 in-memory classes. Zero code to maintain thanks to the BMM!
I’m reading through the “ADL Workbench (AWB) User Guide” to see how to create a few sample .optj files.
(if somebody has done this before and has these files, please send/upload them)
---
### Author:  [@borut.jures](https://discourse.openehr.org/u/borut.jures)
#### Post date: [29 October 2021 17:55 UTC](https://discourse.openehr.org/t/different-types-for-translation-details-language-in-xsd-and-bmm-for-opt-1-4/2003/14 "2021-10-29T17:55:03Z")
I went ahead and installed ADL Workbench on my Mac. That was an experience 😅
If somebody tries doing the same:
- Don’t install in the Documents folder.
- Don’t skip the line “Then clone the iso8601 and error\_message libraries into a directory such as …/EiffelHub/:” =\> create the EiffelHub directory before executing the last two “git clone” commands.
I was able to compile AWB but received 8 errors (they are actually only 1 error):
```auto
1 VCCH(1) Class has deferred feature(s), but is not declared as deferred. Check deferred feature yymax_symbol_equiv_class from class YY_SCANNER_SKELETON. ADL_14_2_REWRITER.yymax_symbol_equiv_class (adl_components)
...
CADL_14_SCANNER.yymax_symbol_equiv_class (adl_components)
ADL_14_SCANNER.yymax_symbol_equiv_class (adl_components)
BMM_TYPE_NAME_SCANNER.yymax_symbol_equiv_class (eomf_bmm)
OG_PATH_SCANNER.yymax_symbol_equiv_class (eomf_object_graph)
ODIN_SCANNER.yymax_symbol_equiv_class (eomf_odin)
ADL_2_SCANNER.yymax_symbol_equiv_class (adl_components)
CADL_2_SCANNER.yymax_symbol_equiv_class (adl_components)
```
I was brave enough to try to fix them. My first experience with Eiffel. No, I wasn’t successful.
Next, I installed the provided AWB EXE file on my Windows computer. I was able to open a template and save it as a .JSON file. It says it is an operational template but doesn’t use the .OPTJ extension as in OPT2 specifications. Well, it is good enough for me even with the .json.
I guess a can now generate serialize/deserialize support to the AOM2 classes. It will save me a lot of coding now and it will be future proof when specifications change.
It was a good day. Thank you to everybody who took the time to help 👋
---
### Author:  [@thomas.beale](https://discourse.openehr.org/u/thomas.beale)
#### Post date: [29 October 2021 18:06 UTC](https://discourse.openehr.org/t/different-types-for-translation-details-language-in-xsd-and-bmm-for-opt-1-4/2003/15 "2021-10-29T18:06:02Z")
I have to say, as the author of AWB, but who uses Windows and Linux, it works on both of those platforms, but to get it working on the Mac, which we did manage in the past, was very difficult, partly due to difficulty of getting GTK2 installed. Anyway, I might have saved you the trouble if I had known you were going to try that platform 😉
I will however check the state of the source build; not many people do that, so it may be out of date with respect to the compiler version you probably installed (can you let me know which compiler version it was?).
Sorry for the annoyance - I’ll try to improve things there.
---
### Author:  [@borut.jures](https://discourse.openehr.org/u/borut.jures)
#### Post date: [29 October 2021 18:28 UTC](https://discourse.openehr.org/t/different-types-for-translation-details-language-in-xsd-and-bmm-for-opt-1-4/2003/16 "2021-10-29T18:28:42Z")
Don’t worry about the Mac. Windows and Linux is enough. I guess there are more important things on your ToDo list than making AWB run on a Mac for one person 😊
I installed the Eiffel Studio successfully. The source build worked. Based on the compiler errors I thought that the deferred feature `yymax_symbol_equiv_class` was added to these classes and they were somehow not in sync with the change.
But it was the first time I saw an Eiffel code so I’m probably completely wrong here 😅
I already deleted Eiffel Studio so I don’t know which compiler version was used. I guess the latest since I installed everything following the instructions from their site.