Their is a difference between a table and its occurrences on the relationships graph.
A table can have 1 or more occurrences on the graph.
The relationships graph is NOT an ERD.
You might want to think of the relationships graph as a graphical query engine.
Table occurrences are abstractions of the base tables.
Simple hover your mouse over the Table Occurrence will show the base table that its bound to.
Everything in FM is about context because UI objects are bound to the relationships graph TO's
That's insightful, I've been treating it as an ERD.
A thoughtful TO naming convention can greatly aid in development
So from what I've learned reading the "Approaches to Graph Modeling" there is no way to tell if something is a copy, because they're really not copies. They're pointers to a table. You can have many pointers that all point to the same table. Likewise, when you are setting a field in a layout, the field is a pointer referencing the TO, not the table. So while setting Table A::Field1 will reflect in Table A Copy::Field1, on the LAYOUT it's still looking at the TO of Table A. If the TO "Table A" were deleted, the field would be missing, even though its contents are still contained in the table and could be accessed via Table A Copy.
That paper was most helpful, thank you very much coherentkris