[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Modified: 4th Tuesday - Regular XLIFF OMOS TC telecenference
|
Event Title: 4th Tuesday - Regular XLIFF OMOS TC telecenference Date: Tuesday, 25 July 2017, 05:00pm to 06:00pm WEST Location: https://www.oasis-open.org/apps/org/workgroup/xliff-omos/members/action_item.php?action_item_id=3822 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 This meeting counts towards voter eligibility. Agenda A. Admin 1- Roll call 8 Voters total
2- Minutes from the last quorum meeting June 13th 2017 https://www.oasis-open.org/apps/org/workgroup/xliff-omos/email/archives/201707/msg00002.html
B. Material 1- XLIFF OM (https://github.com/oasis-tcs/xliff-omos-om) check the wiki mapping https://github.com/oasis-tcs/xliff-omos-om/wiki JLIFF unlike XLIFF has the capability to represent fragments at different logical levels -> need for a wrapper object in JLIFF at the top level - what has to be on the logical root level? list: srcLang / trgLang ...srcDir / trgDir .. whitespace handling (how?) more?
2- JLIFF (https://github.com/oasis-tcs/xliff-omos-jliff) Following the OM discussion and the JLIFF capability to represent fragments from different logical levels Consensus: JLIFF objects and arrays will be always wrapped with a top level object (thus necessarily nameless) indicating jliff version and other global properties of the fragment. What can be inside / what is valid JLIFF content? : files --- the top level object corresponds to XLIFF groups | units --- the top level object corresponds to file subunits --- the top level object corresponds to file Issue: if content is units what's the corresponding XLIFF level? Could be group and could be file. This has potential to break roundtrip.. - what has to be on the wrapper level? list: JLIFF version srcLang / trgLang ...srcDir / trgDir more? - Continue discussion on qualified names Possible prefixes? underscore "_" colon ":" dolar sign "$"
- Look at JSON-LD? Use of context, no namespaces, but a way to shorten IRIs Need to look into a prefix registration mechanism preferably indepnedent on the XLLIFF TC SVN? The group consenus seems tending to identification of context for modules and registered extensions. We can control via the registration mechanism that the first _ or : or $ or whatver the consenus is the separator of the qualifier. Note that this leads to top level "pseudoobject" defining that context that JSON theorists don't seem to like. But we need that the capture the logical top level anyways.
- Using XLIFF 2 test suite to test JLIFF expressivity wait for XLIFF 2.1 test suite Soroush? status?
3- TBX Mapping Report from editorial 1-2-1 meeting [skipping until TC 37 meetings in Vienna late June] current editor's draft: https://tools.oasis-open.org/version-control/browse/wsvn/xliff-omos/trunk/XLIFF-TBX/xliff-tbx-v1.0.pdf Vienna aftermath report (dF/James)
C- Otherr Topics 2- Liaisons Where to place work on extraction reference guides? Seems industry want that.. Proposed that as TAPICC track inside Strand 1 Supply Chain Automation GALA TAPICC https://www.gala-global.org/tapicc-translation-api-class-and-cases-initiative TAPICC does not require GALA Membership. OMOS object model is linked to 2nd and 3rd tracks of TAPICC. TBX Steering Committee / ISO TC37/SC3 - preparation for June meeting in Vienna / Call for XML experts Possible TBX modernization XLIFF TC - 4th public review started on 5th June https://www.oasis-open.org/news/announcements/invitation-to-comment-on-xliff-v2-1-ends-june-20th http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd04/xliff-core-v2.1-csprd04.html Work on cs01 underay, possibly csprd05 3- Promotion 8th XLIFF Symposium CFP has been extended http://bit.ly/XOMOSAn spread the word, consider speaking The main conference is Nov 1-Nov 3, FEISGILTT will be held on Oct 31-Nov 1, 2017. Save the dates. Submit a paper, recruit speakers, volunteer for the PCs. 4- AOB 1- Date of next meeting Doodle for the summer closed https://doodle.com/poll/grchwua93254m49g The rest of this summer seems fine. Need another chair person for Sep 12, as dF will be on JTC1 SC38 plenary 2- Looking for a new secretary. Contact dF Minutes Phil was the note taker, will post his meeting minutes shortly Owner: Dr. David Filip Group: OASIS XLIFF Object Model and Other Serializations (XLIFF OMOS) TC Sharing: This event is shared with the OASIS Open (General Membership), and General Public groups. Public Event Link |
Attachment:
ical_41674.ics
Description: application/ics
BEGIN:VCALENDAR CALSCALE:GREGORIAN METHOD:REQUEST VERSION:2.0 PRODID:-//Kavi Corporation//NONSGML Kavi Groups//EN X-MS-OLK-FORCEINSPECTOROPEN:TRUE BEGIN:VTIMEZONE TZID:Europe/Lisbon BEGIN:STANDARD DTSTART:20001029T020000 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10 TZNAME:WET TZOFFSETFROM:+0100 TZOFFSETTO:+0000 END:STANDARD BEGIN:DAYLIGHT DTSTART:20000326T010000 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3 TZNAME:WEST TZOFFSETFROM:+0000 TZOFFSETTO:+0100 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT STATUS:CONFIRMED TRANSP:OPAQUE DTSTAMP:20170725T173037Z DTSTART;VALUE=DATE-TIME;TZID=Europe/Lisbon:20170725T170000 DTEND;VALUE=DATE-TIME;TZID=Europe/Lisbon:20170725T180000 SEQUENCE:10 SUMMARY:4th Tuesday - Regular XLIFF OMOS TC telecenference LOCATION:https://www.oasis-open.org/apps/org/workgroup/xliff-omos/mem bers/action_item.php?action_item_id=3822 LAST-MODIFIED:20170725T173037Z ORGANIZER:workgroup_mailer@lists.oasis-open.org ATTENDEE;CUTYPE=GROUP:MAILTO:xliff-omos@lists.oasis-open.org DESCRIPTION:See the private action item for dial in details\n\nhttps://w ww.oasis-open.org/apps/org/workgroup/xliff-omos/members/acti on_item.php?action_item_id=3822\n\nAgenda: A. Admin\n\n1- Ro ll call\n\n8 Voters total\n\n \n\n2- Minutes from the last q uorum meeting June 13th 2017\n\nhttps://www.oasis-open.org/ apps/org/workgroup/xliff-omos/email/archives/201707/msg00002 .html\n\n \n\nB. Material\n\n1- XLIFF OM\n\n(https://github. com/oasis-tcs/xliff-omos-om)\n\ncheck the wiki mapping\n\nht tps://github.com/oasis-tcs/xliff-omos-om/wiki\n\nJLIFF unlik e XLIFF has the capability to represent fragments at differe nt logical levels ->\; need for a wrapper object in JLIFF at the top level\n\n- what has to be on the logical root lev el?\n\nlist: srcLang / trgLang ...srcDir / trgDir .. whitesp ace handling (how?) more?\n\n \n\n2- JLIFF\n\n(https://githu b.com/oasis-tcs/xliff-omos-jliff)\n\nFollowing the OM discus sion and the JLIFF capability to represent fragments from di fferent logical levels\n\nConsensus: JLIFF objects and array s will be always wrapped with a top level object (thus neces sarily nameless) indicating jliff version and other global p roperties of the fragment. \n\nWhat can be inside / what is valid JLIFF content? :\n\nfiles --- the top level object c orresponds to XLIFF\n\ngroups | units --- the top level obje ct corresponds to file\n\nsubunits --- the top level object corresponds to file\n\nIssue: if content is units what'\; s the corresponding XLIFF level? Could be group and could be file. This has potential to break roundtrip..\n\n- what has to be on the wrapper level? \n\nlist: JLIFF version srcLang / trgLang ...srcDir / trgDir more?\n\n- Continue discussion on qualified names\n\nPossible prefixes? \n\nunderscore &qu ot\;_"\; \n\ncolon "\;:"\;\n\ndolar sign "\; $"\;\n\n \n\n- Look at JSON-LD? Use of context\, no name spaces\, but a way to shorten IRIs\n\nNeed to look into a pr efix registration mechanism preferably indepnedent on the XL LIFF TC SVN? \n\nThe group consenus seems tending to identif ication of context for modules and registered extensions.\n\ nWe can control via the registration mechanism that the firs t _ or : or $ or whatver the consenus is the separator of th e qualifier.\n\nNote that this leads to top level "\;pse udoobject"\; defining that context that JSON theorists d on'\;t seem to like. But we need that the capture the log ical top level anyways.\n\n \n\n \n\n- Using XLIFF 2 test su ite to test JLIFF expressivity\n\nwait for XLIFF 2.1 test su ite\n\nSoroush? status?\n\n \n\n3- TBX Mapping\n\nReport fro m editorial 1-2-1 meeting [skipping until TC 37 meetings in Vienna late June]\n\ncurrent editor'\;s draft: https://to ols.oasis-open.org/version-control/browse/wsvn/xliff-omos/tr unk/XLIFF-TBX/xliff-tbx-v1.0.pdf\n\nVienna aftermath report (dF/James)\n\n \n\nC- Otherr Topics\n\n2- Liaisons\n\nWhere to place work on extraction reference guides? Seems industry want that..\n\nProposed that as TAPICC track inside Strand 1 Supply Chain Automation\n\nGALA TAPICC https://www.gala-gl obal.org/tapicc-translation-api-class-and-cases-initiative\n \nhttps://www.gala-global.org/publications/translation-api-c lass-and-cases-project-statement-tapicc does not require GAL A Membership. OMOS object model is linked to 2nd and 3rd tra cks of TAPICC.\n\nTBX Steering Committee / ISO TC37/SC3 - pr eparation for June meeting in Vienna / Call for XML experts\ n\nPossible TBX modernization\n\nXLIFF TC - 4th public revie w started on 5th June\n\nhttps://www.oasis-open.org/news/ann ouncements/invitation-to-comment-on-xliff-v2-1-ends-june-20t h\n\nhttp://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd0 4/xliff-core-v2.1-csprd04.html\n\nWork on cs01 underay\, pos sibly csprd05\n\n3- Promotion\n\n8th XLIFF Symposium CFP has been extended\n\nhttp://bit.ly/XOMOSAn\n\nspread the word\, consider speaking\n\nThe main conference is Nov 1-Nov 3\, F EISGILTT will be held on Oct 31-Nov 1\, 2017. Save the dates . Submit a paper\, recruit speakers\, volunteer for the PCs. \n\n4- AOB\n\n1- Date of next meeting\n\nDoodle for the summ er closed\n\nhttps://doodle.com/poll/grchwua93254m49g\n\nThe rest of this summer seems fine.\n\nNeed another chair perso n for Sep 12\, as dF will be on JTC1 SC38 plenary\n\n2- Loo king for a new secretary. Contact dF\nGroup: OASIS XLIFF Obj ect Model and Other Serializations (XLIFF OMOS) TC\nCreator: Dr. David Filip URL:https://www.oasis-open.org/apps/org/workgroup/xliff-omos/event.php?event_id=41674 UID:https://www.oasis-open.org/apps/org/workgroup/xliff-omos/event.php?event_id=41674 BEGIN:VALARM ACTION:DISPLAY DESCRIPTION:REMINDER TRIGGER;RELATED=START:-PT00H15M00S END:VALARM END:VEVENT END:VCALENDAR
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]