-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specify deprecation model #14
Comments
The request above is not easily achievable in many cases, e.g. if |
Thanks for the reference @palemieux |
You mean that it is complex to do in the spec and might require additional authorial support? An authorial mechanism would be a construct or pattern that checks for feature support for |
It is too complex for processors to detect the presence of both, and apply precedence rules. |
@palemieux that would be a comment worth making on w3c/imsc#279 |
@palemieux your statement seems wholly subjective and without factual support |
@skynavga Per w3c/ttml2#482 (comment), <style xml:id="forcedStyleFalse" condition="parameter(forced)==false" tts:visibility="false"/>
<style xml:id="forcedStyleTrue" condition="parameter(forced)==true" tts:visibility="true"/>
<style xml:id="forcedStyle" style="forcedStyleFalse,forcedStyleTrue"/>
...
<p style="forcedStyle">This text is only visible if forced==true</p> so how would a processor enforce precedence rules when encountering the following:
|
The deprecation model needs to define what deprecation should mean in this context. I think from our meetings that we are all agreed that deprecated features are permitted but are expected to be prohibited by future versions of the specification. |
Netflix has requested that IMSC 1.1 should indicate that when TTML2 features are used in the same document at the same time as their non-TTML2 equivalent and deprecated features [from IMSC 1.0.1] the TTML2 features prevail.
The motivation is "this ensures that future versions of IMSC can effectively remove the features marked as deprecated".
The text was updated successfully, but these errors were encountered: