Good reading on Maria Keet's blog!
She aptly states:
> It may be tempting to (over)generalise for other languages once one speaks several languages, but it’s better to be safe than sorry.

That has been the case from what I've seen, where overgeneralizing hurts long term.  But luckily some frameworks support a bite-sized approach to rules, such as what Maria hinted at.  I agree with her that GF Grammatical Framework and others are not for the faint of heart, and I also wish things were simpler.  Still, GF Grammatical Framework indeed allows a focused bite-sized approach for language rules.

Case in point, the categories of Given Name and Second Name, are not generalized within just 1 function, but many functions across each Language as necessary!
This was added across 26 languages (wish it was more!) just 4 months ago: added GN & SN categories for constructing names · GrammaticalFramework/gf-rgl@7085aca (github.com)

I found out today from my wife that there are indeed Chinese compound surnames, like Ouyang - Wikidata , where in the Lexeme namespace we do not have such categorization, but luckily we have the Wikidata namespace and others that hold a wealth of knowledge and categories, like Chinese compound surname - Wikidata

My move to China has solidified my passion for "context is king" and indeed any Wikifunctions or "article generators" will need to tiptoe into the full knowledge stored across Wikidata's namespaces in order to retrieve broad domain content that will be necessary to support Abstract Wikipedia across unique, low-resourced languages like NCB languages.  I fully agree with her that it can and should be done in an agile fashion. Template languages; quick small trial and error experiments.  Even while the grand vision is slow-paced, we can have faster-paced experiments with incremental grammar development for faster feedback. Agile.

Where that "context" will ultimately be stored in Abstract Wikipedia still is yet to be determined, I think.  It might ultimately live in the language specific Constructors.  And that's probably a good thing, and helps to avoid overgeneralizing.  Copy/paste from other language Constructors or borrowing their templates will make things easier, I guess.

Still, LOTS of volunteer work is needed to make sure categories in general, like in linguistic systems such as GF, UD, Lemon structure, etc. are mapped well across each other so that outside experts can tiptoe into the ecosystem also.

Those maps could live inside the Wikidata namespace, just as we did with Schema.org and other Linked Data, but they can certainly just start to be stored in a spreadsheet somewhere started by some Outreachy participants.