Dear colleagues
An issue brought to the attention of Q21/16 experts.
Best regards Simão
From: olivier.dubuisson@orange.com [mailto:olivier.dubuisson@orange.com] Sent: Monday, October 17, 2016 18:10 To: Campos, Simao simao.campos@itu.int Subject: Fwd: [T2Q4] Re: Harmonization on speech-to-speech translation standardization with JTC1/SC35
Simao,
looks like I used the wrong email list for Q21/16. Can you please forward?
Thanks, Olivier
-------- Forwarded Message -------- Subject:
[T2Q4] Re: Harmonization on speech-to-speech translation standardization with JTC1/SC35
Date:
Mon, 17 Oct 2016 17:59:07 +0200
From:
olivier.dubuisson@orange.commailto:olivier.dubuisson@orange.com
Organization:
Orange
To:
S. Senda s.senda@nict.go.jpmailto:s.senda@nict.go.jp, t13sg16q21@lists.itu.intmailto:t13sg16q21@lists.itu.int, t13sg2q4@lists.itu.intmailto:t13sg2q4@lists.itu.int
Dear all,
as discussed at the last Q4/2 meeting, and as further requested by Senda-san's email below, I am pleased to share with you the following two texts which are now under DIS ballot in ISO/IEC JTC 1/SC 35 until 5 Jan 2017: Ballot
Type
Committee
Closing date
ISO/IEC DIS 20382-1
DIS
ISO/IEC JTC 1/SC 35
2017-01-05
Information technology -- User interfaces -- Face-to-face speech translation -- Part 1: User interface
ISO/IEC DIS 20382-2
DIS
ISO/IEC JTC 1/SC 35
2017-01-05
Information technology -- User interface -- Face-to-face speech translation -- Part 2: System architecture and functional components
I would recommend that, if Q4/2 and/or Q21/16 decide to submit comments, the consolidated set of comments (using the attached commenting template), agreed upon on the Q4/2 and Q21/16 mailing-lists, be sent to me no later than 14 Dec 2016, so that I can send transmit them to ISO in time before the ballot closes.
Regards, O. Dubuisson ITU-T liaison officer to ISO/IEC JTC 1 On 14/10/2016 09:58, S. Senda wrote: Dear Noah Luo and Kai wei,
As both of you may know, I have been working on harmonization on speech-to-speech translation standardization not only among ITU-T study groups but also with JTC1/SC35. Recently, I received informal information that JTC1/SC35 would start ballot on DIS 20382: "User Interface - Face-to-Face Speech Translation", Part1: "User Interface" and Part2: "System architecture and functional components".
Q21/16 has sent liaison to JTC1/SC35 calling l collaboration on S2ST standardization (SG16-LS171 and LS217), but no response were returned from JTC1/SC35. As far as the information I got from members of Japanese national committee for JTC1/SC35, any Japanese member had not yet informed any liaison related DIS 20382 and no concern from ITU-T had been identified. At the same time, Mr. Olivier Dubuisson (JTC1 liaison officer) informally informed me that Mr. Noah Luo and Mr. Kai Wei has been listed as liaisons in JTC1/SC35. I believe that Q21/16 need to clarify how JTC1/SC35 has been handled our liaison statements.
Then, I have at least a question to be clarified and a request to our Rapporteurs.
The question is whether you have ever formally informed that you are listed as liaisons in JTC1/SC35.
The request is to get and deliver the formal documents which now under ballot process in JTC1/SC35 to Q21 experts for having the chance to review and to comment their work formally, if our Rapporteurs are formally listed by JTC1/SC35 as liaisons as informed by Mr. Dubuisson.
Best regards,
Show (Shoichi Senda)
NICT
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.