Being able to determine the rates offered by a copy shop can be useful for end users.
Here’s an example I found recently. The sign only specifies “single-side” - it is assumed that they mean black and white, A4-sized sheets.
The pricing listed is 5 INR/page for 1-5 pages, 2 INR/page for 6-50 pages, 1 INR/page for 50-100 pages, and (the sign is a bit unclear about it, but let’s assume for sake of example) 0.80 INR/page for over 101 pages.
Inspired by the conditional access key conventions. More explicit, and keeps the common information in the key. But the number of pages are still comments.
Added a print component to the key to allow differentiating from other tasks, such as copying. The comments have been replaced with values which should be formalized to allow parsing. Also has the side effect of using fewer characters, as the double quotes have been removed.
In which application should/will this be evaluated? I would put this in easy plain language in the description. In my opinion, this is a syntax that no software in the world will be able to interpret correctly in the near future.
There have been many discussions about how to add prices of shops, restaurants or hotels to OSM. All of these have in common that the vast majority of participants oppose adding this kind of data to OSM.