[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Modified: 2nd Tuesday - Regular XLIFF OMOS TC telecenference (Conference Call)
Event Title: 2nd Tuesday - Regular XLIFF OMOS TC telecenference (Conference Call) Date: Tuesday, 14 November 2017, 05:00pm to 06:00pm WET 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 x out 6 Voters total aprove minutes from 10th Oct 2017 http://markmail.org/thread/d75nrfa4bjegfrta
B. Material 1- XLIFF OM (https://github.com/oasis-tcs/xliff-omos-om) dF made some progress on prose
discussion on unsuported modules and extensions http://markmail.org/thread/dw3equt7ae57h6xb relevant for both OM and JLIFF
2- JLIFF (https://github.com/oasis-tcs/xliff-omos-jliff) AI Chase: commit the context file AI Robert: make the schema reference the context file make content (root) type keep information about XLIFF level of content, see dsicussion of "root types" http://markmail.org/thread/75n3r6sxrbzohgkk AI dF: clear usage of XLIFF prefix registration mechanism for JLIFF, request that XLIFF prefixes don't use colon ":"
- qualified names (URI shortening) Agreed separator: colon ":"
New Extraction / Merge examples via TAPICC https://github.com/GALAglobal/TAPICC/tree/master/extraction_examples
3- TBX Mapping Report from editorial 1-2-1 meeting [skipping until January 2018] current editor's draft: https://tools.oasis-open.org/version-control/browse/wsvn/xliff-omos/trunk/XLIFF-TBX/xliff-tbx-v1.0.pdf Is it time to resume work on the TBX Basic mapping? C- Other 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. WG3 Traget to provide technically stable JLIFF 1.0 by GALA Boston March 2018. XLIFF Version 2.1 COS01 review until 19th December 2017 http://bit.ly/XLIFF21COS01
3- Promotion FEISGILTT / XLIFF / JLIFF Symposium took place https://locworld.com/wp-content/uploads/2017/10/FEISGILTT2017Program.pdf 4- AOB 1- Date of next meeting 28th Nov, 12th Dec, [skip Dec 26], 9th Jan 2018 and so on.. did not run Doodle for holiday season.. not needed 2- Looking for a new secretary. Contact dF Minutes OMOS Minutes 2017-11-14 phil (minutes), robert, david, yves Last minutes http://markmail.org/thread/d75nrfa4bjegfrta approval seconded by Yves. 1. XLIFF OMOS df started prose on definitons. It is WIP branch on the GitHub repo, not merged back into master yet.. https://github.com/oasis-tcs/xliff-omos-om/commit/7f91ae591dfbe685adad816cf6893ee945b9d933 2. JLIFF Content types rve's email on this thread http://markmail.org/thread/75n3r6sxrbzohgkk
df: Don't want to have content type as an attribute. rve: ok I will go ahead and implement as per email of 23rd df: yes rve: we dont have a defintion of groups or subgroups rve: unit has subunit df: group purpose is just grouping rve: in json difficult to distinguish two types of object df:
ys: an array of subfiles would be subfile and subgroups? rve: same as subunit being segment or ignorable df: repeat exactly for subgroups and subfiles df: subunit and subfile are abstractions, union of segment and ignorable and group and unit respectively, they are choice groups in the XML grammars, oneOf in JSON schema rve: we are using json-ld to capture namespaces WRT the unsuported modules discussion http://markmail.org/thread/dw3equt7ae57h6xb
ys: my issue is: there will be times we don't know the represretation in JLIFF ys: making the distinction between supported and unsupported modules df: I'm afraid we will have to be more demanding in case of crossing the XLIFF/JLIFF boundary ys: there's no thing such as unsupported module? df: sure, and we can have unsuported modules in JLIFF 2, once they were written once by a tool knowing the typing information.. We will probably need to introduce a new agent type, a tool that converts from XLIFF to JLIFF must know at least about schemas of the modules to be able to write them in JLIFF.. ys: I don't know enough about protobuf df: yaml? rve: yaml is getting more popular df: quite common in oasis to do yaml representations, will need to look into it.. rve: yaml similar to json with hiearchies df: uri or iri type? rve: you can define email as regex df: first priority to define structure Registration ys: yes, this is good requirement, would be an issue in XLIFF too TAPICC best practice document along those examples in progress
df: March 2018 is target for jliff 1.0 df: XLIFF 2.1 COS01 review still open until 19th December 2017 http://bit.ly/XLIFF21COS01
Did not run the Doodle as it was obvius we have to skip 26th Dec. 12th Dec and 9 Jan are normal dates.. Does 9th Jan look good in general? pr: too far in the future [meeting adjourned] 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_41711.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:20171127T160416Z DTSTART;VALUE=DATE-TIME;TZID=Europe/Lisbon:20171114T170000 DTEND;VALUE=DATE-TIME;TZID=Europe/Lisbon:20171114T180000 SEQUENCE:10 SUMMARY:2nd Tuesday - Regular XLIFF OMOS TC telecenference (Conferen ce Call) LOCATION:https://www.oasis-open.org/apps/org/workgroup/xliff-omos/mem bers/action_item.php?action_item_id=3822 LAST-MODIFIED:20171127T160416Z 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\nx out 6 Voters total\n\naprove minutes from 10th Oct 2017\n\nhttp://markmail.org/thread/d75nrfa4bjegfrta\n\n \n\nB. Material\n\n1- XLIFF OM\n\n(https://github.com/oasis- tcs/xliff-omos-om)\n\ndF made some progress on prose\n\n \n\ ndiscussion on unsuported modules and extensions\n\nhttp://m arkmail.org/thread/dw3equt7ae57h6xb\n\nrelevant for both OM and JLIFF\n\n \n\n2- JLIFF\n\n(https://github.com/oasis-tcs/ xliff-omos-jliff)\n\nAI Chase: commit the context file\n\nAI Robert: \n\nmake the schema reference the context file\n\n make content (root) type keep information about XLIFF level of content\,\n\nsee dsicussion of "\;root types"\;\n \nhttp://markmail.org/thread/75n3r6sxrbzohgkk\n\nAI dF: clea r usage of XLIFF prefix registration mechanism for JLIFF\, r equest that XLIFF prefixes don'\;t use colon "\;:&quo t\;\n\n \n\n- qualified names (URI shortening)\n\nAgreed se parator:\n\ncolon "\;:"\;\n\n \n\nNew Extraction / M erge examples via TAPICC\n\nhttps://github.com/GALAglobal/TA PICC/tree/master/extraction_examples\n\n \n\n3- TBX Mapping\ n\nReport from editorial 1-2-1 meeting [skipping until Janua ry 2018]\n\ncurrent editor'\;s draft: https://tools.oasis -open.org/version-control/browse/wsvn/xliff-omos/trunk/XLIFF -TBX/xliff-tbx-v1.0.pdf\n\nIs it time to resume work on the TBX Basic mapping?\n\nC- Other Topics\n\n2- Liaisons\n\nWher e to place work on extraction reference guides? Seems indust ry want that..\n\nProposed that as TAPICC track inside Stran d 1 Supply Chain Automation. WG3\n\nTraget to provide techni cally stable JLIFF 1.0 by GALA Boston March 2018.\n\nXLIFF V ersion 2.1 COS01 review until 19th December 2017\n\nhttp://b it.ly/XLIFF21COS01\n\n \n\n \n\n3- Promotion\n\nFEISGILTT / XLIFF / JLIFF Symposium took place\n\nhttps://locworld.com/w p-content/uploads/2017/10/FEISGILTT2017Program.pdf\n\n4- AOB \n\n1- Date of next meeting\n\n28th Nov\, 12th Dec\, [skip D ec 26]\, 9th Jan 2018 and so on..\n\ndid not run Doodle for holiday season.. not needed\n\n2- Looking for a new secretar y. Contact dF\nGroup: OASIS XLIFF Object Model and Other Ser ializations (XLIFF OMOS) TC\nCreator: Dr. David Filip URL:https://www.oasis-open.org/apps/org/workgroup/xliff-omos/event.php?event_id=41711 UID:https://www.oasis-open.org/apps/org/workgroup/xliff-omos/event.php?event_id=41711 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]