Slide 14 of 52
Notes:
The Object Life cycle in Gothic allows a great degree of control for verification, validation and integrity maintenance. It is one of the strongest arguments for using Gothic as the foundation GIS repository..
The object approach provides efficient support for version merging essential to long transaction handling: Common object ids, Method - based validation rules, Method - based object processing rules: connectivity, topology
Applications become data independent. In an OODB integrity can be verified by asking each object to perform a self-validation method
A dependency method can be used to ensure that only related objects are checked or re-drawn after change.
Formal object life cycles ensure that checks are not missed.
Cached transactions bracket change sequences.
Reflex methods can be tailored to perform range checks on attributes or any other rule-based checks.
Change lists from Merge methods
Provides summaries of incremental changes
History Objects
Recall of past states of objects