Uncancelled: Exceptional 5th Tuesday XLIFF OMOS meeting

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:20181023T140929Z
DTSTART;VALUE=DATE-TIME;TZID=Europe/Lisbon:20181030T170000
DTEND;VALUE=DATE-TIME;TZID=Europe/Lisbon:20181030T180000
SEQUENCE:17
SUMMARY:Exceptional 5th Tuesday XLIFF OMOS meeting
LOCATION:https://www.oasis-open.org/apps/org/workgroup/xliff-omos/mem
 bers/action_item.php?action_item_id=3822
LAST-MODIFIED:20181023T140929Z
ORGANIZER:
ATTENDEE;CUTYPE=GROUP:MAILTO:
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: Agenda\n\n \n\n \
 n\nA. Admin\n\n1- Roll call\n\naprove/ammend minutes from 23
 rd Jan 2018\n\nhttps://www.oasis-open.org/apps/org/workgroup
 /xliff-omos/email/archives/201801/msg00003.html\n\nB. Materi
 al\n\n1- XLIFF OM\n\nIn connection with finalizing the JLIFF
  structure with recursive subroups\, dF modified the OM wiki
 \n\nhttps://github.com/oasis-tcs/xliff-omos-om/wiki\n\nSee A
 I Robert to implement this in JLIFF schema\n\n2- JLIFF\n\n(h
 ttps://github.com/oasis-tcs/xliff-omos-jliff)\n\nPrevious Co
 nsensus: restated\n\nDON&#39\;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 instance
 s\, to prevent hammering of the context file.\n\nExtensions 
 always need to declare or reference their context inline. [W
 IP\, extension points?]\n\nAI Robert [WIP]:  restated\n\nwe 
 have a good structure now\, we just need to add subgroups as
  per previous minutes\n\nsubgroups type is the same as subfi
 les\, both subgroups and a subfiles are arrays of oneOf grou
 p and unit objects\n\nsee discussion of &quot\;root types&qu
 ot\;\n\nhttp://markmail.org/thread/75n3r6sxrbzohgkk\n\nAI Ch
 ase [pending]: Chase temporarily out\, need to fork the cont
 ext files\n\nmake context for 2.0 and 2.1\n\nAI Robert\, imp
 lement meeting consenus for extension points. Extension data
  needs to start with context. Each extension will be one obj
 ect. Try to allow them only where they&#39\;re allowed in XL
 IFF\n\n- Continue discussion on extension points\, look at R
 obert&#39\;s commit to introduce extension\n\nhttps://github
 .com/oasis-tcs/xliff-omos-jliff/commit/85e7c3e0e8d88539df5b2
 eb7519d6735f84256e9\n\n There are several places where conte
 xt 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 possible..\n\nWe a
 lso agreed that having a dedicated extension container is mo
 re validation friendly than just allowing additional propert
 ies on the root structure..\n\n-Continue discussing pros and
  cons of the extensionsData approach\n\ncompare with XML and
  consider going back and forth between XML and JSON.\n\nAI d
 F and Yves [pending\, dependency in XLIFF TC meeting]: clear
  usage of XLIFF prefix registration mechanism for JLIFF\, re
 quest that XLIFF prefixes don&#39\;t use colon &quot\;:&quot
 \;\n\nraised on XLIFF TC 16th Jan\n\nDONE in principle\, som
 e minor fixes pending\n\nhttp://markmail.org/thread/qmvyp4yu
 ihx76g6r\n\n \n\n3- TBX Mapping\n\nTBX-Basic mapping is in o
 rder\, almost done on TBXInfo\n\n@James\, would you share th
 e dev page\, or is it released yet?\n\nC- Other Topics\n\n2-
  Liaisons\n\nXLIFF 2.1 had to go for COS02\, \n\nhttps://www
 .oasis-open.org/committees/ballot.php?id=3166\n\nSpecial maj
 ority ballot closes tomorrow. Then a two weeks OASIS call fo
 r Consent.\n\n3- Promotion\n\nWill have good coverage on GAL
 A Boston in March\, as TAPICC Track 2 will be launched\, bui
 lding on JLIFF\n\n4- AOB\n\n1- Date of next meeting\n\nShoul
 d consider 30 Jan (5th Tue)\, 13th Feb and 27th Feb look goo
 d\n\n2- Looking for a new secretary. Contact dF\n\n \n\n\nMi
 nutes\n\nA. Admin\n\n1- Roll call\n\n? out of 5 voters\n\nap
 rove minutes from 9th Jan 2018\n\nhttp://markmail.org/thread
 /ohzqaonhfdvqenml\n\napproved by CFD\n\nB. Material\n\n1- XL
 IFF OM\n\nIn connection with finalizing the JLIFF structure 
 with recursive subroups\, dF modified the OM wiki\n\nhttps:/
 /github.com/oasis-tcs/xliff-omos-om/wiki\n\nSee AI Robert to
  implement this in JLIFF schema\n\n2- JLIFF\n\n(https://gith
 ub.com/oasis-tcs/xliff-omos-jliff)\n\nPrevious Consensus: re
 stated\n\nDON&#39\;T reference the context file [for core an
 d module] from schema or instances. This is tied via the spe
 c [driven by version number] but not the instances\, to prev
 ent hammering of the context file.\n\nExtensions always need
  to declare or reference their context inline.\n\nAI Robert 
 [DONE]\, implement meeting consenus for extension points. Ex
 tension data needs to start with context. Each extension wil
 l be one object. Try to allow them only where they&#39\;re a
 llowed in XLIFF\n\nreviewed &quot\;element&quot\; extension 
 points implemented as has map rather than an array in the la
 test commit https://github.com/oasis-tcs/xliff-omos-jliff/co
 mmit/85e7c3e0e8d88539df5b2eb7519d6735f84256e9\n\nDiscuss:\n\
 nUse URI type of context or not?\n\nAI Robert [DONE]:  To be
  reviewed\n\nwe have a good structure now\, we just need to 
 add subgroups as per previous minutes\n\nRobert hesitant to 
 add subgroups for lack of semantic difference. Discussed tha
 t offline with Cahse two weeks ago. Chase also thought that 
 subgroups were unnecessary. \n\nsee discussion of &quot\;roo
 t types&quot\;\n\nhttp://markmail.org/thread/75n3r6sxrbzohgk
 k\n\nThe distinction between subgroups and subfiles is impor
 tant for representing all possible root levels as well as en
 suring interoperability\, the original design was a property
  indicating the type of root. But the discussion ensued in t
 he structural proposal that was more automation friendly. In
  general either the root type property or the strutural diff
 erence between subfiles and subgoups are needed to preserve 
 the LIOM fragment level when exchanging between technologies
 .  \n\ndF explained the difference between subfiles and subg
 roups. sublfiles are always top level\, while subgroups can 
 be not only in subfiles but also in other subgroups.\n\nRobe
 rt agreed to implement and document that\, so that we don&#3
 9\;t keep returning to the issue.\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\n \n\n- Continue discussion on extension points\
 , look at Robert&#39\;s commit to introduce extension\n\nhtt
 ps://github.com/oasis-tcs/xliff-omos-jliff/commit/85e7c3e0e8
 d88539df5b2eb7519d6735f84256e9\n\n There are several places 
 where context can be provided: root\, or units\, files\, gro
 ups. \n\n  (Whether @context should be at root or only lower
  levels).\n\nShould mimic XLIFF behavior as close as possibl
 e..\n\nWe also agreed that having a dedicated extension cont
 ainer is more validation friendly than just allowing additio
 nal properties on the root structure..\n\n-Continue discussi
 ng pros and cons of the extensionsData approach\n\ncompare w
 ith XML and consider going back and forth between XML and JS
 ON.\n\nAI dF and Yves [DONE]: clear usage of XLIFF prefix re
 gistration mechanism for JLIFF\, request that XLIFF prefixes
  don&#39\;t use colon &quot\;:&quot\;\n\nraised on XLIFF TC 
 16th Jan\n\nDONE in principle\, some minor fixes pending\, e
 .g. FAQ\n\nhttp://markmail.org/thread/qmvyp4yuihx76g6r\n\n \
 n\n3- TBX Mapping\n\nTBX-Basic mapping is in order\, almost 
 done on TBXInfo\n\n@James\, would you share the dev page\, o
 r is it released yet?\n\nC- Other Topics\n\n2- Liaisons\n\nX
 LIFF 2.1 had to go for COS02 -&gt\; OS Progress \n\n3- Promo
 tion\n\nWill have good coverage on GALA Boston in March\, as
  TAPICC Track 2 will be launched\, building on JLIFF\n\n4- A
 OB\n\n1- Date of next meeting\n\n13th Feb and 27th Feb look 
 good\n\n \n\n2- Looking for a new secretary. Contact dF\n\n 
 \nGroup: OASIS XLIFF Object Model 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=47019
UID:https://www.oasis-open.org/apps/org/workgroup/xliff-omos/event.php?event_id=47019
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT00H15M00S
END:VALARM
END:VEVENT
END:VCALENDAR