wilaw
commented
6 years ago Comments:
- The "protocols" - are those transport protocols (like http), or packaging protocls, like DASH and HLS?
- Hierarchically, the content should sit above the application
- WAVE content also includes manifests
- What does "others" mean in the content block and the device platform block?
The following is from the DPCTF Specification. The DPCTF has asked the TWG to review the diagram and comment.
5.1 WAVE Architecture WAVE specifications and domain consists of three primary domains, the WAVE content, an application that is based on WAVE APIs and the WAVE Device Platform. WAVE specifications are enabler to support
By doing so this, enables an ecosystem of independent content generation, app development and device implementations and permits the use of same content within different apps as well as on many different device platforms.
Figure 1 WAVE Architecture Model
This WAVE specification primarily deals with the requirements of a WAVE Device Platform that may be used by an application implementing WAVE APIs to playback WAVE content. The requirements are purposely help abstract in order to support different application and device interface models. Nevertheless, the use of HTML-5 APIs defined in [ref API spec] is one of the prime objectives. The APIs also differentiate between devices supporting different playback variants, primarily “type 1” and “type 3”: • Type 1 Playback: The WAVE device platform receives a manifest and downloads and plays back the contained media based on the information in the manifest. An application may control the playback with limited control features. • Type 3 Playback: The WAVE application receives a manifest, downloads the media and uses media APIs in order to playback individual tracks of the media experience. The application is controls of the download and playback of the media using the well-defined track buffers.