Skip to content
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

[WR/ARIB] (meta) Compatibility with ARIB-TTML #545

Open
himorin opened this issue May 8, 2020 · 1 comment
Open

[WR/ARIB] (meta) Compatibility with ARIB-TTML #545

himorin opened this issue May 8, 2020 · 1 comment

Comments

@himorin
Copy link
Contributor

himorin commented May 8, 2020

Per: w3c/ttwg#116
Comment 3 (summary part)

Five sub issues will be raised following this.

ARIB-TTML is defined as an extension of SMPTE-TT in Vol. 1, Part 3 of ARIB STD-B62. ARIB-TTML is used in UHDTV and some of streaming services in Japan. In UHDTV receivers, ARIB-TTML document is processed by the pre-installed processor in a receiver. In streaming services, ARIB-TTML documents are processed by applications of Hybridcast that is one of the recognized Integrated Broadcast-Broadband systems by ITU. It allows to handle text and image in the same profile as SMPTE-TT does. ARIB-TTML has the features including additional font handling, animation, audio presentation, and additional style control. While capability of those features are similar to IMSC, conversion is required between ARIB-TTML and IMSC to maintain the equivalent content. For this purpose, major points to be considered for the conversion is provided.

@css-meeting-bot
Copy link
Member

The Timed Text Working Group just discussed [WR/ARIB] (meta) Compatibility with ARIB-TTML w3c/imsc#545, and agreed to the following:

  • SUMMARY: TTWG raised this for discussion today, and would like to discuss the sub-issues in further detail in future meetings.
The full IRC log of that discussion <nigel> Topic: [WR/ARIB] (meta) Compatibility with ARIB-TTML #545
<nigel> github: https://github.com//issues/545
<nigel> Nigel: These 5 issues mainly don't need change right now but they do need discussion.
<nigel> .. I don't think we can make any changes to IMSC 1.2 for them but we can consider
<nigel> .. and discuss changes for future versions, if needed.
<nigel> .. It's also worth noting that some of the ARIB-TTML features look like they are coincident
<nigel> .. with either existing IMSC 1.2 features or TTML2 features. That is why further
<nigel> .. discussion with ARIB would be very useful, to understand the best path forward for
<nigel> .. all parties.
<nigel> Pierre: I think the devil is in the detail and we have to study each issue. I agree with Nigel's summary.
<nigel> Nigel: Any other comments?
<nigel> Cyril: To make sure I understand, you say we will defer to the next version but when
<nigel> .. practically will we start talking about them?
<nigel> Pierre: I suggest agenda+ these for the next meeting, to start discussing it.
<nigel> Nigel: That works for me.
<nigel> Cyril: Fine for me also. I would suggest that at least for the PUA/Gaiji discussion we invite
<nigel> .. Vladimir.
<nigel> Pierre: Yes. At least on that one it is an intersection of many things - what is possible
<nigel> .. with fonts, what ARIB thinks and what we think! A complex discussion.
<nigel> SUMMARY: TTWG raised this for discussion today, and would like to discuss the sub-issues in further detail in future meetings.
<nigel> rrsagent, make minutes v2
<RRSAgent> I have made the request to generate https://www.w3.org/2020/05/21-tt-minutes.html nigel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants