No, those functions are just for singular forms. I guess that it hasn’t been necessary to add corresponding plural functions before, because English is the most used RGL language, and you get the same effect from the following core RGL trees:
1. CompNP (DetCN (DetQuant IndefArt NumPl) cn)
2. PrepNP prep (DetCN (DetQuant IndefArt NumPl) cn)
However, we could easily add functions to Extend and call them e.g. CompBarePlCN and PrepPlCN. And their definitions in ExtendFunctor would be the trees 1. and 2. above.
I have been pretty liberal in adding new funs to Extend, when the structure is new in the whole RGL. However, I tend to be more cautious when the new structure causes ambiguity for English parsing. This is irrational, because the RGL was not meant for parsing in the first place, but I’m used to getting questions from people who are using AllEng (which includes Extend) for parsing, and wonder why simple sentences get so many parses.¹ So that has made me cautious about adding structures like these into Extend, even though I like to claim that Extend can be freely extended.
Maybe the solution is to just extend Extend with the union of the linguistic distinctions needed across the RGL languages, and keep a curated subset of core+Extend that is well-behaved for parsing English? Does anyone else have opinions on this?
Inari
¹ ) Although the worst offenders are already in the core RGL; it’s ApposCN combined with DetNP + plural indefinite article, which creates an NP consisting of an empty string.
Great info, Inari, thanks!