Thanks for the input.
I know svg is formatted just like xml, so I was hoping it wouldn't be that big a step to get the paths data, but yeah parsing it once you get it would be a pain.
Then as you say sharing between plugs is sort of an issue as there would have to be a format they recognize.
Obviously Json would work right now for making paths data, but, the caveat I did not mention is that I think a path plug should work just like how objects do. Like treating each node/point like a sprite, and allow the user to get the xy's just as easy, in expression form. Working with the Json plug is fairly complicated, and confusing for this.
Then again just like 99% of the rest of C3 we don't necessarily need to dig in to its data structures. So if the format needs to be json then so much the better.
The benefits of having paths are huge. In fact we have expressions that beg for them, lerp, cosp, qarp. We need splines, matched with Tween, this is splines. This is splines with ease's.
I haven't even started on containers yet...