Hello, You are mixing correct namespacing (like railway:switch) with... mistaken namespacing (like hydrant:position).
Now, for the reasons for namespacing and just as an example (/it is not the only good reason.../), think about documentation: the documentation for describing a power switch should not be intermixed with the documentation describing power switches. The railways people got that and they did what I think they had to do: to namespace their switch. You didn't (/if that was you.../). Big mistake, IMHO: not all the switches are your switches... Sergio On 2018-12-17 02:24, François Lacombe wrote: > Hi > > Interesting thread about namespacing in tag names. > https://wiki.openstreetmap.org/wiki/Talk:Proposed_features/Pipeline_valves_proposal#Use_namespace_or_not > Spoiler: no consensus shows up at the end. > > I still think that actuator=* is better than two pipeline:valve:actuator=* > and railway:switch:actuator=* because the first is really more concise and > reusable between valves and railway switches. > Like I don't like fire_hydrant:position instead of simpler location=*. > > Can someone brings benefits from using namespaces in this particular > situation please? > > Al the best > > François > > _______________________________________________ > Tagging mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/tagging
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging
