[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, 12 June 2018, 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 RSVP This meeting counts towards voter eligibility. Agenda A. Admin 1- Roll call ? out of 6 voters aprove minutes from 24th April 2018, 22nd May 2018 https://www.oasis-open.org/apps/org/workgroup/xliff-omos/email/archives/201805/msg00003.html https://www.oasis-open.org/apps/org/workgroup/xliff-omos/email/archives/201805/msg00007.html
B. Material 1- XLIFF OM OM wiki needs aligned with current JLIFF structure as per 0.9.7 https://github.com/oasis-tcs/xliff-omos-om/wiki
2- JLIFF (https://github.com/oasis-tcs/xliff-omos-jliff) Consensus on boolean vs a yes/no enumeration restated: Stick with yes/no enumeration becuase boolean default is false, while XLIFF defaults are yes. ACTION ITEM: [pending] David-> Email the working list about keeping yes|no strings (according to the discussion today) and hearing Phil’s perspective as well as others.
AI Robert Express all XLIFF 2.1 and 2.0 modules in JLIFF schema. Have 2.1 and 2.0 branches *[Review progress]* Robert seeked gudance on ITS module, given on 24th April Previous Consensus: restated We agreed to work on 2.1 branch first and only then fork the 2.0 DON'T reference the context file [for core and module] from schema or instances. This is tied via the spec [driven by version number] but not the instances, to prevent hammering of the context file. Do we need to use a different separator for modules? underscore "_"? Extensions always need to declare or reference their context inline. AI Robert [DONE], implement meeting consenus for extension points. Extension data needs to start with context. Each extension will be one object. Try to allow them only where they're allowed in XLIFF reviewed "element" extension points implemented as has map rather than an array in the latest commit https://github.com/oasis-tcs/xliff-omos-jliff/commit/85e7c3e0e8d88539df5b2eb7519d6735f84256e9 Consensus restated:: Don't use external context for extensions. All extension context must be stated inline to avoid parsing external context files.. We also agreed that having a dedicated extension container is more validation friendly than just allowing additional properties on the root structure.. -Continue discussing pros and cons of the extensionsData approach compare with XML and consider going back and forth between XML and JSON.
3- TBX Mapping TBX-Basic mapping is in order, almost done on TBXInfo Update from James? C- Other Topics
3- Promotion Also Phil JLIFF library open sourcing was announced in the GALA week https://twitter.com/VistatecGlobal/status/974538466565373952 https://twitter.com/merzbauer/status/974288543093854208 GALA TAPICC needs to work on launching JLIFF based Track 2 Will probably launch by end of June 4- AOB 1- Date of next meeting 26th June 2018 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_41718.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:20180611T201553Z DTSTART;VALUE=DATE-TIME;TZID=Europe/Lisbon:20180612T170000 DTEND;VALUE=DATE-TIME;TZID=Europe/Lisbon:20180612T180000 SEQUENCE:11 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:20180611T201553Z 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\n? out of 6 voters\n\naprove minutes from 24th Apr il 2018\, 22nd May 2018\n\nhttps://www.oasis-open.org/apps/o rg/workgroup/xliff-omos/email/archives/201805/msg00003.html\ n\nhttps://www.oasis-open.org/apps/org/workgroup/xliff-omos/ email/archives/201805/msg00007.html\n\n \n\nB. Material\n\n1 - XLIFF OM\n\nOM wiki needs aligned with current JLIFF struc ture as per 0.9.7\n\nhttps://github.com/oasis-tcs/xliff-omos -om/wiki\n\n \n\n2- JLIFF\n\n(https://github.com/oasis-tcs/x liff-omos-jliff)\n\nConsensus on boolean vs a yes/no enumera tion restated:\n\nStick with yes/no enumeration becuase bool ean default is false\, while XLIFF defaults are yes. \n\nACT ION ITEM: [pending]\n\nDavid->\; Email the working list ab out keeping yes|no strings (according to the discussion toda y) and hearing Phil&rsquo\;s perspective as well as others.\ n\n \n\nAI Robert\n\nExpress all XLIFF 2.1 and 2.0 modules i n JLIFF schema. Have 2.1 and 2.0 branches\n\n*[Review progre ss]*\n\nRobert seeked gudance on ITS module\, given on 24th April\n\nPrevious Consensus: restated\n\nWe agreed to work o n 2.1 branch first and only then fork the 2.0\n\nDON'\;T reference the context file [for core and module] from schema or instances. This is tied via the spec [driven by version number] but not the instances\, to prevent hammering of the context file.\n\nDo we need to use a different separator for modules? underscore "\;_"\;?\n\nExtensions always n eed to declare or reference their context inline.\n\nAI Robe rt [DONE]\, implement meeting consenus for extension points. Extension data needs to start with context. Each extension will be one object. Try to allow them only where they'\;r e allowed in XLIFF\n\nreviewed "\;element"\; extensi on points implemented as has map rather than an array in the latest commit https://github.com/oasis-tcs/xliff-omos-jliff /commit/85e7c3e0e8d88539df5b2eb7519d6735f84256e9\n\nConsensu s restated::\n\nDon'\;t use external context for extensio ns.\n\nAll extension context must be stated inline to avoid parsing external context files..\n\nWe also agreed that havi ng a dedicated extension container is more validation friend ly than just allowing additional properties on the root stru cture..\n\n-Continue discussing pros and cons of the extensi onsData approach\n\ncompare with XML and consider going back and forth between XML and JSON.\n\n \n\n3- TBX Mapping\n\nT BX-Basic mapping is in order\, almost done on TBXInfo\n\nUpd ate from James?\n\nC- Other Topics\n\n \n\n3- Promotion\n\nA lso Phil JLIFF library open sourcing was announced in the GA LA week \n\nhttps://twitter.com/VistatecGlobal/status/974538 466565373952\n\nhttps://twitter.com/merzbauer/status/9742885 43093854208\n\nGALA TAPICC needs to work on launching JLIFF based Track 2\n\nWill probably launch by end of June\n\n4- A OB\n\n1- Date of next meeting\n\n26th June 2018\nGroup: OASI S XLIFF Object Model and Other Serializations (XLIFF OMOS) T C\nCreator: Dr. David Filip URL:https://www.oasis-open.org/apps/org/workgroup/xliff-omos/event.php?event_id=41718 UID:https://www.oasis-open.org/apps/org/workgroup/xliff-omos/event.php?event_id=41718 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]