Author: TomH
[Added to the original trac issue at 8.39am, Sunday, 30th November 2014]

As far as I know all tags on the selected object are shown in that table already. There is no such thing as an "inherited tag" in our data model.

Author: Dmitriy.Ovdienko[at]gmail.com
[Added to the original trac issue at 10.02am, Sunday, 30th November 2014]

There is no such thing as an "inherited tag" in our data model.
When you create node inside building, this node inherits addr:* tags, associatedStreet relation. For example, if you will try to search "EPAM Systems, Krakow", you will get "EPAM Systems, 25C, Generaa Tadeusza Bora-Komorowskiego, rdmiecie, Prdnik Czerwony, Cracow, Krakow, Lesser Poland Voivodeship, 31-876, Poland" however EPAM Systems node does not have addr:buildingnumber, addr:street, addr:postcode tags.

Author: TomH
[Added to the original trac issue at 10.11am, Sunday, 30th November 2014]

Certain data consumers may choose to interpret our data in our way, but that is not a fundamental feature of our data model - it is semantics layered on top of it by convention.

The data browser's purpose is to show the actual raw data in our database, without any attempt to interpret it beyond a few minimal things like picking out a name or linking URLs - it would be very confusing to show things in the tag table which are not actually present in the database.

We already show the fact that the object is a member of certain relations separately.