Handle the case where 2 different pages could have the same target

Example:

    <page>
      <fullName>Movies.WebHome</fullName>
      <parent>Main.WebHome</parent>
    </page>
    <!-- Create a conflict -->
    <page>
      <fullName>SciFi.List</fullName>
      <parent>Movies.WebHome</parent>
    </page>
    <page>
      <fullName>Dramas.List</fullName>
      <parent>Movies.WebHome</parent>
    </page>

The risk is to have only one page called Movies.List.WebHome which could be both SciFi.List and Dramas.List

Proposition 1: The UI should trigger an event when such a case appears. It shows that maybe the current parent/child relationship should be fixed
Proposition 2: Having Movies.SciFi.List.WebHome and Movies.Dramas.List.WebHome.
It's a bit complicated since it requires to change SciFi.List children that might have been already computed. It needs a step back mechanism and it complicates a lot the algorithm (we end-up with an combinatorial optimization problem which is NP-complete and it's too much for this tool).
Proposition 3: Having Movies.List.WebHome (from SciFi) and Movies.Dramas.List.WebHome (from Dramas). Not as good but more easy to do.