Description:
See the private action item for dial in details
https://www.oasis-open.org/apps/org/workgroup/xliff-omos/members/action_item.php?action_item_id=3822
==========
Agenda:
A. Admin
1- Roll call
2- Approval of July 26 meeting minutes
https://www.oasis-open.org/apps/org/workgroup/xliff-omos/email/archives/201608/msg00002.html
Will need email approval of today's minutes
B. Material
1- XLIFF OM
Still working on the provisional directory: https://github.com/DavidFatDavidF/XLIFFOM/blob/master/model/Class_Diagram.PNG.
Time to move onto the official OASIS repos that are now available, see https://lists.oasis-open.org/archives/chairs/201608/msg00000.html
Have a resolution to create a github repo for the OM development
https://www.oasis-open.org/resources/tc-admin-requests/request-a-tc-github-version-control-instance-be-created
https://github.com/oasis-tcs/xliff-omos-om
Maintainers?
300 character description:
Abstract Object Model for XLIFF Versions 2.0 and higher, developed by OASIS XLIFF OMOS TC
2- JLIFF
Resolution to have a github repo for this
https://www.oasis-open.org/resources/tc-admin-requests/request-a-tc-github-version-control-instance-be-created
https://github.com/oasis-tcs/xliff-omos-jliff
Maintainers?
300 character description:
JSON serialization of the XLIFF Abstract Object Model, developed by OASIS XLIFF OMOS TC
3- TBX Mapping
Continued work on SVN:
https://tools.oasis-open.org/version-control/browse/wsvn/xliff-omos/trunk/XLIFF-TBX/xliff-tbx-10.xml
C. Other Topics
1- Next meeting on September 27, 2016,
2- Liaisons – ISO TC37 SC3.
NEW:
GALA (TAUS, LT-Innovate) TAPICC, see FEISGILTT Montreal
TBX Steering Committtee
The idea is to keep the inline data model of TBX as the one in XLIFF 2. I am appointed to this subcommittee by NSAI (as an Irish national expert) and will be continuing to work on that with Alan.
Alan, would you please provide the correct citation information of TBX for the XLIFF TBX mapping?
Alan AI: TBX normative citations
3- Promotion
1 day FEISGILTT in Montreal
Still time to submit Translation API use cases
http://bit.ly/FEISGILTTM
4- AOB
==========
Minutes:
A. Admin
1- Roll call
Achieved quorum
Alan from BYU request persistent non-voter status until March 2017 – status to switch to persistent non-voter as of Oct-11-2016 meeting.
2- Approval of July 26 meeting minutes
https://www.oasis-open.org/apps/org/workgroup/xliff-omos/email/archives/201608/msg00002.html
David proposes these minutes are approved / Chase seconds / No objections, minutes are approved.
B. Material
1- XLIFF OM
Still working on the provisional directory: https://github.com/DavidFatDavidF/XLIFFOM/blob/master/model/Class_Diagram.PNG.
Time to move onto the official OASIS repos that are now available, see https://lists.oasis-open.org/archives/chairs/201608/msg00000.html
Resolution to request a github repo for the OM development
Link to administrative form: https://www.oasis-open.org/resources/tc-admin-requests/request-a-tc-github-version-control-instance-be-created
Repository URL, using proper naming convention: https://github.com/oasis-tcs/xliff-omos-om
Primary Maintainer: David Filip / Backup Maintainer: Felix Sasaki
300-character description: Abstract Object Model for XLIFF Versions 2.0 and higher, developed by OASIS XLIFF OMOS TC
2- JLIFF
Resolution to request a github repo for the JLIFF development
Link to administrative form: https://www.oasis-open.org/resources/tc-admin-requests/request-a-tc-github-version-control-instance-be-created
Repository URL, using proper naming convention: https://github.com/oasis-tcs/xliff-omos-jliff
Primary Maintainer: Robert van Engelen / Backup Maintainer: Chase Tingley
300-character description: JSON serialization of the XLIFF Abstract Object Model, developed by OASIS XLIFF OMOS TC
Motion: David Filip proposes that the TC requests to create the two github repositories listed above, with the maintainers and description as shown, and the TC instructs the chair to submit the requests to OASIS Administration.
Loïc seconds
Simple majority vote conducted during the meeting
Yes - 8 (unanimous approval)
No - 0
Abstain - 0
Note: Approval of minutes needed via electronic ballot to proceed with motion.
3- TBX Mapping
Continue work on SVN: https://tools.oasis-open.org/version-control/browse/wsvn/xliff-omos/trunk/XLIFF-TBX/xliff-tbx-10.xml
Link to latest Editors' Drfat of TBX mapping: https://tools.oasis-open.org/version-control/browse/wsvn/xliff-omos/trunk/XLIFF-TBX/xliff-tbx-v1.0.pdf
Link to the 26th Sep 2016 version of the TBX mapping:
https://tools.oasis-open.org/version-control/browse/wsvn/xliff-omos/trunk/XLIFF-TBX/xliff-tbx-v1.0-wd01.pdf?rev=11&sc=1
James reports on the progress: mapping is in, needs more explanatory text and review
C. Other Topics
1- Next meeting on October 11, 2016
2- Liaisons
TBX Steering Committee / ISO TC37/SC3
During the current revision of TBX as ISO standrad, the idea is to change the inline data model of TBX to the same is in XLIFF 2. David joined the steering committee, appointed to the ISO TC37/SC3 by NSAI (as an Irish national expert) and will be continuing to work on that with Alan. This will malke the TBX mapping above even more straightforward.
XLIFF TC
XLIFF 2.1 – discussions around change tracking module, a few data categories still need review, DF working on draft, feedback appreciated
http://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-21/xliff-core-v2.1.pdf
XLIFF TC wants to proceed to the 1st public review on 4th October
3- Promotion
1 day FEISGILTT in Montreal (Still time to submit Translation API use cases: http://bit.ly/FEISGILTTM)
GALA working on standard translation API compliant with XLIFF 2 data model
Alan: what is the relationship between XLIFF OMOS API and TAPICC
dF: We at XLIFF OMOS are not working on an API, just the OM, we want their API to be compliant with our OM, use our serializations, mappings etc.
4- AOB
N/A
Meeting adjourned
==========
Attendance:
| Meeting Statistics |
| Quorum rule |
51% of voting members
|
| Achieved quorum |
yes |
| Individual Attendance |
Contributing Members: 9 of 18 (50%)
Voting Members: 8 of 9 (88%) (used for quorum calculation)
|
| Company Attendance |
Contributing Companies: 8 of 14 (57%)
Voting Companies: 7 of 8 (87%)
|