Here is my take on the spec wording

Try to apply the View configuration. If applying the View results in conflicting metric identities the implementation SHOULD apply the View and emit a warning.

Conflicting identities would be as described in the link; all the identifying properties of the Metric are the same (everything but description). This is distinct from the next sentence

If it is not possible to apply the View without producing semantic errors (e.g. the View sets an asynchronous instrument to use the Explicit bucket histogram aggregation) the implementation SHOULD emit a warning and proceed as if the View did not exist.

in addition to instrument/aggregation mismatches, another other semantic error would be "the presence of multiple Metric identities for a given name with the same Resource and Scope attributes.".

It's not 100% clear to me why it's specified this way, but that's my take. Wdyt?

Approving in advance