Hi Mattias,
I just had a look at the Java ADL parser. CONSTRAINT_REF is used in many
places to get node ID, e.g. [ac0003]. But it also used in one place to
create a C_DV_CODED_TEXT as the following Java code. I am afraid this is
perhaps over-simplied because a code constraint could be defined as a
terminology query or a single term by the onology part of the archetype. So
more appropriate implementation would be to consult the ontology part with
the current code and get the full definition, and then instantiate the
C_DV_CODED_TEXT, which might not be ready at the time of parsing. It will
requires some post-parsing processing.
Thomas, can you verify that this is the right way to go?
Regards,
Rong
ref = constraint_ref()
{
// before switch to openehr-ap: c = new CCodedText(path, ref);
c = new CDvCodedText(path, local, ref);
}
On 11/22/06, Mattias Forss mattias.forss at gmail.com wrote:
Hi all,
I'm wondering what the difference is between a CONSTRAINT_REF and a
C_DV_CODED_TEXT that has the query attribute set? The descriptions of the
two are the following:
CONSTRAINT_REF class description:
Reference to a constraint described in the same archetype, but outside the
main constraint structure. This is used to refer to constraints expressed in
terms of external resources, such as constraints on terminology value sets.
Description of query attribute of C_DV_CODED_TEXT:
Constraint in terms of an abstract query expression to be addressed to a
terminology server.
Is there a syntactic difference between the two in ADL?
Mattias
___
openEHR-technical mailing list
openEHR-technical at openehr.org
http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20061214/fd123528/attachment.html
-- next part --
___
openEHR-technical mailing list
openEHR-technical at openehr.org
http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
