Opaque URIs can be a good solution when most of the resources are obtained automatically from other systems like relational databases, tables, etc.
This pattern can also be applied when there is a need to have multilingual concepts and it is preferred not to have any language bias.
Using opaque URIs may help to separate the concept from its different labels.
Opaque URIs can help to emphasize the independence of a resource from its natural language representation. This pattern emphasizes that URIs are not meant for end users but for internal applications.
Depending on the context, URIs with human-readable local names can help users and application developers to manage and debug linked data applications.
Resources with opaque URIs usually depend on labels to hide the URI from the end user.