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. Approve meeting minutes from Maay 10 (May 24 and June 14 did not reach quorum)
https://www.oasis-open.org/apps/org/workgroup/xliff-omos/email/archives/201604/msg00003.html
3. Welcome Robert van Engelen
https://www.oasis-open.org/apps/org/workgroup/xliff-omos/email/archives/201605/msg00003.html
B. Material:
1. Technical Deliverables
Updated diagram from Lucian
https://www.oasis-open.org/apps/org/workgroup/xliff-omos/email/archives/201605/msg00002.html
Progress with collaborative UML diagram editting:
https://github.com/DavidFatDavidF/XLIFFOM/blob/master/model/XLIFFOM.png
Wiki on Papyrus: https://wiki.oasis-open.org/xliff-omos/WorkingWithPapyrus
https://www.oasis-open.org/apps/org/workgroup/xliff-omos/email/archives/201606/msg00001.html
Papyrus, an open source option: http://www.eclipse.org/papyrus/download.html
Somewhat older email from Yves on JSON alpha implementation in Lynx
https://www.oasis-open.org/apps/org/workgroup/xliff-omos/email/archives/201604/msg00009.html
Spec GIT Request – update
Robin said this is in progress and one of last decision points should happen around mid June. Once this becomes available it should be easy to migrate from the temporary github repo managed by merzbauer (dF)
The ticket has been reopened (https://issues.oasis-open.org/browse/TCADMIN-2303).
Copyright Issues with Submissions
No progress on this https://www.oasis-open.org/apps/org/workgroup/xliff-omos/email/archives/201602/msg00021.html.
We will close this one as we're not likely to make use of the thesis beyond standard attributed citation..
TBX Mapping based on a published paper https://www.localisation.ie/resources/publications/2015/260
This has been properly submitted by James on 24th May through the comment list
https://lists.oasis-open.org/archives/xliff-omos-comment/201605/msg00000.html
James is also joining the TC, in the process of prirep approval
Report from Working meetings at FESGILTT Dublin, June 7 http://locworld.localizationworl.netdna-cdn.com/wp-content/uploads/2015/11/FEISGILTTProgram2016.pdf
Reminder:
TC members, please use group e-mail for communication / comments
Non-TC members, use the commenting facility (send a comment button on TC public page)
2. Assignment of editor roles for the technical deliverables
Actually, we're now ready to move on the TBX mapping front, we're just waiting for the git repo, could decide to move ahead on SVN with this one..
Tabled for JLIFF and OM until we have enough material on wiki.
3. TMX Contribution
Report from Dublin TMX Symposium
http://locworld.localizationworl.netdna-cdn.com/wp-content/uploads/2015/11/FEISGILTTProgram2016.pdf
dF contacted Jamie on 18th Feb and 8th Mar, and March 30 but no answer so far.
Copyright transfer agreement needs to be negotiated between ETSI and OASIS.
4. Liaisons
ARIP TC (dF)
ISO/IEC JTC1 SC38 wrt reference architecture for big data. (dF)
XLIFF TC (Yves)
5. Promotion
Looking for someone to write a high level paper on Why XLIFF 2 (and XLIFF OMOS?)
AOB
6. Doodle to check voters availability over the summer
Next meeting on June 28
==========
Minutes:
Meeting minutes 28.06.2016
A. Admin:
- Roll call
Loïc: We have quorum in the meeting. 5 of 7 Voters
2. Approve meeting minutes from May 10 (May 24 and June 14 did not reach quorum)
https://www.oasis-open.org/apps/org/workgroup/xliff-omos/email/archives/201604/msg00003.html
dF: Does any one second?
Loïc: I do.
dF: If there are no objections, it’s approved
3. Welcome Robert van Engelen
https://www.oasis-open.org/apps/org/workgroup/xliff-omos/email/archives/201605/msg00003.html
Robert van Engelen: Hi every one! I am excited to contribute in this committee. My company specializes in XML web services, starting with SOAP and then extending into data binding compliance and participating in W3C workgroups for data-binding patterns. We have been considering development and implementation of particles, in XML and its alternatives, like JSON and other non-XML based representations. I hope I will be able to help this committee and contribute to its work.
dF: Thank you for joining us, you will get your voting rights at the conclusion of your next participation if you can make the 12th July.
B. Material:
- Technical Deliverables
dF: We are currently working on a UML diagram of the object model. Lucian started it (https://www.oasis-open.org/apps/org/workgroup/xliff-omos/email/archives/201605/msg00002.html) on a UML tool, which is not interoperable. As he is not a member of XLIFF OMOS TC anymore, I strated developing the diagram in Papyrus, an Eclipse plugin. This diagram (https://github.com/DavidFatDavidF/XLIFFOM/blob/master/model/XLIFFOM.png) (a temporary repository, not OASIS-guaranteed yet) however contains some improvements. Currently https://github.com/DavidFatDavidF/XLIFFOM/blob/f6d7cfcd969af207bc99df2eb9d87b0e1e2ade23/model/XLIFFOM.png, it is a good representation of the structural levels of XLIFF. We agreed to use the same names as in XLIFF for now to avoid the need to keep a mapping table, but still keeping the diagram XML-independent. We allow xml:space on structural elements, I kept the name xml:space to fix the semantics, as I don't know what's the semantic of preserving whitespace or not in JSON and other possible serializations.. Do we have any thoughts on this issue in the TC?
Chase: I don’t think JSON has any rules for space preserving. It is probably presumed to be preserved. I will check
dF: We should look into it as we move further, remembering that XLIFF follows the XML behaviour when it comes to preserving whitespace.
Wiki page on Papyrus: https://wiki.oasis-open.org/xliff-omos/WorkingWithPapyrus
Latest version of diagram: https://wiki.oasis-open.org/xliff-omos/OMDiagrams.
Meeting time snaphot: https://github.com/DavidFatDavidF/XLIFFOM/commit/97151172a32bc399ef2a31f2179951800da08a34
2. Assignment of editor roles for the technical deliverables
dF: The potential TBX mapping IP issue has been formally resolved with the mapping being contributed to the TC. We will get back to this item in July, as we will have James (the lead author of the mapping, albeit with guidance from Alan and myself). I am currently working on the Object Model, I announce the call for editors to work on JLIFF.
3. TMX Contribution
dF: I will have the full meeting minutes for FEISGILTT 2016 Dublin by tomorrow. Chase, would you please give us a report?
Chase: With regard to TMX, we had a discussion in Dublin. Angelika Zerfaß started the talk by posting out some limitations to TMX and suggestions. In the further discussion, there was a broad consensus that TMX Next will need to align its inline data model with XLIFF2. But it was also proposed to use XLIFF 2 itself instead, dropping further development of TMX. altogether. A firm conclusion was not reached at the end. But the stakeholders who were present in the room seemed inclined to drop TMX in favor of XLIFF 2 with Translation Candidate module, including Angelika
dF: yes, she said that her clients didn't care what the standard was named, they just requested lossless leverage.
dF: Thanks! Basically, the main point was that TMX is multilingual, whereas XLIFF is only bilingual. Ryan proposed a “clean solution” to use the Translation Candidate module with reference languages to host as many languages as necessary. Still, this is not resolved, we'd need to collect feedback from more staleholders. We cannot work on TMX unless the OASIS works out the IPR transfer from ETSI, which is taking too long now. We could work on an XLIFF profile to replace TMX, but we wouldn't be allowed to say it was a TMX successor, unless the TMX IP was transferred from ETSI.
4. Liaisons
dF: No new items in this section.
5. Promotion
dF: Alan Melby and other JIAMCATT network members expressed interest in a paper on business benefits of adopting XLIFF 2 and its data model, please contact Alan Melby or myself if interested in contributing to writing this up.
6. Doodle to check voters availability over the summer
dF: Our August meetings better be dropped, I propose. If no objections, this is considered a consensus decision. We will hold both July meetings as we should have quorum based on the Doodle poll.
dF: AOB? If there are no agenda proposals for the next meeting, we will have our next meeting onJuly 12th.
I adjourn this meeting now.
==========
Attendance:
| Meeting Statistics |
| Quorum rule |
51% of voting members
|
| Achieved quorum |
yes |
| Individual Attendance |
Contributing Members: 7 of 19 (36%)
Voting Members: 5 of 7 (71%) (used for quorum calculation)
|
| Company Attendance |
Contributing Companies: 7 of 15 (46%)
Voting Companies: 5 of 7 (71%)
|