I wasn’t trying to single you out. If a migration to crossing:markings=*, crossing:signals=*, and crossing:signed=* works out, then it would become feasible for you to use crossing=* to encapsulate whatever aspects you want without creating any issues of consistency or ambiguity, but until then, crossing_ref=* exists for any miscellaneous considerations or regional classification systems. In my personal opinion, crossing:markings=* should be a welcome development for anyone who has taken issue with crossing=marked because it preempts crossing=uncontrolled. It’s a worthwhile tradeoff for long-needed expressiveness and clarity over a modicum of concision.