Proposal talk:Opening hours:signed=no
Why not use the 'note' tag ?
Could not this information be included in the note tag? The pages says this is a 'typical reason' .. that hints that there are other reasons .. so those other reasons could also be stated in a note rather than proliferate yet more tags? Warin61 (talk) 23:02, 22 May 2018 (UTC)
- This came to my mind as well. The 'note' tag is defined as containing information specifically for (other) mappers. As far as I understand, the 'opening hours:sign=no' tag would be used exclusively for this purpose as well - at least I cannot come up with any other use case. Therefore, it seems obvious that the information that there is no opening hours sign should be recorded in the 'note' tag. Since this information is solely about the opening hours (sign) and not the whole object, I would propose to record this information in 'note:opening_hours' (or was it 'opening_hours:note'?, I mix this up sometimes).
- I realize that if this note is then written in prose, it will not be possible to process this information automatically beyond detecting if there is a note referencing the opening hours at all. But I guess in the case of StreetComplete, the implementation could then be extended to exclude any elements with have any note referencing the to be edited tag (and this even be implemented generically for any quest). --Westnordost (talk) 12:39, 24 May 2018 (UTC)
- note tag would not be machine readable. opening_hours:note tag is an interesting idea, but main problem is that it would expect freeform text value. It world need to be translated into local languages, value would not be clear for mappers using different language etc. But on the other hand it would cover also all other weird issues and may be clear than a new strange tag Mateusz Konieczny (talk) 16:36, 24 May 2018 (UTC)
- Yes, it wouldn't be machine readable, but is it that important? As I said, an application that wants to read if there is something irregular with opening hours need only to look if there is a note:opening_hours at all. This discussion, sorry about that, seems to touch an issue on a broader scale, that is, what the rule of thumb should be for when to use a "normal" tags like 'noname', 'noaddress', or 'opening_hours:sign' and when to use the suggested 'note' extension. I previously asserted that the information discussed here [whether opening hours are given by sign] is only of interest for the fellow mapper and gave this as a reason why 'note:opening_hours' might be preferable. However, I now realize that it seems to be no different for tags like 'noname', 'noaddress' etc. - they are just as much only interesting for the mapper. I do not have an idea where else one would draw the line for when normal tags or 'note'-extension-tags would be preferable. If noone has an idea, perhaps it is better to stick with normal tags all the way, after all --Westnordost (talk) 18:05, 24 May 2018 (UTC)
- note tag would not be machine readable. opening_hours:note tag is an interesting idea, but main problem is that it would expect freeform text value. It world need to be translated into local languages, value would not be clear for mappers using different language etc. But on the other hand it would cover also all other weird issues and may be clear than a new strange tag Mateusz Konieczny (talk) 16:36, 24 May 2018 (UTC)
Use *:signed rather than *:sign ?
I like the concept of this tag. As a tool writer, it would be very useful to have a standard way of recording the absence of information (not limited to opening_hours) that one would normally expect to find via a survey. However, I think that opening_hours:signed rather than opening_hours:sign would be a better key name for this purpose. Something being "signed" is slightly more general than something appearing on a "sign", so *:signed=no would make better sense in other contexts. For example, for collection_times=* on a post box, where the times are typically written on a plate attached to the box. This plate wouldn't necessarily be thought of as a "sign", but if the times are they they could be thought of as being signed. One might also want to use the tag suffix with the ref key. Here, I think ref:signed is less ambiguous that ref:sign, as the latter could be referring to a sign reference number, or the reference number of a sign related to the object. (ref:signed has 129 uses, whereas ref:sign has none.) -- Rjw62 (talk) 15:00, 13 June 2018 (UTC)
- I did a quick research on taginfo and I agree with Rjw62. something:sign does appear in the database, but it is used for different information than for indicating whether something is signed or not. See note:sign destination:sign ref:sign waterway:sign maxspeed:sign --Westnordost (talk) 15:38, 13 June 2018 (UTC)