The heritage:operator tag is needed because “operator=“ is the operator of the feature, not the operator of the heritage status.
If you have an old residential building which is still in active use, the operator= is whoever manages the building now, but it might also have a heritage:operator= which will be a different value. This isn’t necessary with the ref, since the operator is in the key in the format ref:<operator> —Joseph On Tue, Apr 21, 2020 at 7:24 PM Paul Allen <pla16...@gmail.com> wrote: > On Tue, 21 Apr 2020 at 02:37, António Madeira <antoniomade...@gmx.com> > wrote: > >> So, what's the rationale for using heritage:operator and not heritage:ref? >> It's these inconsistencies that breaks my logic... >> > > Why are the eyes of tetrapods (fish, reptiles, birds, mammals) wired > backwards? Why does the recurrent laryngeal nerve from the brain > to the larynx go down into the chest and around the aorta? Why do > baleen whales develop teeth in embryo that are resorbed before they > are born? > > Same answer. The heritage tags evolved. If somebody had sat down and > thought everything through, it might have turned out differently. > > The endless bickering here is to try to ensure we think things through > and don't end up with schemes that, in hindsight, are sub-optimal. > > -- > Paul > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging >
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
