Hi,
First this, because of some technical issue at my provider, all my
emails of yesterday are gone, I am now replying from the mail-archive of
OpenEHR. So I can not reply inline.
---------------------------
I favour the idea of having an explaining-comment-feature for the
terminology bindings.
How to do that is one item to discuss, but the goal will be that it is
no longer necessary to oppose against unreadable URI's which represent
the SNOMED constraints and expressions, because they will be explained.
Now the how to do it discussion.
Just adding an ADL-comment like they are available in the ADL-syntax is
an easy solution and does not need a change of the ADL grammar.
But the disadvantage is that the parser should ignore everything behind
the comment-dashes .
So, you can write their something, but you cannot enforce any
syntax-structure, because when you enforce syntax in a comment, then it
is not a comment anymore.
So that leaves us a syntax change. (Sorry that below is only readable
for programmers, but it is the fastest way to explain)
Currently the structure for terminology binding is Hash <String,
Hash<String, URI>>
Example Hash <"SNOMED-CT", Hash<"ID26", "
http://snomedct.info/id/169895004";>>
Even when we manage to get something in between we have the problem with
the languages, to create space for all occurring languages (in the
archetype) in this structure will make it too complex/big.
There is another way to consider. I have sometimes seen in
CKM-archetypes tags in the ontology-section with the purpose to define
mappings to HL7 or something, I don't remember exact. This means that it
is widely regarded acceptable to use the ontology-section for other
purposes then text/description. And the ontology-section has already
partitions for languages. So it would be possible to extend the ontology
(for where it is appropriate) with terminology-binding explanations.
This would not change the ADL syntax, doesn't need a change of the
parser-grammars, is available for all languages, and makes it possible
to use non/hard-readable encoded URI's in the terminology-bindings.
Bert
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
