search

codeaudit / dkpro-core-asl

Automatically exported from code.google.com/p/dkpro-core-asl
0 stars 0 forks source link

[api] Review all feature names to stick to naming convention #80

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
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 27 Jun 2012 at 8:27

GoogleCodeExporter commented 9 years ago 
Using "category" now in the "Split" type to determine the kind of split.

Original comment by richard.eckart on 4 Aug 2012 at 4:52

GoogleCodeExporter commented 9 years ago

Original comment by richard.eckart on 13 Oct 2012 at 6:31

GoogleCodeExporter commented 9 years ago

Original comment by richard.eckart on 25 Jun 2013 at 10:53

GoogleCodeExporter commented 9 years ago

Original comment by richard.eckart on 25 Jun 2013 at 10:57

GoogleCodeExporter commented 9 years ago

Original comment by richard.eckart on 26 Mar 2014 at 10:51

GoogleCodeExporter commented 9 years ago

Original comment by richard.eckart on 31 Mar 2014 at 10:48