[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Meeting minutes
|
Dear all, Please find below a summary of todayâs discussion. Best, LucÃa Attendance:
LucÃa, Rodolfo, Yoshito, DavidF. We have quorum.
I. Administration
Y: I second.
R: Meeting minutes approved.
Df: No progress, sorry.
R: are you interested in keeping this?
Df: I think it is important. I might be able to see it before Christmas. TC37 went under systematic review this year.
R: Ok.
R: I have made new builds in github. I do not know if you would like me to add them in the TC repository.
L: Do we have a protocol?
R: We donât. But we could use this feature.
Y: I think the good thing is that you get a snapshot and it is not a moving document. In github we have a moving document. We should have a tag there.
R: In DITA even moving documents, people sent comments to the mailing list.
Y: Tagging or taking a snapshot is a good process to track discussion. We can either create a tag or create a snapshot.
(Rodolfo shows the changes that were made
https://github.com/oasis-tcs/xliff-xliff-22/raw/master/xliff-22/xliff-extended-v2.2wd.pdf
). I will wait to make the new changes until the open ballot will be closed.
(Rodolfo shows the changes included in the spec
https://github.com/oasis-tcs/xliff-xliff-22/raw/master/xliff-22/xliff-extended-v2.2wd.pdf
). Appendix C contains a summary of the changes made in this version. We are adding the links to previous files, so we are not
Df: I saw the ballot. If it does not affect the numbering, I do not mind it.
R: To keep changes in a translation, this module would be useful.
Df: I totally agree with that. I even developed and coded a solution, but the committee did not accept it and we decided to demote the module from the spec.
R:The plan would be to work on it after publishing 2.2, while we wait for the format messaging module.
Df: would it affect the numbering?
R: for the core, it does not matter, as we will not include the modules.
Df: but for the extended version, I mean.
R: What happens if we remove the number?
Df: the other modules would change the numbering, it might be a problem for some people. It is not a big deal. If you are planning to work on it in the future.
R: If we reintroduce it, the numbers might change. I do not see a problem altering the numbers. If they go to the table of contents, they will find the links.
It is not a big deal.
Df: the messaging format is making good progress. I would expect the module soon.
R: That is great. After the ballot finishes tomorrow, I will publish the new draft.
Df: The official review process is populated by Chet.
R: I know, but I am talking about our first internal review. You should get an email when I commit a new version.
C. Open Ballot. Change Tracking module removal.
https://www.oasis-open.org/apps/org/workgroup/xliff/ballot.php?id=3731&referring_url=%2Fkws
So far, we have received 4 votes, 2 are missing.
We met yesterday, the JLIFF committee. We are trying to revive the committee.
R: Are you planning to release support for 2.2 in JLIFF?
Df: we were working on a version based on 2.0 and 2.1 together.
R: The changes made in 2.2 are minimum. You might want to consider that.
Df: we will try and meet again in January.
Other business:
L: We got an email from OASIS requesting information to celebrate the achievement of TCs, if you have any information that you would like to share in this
sense, let us know.
Df: Getting approved by an ISO committee is a long achievement. If we got a new version, we could tell them.
L: No new business, see you in two weeks.
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]