Ah, of course. I only meant in the case of attached images. Bones names and slot names (and i guess bounding box names) are still just names.
But in all those image cases (svg, file from disk, region in an atlas, url), it would arguably be better called a "source" or "path" instead of a "name", at least on the buttons and labels in the editor.
I realized while I was writing this that you might have actually just overloaded that field in the JSON to mean different things for different types of objects. And I understand it's hard to change something so fundamental in the JSON spec at this point.
But I would hate for Spine to be one of those programs where you have to look up a manual to find out about Editor functionality like this because of some naming quirk in the runtime and file spec. ;___;