Bogus "Conflicting values of "surface" and "surface:right""

[matkoniecz]

surface = paved
surface:left = asphalt
surface:right = paving_stones

there is no conflict whatsoever here

https://osmose.openstreetmap.fr/en/issue/92c781b4-6227-53f9-f6d1-d6752fb581f8

at https://osmose.openstreetmap.fr/en/map/#loc=22/50.05784961/19.95799327&item=xxxx&level=1%2C2%2C3

[Famlam]

This way definitely wins the price for most redundant tagging:

cycleway:surface=asphalt	
footway:surface=paving_stones	
surface=paved	
surface:left=asphalt	
surface:right=paving_stones

I'd just mark it as a false positive if you wish to keep the surface=paved tag (for legacy reasons I presume).
Unless there's a third part of this road, e.g. a bridleway in between made of an unspecified paved surface. Or if this means that the left side of the cycleway and footway is asphalt and the right side of the cycleway and footway are paving stones, but the middle part of the cycleway and footway are what is specified in the two *way:surface tags.

Personally I do consider this a tagging mistake, or at least highly redundant tagging.

[matkoniecz]

for legacy reasons I presume

for whatever does not use super-detailed tagging

or at least highly redundant tagging

well, Osmose typically pushes use of pointlessly redundant tagging so I figured it should not complain about one