Context Navigation

Changes between Version 1 and Version 2 of Ticket #20468, comment 18

v1	v2
1	1	The time when `opposite*` was introduced it was already controversial as it was always intended only for opposite direction and it did not clearify how to deal with the bicycle infrastructure in "positive" direction. In these days it also served the purpose for `oneway:bicycle=no` as the later and `:left/:right/:forward/:backward` did all not exist.
2	2
3		Let's take a look at todays tags. First of all, we talk about highways with `oneway=yes`. `cycleway`=* is regarded to be on both side but not together with `oneway=yes` where it only refers to the "positive" direction. At least, that is the common practice and makes it easier to tag all oneway-highways without `oneway:bicycle=no`. If the later is true we might be better of with always using `cycleway:left=lane/track/share_bus_way/no` and `cycleway:right=lane/track/share_bus_way/no`.
	3	Let's take a look at todays tags. First of all, we talk about highways with `oneway=yes`. `cycleway`=* is regarded to be on both side but not together with `oneway=yes` where it only refers to the "positive" direction. At least, that is the common practice and makes it easier to tag all oneway-highways without `oneway:bicycle=no`. If the later is true we might be better off with always using `cycleway:left=lane/track/share_bus_way/no` and `cycleway:right=lane/track/share_bus_way/no`.
4	4
5	5	I hoped, we could deprecate `opposite*` with the changes to `:left/:right` but I does not work.