The following dump represents a part of SPS for MVC+D (profile_idc 138) bitstream:
@367 num_views_minus1 011 ( 2)
@370 view_id 00100 ( 3)
@375 depth_view_present_flag 1 ( 1)
@376 texture_view_present_flag 1 ( 1)
@377 view_id 010 ( 1)
@380 depth_view_present_flag 1 ( 1)
@381 texture_view_present_flag 1 ( 1)
@382 view_id 00110 ( 5)
@387 depth_view_present_flag 1 ( 1)
@388 texture_view_present_flag 1 ( 1)

That is, the base view has view_id equal to 3.

However, the operation points are written in the SPS as follows:
@434 num_applicable_ops_minus1 1 ( 0)
@435 applicable_op_temporal_id 000 ( 0)
@438 applicable_op_num_target_views_minus1 1 ( 0)
@439 applicable_op_target_view_id 1 ( 0)
@440 applicable_op_depth_flag 0 ( 0)
@441 applicable_op_texture_flag 0 ( 0)
@442 applicable_op_num_texture_views_minus1 1 ( 0)
@443 applicable_op_num_depth_views 1 ( 0)

This has the following issues:
1) applicable_op_taget_view_id equal to 1 is a view_id value of a non-base view, hence the operation point does not procuce a conforming sub-bitstream and is therefore invalid.
2) num_applicable_ops_minus1 is equal to 0, while the bitstream would contain a greater number of operation points in practice.
3) applicable_op_temporal_id is equal to 0, while the bitstream contains a greater number of temporal_id values.

Issue 1 is major, while issues 2 and 3 would be nice to fix.

The same issues seem to be present also in the SPS for MVC (with profile_idc equal to 118).