gunnarmorling/beanvalidation-spec — comment on commit ecc902c548ce9830f1aa28cadffe6d721ffaab82
File: specbook/en/modules/validation-api.xml line 904
By gunnarmorling:

So you mean in a path for a method-level validation we should have distinct node instances, one for the concerned method/constructor and one for the concerned parameter or return value?
I think to me a single node makes more sense as we just need one logical node which represents the concerned parameter or return value, of which the related method/constructor is just an additional attribute. I think it's similar to property constraints, there we also have one node instance representing the property and not two node instances, one for the bean and one for the property.
Are there any specific problems you see?