4th Tuesday - Regular XLIFF OMOS TC telecenference (Conference Call) | |
Name | 4th Tuesday - Regular XLIFF OMOS TC telecenference (Conference Call) |
Time | Tuesday, 24 April 2018, 05:00pm to 06:00pm WEST
(Tuesday, 24 April 2018, 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 | OMOS 2018-04-24
|
Agenda | A. Admin 1- Roll call ? out of 5 voters aprove minutes from 10th April 2018 https://www.oasis-open.org/apps/org/workgroup/xliff-omos/email/archives/201804/msg00004.html
B. Material 1- XLIFF OM OM wiki needs aligned with current JLIFF structure as per 0.9.5 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 targeting 24th April, good chance to complete by then. Robert seeks gudance on ITS module 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. 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 4- AOB 1- Date of next meeting 8th May Cancelled, 22nd May 2- Looking for a new secretary. Contact dF |
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
|