-
Notifications
You must be signed in to change notification settings - Fork 245
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nor/CCONJ: Feature to indicate negation? #1056
Comments
I think it's not PronType=anything because it's not a pronoun. As for Polarity=Neg, I'd be all for it, but as I recall, the Core Group voted against anything in English being Polarity=Neg except for "not" in UniversalDependencies/UD_English-EWT#526 So while I also definitely think Polarity=Neg is appropriate, it would also be appropriate for negation with "no", "non" as a token, and arguably morphological negation of adjectives within tokens (un-). But since it's been ruled on quite recently, I imagine the answer is still that it only applies to "not", making it a non-useful (not a useful?) feature in English - see the thread above for discussion. |
I do not see reasons not to annotate it and all other negative words with By the way, there is a big "confusion area" in the guidelines between |
|
OK, happy to discuss it with the group and I'd definitely support more use of Polarity in English. Currently it's not useful at all IMO. |
The Core Group has no objection to |
What about as a determiner in "neither one"? |
That's PronType=Neg |
Oh right! |
English "nor" (and arguably, "neither" when paired with "nor") are coordinating conjunctions that express negation.
Should this be indicated in features? Neither the
PronType=Neg
nor thePolarity=Neg
docs mention CCONJ words as possible targets. The former uses phrasing like "negative pronoun, determiner or adverb" and "pronominal words"—is "nor" a pronominal word? If not, maybePolarity=Neg
is the right solution.The text was updated successfully, but these errors were encountered: