[Tagging] Feature Proposal - RFC - namespaces for key prefixes & suffixes
Mateusz Konieczny
matkoniecz at tutanota.com
Thu Jun 30 14:12:45 UTC 2022
29 cze 2022, 22:50 od martin at push-f.com:
> On 6/29/22 1:51 AM, Mateusz Konieczny via Tagging wrote:
>
>> "move Key:drink to KeyPrefix:drink & document Key:drink as a tagging mistake"
>>
>> I would do it separately. Note
>> "The individual tag values can be yes, served, retail, draught or bottled."
>> at https://wiki.openstreetmap.org/wiki/Key:drink <https://wiki.openstreetmap.org/wiki/Key:drink>
>>
>> The same for other tags mentioned there.
>>
>
> Ah, yes. I removed these deprecations from the proposal. (I don't think anybody would disagree with addr=* and contact=* being tagging mistakes but if that distracts from the proposal, I agree that it's better to keep that separate).
>
thanks
>> Also, I prefer KeyPrefix:disused: over KeyPrefix:disused
>>
>
> I disagree, since that becomes a mess for suffixes.
>
>> I would consider: KeyPart:conditional: over KeySuffix:conditional
>>
>
> I guess you mean KeyPart::conditional? Because with a suffix the : comes before the suffix ... not after.
> I find KeyPart::conditional to be very unpleasing / confusing.
>
> Besides I strongly disagree with using KeyPart for both KeyPrefix and KeySuffix
> because some string might have different meaning as a prefix or a suffix.
>
>> to avoid prefix/suffix understandable by 1% of people
>>
>
> The template could generate a description like "A [[namespace|key prefix]] for {{description}}"
> so that people who don't know what a prefix is can click on that for the explanation.
>
good points, it makes sense
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20220630/4bf3026d/attachment.htm>
More information about the Tagging
mailing list