4th Tuesday - Regular XLIFF OMOS TC telecenference (Conference Call) | |
Name | 4th Tuesday - Regular XLIFF OMOS TC telecenference (Conference Call) |
Time | Tuesday, 26 July 2016, 05:00pm to 06:00pm WEST
(Tuesday, 26 July 2016, 04:00pm to 05:00pm UTC) |
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 |
Minutes | A. Admin
1- Roll call dF:We have quorum for this meeting. (5 of 9)
2- Approval of July 12 meeting minutes dF: I propose these meeting minutes (https://lists.oasis-open.org/archives/xliff-omos/201607/msg00009.html) to be the official record of our previous meeting. Chase: I second. dF: If no objections, it’s approved.
B. Material
1- XLIFF OM dF: I have no progress on this part. The latest version can be found here when updated: https://github.com/DavidFatDavidF/XLIFFOM/blob/master/model/Class_Diagram.PNG. So far, the structural part looks stable and I was thinking if we should merge “source” and “target” datatypes, as we did for “segment” and “ignorable”, distinguishing with an attribute. The issue with id duplication and cloning code, however, might be tricky. We can discuss it on the mailing list.
2- JLIFF dF: We don’t have any progress from Yves and Robert. The work on validating JLIFF and development of JLIFF schema is ongoing. As Yves suggests, we can, for now, use online JSON parsers. Chase: I usually use JSON Python or other libraries. Felix: Here is an online validator: https://jsonformatter.curiousconcept.com/
3- TBX Mapping dF: We decided to move on TBX faster to use James’s time the best (working on SVN not waiting for git). I started an OASIS DocBook template for the TBX mapping spec https://tools.oasis-open.org/version-control/browse/wsvn/xliff-omos/trunk/XLIFF-TBX/xliff-tbx-10.xml Basically, it is about re-creating the paper content by completing the section 2 of the Template, as well as adding citations for TBX, validation methods for TBX and XLIFF 2.0, and finally a Conformance statement for the mapping. James, do you think you can transfer the paper (https://www.localisation.ie/resources/publications/2015/260) to this template on the SVN? James: Sure! I will start working on it. Alan: James, please do on behalf of BYU dF: James, please get in touch if any issues with the template or anything unclear.. C. Other Topics
1- Next meeting on September 13, 2016, as we agreed to skip August meetings dF: Hopefully we will have progress on the JLIFF schema, TBX mapping document and JSON representation examples. Any contribution into the object model diagram is appreciated. Feel free to contact me or Chase for any queries or issues with GIT.
2- Liaisons – ISO TC37 SC3. dF: 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: We should wait for the final draft (fdis stage at ISO), I presume. dF: the Mapping will also need to go through OASIS publishing stages, so it should be fine, just need to know the citation format and TBX should become fdis just on time for us.. will also need TBX Basic citation.. 3- Promotion dF: Status of the Open Standards cup nomination can be found here https://www.oasis-open.org/open-standards-cup , and the winner is to be selected soon by OASIS TAB.
4- AOB dF: If no suggestions, then this meeting is adjourned. |
Agenda | A Admin 1. Roll call 2. Approval of July 12 meeting minutes https://lists.oasis-open.org/archives/xliff-omos/201607/msg00009.html
B Material 1. XLIFF OM a. Latest diagram state https://github.com/DavidFatDavidF/XLIFFOM/blob/master/model/Class_Diagram.PNG [current link]
2. JLIFF a. Progress on JLIFF scema? We don’t have a specification yet, just JLIFF examples on the wiki https://wiki.oasis-open.org/xliff-omos/Examples Plus of course the JLIFF schema needs to be aligned with the OM diagram https://github.com/DavidFatDavidF/XLIFFOM/blob/master/model/Class_Diagram.PNG and later on with any prose spec for the OM and/or JLIFF. The OM diagram gives the structure and all multiplicity constraints..
3. TBX Mapping a. This paper https://www.localisation.ie/resources/publications/2015/260 https://lists.oasis-open.org/archives/xliff-omos-comment/201605/msg00000.html needs transformed into OASIS Standard Work Product format [the document model provided by TC admin..] https://tools.oasis-open.org/version-control/browse/wsvn/xliff-omos/trunk/%21OASIS_Front_Matter/xliff-tbx-v1.0-wd01.docx Starting that on SVN (not waiting for the git repo) We can do that in Word or Docbook, any thooghts? C Other Topics 2. Next meeting on September 13, 2016, as we agreed to skip August meetings 3. Liaisons – ISO TC37 SC3. The purpose to is keep aligned the inline data model of TBX with XLIFF 2 and the LIFF OM. dF appointed to SC3 from NSAI to be able to represent XLIFF and OMOS on SC3.
4. Promotion – Any news? Status of the Open Standards cup nomination https://www.oasis-open.org/open-standards-cup – winner to be selected soon by OASIS TAB. AOB ?
|
Submitter | Dr. David Filip |
Group | OASIS XLIFF Object Model and Other Serializations (XLIFF OMOS) TC |
Access | This event is visible to OASIS XLIFF Object Model and Other Serializations (XLIFF OMOS) TC and shared with
|