Or phrased differently: Why is the role called Product Owner?
I spent some hours researching the term's etymology, but I haven't been particularly successful, which is why this question came to be.
I am explicitly not asking about the definition of the role here. There are plenty of articles explaining that e.g. in the context of Scrum.
In particular, I am interested in the historical reasoning that has led to denoting it as an "owner".
It might also make sense to share some context with you to explain why this question came up in the first place: My experience is that teams unfamiliar with agile methodologies tend to replace the term "owner" in their minds with some variation of a role they already know from traditional hierarchies. This often leads to an interpretation that puts the Product Owner into some kind of principal or even boss position, which may be in stark contrast to what one wants to achieve when implementing agile processes. To be specific, what people intuitively interpret might yield views contrary to servant leadership, self-organizing teams and evolving situational hierarchies. That is why it might be necessary to better explain the context in which e.g. the Scrum definition of the "Product Owner" role should be seen with respect to the goals of the company where it is being implemented. Getting an idea about the intentions of naming it "owner" in the first place might help with that.