W3C home > Mailing lists > Public > public-hcls-coi@w3.org > July to September 2008

RE: Multi-layered Knowledge Representations for Healthcare (was RE: An argument for bridging information models and ontologies at the syntactic level)

From: Kashyap, Vipul <VKASHYAP1@PARTNERS.ORG>
Date: Thu, 24 Jul 2008 08:56:04 -0400
Message-ID: <DBA3C02EAD0DC14BBB667C345EE2D12402E8C829@PHSXMB20.partners.org>
To: <dan.russler@oracle.com>
Cc: "Samson Tu" <swt@stanford.edu>, "Elkin, Peter L., M.D." <Elkin.Peter@mayo.edu>, <public-semweb-lifesci@w3.org>, <public-hcls-coi@w3.org>

	I agree with you below, except I think it's peoples' "interpretation" of
the RIM that causes the confusion, e.g. "The focus of the RIM classes had
primarily been structure and not semantics." Since RIM is communicated in UML,
UML semantic rules apply, and one needs to be strict on the UMLsemantics  in
order to interpret the RIM.
	[VK] Also, one needs to be make sure that the semantics of the various
classes in the RIM, e.g., Observation are consistent with the semantics of the
UML constructs being used. Furthermore, these semantics/definitions of the
various classes should be properly
	defined in the RIM specs. 
	One way to think of "structure" is to think of the "structure" of a
definition in a dictionary, i.e. meaning one, meaning two, etc. Then think of
UML as another kind of structure for definitions, i.e. a class representing a
concept sets up a definition structure of attributes, associations, and state
transitions that define the concept (analogous to the linguistic structure of
"meaning one" in a dictionary).
	[VK] I think this is a stretch. Clearly there is widely accepted
connotation of the word "structure". A better approach would be to introduce the
notion of semantics and differentiate it from structure explicitly across the
RIM Specs. 
	I think that revisiting the RIM definitions and RIM UML diagrams and
rethinking of them as complementary "definitions of concepts" rather than
introducing set theory and other data management tasks into the UML
interpretation would be helpful.
	[VK] I agree with the above, except that set theory is a very useful
mathematical tool to concretely specify the semantics of various artifacts and
has been broadly used in Computer Science. Also agree with separation of data
management issues from information modeling
	Seems to me that we need to do this exercise at least for a few use
cases, before we proceed on our attempts at determining semantic conformance.

The information transmitted in this electronic communication is intended only
for the person or entity to whom it is addressed and may contain confidential
and/or privileged material. Any review, retransmission, dissemination or other
use of or taking of any action in reliance upon this information by persons or
entities other than the intended recipient is prohibited. If you received this
information in error, please contact the Compliance HelpLine at 800-856-1983 and
properly dispose of this information.
Received on Thursday, 24 July 2008 12:56:57 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:46:00 UTC