-
Notifications
You must be signed in to change notification settings - Fork 250
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
Post-positioned cardinal NUMs acting as ordinal (e.g. “section 3”) #466
Comments
Agreed that this is not quantity and that we should try to find a better annotation in a future version of the guidelines. I would not mix it with ordinals either. The ordinal meaning may be there but it is not guaranteed and syntactically it is different, too. Article 50 may turn out to be the fifty-first article if there is article 49A. It is rather something like an entity identifier. I think article 50 should receive the same analysis as Windows 95 (where there really weren't 94 previous versions). |
I think Windows 95 is similar to a left-headed compound (i.e. it's something like the "1995 Windows", a Windows characterized by 95. Maybe similar to Windows Enterprise (the Enterprise kind of Windows). |
I guess the ordinal number of version number (Firefox 54.0) is more of a modifier than a head, but it seems like a subconstruction of proper names. So I'd be fine with |
I think that I suppose that_Firefox 54.0_ can commute with Firefox but not 54.0, so Firefox must be the head (at least it will be like that in French). I think |
In the English corpus there's a sentence mentioning "Adobe Acrobat 3.0" which uses |
I agree with @sylvainkahane's argument about the headedness, but I'm not so sure about the relation. Most of our uses of |
In cases like article 50 or Die Hard 3, the numeral doesn't actually indicate the quantity of a nominal, it rather shows it's order (the fifth article, the third Die Hard movie). It feels weird to mix these concepts and use
nummod
here, but many treebanks do.Can we consider a different (and unified) solution?
The text was updated successfully, but these errors were encountered: