For some applications a single "name" is good enough, but in other cases, even if your application doesn't interpret it, some downstream consumer of that information (either a person or a computer) will interpret it, like it or not, and may well be more likely to screw it up if there's no additional information (family/given distinction etc).

I think there probably isn't any universal solution that will minimize screwups in all cases, and you do need to look at your usage and audience... ><