To: pat mudge who wrote (13402 ) 9/22/1999 12:44:00 PM From: fumble Respond to of 18016
And from IBM, a sure cure for insomnia: research.ibm.com Yes, dull and boring to some, but it is a nice presentation of the deep thought about standards necessary to deliver multimedia to remote users over the (next generation) Internet. Some history: The framework of this work is SGML, which is the generalized predecessor technology from which HTML was derived as a specific instance. (XML is also derived from SGML). The description of the multimedia part of a document is done using HyTime (which is also a derivative of SGML). SGML was developed in the '80s by Charles Goldfarb at IBM (among others). I believe that HyTime was developed by Yuri Rabinski at SoftQuad in Montreal around the end of the '80s. QoS is a vital part of the successful delivery of multimedia documents to their users. This implies that ATM will be a big (and pervasive) part of the delivery of multimedia. Pat - are you going to organize a cheerleading group for the AGM? Post some pictures.. As long as we are waiting for the paint to dry -- Some extracts from the IBM paper follow: ----Enabling technology for distributed multimedia applications 3.Development of a continuous media file server: Content data come in two varieties depending on whether the data are continuous (audio and video) or discrete (image and text). [1] Image and text data are stored in the DBMS. For audio and video data, our system must provide guarantees of delivery, as well as support for synchronization of independent media streams and QoS. We have therefore decided to develop a special-purpose continuous-media file server. A consequence of this decision is that continuous data and discrete data may be stored on separate servers. 4.Synchronization of multiple media streams: In our system, the media objects that make up a multimedia document may be stored on different media servers. This facilitates the development of applications where the same video stream may be combined with one of several possible audio streams, such as those corresponding to different languages. A mechanism is needed to request the delivery of media objects from different servers and to synchronize their presentation at the client. 5.QoS negotiation and adaptation as an integral part of the system architecture: To achieve service flexibility, an application must be able to cope with varying network conditions as well as varying presentation quality requested by the users. The latter is relevant, for example, when a video document is available at multiple levels of resolution. The QoS negotiation process is guided by the users' preferences and priorities, which can be captured in the form of user profiles. The system also adapts to changing user priorities, system parameters, and resource availability. In our system, the various system components must effectively support QoS negotiation and adaptation. ---- Synchronization module. The synchronization module is responsible for the presentation of media objects. Once the QoS manager has determined the QoS variants that should be used for the presentation, it passes this information to the synchronization module, which then manages the synchronized presentation. The CMFS module. The CMFS module provides a capability to deliver continuous media data to the client. It also provides support for QoS negotiation and synchronization. Included in this module is the transport of continuous media data over an ATM network.