Resolves the base URL. Walks down the ancestry, concatenating BaseURL paths according to
MPEG-DASH ISO/IEC 23009-1 standard, section 5.6.4.
The BaseURL elements are used to define the base URL against which relative URLs specified in the manifest are
resolved. This can occur at multiple levels within the manifest (e.g., at the Period, Adaptation Set, or
Representation level).
Relative URLs are resolved according to standard URL resolution rules, as defined by RFC 3986. This involves
resolving the relative URL against the effective base URL, which could be the URL of the manifest itself or
a specified at a higher level in the manifest hierarchy.
Manifest URL as Base: If no is specified, the URL from which the DASH manifest (MPD file) was
retrieved acts as the base URL for resolving any relative URLs.
Resolves the base URL. Walks down the ancestry, concatenating BaseURL paths according to MPEG-DASH ISO/IEC 23009-1 standard, section 5.6.4.
The BaseURL elements are used to define the base URL against which relative URLs specified in the manifest are resolved. This can occur at multiple levels within the manifest (e.g., at the Period, Adaptation Set, or Representation level). Relative URLs are resolved according to standard URL resolution rules, as defined by RFC 3986. This involves resolving the relative URL against the effective base URL, which could be the URL of the manifest itself or a specified at a higher level in the manifest hierarchy.
Manifest URL as Base: If no is specified, the URL from which the DASH manifest (MPD file) was
retrieved acts as the base URL for resolving any relative URLs.
https://standards.iso.org/ittf/PubliclyAvailableStandards/index.html
Note: URL resolution is not a simple concatenation, the
URLclass is used to resolve relative URLs per RFC 3986:2005.