https://dash-industry-forum.github.io/identifiers/ Recent content in Identifiers on DASH Industry Forum Hugo -- gohugo.io en-us https://dash-industry-forum.github.io/identifiers/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 https://dash-industry-forum.github.io/identifiers/introduction/ Introduction The DASH-IF hosts and manages an online cataloging of identifiers for MPEG-DASH profiles, interoperability points, content protection metadata and other DASH related specific schemes. DASH-IF responsibilities include: hosting the online catalog on its website, listing all defined URIs along with a short descriptions of their schemes and names of their owners, providing a simple online mechanism to request the addition of new URIs and associated information, and finally managing the administration and maintenance of the online catalog. https://dash-industry-forum.github.io/identifiers/registration/ Mon, 01 Jan 0001 00:00:00 +0000 https://dash-industry-forum.github.io/identifiers/registration/ New identifiers can be registered at this link: https://bit.ly/dash-identifier-submission. https://dash-industry-forum.github.io/identifiers/audio_source_metadata/ Mon, 01 Jan 0001 00:00:00 +0000 https://dash-industry-forum.github.io/identifiers/audio_source_metadata/ Introduction Audio source data may be used in order to provide details of the audio content source. In general, such characteristics of audio are logically independent of the compression format. In the context of DASH they are typically used in order to select a proper Adaptation Set. This section focuses on source format description. In the context of DASH as specific source descriptor exists, namely AudioConfiguration identifies channel configuration signaling for Representations that contain an audio component. https://dash-industry-forum.github.io/identifiers/authentication_and_authorization/ Mon, 01 Jan 0001 00:00:00 +0000 https://dash-industry-forum.github.io/identifiers/authentication_and_authorization/ Introduction Authentication and authorization may be provided in the MPD. Authentication Schemes The following defines a set of URIs that identify MPD events, i.e., schemes contained in the EventStream element: Identifier Reference Abstract urn: see Authentication Authorization Schemes The following defines a set of URIs that identify MPD events, i.e., schemes contained in the EventStream element: Identifier Reference Abstract urn: see Authorization https://dash-industry-forum.github.io/identifiers/content_protection/ Mon, 01 Jan 0001 00:00:00 +0000 https://dash-industry-forum.github.io/identifiers/content_protection/ Introduction For the element ContentProtection, the @schemeIdUri attribute is used to identify a content protection scheme (for details see ISO/IEC 23009-1 [1], section 5.8.4.1). This attribute can provide sufficient information, possibly in conjunction with the @value and/or extension attributes and elements (such as the DRM system(s), encryption algorithm(s), and key distribution scheme(s) employed) for enabling a client to determine whether or not it can possibly play the protected content. For Representations based on ISO/IEC 14496-12 [6], content protection schemes (or DRM systems) may be identified with ContentProtection elements. https://dash-industry-forum.github.io/identifiers/content_rating/ Mon, 01 Jan 0001 00:00:00 +0000 https://dash-industry-forum.github.io/identifiers/content_rating/ Introduction Content Rating may be provided in the MPD. Content Rating Schemes The following defines a set of URIs that identify MPD events, i.e., schemes contained in the EventStream element: Identifier Reference Section Comment urn:dvb:iptv:guidance:2014 ETSI TS 103 285 clause 9.1.2.3 Where the id is either: G indicating that guidance text relating to the content is provided in the ExplanatoryText element within the ParentalGuidance element or W indicating watershed (safe harbour) content that is only suitable for presentation after the watershed. https://dash-industry-forum.github.io/identifiers/event_schemes/ Mon, 01 Jan 0001 00:00:00 +0000 https://dash-industry-forum.github.io/identifiers/event_schemes/ Introduction Events may be provided in the MPD or within a Representation in order to signal aperiodic information to the DASH client or to an application. Events are timed, i.e. each event starts at a specific media presentation time and typically has a duration. To classify events a proper scheme identifier identifies the application such that the DASH client can forward the event to the proper application. Two ways of signalling events are provided, namely https://dash-industry-forum.github.io/identifiers/functionality/ Mon, 01 Jan 0001 00:00:00 +0000 https://dash-industry-forum.github.io/identifiers/functionality/ Functionality Identifier Reference Section Comment https://dashif.org/guidelines/trickmode DASH-IF IOP v3.2 clause 3.2.9 Defines a trick mode Adaptation Set. If an Adaptation Set in annotated with the EssentialProperty descriptor with URI https://dashif.org/guidelines/trickmode then the DASH client shall not select any of the contained Representations for regular playout. https://dashif.org/guidelines/AdaptationSetSwitching DASH-IF IOP v3.2 clause 3.8 Defines signaling that switching from one Adaptation Set to another Adaptation Set may be possible in a seamless manner from a content and timeline perspective. https://dash-industry-forum.github.io/identifiers/output_protection/ Mon, 01 Jan 0001 00:00:00 +0000 https://dash-industry-forum.github.io/identifiers/output_protection/ Introduction Output protection schemes, such as HDCP are frequently used to protect the rendered output in transit from the decoding device to the displaying device (for example, from a set-top box which is connected to a TV set using an HDMI cable). These output protection schemes and their properties are frequently a pre-requisite for the ability to present the associated Representations. For the element OutputProtection the @schemeIdUri attribute is used to identify an output protection scheme (for details see ISO/IEC 23009-1 [1], section 5. https://dash-industry-forum.github.io/identifiers/profiles/ Mon, 01 Jan 0001 00:00:00 +0000 https://dash-industry-forum.github.io/identifiers/profiles/ General MPEG DASH defines formats for MPDs and segments. In addition MPEG provides the ability to further restrict the applied formats by the definition of Profiles as defined on section 8 of ISO/IEC 23009-1 [1]. Profiles of DASH are defined to enable interoperability and the signaling of the use of features. Profiles are signaled in the @profiles parameter which may be present on different levels of the MPD. Such a profile can also be understood as permission for DASH clients that implement the features required by the profile to process the Media Presentation (MPD document and Segments). https://dash-industry-forum.github.io/identifiers/references/ Mon, 01 Jan 0001 00:00:00 +0000 https://dash-industry-forum.github.io/identifiers/references/ References [1] ISO/IEC 23009-1:2022, Information technology — Dynamic adaptive streaming over HTTP (DASH) — Part 1: Media presentation description and segment formats [2] 3GPP TS26.247, Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH), available at http://www.3gpp.org [3] DASH-IF Guidelines for Implementation: DASH264/AVC Interoperability Points, v2.0, Aug. 2013 [4] ISO/IEC 23001-8, Information technology – MPEG systems technologies –– Part 8: Coding-independent code points [5] ISO/IEC 23009-1:2012, Information technology — Dynamic adaptive streaming over HTTP (DASH) — Part 1: Media presentation description and segment formats, Draft Amd. https://dash-industry-forum.github.io/identifiers/reporting_schemes/ Mon, 01 Jan 0001 00:00:00 +0000 https://dash-industry-forum.github.io/identifiers/reporting_schemes/ Introduction Reporting scheme may be provided in the MPD. Reporting Schemes Identifier Reference Section Comment urn:dvb:dash:reporting:2014 ETSI TS 103 285 clause 10.12.3 The DVB Metric reporting mechanism defined by TS 103 285. urn:3GPP:ns:PSS:DASH:QM10 3GPP TS 26.247 clause 10.5 This section specifies a 3GP-DASH quality reporting scheme. The quality reporting scheme is signaled using in the Reporting element in the Metrics element. The URN to be used for the Reporting@schemeIdUri shall be “urn:3GPP:ns:PSS:DASH:QM10” https://dash-industry-forum.github.io/identifiers/sand/ Mon, 01 Jan 0001 00:00:00 +0000 https://dash-industry-forum.github.io/identifiers/sand/ General MPEG DASH part 5 Server And Network-assisted DASH defines messages and MPD signalling for a DASH client and a DANE (network entity) to exchange such SAND messages. Test vectors for SAND MPDs and messages can be fond at Test Vectors. The following are the identifiers defined in several specification related to SAND. SAND Identifier Reference Section Comment http://dashif.org/guidelines/sand/modes/qoe DASH-IF SAND Interoperability 4. Capability Exchange http://dashif.org/guidelines/sand/modes/pc DASH-IF SAND Interoperability 4. Capability Exchange http://dashif. https://dash-industry-forum.github.io/identifiers/subtitle_and_closed_captioning/ Mon, 01 Jan 0001 00:00:00 +0000 https://dash-industry-forum.github.io/identifiers/subtitle_and_closed_captioning/ Introduction Beyond regular audio and video support, TV programs typically also require support for auxiliary components such as subtitles and closed captioning, often due to regulatory requirements. DASH-IF IOP provides tools to addresses these requirements. We collect them here. Identifiers Signalling for the closed caption services is provided by including Accessibility descriptors. The Accessibility descriptor is included for the AdaptationSet and all included Representations shall provide equivalent captions. The @value attribute of each descriptor can be either list of languages or a complete map of services (or CC channels, in CEA-608 terminology). https://dash-industry-forum.github.io/identifiers/video_source_metadata/ Mon, 01 Jan 0001 00:00:00 +0000 https://dash-industry-forum.github.io/identifiers/video_source_metadata/ Introduction Video source data may be used in order to provide details of the video content source. In general, such characteristics of video are logically independent of the compression format. In the context of DASH they are typically used in order to select a proper Adaptation Set. This section focuses on source format description. In the context of DASH as specific source descriptor exists, namely FramePacking used to identify the frame-packing configuration scheme employed. https://dash-industry-forum.github.io/identifiers/watermarking/ Mon, 01 Jan 0001 00:00:00 +0000 https://dash-industry-forum.github.io/identifiers/watermarking/ Introduction Within DASH-IF watermarking guideline, a watermakring token is defined. This token contains some data that are specific to a watermarking technology vendor. it therefore carries a claim wmvnd that identifies this vendor as an unsigned integer with values between 0 and 255. Watermarking Vendors Identifiers The following table documents registered watermarking identifiers. Values between 0 and 9 are reserved for standard use. Values between 245 and 255 are reserved for private use.