Add cryptocurrenciesAccepted property to LocalBusiness #1866
Comments
Is there a reason why |
Central Banks and the World Bank won't accept cryptocurrencies as normal currencies. So cryptocurrencies are classed as a different asset for legal reasons. That's why I suggested a new property called: "cryptocurrenciesAccepted" See here for more details about that according to the G20: https://www.bloomberg.com/news/articles/2018-03-20/when-is-a-bitcoin-not-a-bitcoin-when-it-s-an-asset-says-g-20 "Countries increasingly see cryptos as an asset, not a currency" |
@ayumihamsaki I understand that in the eyes of some banks etc cyptocurrencies are viewed differently. However, in the use case of a user identifying if a business accepts the currency they prefer, it is exactly the same as for 'normal' currencies. If a business wants to highlight specific types of payment they accept by category (cash, card, etc.,) they could always use the paymentAccepted property. If a banking organization wish to highlight that they handle cyptocurrencies, they should describe it as one of the |
@magico @RichardWallis I see what you both are saying so you both are suggesting users to write the code like this:
If that is fine then the documentation on the schema.org website can be updated to reflect accepting cryptocurrencies found here: LocalBusiness Something like: And maybe provide a code example on the same page. |
… 'paymentAccepted' & 'currenciesAccepted' properties. For consistency, also added to description of properties: 'discountCurrency', 'price', 'priceCurrency', 'currency'.
…tion for 'paymentAccepted' & 'currenciesAccepted' properties." This reverts commit 182dd79.
* Issue (#1866): Added reference to cryptocurrencies in description for 'paymentAccepted' & 'currenciesAccepted' properties. For consistency, also added to description of properties: 'discountCurrency', 'price', 'priceCurrency', 'currency'. * Fix typos * Corrections to and added RDFa & json-ld versions to HowTo examples. Issue (#1884). * Reversed some changes not needed Reversed some changes not needed as already visible on webschemas.org eg. HowToSection now a subtype of ListItem, HowToDirection now a subtype of CreativeWork. * Revert "Fix typos" Removing references to issue (#1866) incorrectly added to branch 1884 This reverts commit fc4ea93. * Revert "Issue (#1866): Added reference to cryptocurrencies in description for 'paymentAccepted' & 'currenciesAccepted' properties." This reverts commit 182dd79.
@RichardWallis Hi I was just looking at the work you are doing and I saw this in the commits:
May I suggest not using the Wikipedia link as it is not very good and well maintained a much better link would be here: http://list.wiki/Cryptocurrencies So my suggestion is this:
~If that is useful or not? |
@ayumihamsaki , @RichardWallis: Perhaps we could consider cryptocurrencies as a "parallel" property to our existing http://schema.org/currency of the financial extension (http://schema.org/docs/financial.html) and it would become the property for types like DatedMoneySpecification, ExchangeRateSpecification, MonetaryAmount (TBD)... |
@ayumihamsaki That looks like an interesting link. Before proposing using that, I would want to find out, with regard to the list.wiki site, how stable it is, who hosts it, who is behind it, how active its community is, etc. I could not ascertain this from browsing the site, or Wikipedia, or the web in general. I would also personally comment that considering the writeup on the site makes much emphasis about complementing, and making the information it contains available to, search engines, I am a little surprised that it does not yet publish Schema.org in its pages. |
@sopekmir I think a separate cryptocurrency property is unnecessary. The currency property is capable of holding a mixture of types. All that is needed is relevant guidance in the term definition. My current proposed version for this is:
|
@RichardWallis I did a quick search in regards to how stable their website is and found this information: Their information is found here: http://list.wiki/index.php?title=Main_Page&action=info I can totally understand if you prefer to link to the main Wikipedia due to link rot. (I didn't think of that issue when I made my suggestion). |
@RichardWallis - I agree. Seems I just did not remember that the range of the currency property is text and can take values from other sources than ISO 4217. And as far as I see - you added the references to the cryptocurrencies for this and other relevant properties. So this seems to be resolved. Is it? |
…#1894) * Issue (#1866): Added reference to cryptocurrencies in description for 'paymentAccepted' & 'currenciesAccepted' properties. For consistency, also added to description of properties: 'discountCurrency', 'price', 'priceCurrency', 'currency'. * Fix typos * Updated the description additions to reference ISO 4217 formats, cryptocurrency Ticker symbols, LETS and other currency types including single inline examples for each.
Released in V3.4 |
See issue for discussion of whether broadcastSignalModulation should be used. Example needs review.
Many businesses now accept cryptocurrencies as real payment exchanges. I am proposing to add the property: "
cryptocurrenciesAccepted
" to the "LocalBusiness
".You can use the same ISO 4217 currency format as for
currenciesAccepted
. For example bitcoin would be "BTC". Because all cryptocurrencies use a Trading Ticker exactly the same as currencies.I also propose updating "
paymentAccepted
" and adding "Cryptocurrency
" to the valid list.An example code is below:
I look forward to the schema team looking into this proposal in more detail.
Many Thanks.
The text was updated successfully, but these errors were encountered: