- From: Nigel Megitt via GitHub <sysbot+gh@w3.org>
- Date: Thu, 04 Apr 2019 13:53:21 +0000
- To: public-tt@w3.org
nigelmegitt has just created a new issue for https://github.com/w3c/ttml2: == `#timeContainer` feature designator has limited usefulness == The [`#timeContainer`](https://www.w3.org/TR/ttml1/#feature-timeContainer) feature is coarse grained. It allows support for `timeContainer` to be asserted by itself. Non-support for this only makes sense when in `ttp:timeBase="smpte" ttp:markerMode="discontinuous"` since in all other cases some form of time containment semantic must apply. This can lead to an inconsistency where a profile apparently does not support [`#markerMode-discontinuous`](https://www.w3.org/TR/ttml1/#feature-markerMode-discontinuous) but also does not support `#timeContainer`]. It is also not possible currently for a profile to state that it supports only `par` or `seq` time containment semantics. This is a problem when specifying a profile where the intent is that processors need only support one or the other. I propose: * [ ] Add a constraint that it is an error to prohibit both `#markerMode-discontinuous` and `#timeContainer`. * [ ] Add new finer grained time containment feature designators for `par` and `seq` semantics. Please view or discuss this issue at https://github.com/w3c/ttml2/issues/1065 using your GitHub account
Received on Thursday, 4 April 2019 13:53:22 UTC