An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20051020/dc94bc9d/attachment.html
Dear Sam,
We have been discussing the issue of templates and whether we keep an
identifier of a template in the data. My concern has been that this ID
might be seen as an absolute constraint on the data, whereas the precedence
of constraint must be:
knowledge models (reference models as
Christian Heller wrote:
Dear Sam,
We have been discussing the issue of templates and whether we keep an
identifier of a template in the data. My concern has been that this ID
might be seen as an absolute constraint on the data, whereas the precedence
of constraint must be:
knowledge
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20051020/f8301f44/attachment.html
/20051020/8b6a3de3/attachment.html
In my opinion the best design is to have one schema per information model.
This facilitate a logical division of the designed types and to keept in
mind the reference model. The use of namespaces is a good idea to clarify
thinks (I belive). To use this philosophy for representing RM in OWL gives
Hi Thomas,
well, that is one design approach, but it is not the one that we use in
openEHR. In openEHR, the archetypes are seen as part of the ontology of
information (distinct from ontologies of the real world like
snomed-ct etc). We use them extensively in their own right. We don't
I
7 matches
Mail list logo