[CDAO-discuss] Fixed bug in definition of SetOfThings

[Hilmar L. <hl...@ne...>]

The class cdao:SetOfThings had a property restriction with universal quantification "has_Element only Character". This is a bug because there is a subclass cdao:SetofNodes with obvious conflict (asserted as "has_Element only Node"). I.e., if an instance of the element is asserted, it will be inferred as an instance of both cdao:Node and cdao:Character, which is non-sensical (even if these aren't expressly declared as disjoint).

I fixed this by deleting the restriction from the SetOfThings class.

In addition, I also made the subclasses of cdao:CDAOAnnotation consistent in being defined through the appropriate property restrictions. I hope this is uncontroversial.

There were a series of other issues / proposed improvements coming out of the Phylotastic II hackathon that just ended in Tucson. I'll post those to the tracker one by one, and presumably some or most of these will trigger some discussion.

However, can we in the meantime do I new release? I've already updated the version number in anticipation of that.

Jim - can you initiate this, or tell me what I need to do, or is this documented somewhere?

	-hilmar
-- 
===========================================================
: Hilmar Lapp  -:- Durham, NC -:- informatics.nescent.org :
===========================================================