You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to document the "inaccuracies" of CasToInlineXml and possibly include some sanity
checks that log warnings if a CAS contains overlapping annotations and complex feature
structures being used as features - just to be that novice users are aware that strange
things my be happening:
- Features whose values are FeatureStructures are not represented.
- Feature values which are strings longer than 64 characters are truncated.
- Feature values which are arrays of primitives are represented by strings that look
like [ xxx, xxx ]
- The Subject of analysis is presumed to be a text string.
-Some characters in the document's Subject-of-analysis are replaced by blanks, because
the characters aren't valid in xml documents.
- It doesn't work for annotations which are overlapping, because these cannot be properly
represented as properly - nested XML.
Original issue reported on code.google.com by richard.eckart on 2011-03-29 18:50:37
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
richard.eckart
on 2011-03-29 18:50:37The text was updated successfully, but these errors were encountered: