The Experts below are selected from a list of 12603 Experts worldwide ranked by ideXlab platform
Paul J Sanders - One of the best experts on this subject based on the ideXlab platform.
-
microsoft repository version 2 and the open information model
Information Systems, 1999Co-Authors: David R Shutt, Philip A Bernstein, Thomas F Bergstraesser, Jason D Carlson, Paul J SandersAbstract:Abstract Microsoft Repository is an object-oriented meta-data management facility that ships in Microsoft Visual Studio and Microsoft SQL Server. It includes two main components: • • A repository engine that implements a set of object-oriented interfaces on top of a SQL database system. A developer can use these interfaces to define information models (i.e., schemas) and manipulate instances of the models. • • The Open Information Model, which is a set of information models that cover object modeling, database modeling, and component reuse. The repository system is designed to meet the Persistent Storage needs of software tools. Its main technical goals are: • • Compatibility with Microsoft's Component Object Model (COM) architecture • • Extensibility by customers and independent software vendors, so they can add behavior to objects stored by the repository engine and extend information models provided by Microsoft and others. • • Flexible and efficient versioning, configuration management, and checkout/checkin to support team-oriented activities. This paper describes the programming interface and implementation of the repository engine and the Open Information Model.
-
microsoft repository version 2 and the open information model
Information Systems, 1999Co-Authors: David R Shutt, Philip A Bernstein, Thomas F Bergstraesser, Jason D Carlson, Paul J SandersAbstract:Abstract Microsoft Repository is an object-oriented meta-data management facility that ships in Microsoft Visual Studio and Microsoft SQL Server. It includes two main components: • • A repository engine that implements a set of object-oriented interfaces on top of a SQL database system. A developer can use these interfaces to define information models (i.e., schemas) and manipulate instances of the models. • • The Open Information Model, which is a set of information models that cover object modeling, database modeling, and component reuse. The repository system is designed to meet the Persistent Storage needs of software tools. Its main technical goals are: • • Compatibility with Microsoft's Component Object Model (COM) architecture • • Extensibility by customers and independent software vendors, so they can add behavior to objects stored by the repository engine and extend information models provided by Microsoft and others. • • Flexible and efficient versioning, configuration management, and checkout/checkin to support team-oriented activities. This paper describes the programming interface and implementation of the repository engine and the Open Information Model.
Jeff Heflin - One of the best experts on this subject based on the ideXlab platform.
-
lubm a benchmark for owl knowledge base systems
Journal of Web Semantics, 2005Co-Authors: Yuanbo Guo, Zhengxiang Pan, Jeff HeflinAbstract:We describe our method for benchmarking Semantic Web knowledge base systems with respect to use in large OWL applications. We present the Lehigh University Benchmark (LUBM) as an example of how to design such benchmarks. The LUBM features an ontology for the university domain, synthetic OWL data scalable to an arbitrary size, 14 extensional queries representing a variety of properties, and several performance metrics. The LUBM can be used to evaluate systems with different reasoning capabilities and Storage mechanisms. We demonstrate this with an evaluation of two memory-based systems and two systems with Persistent Storage.
-
an evaluation of knowledge base systems for large owl datasets
International Semantic Web Conference, 2004Co-Authors: Jeff HeflinAbstract:In this paper, we present an evaluation of four knowledge base systems (KBS) with respect to use in large OWL applications. To our knowledge, no experiment has been done with the scale of data used here. The smallest dataset used consists of 15 OWL files totaling 8MB, while the largest dataset consists of 999 files totaling 583MB. We evaluated two memory-based systems (OWL Jess KB and memory-based Sesame) and two systems with Persistent Storage (database-based Sesame and DLDB-OWL). We describe how we have performed the evaluation and what factors we have considered in it. We show the results of the experiment and discuss the performance of each system. In particular, we have concluded that existing systems need to place a greater emphasis on scalability.
David R Shutt - One of the best experts on this subject based on the ideXlab platform.
-
microsoft repository version 2 and the open information model
Information Systems, 1999Co-Authors: David R Shutt, Philip A Bernstein, Thomas F Bergstraesser, Jason D Carlson, Paul J SandersAbstract:Abstract Microsoft Repository is an object-oriented meta-data management facility that ships in Microsoft Visual Studio and Microsoft SQL Server. It includes two main components: • • A repository engine that implements a set of object-oriented interfaces on top of a SQL database system. A developer can use these interfaces to define information models (i.e., schemas) and manipulate instances of the models. • • The Open Information Model, which is a set of information models that cover object modeling, database modeling, and component reuse. The repository system is designed to meet the Persistent Storage needs of software tools. Its main technical goals are: • • Compatibility with Microsoft's Component Object Model (COM) architecture • • Extensibility by customers and independent software vendors, so they can add behavior to objects stored by the repository engine and extend information models provided by Microsoft and others. • • Flexible and efficient versioning, configuration management, and checkout/checkin to support team-oriented activities. This paper describes the programming interface and implementation of the repository engine and the Open Information Model.
-
microsoft repository version 2 and the open information model
Information Systems, 1999Co-Authors: David R Shutt, Philip A Bernstein, Thomas F Bergstraesser, Jason D Carlson, Paul J SandersAbstract:Abstract Microsoft Repository is an object-oriented meta-data management facility that ships in Microsoft Visual Studio and Microsoft SQL Server. It includes two main components: • • A repository engine that implements a set of object-oriented interfaces on top of a SQL database system. A developer can use these interfaces to define information models (i.e., schemas) and manipulate instances of the models. • • The Open Information Model, which is a set of information models that cover object modeling, database modeling, and component reuse. The repository system is designed to meet the Persistent Storage needs of software tools. Its main technical goals are: • • Compatibility with Microsoft's Component Object Model (COM) architecture • • Extensibility by customers and independent software vendors, so they can add behavior to objects stored by the repository engine and extend information models provided by Microsoft and others. • • Flexible and efficient versioning, configuration management, and checkout/checkin to support team-oriented activities. This paper describes the programming interface and implementation of the repository engine and the Open Information Model.
Philip A Bernstein - One of the best experts on this subject based on the ideXlab platform.
-
Microsoft Corporation
2008Co-Authors: Philip A BernsteinAbstract: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. 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. 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)
-
microsoft repository version 2 and the open information model
Information Systems, 1999Co-Authors: David R Shutt, Philip A Bernstein, Thomas F Bergstraesser, Jason D Carlson, Paul J SandersAbstract:Abstract Microsoft Repository is an object-oriented meta-data management facility that ships in Microsoft Visual Studio and Microsoft SQL Server. It includes two main components: • • A repository engine that implements a set of object-oriented interfaces on top of a SQL database system. A developer can use these interfaces to define information models (i.e., schemas) and manipulate instances of the models. • • The Open Information Model, which is a set of information models that cover object modeling, database modeling, and component reuse. The repository system is designed to meet the Persistent Storage needs of software tools. Its main technical goals are: • • Compatibility with Microsoft's Component Object Model (COM) architecture • • Extensibility by customers and independent software vendors, so they can add behavior to objects stored by the repository engine and extend information models provided by Microsoft and others. • • Flexible and efficient versioning, configuration management, and checkout/checkin to support team-oriented activities. This paper describes the programming interface and implementation of the repository engine and the Open Information Model.
-
microsoft repository version 2 and the open information model
Information Systems, 1999Co-Authors: David R Shutt, Philip A Bernstein, Thomas F Bergstraesser, Jason D Carlson, Paul J SandersAbstract:Abstract Microsoft Repository is an object-oriented meta-data management facility that ships in Microsoft Visual Studio and Microsoft SQL Server. It includes two main components: • • A repository engine that implements a set of object-oriented interfaces on top of a SQL database system. A developer can use these interfaces to define information models (i.e., schemas) and manipulate instances of the models. • • The Open Information Model, which is a set of information models that cover object modeling, database modeling, and component reuse. The repository system is designed to meet the Persistent Storage needs of software tools. Its main technical goals are: • • Compatibility with Microsoft's Component Object Model (COM) architecture • • Extensibility by customers and independent software vendors, so they can add behavior to objects stored by the repository engine and extend information models provided by Microsoft and others. • • Flexible and efficient versioning, configuration management, and checkout/checkin to support team-oriented activities. This paper describes the programming interface and implementation of the repository engine and the Open Information Model.
Jason D Carlson - One of the best experts on this subject based on the ideXlab platform.
-
microsoft repository version 2 and the open information model
Information Systems, 1999Co-Authors: David R Shutt, Philip A Bernstein, Thomas F Bergstraesser, Jason D Carlson, Paul J SandersAbstract:Abstract Microsoft Repository is an object-oriented meta-data management facility that ships in Microsoft Visual Studio and Microsoft SQL Server. It includes two main components: • • A repository engine that implements a set of object-oriented interfaces on top of a SQL database system. A developer can use these interfaces to define information models (i.e., schemas) and manipulate instances of the models. • • The Open Information Model, which is a set of information models that cover object modeling, database modeling, and component reuse. The repository system is designed to meet the Persistent Storage needs of software tools. Its main technical goals are: • • Compatibility with Microsoft's Component Object Model (COM) architecture • • Extensibility by customers and independent software vendors, so they can add behavior to objects stored by the repository engine and extend information models provided by Microsoft and others. • • Flexible and efficient versioning, configuration management, and checkout/checkin to support team-oriented activities. This paper describes the programming interface and implementation of the repository engine and the Open Information Model.
-
microsoft repository version 2 and the open information model
Information Systems, 1999Co-Authors: David R Shutt, Philip A Bernstein, Thomas F Bergstraesser, Jason D Carlson, Paul J SandersAbstract:Abstract Microsoft Repository is an object-oriented meta-data management facility that ships in Microsoft Visual Studio and Microsoft SQL Server. It includes two main components: • • A repository engine that implements a set of object-oriented interfaces on top of a SQL database system. A developer can use these interfaces to define information models (i.e., schemas) and manipulate instances of the models. • • The Open Information Model, which is a set of information models that cover object modeling, database modeling, and component reuse. The repository system is designed to meet the Persistent Storage needs of software tools. Its main technical goals are: • • Compatibility with Microsoft's Component Object Model (COM) architecture • • Extensibility by customers and independent software vendors, so they can add behavior to objects stored by the repository engine and extend information models provided by Microsoft and others. • • Flexible and efficient versioning, configuration management, and checkout/checkin to support team-oriented activities. This paper describes the programming interface and implementation of the repository engine and the Open Information Model.
