On Nov 5, 2009, at 9:13 AM, PhilA wrote:
> > Thanks Holger > Point 1. Could you update the help file? I did check to see if there > was a syntax change. Ta. Thanks, I have updated the help page on Creating enumerations (this was the only reference to owl:oneOf I found). > As for point 2. > So even though I don't have owl2 activated in the ontology are your > saying I am going to be restricted by it? Yes, in 3.2.0 at least because we have moved to a new rendering API for OWL in general. But I have just fixed this to work around this limitation of the OWL API. > When you say that it will be handled more gracefully I presume you are > saying that it will still be an error? I think it's an error of the OWL API to not handle such cases, because what you are doing is perfectly valid in RDF and OWL Full. But since the OWL API is not using RDF under the hood, I am not terribly surprised about such problems. We will replace this component soon. > This is going to cause me some massive problems as I have lots of > ontologies that have inversefunctional datatype properties. > I see it loads of places in other ontologies as well. We are doing nightly builds now, and we can make an intermediate 3.2.1 with critical things like that available. I will keep you posted. Holger --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
