Open technogeek00 opened 5 months ago
Overall questionaire score: 8
Question | Answer |
---|---|
Does the feature relate to an industry streaming use-case? | Yes, Stream Personalization / Tokenization |
- What is the commonality of this case? | Very Common |
- Is this an established or emerging practice? | Emerging |
Does this feature have related mechanisms in both DASH and HLS? | Yes |
- What is the maturity of support in both specifications? | HLS - Mature , DASH - Mature |
- What is the maturity of implementation support for both specifications? | HLS - Immature, DASH - Immature |
- Are there known interoperability issues between specs? | Yes, HLS only provides query arg alignment |
- Has anyone implemented this interoperably? | Yes |
- Are there features missing in a specification with open proposals for it? | No |
Has the industry defined defacto mechanisms not present in both DASH and/or HLS? | No |
- Why was functionality defined outside of the main specifications? | N/A |
- Has the functionality been standardized elsewhere (DASH-IF, CTA, SVA)? | N/A |
- Is the functionality proprietary or openly developed? | N/A |
- Could the functionality be incorporated into specifications with evangelism? | N/A |
This comment summarizes information for this work prior to formal specification drafting
{$VARNAME}
where VARNAME
follows the semantics outlined by EXT-X-DEFINE
EXT-X-DEFINE
lines (HLS spec 4.4.2.3), attributes:Attribute | Required | Description |
---|---|---|
NAME |
No | The name of the variable being defined by the tag. |
VALUE |
When NAME exists |
The explicit value to set the variable to. |
IMPORT |
No | The name of the variable definition in the parent Multivariant to import. Not allowed in multivariants, variable name is inherited to this variant. |
QUERYPARAM |
No | The name of the query parameter the variable value is sourced from. Variable name is equal to query parameter name. |
EXT-X-VERSION
of 11up:URLQueryInfo
and up:ExtUrlQueryInfo
, and up:ExtHttpHeaderInfo
Ext*
types were introduced in later versions and succeed the base up:URLQueryInfo
functionalityup:ExtUrlQueryInfo
onlyup:ExtUrlQueryInfo
in I.3
EssentialProperty
or SupplementalProperty
Descriptor with URN urn:mpeg:dash:urlparam:2016
Attribute | Required / Default | Description |
---|---|---|
@queryTemplate |
No | Defines a query template containing one or more template identifiers |
@useMPDUrlQuery |
No, default false |
Whether or not the query string of the MPD URL should be used for query reference. When ture and @queryString are present, they are concatenated together |
@queryString |
No | A base query string to use for query reference |
@includeInRequests |
No, default segment |
The requests to include parameters on. White space separated list of potential values: segment , xlink , mpd , callback , chaining , fallback |
@headerParamSource |
No, default segment |
HTTP responses where header templates should source values from. White space separated list of potential values: segment , xlink , mpd , callback |
@sameOriginOnly |
No, default false |
Restricts parameters to only the origins they were received from. |
Identifier | Meaning |
---|---|
$$ |
Escape sequence for utilizing the value $ in a query template |
$querypart$ |
Identifier replaced by the full query part of the initialQueryString , cannot be used with other identifiers |
$query:<param>$ |
Identifier replaced by the value of the <param> parameter in the initialQueryString . Empty string if that parameter does not exist. |
$header:<header-name>$ |
Identifier replaced by the latest received value of the <header-name> HTTP header in the indicated @headerParamSource s |
initialQueryString
is derived based on element parameter valuesfinalQueryString
is computed based on the @queryTemplate
and initialQueryString
finalQueryString
is attached to identified requests as they are madeup:ExtUrlQueryInfo
elements may exist at multiple hierarchies in the DASH manifest and in this case they are a concatenation of the computed finalQueryString
at each level of the hierarchy declaredinitialQueryString
utilize the last declared value
Use Case Description
Content providers desire for players to make personalized / individualized requests while providing cacheable manifest responses.
Working Notes
EXT-X-DEFINE
with theQUERYPARAM
/IMPORT
parametersExtUrlQueryInfo
from the Annex I definitionOpen Questions