id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
16093	handling of (lifecycle) prefixes	Klumbumbus	team	"[https://wiki.openstreetmap.org/wiki/Lifecycle_prefix lifecycle prefixes] become more and more popular in osm tagging and already have high usage numbers. This leads to the situation that e.g. a lot of validator rules can produce false positives. E.g. a way tagged with disused:railway=* + electrified=* results in a warning ""electrified without railway"".
Explizitly adding all possible prefixes to all possible selectors seems impossible and inefficient. (Basically every tag could have a lifecycle prefix.)

Any ideas how we could handle (lifecycle) prefixes in styles/validator rules/presets?

Maybe also a more universal prefix solution is possible which could be used for other tagging schemas, like contact: or seamark:?

some cross references:
- #12866
- https://github.com/osm-fr/osmose-backend/issues/283
- osmwiki:Lifecycle_prefix"	enhancement	new	normal		Core			lifecycle prefix	daganzdaanda demon_box