Because subject class concord and object class concord uses the same form (for example "c5"), we don't have yet a way to distinguish them. The meaning is human-parsable because we can look at the alignment of the headers (horizontal=subject concord, vertical=object concord), but the parser does not (yet) have this kind of memory or spatial awareness. /////// Sep 9th 2022: I've recently implemented a way to transform row or column tags into other tags based on language, but it doesn't solve an underlying issue with Swahili tables that I'd missed or forgotten about: The horizontal column headers for class and person don't get inherited through the whole template because it is chopped up into several subtables that don't directly inherit from above. It's an issue with 'bleed' again. /////// Later (comment in Dec 2022): forgot to put this here, but Swahili tables have now gotten their own big systems that make them work, including a "save to register" feature that can keep column headers in memory to be used in a later subtable within a template.