Open AccessProceedings Article
The Microsoft Repository
Reads0
Chats0
TLDR
This paper explains how the Repository attains its goals by providing an object-oriented database (OODB) architecture based on Microsoft’s binary object model (COM) and type system of Visual Basic (Automation).Abstract:
The Microsoft Repository is an object-oriented repository that ships as a component of Visual Basic (Version 5.0). It includes a set of ActiveX interfaces that a developer can use to define information models, and a repository engine that is the underlying storage mechanism for these information models. The repository engine sits on top of a SQL database system. The repository is designed to meet the persistent storage needs of software tools. Its two main technical goals are: . compatibility with Microsoft’s existing ActiveX object architecture consisting of the Component Object Model (COM) and Automation and that a developer can use to define information models, and a repository engine that is the underlying storage mechanism for these information ‘models. (Znformurion model is repository terminology for database schema [3].) The repository engine sits on top of either Microsoft SQL Server or Microsoft Jet (the database system in Microsoft Access) and supports both navigational access via the object-oriented interfaces and direct SQL access to the underlying store. In addition, the Repository includes a set of information models that cover the data sharing needs of software tools. . extensibility by customers and independent software vendors who need to tailor the repository by adding functionality to objects stored by the repository engine and extending information models provided by Microsoft and others. The two main technical goals of Microsoft Repository are 1. COMZActiveX Compatibility It should fit naturally into Microsoft’s existing object architecture, consisting of COM and Automation (now subsumed under ActiveX). Thus, the repository should use existing ActiveX interfaces and implementation technology wherever possible and minimize the number of new concepts that the large community of ActiveX users needs to learn. This paper explains how the Repository attains these goals by providing an object-oriented database (OODB) architecture based on Microsoft’s binary object model (COM) and type system of Visual Basic (Automation).read more
Citations
More filters
Proceedings ArticleDOI
XWRAP: an XML-enabled wrapper construction system for Web information sources
Ling Liu,Calton Pu,W. Han +2 more
TL;DR: The paper describes the methodology and the software development of XWRAP, an XML-enabled wrapper construction system for semi-automatic generation of wrapper programs, and introduces and develops a two-phase code generation framework.
Patent
Storage platform for organizing, searching, and sharing data
TL;DR: In this article, the authors present a storage platform comprising a database engine, a data store, an application programming interface, and a data model that supports the organization, searching, sharing, synchronization, and security of data stored in the data store.
Patent
Systems and methods for the implementation of a digital images schema for organizing units of information manageable by a hardware/software interface system
Scott E. Dart,Bradley P. Gibson,Christopher A. Evans,Paul S. Hellyar,Alexander Vaschillo,John Platt,Steve Glenner,Nathaniel H. Ballou +7 more
TL;DR: In this article, the authors propose an image schema that defines the properties, behaviors, and relationships for Images in the system, and the Schema also enforces rules about Images, for example, what data specific Images must contain, how specific Images can be extended, and so on and so forth.
Book
Large Scale Component Based Development
TL;DR: Large-Scale, Component-Based Development offers a start-to-finish blueprint for managing the Web and component technologies that enable e-business and is an invaluable resource for every decision-maker involved withInternet-focused, multi-tiered enterprise systems.
Patent
Systems and methods for interfacing application programs with an item-based storage platform
TL;DR: In this paper, the authors describe a data store in which data stored therein is defined in terms of items, elements, and relationships, where an item is a unit of data storable in the data store, an element is an instance of a type comprising one or more fields, and a relationship is a link between at least two items.
References
More filters
Book
The object database standard: ODMG 2.0
R. G. G. Cattell,Douglas K. Barry,Dirk Bartels,Mark Berler,Jeff Eastman,Sophie Gamerman,David Jordan,Adam Springer,Henry Strickland,Drew Wade +9 more
TL;DR: With this book, standards are defined for object management systems and this will be the foundational book for object-oriented database product.
Proceedings ArticleDOI
A critique of ANSI SQL isolation levels
TL;DR: It is shown that these phenomena and the ANSI SQL definitions fail to properly characterize several popular isolation levels, including the standard locking implementations of the levels covered, and new phenomena that better characterize isolation types are introduced.
Book
Readings in object-oriented database systems
Stanley B. Zdonik,David Maier +1 more
TL;DR: The interface, implementation, and use of a server process that is used as a backend by an object-oriented database system responsible for managing objects on secondary storage, managing transactions, and implementing a simple form of trigger are summarized.