[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, 27 March 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 5 voters aprove minutes from 27th Feb 2018 https://www.oasis-open.org/apps/org/workgroup/xliff-omos/email/archives/201803/msg00000.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) AI Robert Express all XLIFF 2.1 and 2.0 modules in JLIFF schema. Have 2.1 and 2.0 branches
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 Discuss: Use URI type of context or not?
- Continue discussion on extension points, look at Robert's commit to introduce extension https://github.com/oasis-tcs/xliff-omos-jliff/commit/85e7c3e0e8d88539df5b2eb7519d6735f84256e9 There are several places where context can be provided: root, or units, files, groups. (Whether @context should be at root or only lower levels). Should mimic XLIFF behavior as close as possible.. 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. AI dF and Yves [DONE]: clear usage of XLIFF prefix registration mechanism for JLIFF, request that XLIFF prefixes don't use colon ":" raised on XLIFF TC 16th Jan DONE in principle, some minor fixes pending, e.g. FAQ http://markmail.org/thread/qmvyp4yuihx76g6r
3- TBX Mapping TBX-Basic mapping is in order, almost done on TBXInfo Update? C- Other Topics 2- Liaisons XLIFF TAPICC - Track 2
3- Promotion Had good coverage on GALA Boston in March, as TAPICC Track 2 was launched, building on JLIFF Also Phil JLIFF library open sourcing was announced in the GALA week https://twitter.com/VistatecGlobal/status/974538466565373952 https://twitter.com/merzbauer/status/974288543093854208 4- AOB 1- Date of next meeting 10th April? 2- Looking for a new secretary. Contact dF 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_41682.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:20180327T130421Z DTSTART;VALUE=DATE-TIME;TZID=Europe/Lisbon:20180327T170000 DTEND;VALUE=DATE-TIME;TZID=Europe/Lisbon:20180327T180000 SEQUENCE:13 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:20180327T130421Z 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 5 voters\n\naprove minutes from 27th Feb 2018\n\nhttps://www.oasis-open.org/apps/org/workgroup/xliff -omos/email/archives/201803/msg00000.html\n\n \n\n \n\nB. Ma terial\n\n1- XLIFF OM\n\nOM wiki needs aligned with current JLIFF structure as per 0.9.5\n\nhttps://github.com/oasis-tcs /xliff-omos-om/wiki\n\n \n\n2- JLIFF\n\n(https://github.com/ oasis-tcs/xliff-omos-jliff)\n\nAI Robert\n\nExpress all XLIF F 2.1 and 2.0 modules in JLIFF schema. Have 2.1 and 2.0 bran ches\n\n \n\nPrevious Consensus: restated\n\nWe agreed to wo rk on 2.1 branch first and only then fork the 2.0\n\nDON' \;T reference the context file [for core and module] from sc hema or instances. This is tied via the spec [driven by vers ion number] but not the instances\, to prevent hammering of the context file.\n\nExtensions always need to declare or re ference their context inline.\n\nAI Robert [DONE]\, implemen t meeting consenus for extension points. Extension data need s to start with context. Each extension will be one object. Try to allow them only where they'\;re allowed in XLIFF\n \nreviewed "\;element"\; extension points implemente d as has map rather than an array in the latest commit https ://github.com/oasis-tcs/xliff-omos-jliff/commit/85e7c3e0e8d8 8539df5b2eb7519d6735f84256e9\n\nDiscuss:\n\nUse URI type of context or not?\n\n \n\n- Continue discussion on extension p oints\, look at Robert'\;s commit to introduce extension\ n\nhttps://github.com/oasis-tcs/xliff-omos-jliff/commit/85e7 c3e0e8d88539df5b2eb7519d6735f84256e9\n\n There are several p laces where context can be provided: root\, or units\, files \, groups. \n\n (Whether @context should be at root or only lower levels).\n\nShould mimic XLIFF behavior as close as p ossible..\n\nWe also agreed that having a dedicated extensio n container is more validation friendly than just allowing a dditional properties on the root structure..\n\n-Continue di scussing pros and cons of the extensionsData approach\n\ncom pare with XML and consider going back and forth between XML and JSON.\n\nAI dF and Yves [DONE]: clear usage of XLIFF pre fix registration mechanism for JLIFF\, request that XLIFF pr efixes don'\;t use colon "\;:"\;\n\nraised on XLI FF TC 16th Jan\n\nDONE in principle\, some minor fixes pendi ng\, e.g. FAQ\n\nhttp://markmail.org/thread/qmvyp4yuihx76g6r \n\n \n\n3- TBX Mapping\n\nTBX-Basic mapping is in order\, a lmost done on TBXInfo\n\nUpdate?\n\nC- Other Topics\n\n2- Li aisons\n\nXLIFF\n\nTAPICC - Track 2\n\n \n\n3- Promotion\n\n Had good coverage on GALA Boston in March\, as TAPICC Track 2 was launched\, building on JLIFF\n\nAlso Phil JLIFF librar y open sourcing was announced in the GALA week \n\nhttps://t witter.com/VistatecGlobal/status/974538466565373952\n\nhttps ://twitter.com/merzbauer/status/974288543093854208\n\n4- AOB \n\n1- Date of next meeting\n\n10th April?\n\n2- Looking for a new secretary. Contact dF\nGroup: OASIS XLIFF Object Mode l and Other Serializations (XLIFF OMOS) TC\nCreator: Dr. Dav id Filip URL:https://www.oasis-open.org/apps/org/workgroup/xliff-omos/event.php?event_id=41682 UID:https://www.oasis-open.org/apps/org/workgroup/xliff-omos/event.php?event_id=41682 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]