search

dkpro / dkpro-uby

Framework for creating and accessing UBY resources – sense-linked lexical resources in standard UBY-LMF format
https://dkpro.github.io/dkpro-uby
Other
22 stars 3 forks source link

Use 3-state type Boolean (rather than boolean) for Sense.transparentMeaning #107

Closed judithek closed 9 years ago

judithek commented 9 years ago 
Currently, we have getters and setters using the class type rather than the primitive
type, but a member attribute using the primitive type.

Using the class type makes more sense, since the transparentMeaning attribute is likely
to be undefined by the source lexicon and thus should be null in the database and the
OR mapped entities.

Original issue reported on code.google.com by chmeyer.de on 2014-10-09 08:05:27

judithek commented 9 years ago 
(No text was entered with this change)

Original issue reported on code.google.com by chmeyer.de on 2014-10-09 08:12:28

judithek commented 9 years ago 
Sounds evil... how about using an integer value or enum (rendered as an integer value)?

Wherever possible, primitive types should be used instead of class types.

Original issue reported on code.google.com by richard.eckart on 2014-10-09 09:49:15

judithek commented 9 years ago 
Changed the member type to "Boolean" for now (consistent with getter and setter). Will
leave the issue unclosed in case we decide for a different solution.

Original issue reported on code.google.com by chmeyer.de on 2014-10-09 13:30:02