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:20180410T174019Z
DTSTART;VALUE=DATE-TIME;TZID=Europe/Lisbon:20180410T170000
DTEND;VALUE=DATE-TIME;TZID=Europe/Lisbon:20180410T180000
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:20180410T174019Z
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: A. Admin\n\n1- Ro
ll call\n\n? out of 5 voters\n\naprove minutes from 27th Mar
ch 2018\n\nhttps://www.oasis-open.org/apps/org/workgroup/xli
ff-omos/email/archives/201803/msg00016.html\n\n \n\n \n\nB.
Material\n\n1- XLIFF OM\n\nOM wiki needs aligned with curren
t JLIFF structure as per 0.9.5\n\nhttps://github.com/oasis-t
cs/xliff-omos-om/wiki\n\n \n\n2- JLIFF\n\n(https://github.co
m/oasis-tcs/xliff-omos-jliff)\n\n \n\nDiscuss pros & cons of
boolean vs a yes/no enumeration\n\n \n\nAI Robert\n\nExpres
s all XLIFF 2.1 and 2.0 modules in JLIFF schema. Have 2.1 an
d 2.0 branches\n\n*[Review progress]*\n\nPrevious Consensus:
restated\n\nWe agreed to work on 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 instance
s\, to prevent 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. Extension data needs to start with context. Each ex
tension will be one object. Try to allow them only where the
y'\;re allowed in XLIFF\n\nreviewed "\;element"\;
extension points implemented as has map rather than an arra
y in the latest commit https://github.com/oasis-tcs/xliff-om
os-jliff/commit/85e7c3e0e8d88539df5b2eb7519d6735f84256e9\n\n
\n\nDiscuss:\n\nUse URI type of context or not?\n\n- Contin
ue discussion on extension points\, look at Robert'\;s co
mmit to introduce extension\n\nhttps://github.com/oasis-tcs/
xliff-omos-jliff/commit/85e7c3e0e8d88539df5b2eb7519d6735f842
56e9\n\n There are several places where context can be provi
ded: root\, or units\, files\, groups. \n\n (Whether @conte
xt should be at root or only lower levels).\n\nShould mimic
XLIFF behavior as close as possible..\n\nWe also agreed that
having a dedicated extension container is more validation f
riendly than just allowing additional properties on the root
structure..\n\n-Continue discussing pros and cons of the ex
tensionsData approach\n\ncompare with XML and consider going
back and forth between XML and JSON.\n\n3- TBX Mapping\n\nT
BX-Basic mapping is in order\, almost done on TBXInfo\n\nUpd
ate?\n\nC- Other Topics\n\n2- Liaisons\n\nXLIFF\n\nTAPICC -
Track 2\n\n \n\n3- Promotion\n\nHad good coverage on GALA Bo
ston in March\, as TAPICC Track 2 was launched\, building on
JLIFF\n\nAlso Phil JLIFF library open sourcing was announce
d in the GALA week \n\nhttps://twitter.com/VistatecGlobal/st
atus/974538466565373952\n\nhttps://twitter.com/merzbauer/sta
tus/974288543093854208\n\n4- AOB\n\n1- Date of next meeting\
n\n22nd May\n\n2- Looking for a new secretary. Contact dF\nG
roup: OASIS XLIFF Object Model and Other Serializations (XLI
FF OMOS) TC\nCreator: Dr. David Filip
URL:https://www.oasis-open.org/apps/org/workgroup/xliff-omos/event.php?event_id=41716
UID:https://www.oasis-open.org/apps/org/workgroup/xliff-omos/event.php?event_id=41716
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT00H15M00S
END:VALARM
END:VEVENT
END:VCALENDAR