- From: Kashyap, Vipul <VKASHYAP1@PARTNERS.ORG>
- Date: Thu, 11 Jan 2007 19:37:21 -0500
- To: "Nigam Haresh Shah" <nigam@stanford.edu>, "Chimezie Ogbuji" <ogbujic@bio.ri.ccf.org>
- Cc: "Trish Whetzel" <whetzel@pcbi.upenn.edu>, "kc28" <kei.cheung@yale.edu>, "Alan Ruttenberg" <alanruttenberg@gmail.com>, "w3c semweb hcls" <public-semweb-lifesci@w3.org>
> We are not talking about the Class here. Nothing is happening to the class > definition and its criteria for membership for an instance are unchanged. > It is the instance that changes its characteristics and now has > characteristics that can make it a member of a different class. The two > classes in question are unchanged. [VK] True, but Chimezie's question still remains valid. I wonder if someone has developed guidelines on when something is a version vs a new class? > > So, my example still stands. The next version of the instance now belongs > to > a different class (it is still Tom's tumor, now it might be TNM 3 instead > of > TNM 1).... it is this change in instances that needs to be tracked. [VK] The only difference is I do not view it as a version in the content management sense. IMHo, it's more appropriate to view and model as a dynamic state variable changing over time. ---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.
Received on Friday, 12 January 2007 00:38:17 UTC