Proposal:Add ability to specify ordering-only phone number, sms-only phone numbers and related tags
| Add ordering:* keys mimicking contact:* keys for placing orders; add contact:sms for text-only contact | |
|---|---|
| Proposal status: | Approved (active) |
| Proposed by: | JOlshefsky |
| Draft started: | 2024-05-22 |
| RFC start: | 2024-06-24 |
| Vote start: | 2024-07-15 |
| Vote end: | 2024-07-29 |
Proposal
This proposal is to clarify the usage of takeaway=*, delivery=*, and drive_through=* to use the same sub-tags as contact:*=*, and formally add contact:sms=*, currently in rare use with a phone number (per contact:sms taginfo).
[Note that the original proposal called for a new ordering:*=* but through discussion with Kovposch, I have changed the proposal, extending the dates to start voting. A later change removed the duplication of the contact:*=* sub-tags, instead making a reference to them, and I extended the voting date to allow for more comments.]
| Key | Usage examples | Elements | Description |
|---|---|---|---|
| takeaway:*=* | delivery:website=https://ordering.example.com/
takeaway:email=order@example.com drive_through:sms=+44 11223 456-789 |
  
|
Update the documentation for these tags to refer to sub-tags from contact:*=*, allowing the use of the same set of sub-tags. |
| contact:sms=* | contact:sms=+44 11223 456-789} | 
|
Formally define the sub-tag to accept phone-number values. |
Rationale
After finding a restaurant Founder's Cafe Founder's Cafe that had an SMS-only ordering phone, I found there was no way to tag either ordering or SMS-only.
In the case of contact-information specifically for placing an order, there does not appear to be a key that has a similar rationale. (A similar feature might be for pre-recorded message phone numbers, but for the most part, contact:phone=* would likely be fine for that purpose.) Expanding to include the Contact Details options would permit, say, a specific ordering website if it is different from the main website. Extending the existing takeaway=*, delivery=*, and drive_through=* allows a more fine-grained method of specifying information for each of those purposes.
In the case of SMS-only, this is new-to-me personally, but not surprising at all to have a phone number that is never voice-answered. The purpose of adding keys like the existing general-purpose sms=yes/no/only is to help users avoid the error of calling such a number and possibly leaving a message that would never be heard or answered.
Tagging
The takeaway:*=*, delivery:*=*, and drive_through:*=*, is primarily to attach to restaurants, but it should be applicable to nodes, areas, and relations. It could also be applicable to other kinds of businesses or services that permit placing orders—say a grocery delivery service, or a hardware store.
The contact:sms=* is an extension to the existing Contact Details, it would be applicable to nodes, ways, areas, and relations.
Examples
For ordering, the specific example above is Founder's Cafe Founder's Cafe (iD JOSM history) which, according to its website, has a text-only number to place orders. An area would be, for instance, Domino's Domino's (iD JOSM history) rendered as a building.
Features/Pages affected
- Extend contact:*=* by adding contact:sms=*.
- Extend the existing takeaway=*, delivery=*, and drive_through=* to refer to the sub-tags from contact:*=* (including the new contact:sms=*).
External discussions
Please, cross post this announcement on the tagging mailing list on my behalf by sending an email to: tagging@openstreetmap.org
- Community Forum:
Comments
Please comment on the discussion page.
Voting
Voting on this proposal has been closed.
It was approved with 10 votes for, 0 votes against and 5 abstentions.
The concerns expressed by the voters should be taken into account in the documentation on new or updated feature pages.
I approve this proposal. --JOlshefsky (talk) 10:52, 16 July 2024 (UTC)- I approve this proposal. --Mueschel (talk) 09:40, 18 July 2024 (UTC)
- I approve this proposal. --Chris2map (talk) 17:11, 18 July 2024 (UTC)
- I approve this proposal. --Broiledpeas (talk) 22:20, 18 July 2024 (UTC)
I have comments but abstain from voting on this proposal. If this gets accepted, please add wording to make it clear that the specific tags should only be added if the general contact method is not for ordering. Otherwise I foresee people adding the standard phone number three times in different tags. Also care should be taken that any ordering website specification does not invite spam (eg. tagging some food delivery service in every restaurants's delivery website URL) --Woodpeck (talk) 21:15, 19 July 2024 (UTC)- I have comments but abstain from voting on this proposal. I'm undecided whether it would be better to have the info's attached to the type of service (deliveryphone) or if keeping things under contact:* (contact:phone:delivery) would be better. The later one would allow data users to easily display those means of contact even if they are not aware of each indivudal tag (display all contact:*) --Hedaja (talk) 15:41, 21 July 2024 (UTC)
- I approve this proposal. --Nospam2005 (talk) 19:59, 21 July 2024 (UTC)
- I approve this proposal. --GanderPL (talk) 08:50, 22 July 2024 (UTC)
- I approve this proposal. --EneaSuper (talk) 14:04, 22 July 2024 (UTC)
- I have comments but abstain from voting on this proposal. I agree with Woodpeck's and Hedaja's comments. --501ghost (talk) 06:36, 24 July 2024 (UTC)
- I approve this proposal. --Uboot (talk) 07:20, 25 July 2024 (UTC)
- I have comments but abstain from voting on this proposal. I have the same reservations as Woodpeck --Nadjita (talk) 08:33, 26 July 2024 (UTC)
- I approve this proposal. --Jean-Baptiste (talk) 12:40, 28 July 2024 (UTC)
- I have comments but abstain from voting on this proposal. I agree with Woodpeck Mateusz Konieczny (talk) 17:47, 28 July 2024 (UTC)
- I approve this proposal. --Emmanuel 18:14, 28 July 2024 (UTC)
