W3C home > Mailing lists > Public > www-webont-wg@w3.org > December 2002

Re: LANG: Proposal to close ontology versioning (ISSUE 5.14)

From: Jeff Heflin <heflin@cse.lehigh.edu>
Date: Tue, 03 Dec 2002 12:15:20 -0500
Message-ID: <3DECE6A8.29C14FB2@cse.lehigh.edu>
To: Jim Hendler <hendler@cs.umd.edu>
CC: Massimo Marchiori <massimo@w3.org>, WebOnt <www-webont-wg@w3.org>

Jim Hendler wrote:
> 
> >
> >Backward-compatibility is only a relation that can hold between two
> >versions of the same ontology. I should have been clearer and said that
> >if one ontology is a priorVersion of another and backward-compatibility
> >is not declared, then incompatibility should be assumed. The ontology
> >author is the one who knows best whether the two versions are
> >incompatible, so I don't see how merging has anything to do with it.
> ><snip>
> 
> Jeff -
>   while I support your current proposal, I have a lot of trouble with
> "If ... backward-compatibility is not declared, then incompatibility
> should be assumed"
> I think that is way to strong -- I think it should be something more like
> 
> If ... backward-compatibility is not declared, then compatibility
> should not be assumed"
> 
> that is, if you have a new version and don't make any declarations at
> all, why should I assume that everything must be broken.  Rather I
> should have a caveat that it may be broken and proceed with caution.
> I think this is most important for those of us who don't intend to
> use the strong imports unless we have to, and thus if we are pointing
> to a small piece of ontology with our own policy on how to process
> it, it should be up to me to decide about compatibility.  I could
> also live with
> If ... backward-compatibility is not declared, then incompatibility
> MAY be assumed"
> 

I could live with either of the above rewordings, although I prefer the
second one.

Jeff
Received on Tuesday, 3 December 2002 12:15:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:57:55 GMT