Examine individual changes

Abuse Filter navigation (Home | Recent filter changes | Examine past edits | Abuse log)
Jump to navigation Jump to search

This page allows you to examine the variables generated by the Abuse Filter for an individual change.

Variables generated for this change

VariableValue
Edit count of the user (user_editcount)
17
Name of the user account (user_name)
'JOlshefsky'
Whether or not a user is editing through the mobile interface (user_mobile)
false
Page ID (page_id)
318297
Page namespace (page_namespace)
3000
Page title (without namespace) (page_title)
'Phone: key variations for sms-only add ordering: key like contact:'
Full page title (page_prefixedtitle)
'Proposal:Phone: key variations for sms-only add ordering: key like contact:'
Action (action)
'edit'
Edit summary/reason (summary)
'Release the proposal.'
Old content model (old_content_model)
'wikitext'
New content model (new_content_model)
'wikitext'
Old page wikitext, before the edit (old_wikitext)
'{{Proposal page |name = Phone: key variations for sms-only add ordering: key like contact: |user = JOlshefsky |key = <!-- The key of the proposed new tag, if relevant --> |value = <!-- The value of the proposed new tag, if relevant --> |type = <!-- node, way, area, relation --> |definition = <!-- A short, clear definition of the feature or property which the new tag represents --> |appearance = <!-- A possible rendering, if relevant - optional --> |status = Draft |draftStartDate = 2024-05-22 |rfcStartDate = <!-- Date the RFC email is sent to the Tagging list: YYYY-MM-DD --> |voteStartDate = <!-- Date voting will start: at least 2 weeks after RFC, YYY-MM-DD format --> |voteEndDate = <!-- Date voting will end: at least 2 weeks after start of voting, YYY-MM-DD format --> }} ==Proposal== <!-- A short statement of what you propose, including a list of what tag(s) are being proposed to be added, changed, or deprecated --> This proposal is to copy the Contact Details elements from {{Tag|contact:*}}, add {{Tag|ordering:sms}}, and add {{Tag|contact:sms}}. <!-- Which Database Elements (nodes, ways, areas, relations) each of the tags can be used on could be included here or under the Tagging heading, or both. --> {| class="wikitable" |- !Key!!Value!!Elements!!Description |- | {{Tag|ordering:phone}} | +44 11223 456-789 | {{iconNode}} {{iconArea}} {{iconRelation}} |A phone number associated only with placing an order, such as at a restaurant where there is a different number for general information/contact. |- |{{Tag|ordering:website}} |http://orders.example.com |{{iconNode}} {{iconArea}} {{iconRelation}} | A website specifically for placing an order, not for general information. |- |{{Tag|ordering:email}} |order@example.com |{{iconNode}} {{iconArea}} {{iconRelation}} |An e-mail address specifically for placing an order. |- | {{Tag|ordering:fax}} | +44 11223 456-789 |{{iconNode}} {{iconArea}} {{iconRelation}} |A fax number specifically for placing an order. |- | {{Tag|ordering:mobile}} | +44 11223 456-789 | {{iconNode}} {{iconArea}} {{iconRelation}} | A phone number associated only with placing an order, either by voice-call or SMS text messaging. |- |{{Tag|ordering:tty}} | +44 11223 456-789 |{{iconNode}} {{iconArea}} {{iconRelation}} |A phone number connected to a teletypewriter (tty) specifically for placing an order. |- |{{Tag|contact:sms}} | +44 11223 456-789 |{{IconNode}} {{IconWay}} {{IconArea}} {{IconRelation}} |A general contact phone number that only accepts SMS text messaging. This is to differentiate from {{Tag|contact:mobile}} which can accept voice-calls as well. |} ==Rationale== <!-- Explanation of why the proposal is needed, and why you chose the specific key and value of the tag. Compare with similar tags or previous proposals, if relevant. Consider significance and potential uses of the data.-->After finding a restaurant {{Node|4239863491|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 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, {{Tag|contact:phone}} would likely be fine for this purpose. Expanding to include the Contact Details options would permit, say, a specific ordering website if it is different from the main website (with the caveat that this opens up potential <s>abuse</s> ... <s>misuse</s> ... "over-"use with online-ordering systems like Grubhub or UberEats.) 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 the tagging is to help users avoid the error of calling such a number and possibly leaving a message that would never be heard or answered.<!-- Keep the tag short while still being logical and descriptive enough to need little explanation. Avoid tag names which might cause confusion with a different tag. British English terms are preferred, when possible --> ==Tagging== <!-- A table, list, or set of subheadings explaining each tag: * Definition of the meaning of the tag and how it should be used * Elements tagged: nodes, ways, areas or relations? [if a feature is smaller than 5m by 5m it would usually be mapped only as a node] * Comparison with current tagging schemes (if applicable) * Additional tags used in combination (including existing tags) * When other tags should be used instead. -->Since the {{Tag|ordering:*}} is primarily to attach to restaurants, 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 {{Tag|contact:sms}} is an extension to the existing Contact Details, it would be applicable to nodes, ways, areas, and relations. ==Examples== <!-- Examples of what elements should be tagged: real-world images, openstreetmap.org screenshots, links to OpenStreetMap elements that use the proposed tagging. -->For ordering, the specific example above is {{Node|4239863491|Founder's Cafe|tools=all}} which, according to [https://founderscaferochester.com/ its website], has a text-only number to place orders. An area would be, for instance, {{Area|1145124784|Domino's|tools=all}} rendered as a building. ==Features/Pages affected== # <!-- List of wiki pages that would be edited if the proposal is approved -->[[Template:Map Features:contact]]: add {{Tag|contact:sms}} # New page for {{Tag|ordering:*}} ==External discussions== <!-- Links to mailing lists, other forums where this proposal has been discussed... -->Please, cross post this announcement on the tagging mailing list on my behalf by sending an email to: tagging@openstreetmap.org <!-- todo: add link to RFC in forum. --> ==Comments== <!-- There must be at least 2 weeks set aside for comment on the proposal. Do not go to a vote without addressing the comments and fixing any problems with the proposal. The wiki talk page is used for comments, it is linked from the proposal page for those unfamiliar with wikis. --> Please comment on the [[{{TALKPAGENAME}}|discussion page]].'
New page wikitext, after the edit (new_wikitext)
'{{Proposal page | name = Add ordering:* keys mimicking contact:* keys for placing orders; add contact:sms for text-only contact | user = JOlshefsky | key = <!-- The key of the proposed new tag, if relevant --> | value = <!-- The value of the proposed new tag, if relevant --> | type = <!-- node, way, area, relation --> | definition = <!-- A short, clear definition of the feature or property which the new tag represents --> | appearance = <!-- A possible rendering, if relevant - optional --> | status = Proposed | draftStartDate = 2024-05-22 | rfcStartDate = 2024-05-22 | voteStartDate = 2024-06-10 | voteEndDate = 2024-07-01 }} ==Proposal== <!-- A short statement of what you propose, including a list of what tag(s) are being proposed to be added, changed, or deprecated --> This proposal is to copy the Contact Details elements from {{Tag|contact:*}}, add {{Tag|ordering:sms}}, and add {{Tag|contact:sms}}. <!-- Which Database Elements (nodes, ways, areas, relations) each of the tags can be used on could be included here or under the Tagging heading, or both. --> {| class="wikitable" |- !Key!!Value!!Elements!!Description |- | {{Tag|ordering:phone}} | +44 11223 456-789 | {{iconNode}} {{iconArea}} {{iconRelation}} |A phone number associated only with placing an order, such as at a restaurant where there is a different number for general information/contact. |- |{{Tag|ordering:website}} |http://orders.example.com |{{iconNode}} {{iconArea}} {{iconRelation}} | A website specifically for placing an order, not for general information. |- |{{Tag|ordering:email}} |order@example.com |{{iconNode}} {{iconArea}} {{iconRelation}} |An e-mail address specifically for placing an order. |- | {{Tag|ordering:fax}} | +44 11223 456-789 |{{iconNode}} {{iconArea}} {{iconRelation}} |A fax number specifically for placing an order. |- | {{Tag|ordering:mobile}} | +44 11223 456-789 | {{iconNode}} {{iconArea}} {{iconRelation}} | A phone number associated only with placing an order, either by voice-call or SMS text messaging. |- |{{Tag|ordering:tty}} | +44 11223 456-789 |{{iconNode}} {{iconArea}} {{iconRelation}} |A phone number connected to a teletypewriter (tty) specifically for placing an order. |- |{{Tag|contact:sms}} | +44 11223 456-789 |{{IconNode}} {{IconWay}} {{IconArea}} {{IconRelation}} |A general contact phone number that only accepts SMS text messaging. This is to differentiate from {{Tag|contact:mobile}} which can accept voice-calls as well. |} ==Rationale== <!-- Explanation of why the proposal is needed, and why you chose the specific key and value of the tag. Compare with similar tags or previous proposals, if relevant. Consider significance and potential uses of the data.-->After finding a restaurant {{Node|4239863491|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 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, {{Tag|contact:phone}} would likely be fine for this purpose. Expanding to include the Contact Details options would permit, say, a specific ordering website if it is different from the main website (with the caveat that this opens up potential <s>abuse</s> ... <s>misuse</s> ... "over-"use with online-ordering systems like Grubhub or UberEats.) 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 the tagging is to help users avoid the error of calling such a number and possibly leaving a message that would never be heard or answered.<!-- Keep the tag short while still being logical and descriptive enough to need little explanation. Avoid tag names which might cause confusion with a different tag. British English terms are preferred, when possible --> ==Tagging== <!-- A table, list, or set of subheadings explaining each tag: * Definition of the meaning of the tag and how it should be used * Elements tagged: nodes, ways, areas or relations? [if a feature is smaller than 5m by 5m it would usually be mapped only as a node] * Comparison with current tagging schemes (if applicable) * Additional tags used in combination (including existing tags) * When other tags should be used instead. -->Since the {{Tag|ordering:*}} is primarily to attach to restaurants, 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 {{Tag|contact:sms}} is an extension to the existing Contact Details, it would be applicable to nodes, ways, areas, and relations. ==Examples== <!-- Examples of what elements should be tagged: real-world images, openstreetmap.org screenshots, links to OpenStreetMap elements that use the proposed tagging. -->For ordering, the specific example above is {{Node|4239863491|Founder's Cafe|tools=all}} which, according to [https://founderscaferochester.com/ its website], has a text-only number to place orders. An area would be, for instance, {{Area|1145124784|Domino's|tools=all}} rendered as a building. ==Features/Pages affected== # <!-- List of wiki pages that would be edited if the proposal is approved -->[[Template:Map Features:contact]]: add {{Tag|contact:sms}} # New page for {{Tag|ordering:*}} ==External discussions== <!-- Links to mailing lists, other forums where this proposal has been discussed... -->Please, cross post this announcement on the tagging mailing list on my behalf by sending an email to: tagging@openstreetmap.org <!-- todo: add link to RFC in forum. --> ==Comments== <!-- There must be at least 2 weeks set aside for comment on the proposal. Do not go to a vote without addressing the comments and fixing any problems with the proposal. The wiki talk page is used for comments, it is linked from the proposal page for those unfamiliar with wikis. --> Please comment on the [[{{TALKPAGENAME}}|discussion page]].'
Unified diff of changes made by edit (edit_diff)
'@@ -1,15 +1,15 @@ {{Proposal page -|name = Phone: key variations for sms-only add ordering: key like contact: -|user = JOlshefsky -|key = <!-- The key of the proposed new tag, if relevant --> -|value = <!-- The value of the proposed new tag, if relevant --> -|type = <!-- node, way, area, relation --> -|definition = <!-- A short, clear definition of the feature or property which the new tag represents --> -|appearance = <!-- A possible rendering, if relevant - optional --> -|status = Draft -|draftStartDate = 2024-05-22 -|rfcStartDate = <!-- Date the RFC email is sent to the Tagging list: YYYY-MM-DD --> -|voteStartDate = <!-- Date voting will start: at least 2 weeks after RFC, YYY-MM-DD format --> -|voteEndDate = <!-- Date voting will end: at least 2 weeks after start of voting, YYY-MM-DD format --> +| name = Add ordering:* keys mimicking contact:* keys for placing orders; add contact:sms for text-only contact +| user = JOlshefsky +| key = <!-- The key of the proposed new tag, if relevant --> +| value = <!-- The value of the proposed new tag, if relevant --> +| type = <!-- node, way, area, relation --> +| definition = <!-- A short, clear definition of the feature or property which the new tag represents --> +| appearance = <!-- A possible rendering, if relevant - optional --> +| status = Proposed +| draftStartDate = 2024-05-22 +| rfcStartDate = 2024-05-22 +| voteStartDate = 2024-06-10 +| voteEndDate = 2024-07-01 }} '
Unified diff of changes made by edit, pre-save transformed (edit_diff_pst)
'@@ -1,15 +1,15 @@ {{Proposal page -|name = Phone: key variations for sms-only add ordering: key like contact: -|user = JOlshefsky -|key = <!-- The key of the proposed new tag, if relevant --> -|value = <!-- The value of the proposed new tag, if relevant --> -|type = <!-- node, way, area, relation --> -|definition = <!-- A short, clear definition of the feature or property which the new tag represents --> -|appearance = <!-- A possible rendering, if relevant - optional --> -|status = Draft -|draftStartDate = 2024-05-22 -|rfcStartDate = <!-- Date the RFC email is sent to the Tagging list: YYYY-MM-DD --> -|voteStartDate = <!-- Date voting will start: at least 2 weeks after RFC, YYY-MM-DD format --> -|voteEndDate = <!-- Date voting will end: at least 2 weeks after start of voting, YYY-MM-DD format --> +| name = Add ordering:* keys mimicking contact:* keys for placing orders; add contact:sms for text-only contact +| user = JOlshefsky +| key = <!-- The key of the proposed new tag, if relevant --> +| value = <!-- The value of the proposed new tag, if relevant --> +| type = <!-- node, way, area, relation --> +| definition = <!-- A short, clear definition of the feature or property which the new tag represents --> +| appearance = <!-- A possible rendering, if relevant - optional --> +| status = Proposed +| draftStartDate = 2024-05-22 +| rfcStartDate = 2024-05-22 +| voteStartDate = 2024-06-10 +| voteEndDate = 2024-07-01 }} '
Lines added in edit (added_lines)
[ 0 => '| name = Add ordering:* keys mimicking contact:* keys for placing orders; add contact:sms for text-only contact', 1 => '| user = JOlshefsky', 2 => '| key = <!-- The key of the proposed new tag, if relevant -->', 3 => '| value = <!-- The value of the proposed new tag, if relevant -->', 4 => '| type = <!-- node, way, area, relation -->', 5 => '| definition = <!-- A short, clear definition of the feature or property which the new tag represents -->', 6 => '| appearance = <!-- A possible rendering, if relevant - optional -->', 7 => '| status = Proposed', 8 => '| draftStartDate = 2024-05-22', 9 => '| rfcStartDate = 2024-05-22', 10 => '| voteStartDate = 2024-06-10', 11 => '| voteEndDate = 2024-07-01' ]
Lines removed in edit (removed_lines)
[ 0 => '|name = Phone: key variations for sms-only add ordering: key like contact:', 1 => '|user = JOlshefsky', 2 => '|key = <!-- The key of the proposed new tag, if relevant -->', 3 => '|value = <!-- The value of the proposed new tag, if relevant -->', 4 => '|type = <!-- node, way, area, relation -->', 5 => '|definition = <!-- A short, clear definition of the feature or property which the new tag represents -->', 6 => '|appearance = <!-- A possible rendering, if relevant - optional -->', 7 => '|status = Draft', 8 => '|draftStartDate = 2024-05-22', 9 => '|rfcStartDate = <!-- Date the RFC email is sent to the Tagging list: YYYY-MM-DD -->', 10 => '|voteStartDate = <!-- Date voting will start: at least 2 weeks after RFC, YYY-MM-DD format -->', 11 => '|voteEndDate = <!-- Date voting will end: at least 2 weeks after start of voting, YYY-MM-DD format -->' ]
Lines added in edit, pre-save transformed (added_lines_pst)
[ 0 => '| name = Add ordering:* keys mimicking contact:* keys for placing orders; add contact:sms for text-only contact', 1 => '| user = JOlshefsky', 2 => '| key = <!-- The key of the proposed new tag, if relevant -->', 3 => '| value = <!-- The value of the proposed new tag, if relevant -->', 4 => '| type = <!-- node, way, area, relation -->', 5 => '| definition = <!-- A short, clear definition of the feature or property which the new tag represents -->', 6 => '| appearance = <!-- A possible rendering, if relevant - optional -->', 7 => '| status = Proposed', 8 => '| draftStartDate = 2024-05-22', 9 => '| rfcStartDate = 2024-05-22', 10 => '| voteStartDate = 2024-06-10', 11 => '| voteEndDate = 2024-07-01' ]
New page wikitext, pre-save transformed (new_pst)
'{{Proposal page | name = Add ordering:* keys mimicking contact:* keys for placing orders; add contact:sms for text-only contact | user = JOlshefsky | key = <!-- The key of the proposed new tag, if relevant --> | value = <!-- The value of the proposed new tag, if relevant --> | type = <!-- node, way, area, relation --> | definition = <!-- A short, clear definition of the feature or property which the new tag represents --> | appearance = <!-- A possible rendering, if relevant - optional --> | status = Proposed | draftStartDate = 2024-05-22 | rfcStartDate = 2024-05-22 | voteStartDate = 2024-06-10 | voteEndDate = 2024-07-01 }} ==Proposal== <!-- A short statement of what you propose, including a list of what tag(s) are being proposed to be added, changed, or deprecated --> This proposal is to copy the Contact Details elements from {{Tag|contact:*}}, add {{Tag|ordering:sms}}, and add {{Tag|contact:sms}}. <!-- Which Database Elements (nodes, ways, areas, relations) each of the tags can be used on could be included here or under the Tagging heading, or both. --> {| class="wikitable" |- !Key!!Value!!Elements!!Description |- | {{Tag|ordering:phone}} | +44 11223 456-789 | {{iconNode}} {{iconArea}} {{iconRelation}} |A phone number associated only with placing an order, such as at a restaurant where there is a different number for general information/contact. |- |{{Tag|ordering:website}} |http://orders.example.com |{{iconNode}} {{iconArea}} {{iconRelation}} | A website specifically for placing an order, not for general information. |- |{{Tag|ordering:email}} |order@example.com |{{iconNode}} {{iconArea}} {{iconRelation}} |An e-mail address specifically for placing an order. |- | {{Tag|ordering:fax}} | +44 11223 456-789 |{{iconNode}} {{iconArea}} {{iconRelation}} |A fax number specifically for placing an order. |- | {{Tag|ordering:mobile}} | +44 11223 456-789 | {{iconNode}} {{iconArea}} {{iconRelation}} | A phone number associated only with placing an order, either by voice-call or SMS text messaging. |- |{{Tag|ordering:tty}} | +44 11223 456-789 |{{iconNode}} {{iconArea}} {{iconRelation}} |A phone number connected to a teletypewriter (tty) specifically for placing an order. |- |{{Tag|contact:sms}} | +44 11223 456-789 |{{IconNode}} {{IconWay}} {{IconArea}} {{IconRelation}} |A general contact phone number that only accepts SMS text messaging. This is to differentiate from {{Tag|contact:mobile}} which can accept voice-calls as well. |} ==Rationale== <!-- Explanation of why the proposal is needed, and why you chose the specific key and value of the tag. Compare with similar tags or previous proposals, if relevant. Consider significance and potential uses of the data.-->After finding a restaurant {{Node|4239863491|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 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, {{Tag|contact:phone}} would likely be fine for this purpose. Expanding to include the Contact Details options would permit, say, a specific ordering website if it is different from the main website (with the caveat that this opens up potential <s>abuse</s> ... <s>misuse</s> ... "over-"use with online-ordering systems like Grubhub or UberEats.) 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 the tagging is to help users avoid the error of calling such a number and possibly leaving a message that would never be heard or answered.<!-- Keep the tag short while still being logical and descriptive enough to need little explanation. Avoid tag names which might cause confusion with a different tag. British English terms are preferred, when possible --> ==Tagging== <!-- A table, list, or set of subheadings explaining each tag: * Definition of the meaning of the tag and how it should be used * Elements tagged: nodes, ways, areas or relations? [if a feature is smaller than 5m by 5m it would usually be mapped only as a node] * Comparison with current tagging schemes (if applicable) * Additional tags used in combination (including existing tags) * When other tags should be used instead. -->Since the {{Tag|ordering:*}} is primarily to attach to restaurants, 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 {{Tag|contact:sms}} is an extension to the existing Contact Details, it would be applicable to nodes, ways, areas, and relations. ==Examples== <!-- Examples of what elements should be tagged: real-world images, openstreetmap.org screenshots, links to OpenStreetMap elements that use the proposed tagging. -->For ordering, the specific example above is {{Node|4239863491|Founder's Cafe|tools=all}} which, according to [https://founderscaferochester.com/ its website], has a text-only number to place orders. An area would be, for instance, {{Area|1145124784|Domino's|tools=all}} rendered as a building. ==Features/Pages affected== # <!-- List of wiki pages that would be edited if the proposal is approved -->[[Template:Map Features:contact]]: add {{Tag|contact:sms}} # New page for {{Tag|ordering:*}} ==External discussions== <!-- Links to mailing lists, other forums where this proposal has been discussed... -->Please, cross post this announcement on the tagging mailing list on my behalf by sending an email to: tagging@openstreetmap.org <!-- todo: add link to RFC in forum. --> ==Comments== <!-- There must be at least 2 weeks set aside for comment on the proposal. Do not go to a vote without addressing the comments and fixing any problems with the proposal. The wiki talk page is used for comments, it is linked from the proposal page for those unfamiliar with wikis. --> Please comment on the [[{{TALKPAGENAME}}|discussion page]].'
Unix timestamp of change (timestamp)
'1716415777'