search

w3c / adpt

Audio Description Profile of TTML2
https://w3c.github.io/adpt/
Other
5 stars 7 forks source link

Do we need to support `#contentProfiles` or `#processorProfiles`? #10

Closed nigelmegitt closed 4 years ago

nigelmegitt commented 5 years ago

TTML2 requires support for the #contentProfiles and #processorProfiles features in both the TTML2 Transformation Profile and the TTML2 Presentation Profile.

Those features permit documents to signal which processor type is needed to process them, and to signal their content conformance. These signalling requirements are often not considered in early versions of a specification, but including them allows for future use more easily by allowing later processors to process earlier documents with the appropriate constraints that apply to those documents.

It also means that earlier processors can identify if they cannot process documents that conform to later versions of a specification, if new required features are added, for example.

I do not think we can require the syntax to be present in documents, but we should require support the features from the beginning.

simpson-matt commented 5 years ago

So we permit people to specify, but don't require them to; makes sense to me - as I think there is an increasing interest in automated voicing of AD in some new markets that could benefit here.

nigelmegitt commented 5 years ago

From the comment from @simpson-matt and the call today, I believe we have consensus to go ahead with support for these features, so I will prepare a pull request for it.