In the spec of ARCHETYPE_TERMINOLOGY :
I think parent_archetype is confusing, because in normal understanding in ICT, it refers to inheritance. owner_archetype tells us exactly what it is, the archetype which owns the terminology
I think that's a sensible change.
Me too, I already changed it in my code (implemented it to reach on both names), because it confused me too at some moment.
It seems to make sense. I am not able to tell the consequences for existing systems (how major the change is)
I think that existing systems use AOM 1.4, so the owners should anyway keep this separated.
Agree, parent_archetype is probably confusing.