dkpro
[api] Review all feature names to stick to naming convention
All annotation types should be revised so that the feature names stick to a naming convention:
- feature names are in CamelCase and start with a lower-case letter
- generic types (e.g. POS, Constituent, NamedEntity, etc.) have a feature specifying
the tag/category assigned by the tagger. We currently use "value" most of the time,
but we may want to consider another standard name if there are suggestions. "type"
would be good here, but that is reserved by UIMA, so maybe "category"?
- for other extension-point types, e.g. Lemma and Stem, "value" seems to be better
Original issue reported on code.google.com by richard.eckart on 2012-06-27 20:27:26
Using "category" now in the "Split" type to determine the kind of split.
Original issue reported on code.google.com by richard.eckart on 2012-08-04 16:52:05
(No text was entered with this change)
Original issue reported on code.google.com by richard.eckart on 2012-10-13 18:31:41
- Labels added: DKPro-ASL
(No text was entered with this change)
Original issue reported on code.google.com by richard.eckart on 2013-06-25 10:53:40
- Labels added: Milestone-1.6.0
(No text was entered with this change)
Original issue reported on code.google.com by richard.eckart on 2013-06-25 10:57:26
(No text was entered with this change)
Original issue reported on code.google.com by richard.eckart on 2014-03-26 10:51:38
- Labels added: Milestone-1.7.0
- Labels removed: Milestone-1.6.0
(No text was entered with this change)
Original issue reported on code.google.com by richard.eckart on 2014-03-31 10:48:51
- Labels added: Milestone-2.0.0
- Labels removed: Milestone-1.7.0
Won't do this because it would break backwards data compatibility. We'll use DKPro Core 2.0.0 to do the UIMAv3 upgrade but leave the type system largely untouched.