- From: Kashyap, Vipul <VKASHYAP1@PARTNERS.ORG>
- Date: Thu, 11 Jan 2007 19:31:01 -0500
- To: "Chimezie Ogbuji" <ogbujic@bio.ri.ccf.org>
- Cc: "Nigam Haresh Shah" <nigam@stanford.edu>, "Trish Whetzel" <whetzel@pcbi.upenn.edu>, "kc28" <kei.cheung@yale.edu>, "Alan Ruttenberg" <alanruttenberg@gmail.com>, "w3c semweb hcls" <public-semweb-lifesci@w3.org>
> If a class has a particular 'definition' (i.e., the criteria for > membership of its instances) at a particular time and that definition > 'changes' then we are talking about a different class > altogether not a 'version' of the same class - the extension of both > classes are no longer the same. Unless the definition change is > annotative only and doesn't really have any 'logical' consequences. In > which case a SKOS, time-stamped annotation for a human reader is > sufficient and what we really have in mind. [VK] This is a very interesting question and Chimezie has suggested some criteria to address this. Maybe we can take some ideas from way software is versioned, i.e., when is something a major release vs a minor release? Just thinking aloud ... 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:31:31 UTC