rbouqueau / TTML_in_MP4_DASH_statement

TTML in MP4 and MPEG-DASH guidelines
Other
11 stars 1 forks source link

Profile signaling #9

Open palemieux opened 8 years ago

palemieux commented 8 years ago

Should the guidelines include recommendations on signaling the TTML profiles to which the TTML document conform?

See for instance https://www.w3.org/TR/ttml-imsc1/#profile-signaling .

cconcolato commented 8 years ago

Yes they should. Could you propose some text?

palemieux commented 8 years ago

Will do.

palemieux commented 8 years ago

It looks like I do not have permissions to push an issue branch and create a PR. Below is the proposed text.


Determining the profile(s) of a TTML document

The following algorithm uses in-band profile signaling mechanisms to determine if the TTML document conforms to one or more common profiles. Simultaneous conformance to multiple profiles is possible since some profiles are subset of others, e.g. EBU-TT-D is a practical subset of IMSC Text Profile. Additional means of determining the profile(s) of a TTML document exist, such as explicit signaling by the user or heuristic-based inspection of the document.

The ebuttm:conformsToStandard element is specified in [EBU-TT-D].

andreastai commented 8 years ago

Makes sense to me. You may add that the following XSLT 1 script simply detects the profile and outputs the profile identifier.

https://github.com/IRT-Open-Source/scf/blob/master/modules/TT-Helper/GetTTMLProfile/GetTTMLProfile.xsl

At the moment only one profile identifier is detected if one document is both, an IMSC 1 and an EBU-TT-D document, because EBU-TT-D is implictly (nearly) always a IMSC 1 document.

rbouqueau commented 8 years ago

Thank you both for the inputs. I think determining the TTML profile is very useful. However I think that 1) it is not related to MP4 or DASH (correct me if I'm wrong) and 2) the current document is already too long.

Could we consider putting the information in a separate document and putting a link in the original doc in case people are interested?

It looks like I do not have permissions to push an issue branch and create a PR.

Correct. You don't have the right to create the branch on this repo but you can fork the project on github and then make a PR.