VODAK V4.0 user manual. GMD Technical Report No. 910, 1995.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....media streams, clientside buffering mechanisms exploiting stream and interaction semantics, and client side quality adaptation mechanisms to overcome fluctuations in the network and server resources. Most of the concepts were already developed when we extended the object oriented DBMS VODAK [V95] to a (proprietary) MM DBMS [RKN96] This paper shows that the concepts for presentational support, developed in this earlier proprietary work, can be smoothly integrated into standard platforms, taking advantage of the available functionality of these systems. Thus there is no principal ....

VODAK V4.0 User Manual, GMD Technical Report No. 910, Sankt Augustin, April 1995.

....media streams, client side buffering mechanisms exploiting stream and interaction semantics, and client side quality adaptation mechanisms to overcome fluctuations in the network and server resources. Most of the concepts were already developed while we extended the object oriented DBMS VODAK [V95] to a (proprietary) multimedia DBMS [RKN96] This paper shows that the concepts for presentational support developed in this earlier proprietary work can be smoothly integrated into standard platforms, taking advantage of the available functionality of these systems. Thus there is no principal ....

VODAK V4.0 User Manual, GMD Technical Report No. 910, Sankt Augustin, April 1995.

....has to take place before the evaluation actually starts, such that its results can have an influence on the choice of the appropriate physical operators for the final EP. We shortly describe how the results of this paper will be integrated in the query optimizer of the object oriented DBMS VODAK [17]. In VODAK we follow a rule based approach for query optimization based on the Volcano optimizer generator [1] 7] The optimizer may enforce constraints in the generation of (sub)plans by using so called physical properties (for example sortedness) According to Theorem 1 such constraints may ....

VODAK V4.0 User Manual, GMD Technical Report No. 910, Sankt Augustin, April 1995.

....deterministically in a set oriented way. This may have been proven by using the techniques introduced in [13] and [2] 3 The query processing model In general, update queries are formulated using a declarative query language. For this purpose, we use the query language VQL of the OODBMS VODAK [21]. We rely on the algebraic approach for query processing, and follow the distinction between a logical and a physical query algebra as introduced in [9] In this section, we will shortly present VQL and the logical algebra 7 (which have been introduced in [1] introduce the operators of the ....

VODAK V4.0 User Manual, GMD Technical Report No. 910, Sankt Augustin, April 1995.

....views on documents are part of the database schema. Index structures have been constructed so that they do not have to be updated after small document modifications. Queries are optimized using applicationspecific semantics. The framework has been implemented on top of the OODBMS VODAK [VOD95]. Demonstration Outlook. With the demonstration, we illustrate how the database configuration can be specified in a natural, SGML compliant way, how documents of arbitrary type can be accessed both by navigation and declarative access (via the WWW) and how database technology can be exploited to ....

VODAK V 4.0 User Manual, GMD Technical Report No. 910, 1995.

....are embedded into the hypermedia desktop and database environment. Storage and manipulation of hyperstructures and the documents contained in the hypernodes are modeled at the database level[KAN93] In addition to the management of conventional data, the underlying database management system VODAK[GMD95, RL94, AK94, KNS90, BA94] offers mechanisms for the storage, manipulation and presentation of multimedia data. Therefore, the system allows an extended notion of documents including text, images, audio, video and data produced from the tools of the MuSE environment. The object oriented model of ....

....electronic mail by means of composite multimedia documents. Figure 3 shows the overall client server based architecture of the teleservice prototyped in the context of the GAMMA project at GMD IPSI. The multimedia document archive is based on the open object oriented database system VODAK [GMD95, RL94, AK94, KNS90, BA94] The archive and the clients are connected to the Multimedia Mail User Agent (MMM UA) providing the X.400 Message Handling System functionality. The archive contains complete structured multimedia documents and keeps track of received and sent multimedia mails, part of) ....

[Article contains additional citation context not shown here]

GMD. VODAK V4.0 User Manual, apr 1995. GMD Technical Report No. 910, Sankt Augustin.

....class is a special kind of type that refers to the notions (CONCEPT) through (EXTENT) In Iris [10] type refers to the notions (CONCEPT) REPRESENTATION) FACTORY) and (EXTENT) the (INTERFACE) and (IMPLEMENTATION) are defined with respect to the type but are not a part of the type. In VODAK [1] (which is built on top of ObjectStore but has a different data model) type refers to the notions (INTERFACE) IMPLEMENTATION) and (REPRESENTATION) while class refers to the notions (CONCEPT) and (FACTORY) Type in VODAK has two components: the interface, referring to the notion (INTERFACE) ....

VODAK V4.0 User Manual, April 1995. GMD Technical Report No. 910.

No context found.

VODAK V4.0 user manual. GMD Technical Report No. 910, 1995.

No context found.

VODAK V 4.0, User Manual 1995. GMD technical report No.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC