On 16-12-15 14:01, Thomas Beale wrote:
That is gone in ADL2.
in ADL2 you can know the specialisation depth of the archetype by
looking at the root node code, e.g.
id1 -> depth = 0
id1.1 -> depth = 1
etc
I write, as you suggest, from now on the errors/remarks in the PR
tracker, I had not used it for some years, but I found it, and also my
login credentials again. As you say, I create one single PR for all my
errors/remarks, which are probably not very many.
For US/international English spelling, we tend to use International
English for all natural language, and where we can, accommodate US
English in the formal spec. Thus, an ADL parser has to be able to
parse specialise | specialize. The error texts probably are not
consistent.
The problem is only important for keywords in a definition language, it
is cumbersome to let a parser check several spelling-forms in keywords.
The problem I found, however was in a data-string (an error-message),
and in that case, it is possible to have more languages, which can be
changed and do not effect the parser. So, I take back my remark on this.
Bert
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
