hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.2.1 System, video, audio and subtitle formats | The present document does not contain any requirements for system, video, audio and subtitle formats for the broadcast channel. These requirements are defined by the appropriate specifications for each market where the terminals are to be deployed. |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.2.2 Protocol for application transport | DSM-CC object carousel as defined in clause 7 of ETSI TS 102 809 [3] shall be supported. The present document does not require the use of the protection mechanism described in clause 9 of ETSI TS 102 809 [3] by either broadcasters or terminals. Requirements for the use of this mechanism may be defined by the appropriat... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.2.3 Signalling of applications | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.2.3.1 Broadcast signalling | Table 5 identifies the descriptors and other signalling entities whose MPEG-2 encoding shall be supported. Clause numbers and page numbers refer to ETSI TS 102 809 [3]. The present document does not require the use of the protection mechanism described in clause 9 of ETSI TS 102 809 [3] by either broadcasters or termin... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.2.3.2 Broadcast-independent application signalling | The present document does not define any signalling, announcement or discovery of broadcast-independent applications. Clause 5.3.5 of the present document defines how they can be started. Broadcast-independent applications shall be identified either by the URL of the first page of the application or by the URL of a XML... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.2.4 Synchronization | The terminal shall support "do-it-now" events as defined in clause 8 of ETSI TS 102 809 [3]. Support of events synchronized to a DVB timeline as referred to in that document is not included. Broadcasters shall place all "do-it-now" stream descriptors to be monitored simultaneously by an application on a single PID. Thi... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.2.5 DSM-CC carousel | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.2.5.1 Mounting related constraints | A terminal shall mount a maximum of one carousel at a time for use by the running application. Mounting means that the terminal makes the latest version of the files of the carousel available to the application. Additionally a terminal may read, cache and monitor several carousels in parallel in order to decrease the l... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.2.5.2 Initial carousel mounting | A broadcast-related application whose initial page is broadcast will cause its carousel to be mounted by the terminal (in order to be loaded and launched) unless mounting the carousel would require tuning to a transport stream other than the one carrying the current channel. If tuning would be required, the attempt to ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.2.5.3 Subsequent carousel mountings (during the lifecycle of an application) | For a broadcast-related application, once a carousel has been mounted, a request that would require another carousel to be mounted shall succeed and cause the previous carousel to be un-mounted and all of its pending requests to be cancelled, unless mounting the carousel would require tuning to a transport stream other... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.2.5.4 Constraints | A resolved DSM-CC object reference shall be at most 64 bytes. |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.2.6 Data services | HbbTV® services may exist that do not have any broadcast audio or video components (i.e. pure data services). Their broadcast signalling shall be as follows. The SDT entry for the pure data service shall use a service_descriptor with a service_type of 0x0C. It shall also contain a data_broadcast_descriptor as defined i... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.2.7 File system acceleration | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.2.7.1 Introduction | Terminals shall support File System Acceleration (FSA) as defined by ETSI ES 202 184 [36] and further profiled in this clause. |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.2.7.2 HbbTV® stored groups descriptor | HbbTV® profile of File System Acceleration replaces the stored_groups_descriptor defined by ETSI ES 202 184 [36], clause 11.17.3 with the HbbTV® stored group descriptor as defined in Table 8. Table 8: Syntax of the HbbTV® stored group descriptor Syntax Bits Type hbbtv_stored_groups_descriptor { descriptor_tag 8 uimsbf ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.2.7.3 Group location descriptor | The group_location_descriptor defined in Table 11.73 of ETSI ES 202 184 [36] may be included in the private data bytes of the hbbtv_stored_groups_descriptor to define a Group Location other than the default of "DSM:/". Terminals are not required to support Group Locations not in the current object carousel. File Groups... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.2.7.4 Group Manifest file name | HbbTV® profile of File System Acceleration redefines the Group Manifest file name as follows: /<organisation_id>-<group_id>.man Where <organisation_id> and <group_id> are the values from the hbbtv_stored_groups_descriptor. The organisation_id is a 32 bit value and represented as 8 hexadecimal chars with lower case char... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.2.7.5 File groups referenced by multiple carousels | A file group might be referenced by several carousels. If a carousel is unmounted and a new carousel mounted which references the same file group then the following apply: • The file group cache may continue to be filled. • Pending requests for files in the group to be cached may continue or be restarted in an implemen... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.2.7.6 The use_version flag | Clause 11.17.7.1 of ETSI ES 202 184 [36] shall be modified as shown using strike-through below. 11.17.7.1 Read access Read access to stored files shall be transparent to any process that accesses the File System in that file references into the File System shall instead reference the stored equivalent if the following ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.2.8 Protocol for download | Where content download is supported, the FDP protocol, defined in annex H, shall be supported. A/V content downloaded via FDP shall satisfy the same requirements as A/V content downloaded via broadband, as specified in clause 7.3.1. |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.3 Broadband-specific format and protocols | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.3.1 System, video and audio formats | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.3.1.1 General requirements | The system formats and their labels are specified in the OIPF Media Formats specification [2] with the restrictions in clause 7.3.1.2. The video formats and their labels are specified in the OIPF Media Formats specification [2] with the restrictions and extensions in clause 7.3.1.3. Additional video formats are defined... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.3.1.2 Systems layers | The usage of the systems layer format MPEG-2 Transport Stream shall comply with clause 4 of the OIPF Media Formats specification [2]. Support for the DLNA extension "time stamped MPEG-2 transport stream" is not required. Support for EIT, object carousel and 3D is not required. Support for AIT signalling is not required... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.3.1.3 Video | The video format AVC_SD_25 shall comply with clauses 5.1.2.1 and 5.1.6 of the OIPF Media Formats specification [2]. The video format AVC_HD_25 shall comply with clauses 5.1.1.1 and 5.1.6 of the OIPF Media Formats specification [2]. For content delivered via MPEG DASH, terminals shall support the requirements of the avc... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.3.1.4 Audio | Audio formats shall comply with clause 8.1 of the OIPF Media Formats specification [2] with the following additional requirements for multichannel audio: • If the terminal supports a stereo output, it shall be capable of providing a down-mix of multichannel audio to stereo. • If the terminal is equipped with a digital ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.3.1.5 Subtitles | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.3.1.5.1 TTML based subtitles | Terminals shall be able to correctly render TTML based subtitles with the following constraints: • The subtitle document shall be compliant with the EBU-TT-D specification version 1.0.1 [43] (referred to as "EBU-TT-D" format). ETSI ETSI TS 102 796 V1.5.1 (2018-09) 69 • The subtitle document shall have no more than 4 co... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.3.1.5.2 Broadcast subtitles | As defined in clause 7.3.1.1, terminals shall support the same subtitle formats for MPEG-2 transport stream content received by the broadband connection as are supported for the broadcast connection. Specifically: • DVB subtitles • EBU teletext subtitles Basic specification references and labels for both are specified ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.3.2 Protocols | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.3.2.1 Protocols for streaming | Unicast streaming using HTTP 1.1 shall be supported as defined in clause 5.3.2.2 of the OIPF protocols specification [4] with the addition that the Content-Range header shall be supported in seek operations thus allowing the application to seek to any arbitrary position within the streaming video without the need of do... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.3.2.2 Protocols for download | Where content download is supported, HTTP shall be supported as defined in clause 5.3.4 of the OIPF protocols specification [4]. |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.3.2.3 Void | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.3.2.4 HTTP User-Agent header | All outgoing HTTP requests made on behalf of an HbbTV® application, and during the process of launching an HbbTV® application, shall include a User-Agent header using the syntax described in this clause. NOTE: This does not apply to HTTP requests made by the MPEG DASH player or the DRM agent. The User-Agent header shal... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.3.2.5 HTTP Redirects | HTTP redirects as defined in IETF RFC 2616 [6] in response to an HTTP request shall be supported as described in this clause. • The terminal shall support responses with a status code of "301 Moved Permanently", "302 Found", "303 See Other" and "307 Temporary Redirect" by using the temporary URL given in the Location f... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.3.2.6 HTTP Caching | Terminals shall observe the caching rules defined in HTTP/1.1 [6] including support for issuing requests for cached content using the "If-Modified-Since" header (where a server provides a Last-Modified header) and the "If-None- Match" HTTP header (where a server provides an ETag header). Terminals shall support an HTTP... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 7.3.2.7 Simultaneous HTTP connections | Terminals shall support at least two simultaneous HTTP connections for application content in addition to any connections required for HTTP-based media streaming. Specifically, an HTTP request to one server that takes time to complete shall not delay a second HTTP request to a different server if no other application-i... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8 Browser application environment | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8.1 DAE specification usage | The OIPF DAE specification [1] shall be supported as defined in annex A of the present document. |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8.2 Defined JavaScript APIs | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8.2.1 Acquisition of DSM-CC stream events | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8.2.1.1 Adding and removing stream event listeners | The following additional methods on the video/broadcast object (as defined in the OIPF DAE specification [1]) shall be supported for synchronization to broadcast events as defined in clause 7.2.4. ETSI ETSI TS 102 796 V1.5.1 (2018-09) 73 void addStreamEventListener(String targetURL, String eventName, EventListener list... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8.2.1.2 DSM-CC StreamEvent event | interface StreamEvent : Event { readonly attribute String name; readonly attribute String data; readonly attribute String text; readonly attribute DOMString status; } Properties name The name of the DSM-CC StreamEvent's event. data Data of the DSM-CC StreamEvent's event encoded in hexadecimal. EXAMPLE: "0A10B81033" (fo... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8.2.2 Carousel objects access with XMLHttpRequest | In order to access the content of a carousel file, the XMLHttpRequest object can be used with the following constraints: • Parameters passed to the open() method: - method: Shall be set to "GET". - url: Can be relative (to the location of the current page in the carousel's file system) or an absolute dvb: URL. - async:... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8.2.3 APIs for media synchronization | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8.2.3.1 Introduction (Informative) | This clause defines the API for multi-stream synchronization as defined in clause 10.2.8 and the API for the inter- device synchronization with a media presentation on a second terminal or companion screens. As the architecture for multi-stream and inter-device synchronization is basically the same, the MediaSynchronis... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8.2.3.2 The MediaSynchroniser embedded object | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8.2.3.2.0 General | The terminal shall support a non-visual embedded object of type "application/hbbtvMediaSynchroniser" with the following JavaScript API. The terminal shall support one operable MediaSynchroniser embedded object. If an application creates multiple instances only the last one created needs to be operable. A MediaSynchroni... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8.2.3.2.1 Properties | function onError (Number lastError, Object lastErrorSource) Description The function that gets called when an error occurs for this MediaSynchroniser object. The terminal shall pass two arguments in the call. The first argument shall be the error code as defined in clause 8.2.3.2.4. The second argument shall be the med... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8.2.3.2.2 Methods | void initMediaSynchroniser() (Object mediaObject, String timelineSelector) Description Initializes a MediaSynchroniser for multi-stream synchronization and for inter-device synchronization as a master terminal. After this method has been called, it is only possible to use this MediaSynchroniser object as a master for m... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8.2.3.2.3 DOM2 events | When an error occurs for the MediaSynchroniser object then the intrinsic event onError shall be generated and a corresponding DOM level 2 event shall be generated in the following manner: Intrinsic event Corresponding DOM 2 event DOM 2 Event properties onError Error Bubbles: No Cancelable: No Context Info: lastError, l... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8.2.3.2.4 Error codes | The values of the error property are defined in this clause. ETSI ETSI TS 102 796 V1.5.1 (2018-09) 86 Value Description Permanent or Transient 1 Synchronization is unachievable because the terminal could not delay presentation of content (represented by a media object added using the addMediaObject() method) sufficient... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8.2.3.3 The CorrelationTimestamp class | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8.2.3.3.1 General | Applications shall construct objects that conform to this class definition to deliver correlation timestamps to the terminal. Any object conforms to this class definition if it includes the named properties described in this class definition. ETSI ETSI TS 102 796 V1.5.1 (2018-09) 87 |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8.2.3.3.2 Properties | Number tlvMaster Description A value on the timeline used by the MediaSynchroniser API. Number tlvOther Description A value on the timeline of a media object that correlates to the value on the timeline used by the MediaSynchroniser API. The significance of the properties of this class for both multi-stream and inter-d... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8.2.4 APIs for automatic deletion of downloaded content | The following additional property on the Download object (as defined in the OIPF DAE specification [1]) shall be supported. Boolean flaggedForDeletion Description Boolean property set by the application indicating whether the content item has been flagged as suitable for automatic deletion. When additional storage spac... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8.2.5 APIs for obtaining the LCN of a service | The following additional property on the Channel class (as defined in OIPF DAE specification [1]) shall be supported. readonly Number terminalChannel Description An integer property which shall be set to the value of the terminal's Logical Channel Number as used by the terminal's native UI. This allows for terminals to... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8.2.6 Companion Screen discovery APIs | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8.2.6.1 HbbTVCSManager embedded object | This embedded object shall have the MIME type "application/hbbtvCSManager". It enables applications to: • discover companion screens with a running Launcher application and for launching / installing CS applications; • discover the base URLs of the local and remote endpoints for application to application communication... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8.2.6.2 DiscoveredTerminal class | Instances of this class provide details of endpoints of a Terminal that has been discovered using the discoverTerminals() method of the HbbTVCSManager object (see clause 8.2.6.1). ETSI ETSI TS 102 796 V1.5.1 (2018-09) 92 A DiscoveredTerminal object shall have the following properties: readonly Number enum_id Descriptio... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 8.2.6.3 DiscoveredCSLauncher class | Instances of this class provide details of a discovered CS Launcher that was discovered using the discoverCSLaunchers() method of the HbbTVCSManager object (see clause 8.2.6.1). A DiscoveredCSLauncher object shall have the following properties: readonly Number enum_id Description The unique ID of an instance of a CS La... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9 System integration | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.1 Mapping from APIs to protocols | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.1.1 Unicast streaming | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.1.1.1 General streaming requirements | In Unicast streaming: • Pausing playback shall cause the video to freeze and the audio to suspend. • Stopping playback shall cause the video and audio to stop. • When not presenting video, the A/V Control object shall be rendered as an opaque black rectangle. NOTE: An A/V Control object that is not presenting video can... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.1.1.2 HTTP streaming | The mapping from the APIs for unicast streaming to the protocols shall be as defined in clause 8.2.5.1 of the OIPF DAE specification [1] for HTTP streaming. |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.1.1.3 Media player implementations and API behaviour | For DASH, terminals shall use the same DASH player implementation for any given MPD regardless of whether the A/V control object or the HTML5 video element are used. |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.1.2 Unicast content download | Where unicast content download is supported, the mapping from the APIs for unicast content download to the protocols shall be as defined in clause 8.2.1 of the OIPF DAE specification [1]. |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.1.3 Seek accuracy | The play position of media content being presented by a video/broadcast object, an HTML5 media element or an A/V Control object can be controlled using the appropriate seek API. The information available to the terminal to assist with navigating to a requested seek point depends on the container format and protocol bei... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.2 URLs | This clause describes how URL schemas can be used within HbbTV applications (HTML, JavaScript, images and references to A/V content). This clause describes how URL schemas can be used with HbbTV applications (e.g. HTML, JavaScript, images and references to A/V content). The http: and https: URL schemes shall be support... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.3 Other file formats | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.3.1 Stream event | Both mechanisms for referencing sources of stream events defined in clause 8.2 of ETSI TS 102 809 [3] shall be supported. For the XML schema defined in clause 8.2 of ETSI TS 102 809 [3] the following restrictions shall apply: • The stream_event_id attribute of the type StreamEventType shall represent a positive/unsigne... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.3.2 MPEG DASH event integration | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.3.2.1 General | The DVB DASH specification [45] requires support for the event mechanism defined in clause 5.10 of the MPEG DASH specification ISO/IEC 23009-1 [29]. This clause defines how those events will be exposed to applications. |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.3.2.2 HTML5 media element | Specifically the TextTrackList shall include TextTracks corresponding to DASH event streams as follows: • A TextTrack shall be provided for each event stream signalled in the MPD as defined in clause 5.10.2 of MPEG DASH ISO/IEC 23009-1 [29] excluding DASH-specific events as defined in clause 5.10.4 of MPEG DASH ISO/IEC... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.4 Presentation of adaptive bitrate content | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.4.1 General | Terminals shall support the <ContentURL> element of the content access streaming descriptor referencing an MPD as defined in DASH ISO/IEC 23009-1 [29]. It is optional for a terminal to support play speeds other than 0 or 1 for adaptive bitrate content. If paused, terminals shall not auto-resume if DASH live media no lo... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.4.2 Behaviour for HTML5 media objects | Media timeline The origin of the media timeline used by HTML5 media elements (i.e. the <audio> and <video> elements) shall be the start time of the first Period that was defined in the MPD when the MPD was first loaded. The origin of the media timeline shall not change unless the HTML5 media element source is changed o... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.4.3 Behaviour for the A/V Control object | Terminals shall support applications setting the data attribute of an A/V Control object to a URL referencing an MPD as defined in DASH ISO/IEC 23009-1 [29] and identified by the MIME type in annex C of [29]. The type attribute of the A/V Control object shall be set to "application/dash+xml". In order to play the conte... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.5 Downloading content via FDP | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.5.1 Download registration | Download of content delivered via FDP can be registered by using the registerDownload() or registerDownloadURL() methods, as defined in the OIPF DAE specification [1]. To do so, these methods are called with a Content Access Download Descriptor (or a URL of a Content Access Download Descriptor) including the content it... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.5.2 Single file with multiple URLs | When one Content Access Download Descriptor includes multiple <ContentItem> elements containing FDP URLs pointing to the same file (according to the criteria defined in clause H.2.3), the terminal shall consider that all these <ContentItem> elements correspond to one single content item, i.e. that the corresponding fil... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.5.3 Properties of the Download object | In the case of a download via FDP, the following properties of the Download object shall be constrained in the following manner: 1) timeElapsed: this element shall have the value undefined. 2) timeRemaining: this element shall have the value undefined. 3) currentBitRate: this element shall have the value undefined. 4) ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.5.4 Download state diagram | In the case of a download via FDP, the state diagram of section 7.4.3.1 of the OIPF DAE specification [1] does not apply, and the diagram shown in Figure 16 shall prevail. ETSI ETSI TS 102 796 V1.5.1 (2018-09) 103 Figure 16: State diagram for embedded application/oipfDownloadManager objects for FDP downloads (normative... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.6 Media element integration | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.6.1 General | The media elements from HTML5 [54] are included in the present document through the reference to the OIPF DAE specification [1]. Terminals shall support presenting content using the media elements as follows: • Non-adaptively streamed video and/or audio as defined in clause 7.3.2.1 of the present document shall be supp... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.6.2 Resource management | The terminal shall support the existence within the same DOM of at least one HTML5 media element that is playing together with at least two HTML5 media elements in a paused state, where each HTML5 media element may be in a readyState of HAVE_CURRENT_DATA or higher. The terminal shall support each of the following scena... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.6.3 Transition behaviour | The delay between the end of presentation of an HTML5 media element and starting presentation of another HTML5 media element shall be less than 250 ms if all of the following conditions are met: • the pause() function on the first HTML5 media element and the play() function on the second HTML5 media element are called ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.6.4 Reporting and control of buffering | The terminal shall provide information on the amount of data that is buffered for each HTML5 media element by providing a TimeRanges object via the buffered attribute of the HTML5 media element. The accuracy of the range (or ranges) in the TimeRanges object shall be within ±T seconds of the actual amount of media that ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.6.5 Distinguishing multiple media tracks (informative) | When content items include multiple video tracks and/or audio tracks, applications may wish to use a wide range of properties to decide which track should be presented at a particular time or under particular conditions. The HTML5 VideoTrack and AudioTrack interfaces permit video tracks and audio tracks to be distingui... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.6.6 Controls attribute | Applications should not set the controls attribute on the video media elements. Terminal behaviour if this is set is implementation dependent. NOTE: In clause 4.7.10.13 "User interface", the HTML5 specification as referenced by [i.6] states that "Even when the attribute is absent, however, user agents may provide contr... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.6.7 DRM | If an application attempts to present DRM protected MPEG DASH content using the HTML5 <video> element and this is not decrypted by any of the DRM systems that are both listed in the DASH MPD using a ContentProtection element and active according to the state of the oipfDrmAgent object (see the setActiveDRM method defin... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.6.8 Parental Rating Errors | If an application attempts to present content using an HTML5 media element and this is blocked due to parental access control, the application shall receive a MediaError with the code property set to MEDIA_ERR_DECODE. NOTE: The present document does not provide a way for an application to distinguish failure due to par... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.6.9 Downloaded Content | Clause 7.14.1.3 of the OIPF DAE specification [1] shall apply as follows when an application uses the HTML5 media element to present downloaded content: • If the download was triggered using registerDownloadURL() with a contentType other than "application/vnd.oipf.ContentAccessDownload+xml" or the download was triggere... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.6.10 Video presentation | Video presented by an HTML5 <video> element shall always be presented according to the requirements for full screen mode being false as defined in clause H.2 of the OIPF DAE specification [1] and modified by clause A.2.14 of the present document. |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.6.11 getStartDate method | As defined in clauses A.3.2 and 9.4.2, the getStartDate() method shall be supported for MPEG DASH content. The behaviour of getStartDate() for other types of content is not defined by the present document. |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.6.12 End of stream indication | The end of presentation of an HTML5 media element is notified to the application by means of an 'ended' event. This event shall not arrive before the last frame of video or the last audio sample is guaranteed to be presented (e.g. because it has entered a display processing pipeline). It should arrive within 80 ms of t... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.7 Synchronization | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.7.1 Synchronization and video objects | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 9.7.1.1 video/broadcast object | A video/broadcast object that is passed to the initMediaSynchroniser() or addMediaObject() methods shall always be in the connecting or presenting states. Passing a video/broadcast object in any other state to these methods shall result in an error being triggered with error number '9' or '16'. Like timeshift, synchron... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.