id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
12866	Display disused:railway=* and abandoned:railway=* like railway=disused/abandoned whenever relevant	Penegal	team	"Hello, there.

The lifecycle prefixes are spreading, but JOSM doesn't really take them into account, which is a shame, as this slows down the correct tagging and modelling using this tagging scheme. The first example which bothers me concerns railways: JOSM should display them like {{{railway=disused/abandoned}}}; of course, not all {{{disused:railway=*}}} and {{{abandoned:railway=*}}} should be rendered this way, only the ones about tracks:

||= current tag =||= tags to be displayed the same way =||
||{{{railway=disused}}}||{{{disused:railway=funicular|miniature|monorail|narrow_gauge|preserved|rail|tram|subway|light_rail}}}||
||{{{railway=abandoned}}}||{{{abandoned:railway=funicular|miniature|monorail|narrow_gauge|preserved|rail|tram|subway|light_rail}}}||

This could be applied to other lifecycle prefixes, as {{{construction:railway=*}}} and {{{*:highway=*}}}; I will try to make the list if this is needed or to start the debate if one is required, but these railway tags are the most bothering me, so I start with them. Of course, these lifecycle prefixes should be taken into account in the whole code, for example in the validator, as a partial support would probably accentuate the problem rather than solving it.

I must add that I looked for previous requests regarding the lifecycle prefixes, without results; that surprised me, as this tagging scheme is spreading rather quickly now. I could have simply missed these requests, so don't hit too hard if I failed to locate them…

Regards."	enhancement	new	normal		Internal mappaint style	tested		lifecycle prefix display validator