From https://rocrate-validator.readthedocs.io/en/latest/11_writing_a_profile/#overriding-inherited-checks:
Each SHACL NodeShape / PropertyShape becomes a check whose name is its sh:name. To override an inherited check, declare a shape in the extension profile with the same sh:name as the inherited one:
I don't think this is new (we already exploited it here), it's just more explicitly supported now - I'm not sure how it works with different files that don't inherit. We should be aware that we might inadvertently be overriding some checks.
Having unique names is also just better for clearer output.
From https://rocrate-validator.readthedocs.io/en/latest/11_writing_a_profile/#overriding-inherited-checks:
I don't think this is new (we already exploited it here), it's just more explicitly supported now - I'm not sure how it works with different files that don't inherit. We should be aware that we might inadvertently be overriding some checks.
Having unique names is also just better for clearer output.