|
From: Lorenz B. <spo...@st...> - 2014-10-28 09:46:25
|
Hi Céline, thanks for your interest and comments. I'll try to answer them. 1. Unfortunately, the manual is quite old and as you pointed out things are missing. Basically, the target language depends on the allowed DL constructs, which can be set in the refinement operator. In general we support ALCQ(D), that means we also support qualified cardinality restrictions(Q). The is also one option for hasValue constructs, which are some kind of syntactic sugar for existential restrictions combined with a singleton nominal cconcept. In that case we would have ALCOQ(D). 2. Currently, only xsd:integer and xsd:double are implemented, but in general every numerical xsd datatype is possible as long as there exists a corresponding Java class. Let me know if you need support for the other datatypes. 3. Well, I thought everything in DL-Learner is based on UTF-8, but it sound like an encoding bug. We will investigate it. 4. Yes, you're right. I guess the language is left-bound and based on the OR the parser expects a DataUnionOf. We should follow the precedence rules and will add parenthesis if necessary. Thanks for the hint. All the best, Lorenz On 27.10.2014 16:10, alec wrote: > Hello, > > I have some questions and remarks on DL-Learner. I would be very > grateful if you could answer my questions. I am using > dllearner-1.0-beta-3 on Windows. > > 1. In the manual, for the learning algorithms, sometimes the target > language is written but sometimes it is not. For example, it is > ALCN(D) for Refinement but it is not written for CELOE. Would it be > possible to add it? Or just to tell me the target language for each > algorithm. > > 2. Moreover, when “datatype properties” are taken into account, could > you tell me exactly with what kind of ranges does it work? For > example, I tried to get a solution like > "hasAge some integer[>=28]" > with CELOE and it worked. It was working with doubles too. But it was > not working with floats. Do you have a list of ranges which are > working/ not working? > > 3. I also noticed that, when there are accents, the solution can > change. For example, the solution is not the same if I just add > accents in some words in both the .conf and .owl files. > > 4. Finally, I think some parenthesis are missing in solutions with > datatype properties. For example, I can get something like > "hasAge some integer[>= 28] or (not male)". > I tried to copy it on Protege saying that some new class of mine was > equivalent to > "hasAge some integer[>= 28] or (not male)" > with the class expression editor. But it said it was expecting > something like a datatype name instead of “male”. It is working when I > write > "(hasAge some integer[>=28]) or (not male)". > > > Thank you in advance for your answers. I attached examples in a zip > directory if needed. > > Best regards, > Céline > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > dl-learner-discussion mailing list > dl-...@li... > https://lists.sourceforge.net/lists/listinfo/dl-learner-discussion |