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

Incoming liaison from ARIB re IMSC 1.2 #116

Closed
nigelmegitt opened this issue Apr 22, 2020 · 8 comments
Closed

Incoming liaison from ARIB re IMSC 1.2 #116

nigelmegitt opened this issue Apr 22, 2020 · 8 comments

Comments

@nigelmegitt
Copy link
Contributor

Liaison received at https://lists.w3.org/Archives/Member/member-tt/2020Apr/0000.html

Opening this issue to track discussion and response.

@css-meeting-bot
Copy link
Member

The Timed Text Working Group just discussed ARIB incoming liaison, and agreed to the following:

  • SUMMARY: Discussed in call today, Chairs to consider potential next steps, @himorin to look into history of collaboration with ARIB and W3C.
The full IRC log of that discussion <nigel> Topic: ARIB incoming liaison
<nigel> -> https://lists.w3.org/Archives/Member/member-tt/2020Apr/0000.html ARIB incoming liaison
<nigel> github: https://github.com//issues/116
<nigel> Nigel: Is there anything we can action in IMSC 1.2 or requirements for v.next?
<nigel> Pierre: The easy one is character set but that is a normative part of IMSC so we can't
<nigel> .. easily do it in 1.2. I think this came too late to deal with in IMSC 1.2
<nigel> .. We should probably do the character set one at some point - that seems like low hanging fruit.
<nigel> .. The rest: it is hard to understand if it is an encouragement to try to seek convergence
<nigel> .. or just some input that says "we're already doing this, you might want to". It is unclear.
<nigel> Andreas: Yes, and it would be important to find out.
<nigel> .. If they have an interest in convergence then it would really make sense to build a liaison
<nigel> .. with a common goal, but that's a big question.
<nigel> Pierre: It is also really formal. Thinking out loud, TTWG could try to find a way to have
<nigel> .. a more interactive discussion. Is this an invitation to seek convergence on a future
<nigel> .. version of IMSC in ARIB B62 or is this just input for TTWG's benefit only.
<nigel> Nigel: The easy thing is to ask them, to respond with a liaison to say thank you,
<nigel> .. we can't do this in IMSC 1.2, but we could in IMSC 1.3 and what is their timeline.
<nigel> Andreas: Yes, sounds good but we all know liaison process can be very slow.
<nigel> .. I propose to consider what Pierre said and try a less formal way to have a conversation,
<nigel> .. maybe with the Chairs or Editors, to get a feeling what is the way to go. That may help.
<nigel> Nigel: OK that sounds like a good idea, I can try to use the contacts I have.
<nigel> Pierre: Maybe the formal nature of this suggests they want to know it is being taken
<nigel> .. seriously. Maybe a formal invitation to collaborate with W3C would help. I've seen something
<nigel> .. like this before. Maybe that's their expectation, and the answer would be different
<nigel> .. if W3C invites them to collaborate rather than individuals talking. Food for thought.
<nigel> Atsushi: I fully agree that this is a quite formal comment and with this statement.
<nigel> .. Maybe a formal reply and conversation is their intention.
<nigel> Nigel: I think I need to think about this more.
<nigel> Pierre: Has there been formal collaboration between W3C and ARIB in the past?
<nigel> Nigel: I do not know.
<nigel> Pierre: Atsushi, maybe you could look into that, maybe asking the staff if this has
<nigel> .. happened in the past.
<nigel> Atsushi: For now I can only say that there is a liaison relationship between us and them,
<nigel> .. so in any case we can communicate to them about that.
<nigel> .. For some case I need to dig out something.
<nigel> SUMMARY: Discussed in call today, Chairs to consider potential next steps, @himorin to look into history of collaboration with ARIB and W3C.

@himorin
Copy link
Contributor

himorin commented Apr 27, 2020

Only found one example in the past, and also I've got suggestion as (similar to what was written in an example):

  • no formal action is necessity
  • add comments into GitHub issue for tracking (as usual discussion and tracking)

should I file issues to imsc repository for the reply?

@nigelmegitt
Copy link
Contributor Author

As discussed on today's call (#111), @himorin or @palemieux to open issues on the w3c/imsc repo for each of the comments raised by ARIB in their liaison, for our discussion prior to writing a liaison message back.

@nigelmegitt
Copy link
Contributor Author

Thank you @himorin for raising the issues on the IMSC repository directly. The next step is for us to discuss those issues before responding back to ARIB.

@nigelmegitt
Copy link
Contributor Author

nigelmegitt commented May 28, 2020

This was referenced Jun 16, 2020
@css-meeting-bot
Copy link
Member

The Timed Text Working Group just discussed Incoming liaison from ARIB re IMSC 1.2 ttwg#116, and agreed to the following:

  • SUMMARY: @nigelmegitt to collate discussions and questions and propose a draft liaison message in response to ARIB.
The full IRC log of that discussion <nigel> Topic: Incoming liaison from ARIB re IMSC 1.2 ttwg#116
<nigel> github: https://github.com//issues/116
<nigel> Nigel: We have now concluded our run-through of all the points made in the ARIB liaison,
<nigel> .. and I think I have the action now to collate the conclusions from our discussions into
<nigel> .. proposed feedback to ARIB.
<nigel> Pierre: Sounds great.
<nigel> Atsushi: Great
<nigel> Nigel: Okay, thank you, I'll pick that up.
<nigel> SUMMARY: @nigelmegitt to collate discussions and questions and propose a draft liaison message in response to ARIB.

@nigelmegitt
Copy link
Contributor Author

@mikedo sent a link to the English language translation of ARIB STD-B62:

And the English version of the ARIB spec is here:
https://www.arib.or.jp/english/std_tr/broadcasting/std-b62.html

@nigelmegitt
Copy link
Contributor Author

Response sent, archived at https://lists.w3.org/Archives/Member/member-tt/2020Sep/0001.html

On the basis that all other actions are now logged as separate issues, I'm closing this.

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

No branches or pull requests

4 participants