Rong,
I had a play around with the ADL parser and had a several questions on
the following archetype
archetype
openVPMS-VPMS-ACCOUNT.draft.v1
concept
[at0000]
description
author = <"Jim Alateras">
status = <"draft">
version = <"draft">
revision = <"1.0">
adl_version = <"1.2draft">
description("en") = <
purpose = <"NAB Account">
>
definition
ACCOUNT[at0000] matches {
accountName existence matches {0..1} matches {/this.*/}
details matches {
TREE[at0002] matches {
items existence matches {0..1} matches {
ELEMENT[at0003] occurrences matches {1..1} matches {
value matches {
TEXT matches {
value matches {".+"}
}
}
}
}
}
}
}
ontology
primary_language = <"en">
languages_available = <"en", ...>
terminologies_available = <"en", ...>
term_definitions("en") = <
items("at0000") = <
text = <"account">;
description = <"account">
>
>
1. How is the constraint type bound to the information model type? Where
does it happen? (i.e. how does the constraint type ACCOUNT get bound to
the Java class org.openvpms.test.Account)
2. Once we have an Archetype instance in memory, we can make a call to
buildRMObject. Can you describe the parameters to method call?
3. This question has to do with terminology. Can you confirm (to ensure
that we are on the right track) that if our terminology is stored in a
DBMS we need to implement a DBMSTerminologyService for our system?
-
If you have any questions about using this list,
please send a message to d.lloyd at openehr.org
