Re: Specialization depth

ARCHETYPE_ID is for AOM 1.4, ARCHETYPE_HRID is for AOM 2.0 We will rationalise all these classes in to the BASE component in Release 1.1.0 of the RM. - thomas On 17/12/2015 07:24, Bert Verhees wrote: On 16-12-15 14:05, Thomas Beale wrote: that's why it is gone in ADL2/AOM2. The new

Re: Specialization depth

The error messages are actually in ODIN format, which can accommodate EN-US as well as EN, if we really want to bother with that. - thomas On 17/12/2015 07:16, Bert Verhees wrote: For US/international English spelling, we tend to use International English for all natural language, and

Re: Specialization depth

On 17-12-15 11:09, Thomas Beale wrote: The error messages are actually in ODIN format, which can accommodate EN-US as well as EN, if we really want to bother with that. That is the good thing, you can create error messages in any language, even switch the language if wanted, which fits fine

Re: Specialization depth

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

Re: Specialization depth

On 16-12-15 14:05, Thomas Beale wrote: that's why it is gone in ADL2/AOM2. The new ARCHETYPE_HRID class is the one that matters, and it does not know about specialisation depth. Please allow me a question, maybe it is explained somewhere. What is the meaning of the class Archetype_Id in the

Re: Specialization depth

Thanks Thomas for your answers, I will study them tomorrow Best regards Bert On 16-12-15 14:12, Diego Boscá wrote: Must put AOM2 glasses on! 8-) 2015-12-16 14:03 GMT+01:00 Thomas Beale : This is not a specialised identifier, it's just an identifier that has '-'

Re: Specialization depth

helping me with this. Bert 2015-12-16 10:56 GMT+01:00 David Moner <dam...@gmail.com>: In AOM/ADL 2 this is not true anymore, so I fear we have lost the only way to know the specialization depth of an archetype (without navigating through all its parents). 2015-12-16 10:52 GMT+01:00 Diego Boscá &l

Re: Specialization depth

On 16/12/2015 10:54, Bert Verhees wrote: On 16-12-15 11:37, Diego Boscá wrote: but there is an example of an specialized identifier in that same document e.g. "uk.nhs.clinical::openEHR-EHR-SECTION.t_encounter_report-vital_signs_headings-0001.v1" in

Re: Specialization depth

Must put AOM2 glasses on! 8-) 2015-12-16 14:03 GMT+01:00 Thomas Beale : > > This is not a specialised identifier, it's just an identifier that has '-' > characters in it, which in ADL2 are not special. > > Just look at the id1.x code of the root node to get the

Re: Specialization depth

On 16-12-15 11:54, Bert Verhees wrote: I think it is best to wait for an official reaction of the openehr chief architect. No offending intended, just joking ;-) ___ openEHR-technical mailing list openEHR-technical@lists.openehr.org

Re: Specialization depth

wrote: The concept_id part from the archetype_hrid shows all the parents of a given node (or at least did in 1.4) 2015-12-16 10:42 GMT+01:00 Bert Verhees <bert.verh...@rosa.nl>: On 16-12-15 09:50, Diego Boscá wrote: Parsing current archetype identifiers you can know the specialization depth

Re: Specialization depth

This is not a specialised identifier, it's just an identifier that has '-' characters in it, which in ADL2 are not special. Just look at the id1.x code of the root node to get the specialisation depth of any ADL2 archetype. - thomas On 16/12/2015 10:37, Diego Boscá wrote: but there is an

Re: Specialization depth

On 16-12-15 09:50, Diego Boscá wrote: Parsing current archetype identifiers you can know the specialization depth and compare it with root node_id. Hi Diego, Thanks for your answer, and I hope you will answer my follow up question I thought the the versionId's in the archetype_hrid denote

Re: Specialization depth

The concept_id part from the archetype_hrid shows all the parents of a given node (or at least did in 1.4) 2015-12-16 10:42 GMT+01:00 Bert Verhees <bert.verh...@rosa.nl>: > On 16-12-15 09:50, Diego Boscá wrote: >> >> Parsing current archetype identifiers you can know the sp

Specialization depth

the specalisation depth, and must be defined in the terminology. /(which has a spelling-error in "specalisation", it should be "specialisation") /My first question: How can the parser know the specialization-depth? When I look at the grammar, it seems n

Re: Specialization depth

Parsing current archetype identifiers you can know the specialization depth and compare it with root node_id. 2015-12-16 9:42 GMT+01:00 Bert Verhees <bert.verh...@rosa.nl>: > Hi all, > > I am looking at this error message from > http://www.openehr.org/releases/AM/latest/d

Re: Specialization depth

GMT+01:00 Bert Verhees <bert.verh...@rosa.nl>: On 16-12-15 09:50, Diego Boscá wrote: Parsing current archetype identifiers you can know the specialization depth and compare it with root node_id. Hi Diego, Thanks for your answer, and I hope you will answer my follow up question I t

Re: Specialization depth

In AOM/ADL 2 this is not true anymore, so I fear we have lost the only way to know the specialization depth of an archetype (without navigating through all its parents). 2015-12-16 10:52 GMT+01:00 Diego Boscá <yamp...@gmail.com>: > The concept_id part from the archetype_hrid

Re: Specialization depth

On 16-12-15 10:56, David Moner wrote: In AOM/ADL 2 this is not true anymore, so I fear we have lost the only way to know the specialization depth of an archetype (without navigating through all its parents). Thanks, David, I am afraid then we must say that there is a not very effective

Re: Specialization depth

Moner <dam...@gmail.com>: > In AOM/ADL 2 this is not true anymore, so I fear we have lost the only way > to know the specialization depth of an archetype (without navigating through > all its parents). > > 2015-12-16 10:52 GMT+01:00 Diego Boscá <yamp...@gmail.com>: >> >