There is nothing wrong with BioPAX in this regard - 'control' (BioPAX Level2 class) and 'Control' (and Catalysis, Modulation subclasses in BioPAX Level3) are still there, in the specification.
This does not require every data provider generate all the available in the BioPAX ontology classes and properties every time, alright.
You're dealing with BioPAX instance data (models of pathways/interactions), such as from BioModels, BioPAX Level2 I suppose, where there might be no 'control' objects indeed (I haven't checked), which is possibly ok, as long as the authors meant that.
They exported to BioPAX what they wanted or could. There might be other semantic problems, such as with identifiers, controlled vocabularies, etc., - critical or not so (you can tell some is you'd run it through the BioPAX Validator, or summarize with Paxtools app, etc.)