Hi, I assume that this will only affect feature (match/assignment) expressions concerning non-primitive values for now. So we could add a new type of (dummy) expression only in combination with complex features.
I further assume that we do not need null-expression in combinations with primitive values, right? Thanks for the offer, but maybe it's better if I implement the changes since I am not sure yet which and how many consequences the changes will have, e.g., the compare method of FeatureMatchExpressions does not work yet with complex features. Best, Peter Am 06.01.2015 um 19:54 schrieb Silvestre Losada: > Hi Peter, > > I opened new feature request, so if you wish you can explain to me the > ideas that you have and I can implement it. > > > Best. > > On 5 January 2015 at 11:38, Peter Klügl <[email protected]> wrote: > >> Hi, >> >> that's not (yet) supported. You can open a feature request if you want. >> This shouldn't be too complicated to implement. I already have some ideas... >> >> This functionality is specified right now in ruta by using an additional >> boolean feature, which stores whether the original feature was set. >> >> Best, >> >> Peter >> >> Am 05.01.2015 um 10:41 schrieb Silvestre Losada: >> >> Hi all, >>> I was looking into the UIMA ruta documentation and I dont know how to >>> check >>> in ruta script a feature of given annotation is null. Something like this >>> >>> MyAnnotation.feature== NULL{-> ...} >>> >>> >>> is that possible? >>> >>> Kind regards. >>> >>>
