id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
22637	Allow positive matching for match_expression attribute in preset item	Woazboat	team	"Currently the `match_expression` attribute for preset `<item>` only allows you to further restrict matches for presets. (i.e. exclude things that are matched by fields in the preset but not by the match expression)

Allowing the item match expression to act as a positive match would unlock greater flexibility for presets. 

For example, [https://wiki.openstreetmap.org/wiki/Key:crossing crossing ways] can be tagged either as [https://wiki.openstreetmap.org/wiki/Tag:footway%3Dcrossing footway=crossing], [https://wiki.openstreetmap.org/wiki/Tag:cycleway%3Dcrossing cycleway=crossing] or [https://wiki.openstreetmap.org/wiki/Tag:path%3Dcrossing path=crossing]. All of these have the same additional tags that could be used to further describe them (e.g. [https://wiki.openstreetmap.org/wiki/Key:crossing:markings crossing:markings=*]). At the moment, we would need to create three separate presets with the same content to be able to show a matching preset for each of these tags (one each with `<key key=""footway"" value=""crossing"" />`, `<key key=""cycleway"" value=""crossing"" />`, ...). It's also possible for these crossing ways to have both `footway=crossing` and `cycleway=crossing` tags if the crossing is a shared foot- and cycleway. In this case, both matching presets for `footway=crossing` and `cycleway=crossing` would be shown.

If the `match_expression` attribute on `<item>` was able to positively match objects, a single preset for these crossing ways could be created via `<item type=""way"" match_expression=""footway=crossing | cycleway=crossing | path=crossing"" ...>`"	enhancement	new	normal		Core			match_expression	simon04