Jan-Christoph Klie
Jan-Christoph Klie
How would cassis know what feature to use for `as_text()`?
In Python, one would normally just use a list comprehension for that, e.g. values = [x.value for x in cas.select(LEMMA)]
I will track the extension mechanism in #83 and the extension methods you want here so that we do not mix up the issues.
Maybe only put them on the type or remove them atleast from the type system. If one adds a new function like these, it needs to be added in 3...
Right now, I do not serialize it at all which is not so good.
@Br0ce I made it so that we do not crash if a type system already defines custom `DocumentAnnotation`. Can you try out the master?
Right now, it fails because `uima.tcas.DocumentAnnotation` is missing. Is it also a predefined annotation like `uima.tcas.DocumentAnnotation` and `uima.tcas.DocumentAnnotation`?
I found that when I serialize an UIMA Cas then it always creates a `uima.tcas.DocumentAnnotation` in both cas and type system. Therefore I do not add it to the predefined...
I do not serialize predefined types and features.
I added the type system support, I wait for @reckart to give me some CAS XMI that contains one of each DKPro annotation (or as many different types as possible).