[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, 13 February 2018, 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 RSVP This meeting counts towards voter eligibility. Agenda A. Admin 1- Roll call ? out of 5 voters aprove minutes from 30th Jan 2018 https://lists.oasis-open.org/archives/xliff-omos/201802/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) Previous Consensus: restated 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?
make context for 2.0 and 2.1 dF AI to make a PR for forking the 2.0 and 2.1 contexts https://github.com/oasis-tcs/xliff-omos-jliff/pull/5 [DONE, review]
- 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 @James, would you walk us through the TBX Basic changes? C- Other Topics 2- Liaisons OS ballot closes today 23:59 UTC https://www.oasis-open.org/committees/ballot.php?id=3171 https://www.oasis-open.org/apps/org/workgroup/voting/ballot.php?id=3171
3- Promotion Will have good coverage on GALA Boston in March, as TAPICC Track 2 will be launched, building on JLIFF 4- AOB 1- Date of next meeting 27th Feb look good, probably cannot make 13th March (GALA coneference), 27th March?
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_41714.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:20180213T155359Z DTSTART;VALUE=DATE-TIME;TZID=Europe/Lisbon:20180213T170000 DTEND;VALUE=DATE-TIME;TZID=Europe/Lisbon:20180213T180000 SEQUENCE:9 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:20180213T155359Z 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 30th Jan 2018\n\nhttps://lists.oasis-open.org/archives/xliff-omos/20 1802/msg00000.html\n\n \n\nB. Material\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\n 2- JLIFF\n\n(https://github.com/oasis-tcs/xliff-omos-jliff)\ n\nPrevious Consensus: restated\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 no t the instances\, to prevent hammering of the context file.\ n\nExtensions always need to declare or reference their cont ext inline.\n\nAI Robert [DONE]\, implement meeting consenus for extension points. Extension data needs to start with co ntext. Each extension will be one object. Try to allow them only where they'\;re allowed in XLIFF\n\nreviewed "\; element"\; extension points implemented as has map rathe r than an array in the latest commit https://github.com/oasi s-tcs/xliff-omos-jliff/commit/85e7c3e0e8d88539df5b2eb7519d67 35f84256e9\n\nDiscuss:\n\nUse URI type of context or not?\n\ n \n\nmake context for 2.0 and 2.1\n\ndF AI to make a PR for forking the 2.0 and 2.1 contexts\n\nhttps://github.com/oasi s-tcs/xliff-omos-jliff/pull/5\n\n[DONE\, review]\n\n \n\n- C ontinue discussion on extension points\, look at Robert'\ ;s commit to introduce extension\n\nhttps://github.com/oasis -tcs/xliff-omos-jliff/commit/85e7c3e0e8d88539df5b2eb7519d673 5f84256e9\n\n There are several places where context can be provided: root\, or units\, files\, groups. \n\n (Whether @ context should be at root or only lower levels).\n\nShould m imic XLIFF behavior as close as possible..\n\nWe also agreed that having a dedicated extension container is more validat ion friendly than just allowing additional properties on the root structure..\n\n-Continue discussing pros and cons of t he extensionsData approach\n\ncompare with XML and consider going back and forth between XML and JSON.\n\nAI dF and Yves [DONE]: clear usage of XLIFF prefix registration mechanism for JLIFF\, request that XLIFF prefixes don'\;t use colon "\;:"\;\n\nraised on XLIFF TC 16th Jan\n\nDONE in p rinciple\, some minor fixes pending\, e.g. FAQ\n\nhttp://mar kmail.org/thread/qmvyp4yuihx76g6r\n\n \n\n3- TBX Mapping\n\n TBX-Basic mapping is in order\, almost done on TBXInfo\n\n@J ames\, would you walk us through the TBX Basic changes?\n\nC - Other Topics\n\n2- Liaisons\n\nOS ballot closes today 23:5 9 UTC\n\nhttps://www.oasis-open.org/committees/ballot.php?id =3171\n\nhttps://www.oasis-open.org/apps/org/workgroup/votin g/ballot.php?id=3171\n\n \n\n \n\n3- Promotion\n\nWill have good coverage on GALA Boston in March\, as TAPICC Track 2 wi ll be launched\, building on JLIFF\n\n4- AOB\n\n1- Date of n ext meeting\n\n27th Feb look good\, probably cannot make 13t h March (GALA coneference)\, 27th March?\n\n \n\n2- Looking for a new secretary. Contact dF\nGroup: OASIS XLIFF Object M odel 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=41714 UID:https://www.oasis-open.org/apps/org/workgroup/xliff-omos/event.php?event_id=41714 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]