Um , mostly the top one is sort of image schematic. And just a note , which was that , um  s so when we actually ha so for instance , um , some of them seem more inherently static , OK , like a container or sort of support - ish. And others are a little bit seemingly inherently dynamic like " source , path , goal " is often thought of that way or " force " , or something like that. But in actual fact , I think that they 're intended to be sort of neutral with respect to that. And different X - schemas use them in a way that 's either static or dynamic. So " path " , you could just be talking about the path between this and this.
Mmm.
And you know , " container " that you can go in and out. All of these things. And so , um , I think this came up when , uh , Ben and I were working with the Spaniards , um , the other day  the " Spaniettes " , as we  called them  um , to decide like how you want to split up , like , s image schematic contributions versus , like , X - schematic contributions. How do you link them up. And I think again , um , it 's gonna be something in the X - schema that tells you " is this static or is this dynamic ". So we definitely need  that sort of aspectual type gives you some of that. Um , that , you know , is it , uh , a state or is it a change of state , or is it a , um , action of some kind ?
Uh , i i i is there any meaning to when you have sort of parameters behind it and when you don't ?