From SQL's point of view, there is no difference between a table and a feature class.
If you have a "point table", that is the table which should contain the geometry.
If you don't want/need the power/complexity of a versioned table, don't version it.
If you want edits to the text DMS or DD real data columns to manifest a change
to the geometry, use a trigger (the same is possible from an edit to the geometry,
though doing both would be difficult).
But there isn't really any reason to do this in multiple tables -- Creating complex
links between tables only harms performance.
- V