Open palemieux opened 8 years ago
Yes they should. Could you propose some text?
Will do.
It looks like I do not have permissions to push an issue branch and create a PR. Below is the proposed text.
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.
ttp:profile
attribute of the head
element or an ebuttm:conformsToStandard
element is equal to http://www.w3.org/ns/ttml/profile/imsc1/text
ttp:profile
attribute of the head
element or an ebuttm:conformsToStandard
element is equal to http://www.w3.org/ns/ttml/profile/imsc1/image
ebuttm:conformsToStandard
element is equal to urn:ebu:tt:distribution:2014-01
ttp:profile
element with a use attribute equal to http://www.w3.org/ns/ttml/profile/sdp-us
head
element contains a ttp:profile
element with a use
attribute of the form http://www.decellc.org/profile/cff-tt-text-{DMEDIA_VERSION_POINTS}
, where {DMEDIA_VERSION_POINTS} is specified in [UVVU DMedia]head
element contains a ttp:profile
element with a use
attribute of the form http://www.decellc.org/profile/cff-tt-image-{DMEDIA_VERSION_POINTS}
, where {DMEDIA_VERSION_POINTS} is specified in [UVVU DMedia]The ebuttm:conformsToStandard
element is specified in [EBU-TT-D].
Makes sense to me. You may add that the following XSLT 1 script simply detects the profile and outputs the profile identifier.
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.
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.
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 .