Actually, I don't think this should change becase ResourceId is the unique key used to join between may different tables for resource state.  For example, the transactions table has a ResourceId column that identifies the resource state that was transacted between two agents.  In terms of data analysis, the id we are usually needing is the graphid - so I think leaving its name as is in the db is an okay/better choice.