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: | Voting (under way) |
| Proposed by: | JOlshefsky |
| Draft started: | 2024-05-22 |
| RFC start: | 2024-05-22 |
| Vote start: | 2024-06-20 |
| Vote end: | 2024-07-11 |
Proposal
This proposal is to copy the Contact Details elements from contact:*=* to takeaway:*=*, delivery:*=*, and drive-thru:*=* to specify ways to order for by those methods, and add ordering:sms=*, and contact:sms=* to indicate the capabilities of each of those phone numbers.
[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.]
| Key | Value Example | Elements | Description |
|---|---|---|---|
| takeaway:phone=* | +44 11223 456-789 |   
|
A phone number associated only with placing an order for takeaway/delivery/drive-thru, such as at a restaurant where there is a different number for general information/contact. If there is only a phone number for those purposes, the existing takeaway=*, delivery=*, and drive-thru=* would continue to be an option for just a phone number. |
| takeaway::sms=yes/no/only | only |
|
An indicator that the ordering phone number accepts SMS text messaging/does not/exclusively like the existing sms=yes/no/only works. |
| takeaway:website=* | http://orders.example.com |
|
A website specifically for placing an order for takeaway/delivery/drive-thru, not for general information. |
| takeaway:email=* | order@example.com |
|
An e-mail address specifically for placing an order for takeaway/delivery/drive-thru. |
| takeaway:fax=* | +44 11223 456-789 |
|
A fax number specifically for placing an order for takeaway/delivery/drive-thru. |
| takeaway:tty=* | +44 11223 456-789 |
|
A phone number connected to a teletypewriter (tty) specifically for placing an order. |
| contact:sms=yes/no/only | only | 
|
An indicator that the contact phone number accepts SMS text messaging/does not/exclusively like the existing sms=yes/no/only works. |
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-thru=* 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-thru:*=*, 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=yes/no/only 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
- Template:Map Features:contact: add contact:sms=*
- Extend the existing takeaway=*, delivery=*, and drive-thru=* with the same elements 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
Comments
Please comment on the discussion page.
Voting
- Log in to the wiki if you are not already logged in.
- Scroll down to voting and click 'Edit source'. Copy and paste the appropriate code from this table on its own line at the bottom of the text area:
| To get this output | you type | Description |
|---|---|---|
|
{{vote|yes}} --~~~~
|
Feel free to also explain why you support proposal. |
|
{{vote|no}} reason --~~~~
|
Replace reason with your reason(s) for voting no. |
|
{{vote|abstain}} comments --~~~~
|
If you don't want to vote but have comments. Replace comments with your comments. |
~~~~ automatically inserts your name and the current date.For full template documentation see Template:Vote. See also how vote outcome is processed.
I oppose this proposal. Sorry that I have not seen it earlier. I think drive-thru:*=* is a bad naming choice, since the original key is called drive_through=*. Thus, I think it should be drive_through:*=*. Overall, I'm not against this proposal though. --Flo Edelmann (talk) 11:49, 21 June 2024 (UTC)
- I'm sorry I mistyped it in my discussion, likely causing this mistake. Didn't catch it because it is blue-linked — Kovposch (talk) 11:55, 21 June 2024 (UTC)
I have comments but abstain from voting on this proposal. I would want to discuss *:website=* vs *:url=* further, and whether contact:sms=* meaning and style is good vs other contact:*=* and sms=* — Kovposch (talk) 11:55, 21 June 2024 (UTC)- I oppose this proposal. There was a proposal (which I read) to add "ordering:" keys announced in the forums. The voting now is on something completely different. (1) As Flo2154: "drive-thru" is a bad idea. (2) "contact:sms" is already in use with a phone number. yes/no doesn't make sense IMO ("There is a way to send an sms, but we don't tell you how"). (3) The keys 'phone:delivery', 'phone:orders' and 'phone:takeaway' are already used in some dozen places. (4) What happened to "orders"? The proposal ignores the hundreds of orders-related tags, e.g. "website:orders". (5) common ways of sending orders, e.g. Whatsapp are missing. (6) Explicitly defining a limited set of tags, including obscure things like "drive-thru:tty" (was that ever a thing anywhere in the past decades?) seems problematic. A proposal should define the generic use of "delivery", "takeaway" or "orders" namespaces and link to the "contact:" keys for definitions of subkeys.--Mueschel (talk) 12:20, 21 June 2024 (UTC)