Open andorm opened 12 years ago
I think this is already supported as a part of the verification mechanism, but I do believe it has to be turned on explicitly and I am not sure in regards to the documentation status. @spyysalo: I think you are better suited than me for this one.
@andorm : using multi-valued attributes as you do now is a good way to make sure an attribute is present, but there isn't currently any way to mark one of the possible values as erroneous (i.e. indicating lack of a mandatory choice).
There's a "special argument" mechanism in the config system which would allow something like
Tense Arg:Verb, Value:Past|Present|Future|Unspecified, <MISSING>:Unspecified
Would this work?
thank you for the recommendation, i'll have to read up on how the macros work. just trying it quickly now didn't work, but i must be missing something.
@andorm : sorry, that wasn't clear -- this isn't implemented yet, I was just asking if this type of implementation (and, to a lesser extent, this syntax) would resolve what you need.
ideally, it would be nice to be able to tell Brat to check if an attribute has a value assigned. The suggestion above seems to check whether "Unspecified" value is missing and that wouldn't be as useful. So something along the lines of
Tense Arg:Verb, Value:Past|Present|Future|Unspecified, ValueSelected=TRUE
Is it possible to mark event attributes as mandatory? So that the annotator gets an error if they didn't select an attribute. I need to have tense marked on all events, currently defied as:
Tense Arg:, Value:Past|Present|Future|Unspecified