W3C home > Mailing lists > Public > public-semweb-lifesci@w3.org > January 2007

RE: Versioning vs Temporal modeling of Patient State

From: Kashyap, Vipul <VKASHYAP1@PARTNERS.ORG>
Date: Thu, 11 Jan 2007 19:41:24 -0500
Message-ID: <2BF18EC866AF0448816CDB62ADF6538105EAF0A0@PHSXMB11.partners.org>
To: "Kei Cheung" <kei.cheung@yale.edu>
Cc: "Nigam Haresh Shah" <nigam@stanford.edu>, "Trish Whetzel" <whetzel@pcbi.upenn.edu>, "Alan Ruttenberg" <alanruttenberg@gmail.com>, "w3c semweb hcls" <public-semweb-lifesci@w3.org>


> I need to go, but just want to quickly add another biological example
> that involves DNA sequences (instances of the Sequence class) that have
> been submitted to GenBank. GenBank uses version numbers to keep track of
> the submissions by the same or different labs of the same reference
> sequence. Again, version to a biologist may not be the same as version
> to a computer scientist. What is the context of version?

[VK] I think the last statement is key to this debate. I would model the above
as "source" information associated with each sequence. This in some sense
buttresses my point that content-management notion of versioning doesn't apply
to instances. If we look at the various use cases, it turns out that a rigorous
modeling of information will eliminate the need for versioning.

---Vipul

> 
> Cheers,
> 
> -Kei
> 
>   Kashyap, Vipul wrote:
> 
> >Nigam,
> >
> >This is an interesting example...
> >
> >
> >
> >>Have an example for this one: If the instance is of a the class "Tumor"
> >>then
> >>on giving treatment it changes in size, shape etc, and might ultimately
> >>disappear. On each visit we are observing a different version of the
> tumor
> >>instance [in Tom].
> >>
> >>
> >
> >[VK] Clearly there is a longitudinal aspect to this as the state of the
> tumor
> >changes over time....
> >
> >This could be modeled in two ways:
> >
> >Tumor1.state = X at time T1
> >Tumor1.state = Y at time T2
> >...
> >Tumor1.state = "Non-existent" at time Tn
> >
> >Essentially you are modeling state as a multivalued property or as a
> ternary
> >relationship (Tumor, state, Time)
> >
> >Alternatively,
> >
> >Tumor1, v1.state = X
> >Tumor1, v2.state = Y
> >...
> >Tumor1, vN.state = "Non-existent"
> >
> >
> >IMHO, the former representation conveys more information and meaning...
> >So, it may make sense not to confound versioning with temporal
> progression...
> >
> >Look forward to the commounities thoughts on the issue.
> >
> >Cheers,
> >
> >---Vipul
> >
> >
> >
> >
> >
> >
> >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 SENDER AND THE PRIVACY OFFICER, AND PROPERLY DISPOSE OF THIS
> INFORMATION.
> 
> >
> >
> >
> >
> 





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 SENDER AND THE PRIVACY OFFICER, AND PROPERLY DISPOSE OF THIS INFORMATION.
Received on Friday, 12 January 2007 00:42:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:20:22 UTC