Talk:Key:ref:vatin

• What do you think, does it make sense to tag the VAT numbers? Are they being used somewhere to your knowledge? Out is it a waste of time and date storage? -User:Geohobbes 06:00, 23 August 2022‎
• Yes, if we purchase something in a shop or fast food place, take the receipt and write down the VAT number. It can be useful to later correlate with company registries if the official name is different than that signed. We can also cross correlate with outside databases or imports later on to validate whether a company is still alive. It also helps on the ground to discern between the various vendors or fast food places at high density malls, especially if the address only includes the house number of the building. As it is mandated by law that they must post it on their website, it also helps in finding the website of a shop if the name would otherwise be too generic to search for. -Bkil (talk) 10:48, 23 August 2022 (UTC)

Should China's unified social credit ID be seen as vatin?

Here are 2 kinds of business license in China(old version and latest version, both are vaild):

• old version, this business license contain Registration Number, Organization Code and Tax Registration Number(National one and Local one, those 2 like USA’s EIN and can be seen as VAT id, I think)(注册号、组织机构代码和税务登记号)
• latest version, this only have a Unified Social Credit ID(统一社会信用代码) in license. Then it will be only identifier for company.

This license is mandatory if someone want to do any business in China, and those 3 ID was merged into 1 after 2012.

So should this be seen as value for ref:vatin? Or something like ref:uni_social_credit?

If so I'll change this: ref:vatin in id-tagging-schema.

I searched that US use EIN to identify company, and it excluded in vatin.

(BTW, in Taiwan they also have a 統一編號 play similar role like Unified Social Credit ID, this will need local community's discussion.)

--快乐的老鼠宝宝 (talk) 12:59, 13 November 2022 (UTC)

onWay and onRelation

@Maro21: About this change of the ref:vatin data item. I think that both ways and relations can have meaningful uses of ref:vatin=*. Examples are an aerialway=cable_car 30838313 30838313 and type=route 7085517 7085517. They're rare, but possible. --Henry572 (talk) 22:19, 10 March 2024 (UTC)

The question is "SHOULD it be used on ways and relation?", not "Are there any cases where it has been used on ways and relation?". Articles Tag:aerialway=cable_car and Relation:route don't mention tags such as [phone], [email] or [ref:vatin] as used in combination. Can cable cars have VAT? Can routes have VAT? Route is abstract, not a physical object. What I care about is that the documentation is consistent. maro21 23:05, 10 March 2024 (UTC)

As mentioned on the other talk page, if you execute the shared overpass query, you can find examples of quite a few other kinds of objects where you should add ref:vatin=* and certain other POI-relevant tags. We don't want to make documentation consistent for editors with OCD, we want it to be true. Bkil (talk) 08:50, 11 March 2024 (UTC)