Abstract
An office database should be a “total” information resource in that it should be capable of storing data of many arbitrary types. Users of such a system should be able to store conveniently their documents and graphics objects in the same logical storage space as their more traditional records-oriented data. This paper presents a data model that can be used to describe more effectively the objects that occur naturally in the office environment. This model exploits some of the richer semantics of office objects such as the containment of one object within another (e.g., reports contain chapters) and the version histories of objects and their constituent parts. This model forms the basis for our experimental object management system which is used to support the creation of new office application programs.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
