[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Modified: XLIFF TC Meeting
|
Event Title: XLIFF TC Meeting Date: Tuesday, 21 April 2015, 11:00am to 12:00pm EDT Description Unable to access action item from KAVI Sunday night - will upate when KAVI is back up. This meeting counts towards voter eligibility. Agenda I Administration (0:00 - 0:10) (* indicates new since last meeting) IV Current and New Business (0:55 - ) Minutes I Administration (0:00 - 0:10) Present: [13 members] Tom Comerford, Fredrik Estreen, DavidF Filip, Ryan King, Lucía Morado, Yves Savourel, Bryan Schnabel, Joachim Schurig, Uwe Stahlschmidt, DavidW Walters, Asanka Wasala, Soroush Saadatfar, Michael Ow, [Ryan King regained Voting rights at the end of the meeting] Quorum achieved: 11 out 11 voters present B. Approve meeting minutes, 17 March 2015 AI Bryan to post F2F logistics on wiki [DONE: https://wiki.oasis-open.org/xliff/F2F2015] [Pending AI dF] https://www.oasis-open.org/apps/org/workgroup/xliff/email/archives/201504/msg00008.html [Fredrik discussed ITS Storage Restriction Data category mapping in XLIFF 2.1 based on the above] Some points: ITS assumes/allows mixed encodings, this necessitates a particular design in XLIFF that is always one encoding. Technically all agents supporting this category should be able to support *ANY* encoding In order to determine storage restrictions with inline codes, it will be non-normatively advised that extractors store all native data in <data>. Otherwise slr agents wouldn’t be able to calculate the restriction. dF: Would be happy to have this a normative SHOULD Fredrik: This should be strictly informative. ITS storage should not normatively affect behavior of Extractors, even with a SHOULD dF: That’s fine, but if it’s informative and I agree it should be only informative, maybe a Warning. But in that case you must not use the normative keywords (SHOULD, RECOMMEND) it would be confusing to the user. AI Fredrik, implement the proposal to spec. Fredrik, this is in progrees I already have it Docbook, I will make sure not to use normative keywords in non-normaive advise. dF: That’s OK, I will review it for normative language once on SVN N. Mistakes in the spec (Soroush) [Peneding AI dF] Register for 6th Symposium http://www.locworld.com/register-for-feisgiltt-2015/ 6th XLIFF Symposium and 4th FEISGILTT Program http://www.locworld.com/feisgiltt-program/
New questionnaire still in progress dF: We should discuss option for where to place work on non-XML serializations, Wed FEISGILTT will have a panel on OM and non-XML serializations of XLIFF. But also in the F2F we should discuss this, as one option is to re-charter the XLIFF TC. Either way there will be impact on TC work. Owner: Bryan Schnabel Group: OASIS XML Localisation Interchange File Format (XLIFF) TC Sharing: This event is shared with the OASIS Open (General Membership), and General Public groups. Public Event Link
Microsoft Outlook users: You will see event notifications requiring further
action in your Outlook mail application. |
Attachment:
ical_40298.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:America/New_York BEGIN:STANDARD DTSTART:20001029T020000 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T060000Z TZNAME:EST TZOFFSETFROM:-0400 TZOFFSETTO:-0500 END:STANDARD BEGIN:STANDARD DTSTART:20071104T020000 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:EST TZOFFSETFROM:-0400 TZOFFSETTO:-0500 END:STANDARD BEGIN:DAYLIGHT DTSTART:20000402T020000 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T070000Z TZNAME:EDT TZOFFSETFROM:-0500 TZOFFSETTO:-0400 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:20070311T020000 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:EDT TZOFFSETFROM:-0500 TZOFFSETTO:-0400 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT STATUS:CONFIRMED TRANSP:OPAQUE DTSTAMP:20150519T120502Z DTSTART;VALUE=DATE-TIME;TZID=America/New_York:20150421T110000 DTEND;VALUE=DATE-TIME;TZID=America/New_York:20150421T120000 SEQUENCE:1 SUMMARY:XLIFF TC Meeting LAST-MODIFIED:20150519T120502Z ORGANIZER:workgroup_mailer@lists.oasis-open.org DESCRIPTION:Unable to access action item from KAVI Sunday night - will u pate when KAVI is back up.\n\nAgenda: I Administration (0:00 - 0:10)\n A. Roll call\n B. Approve meeting minutes\, 7 A pril 2015\n url not yet available - will add it here\n C. Revise schedule for XLIFF 2.1 \n https://lists.oas is-open.org/archives/xliff/201406/msg00001.html\n\n(* indica tes new since last meeting)\nII XLIFF 2.1 (0:10 - 0:45)\n K . Add N Constraint to the core order attribute\n DF will make a CFD for this on mailing list. This has been now suff iciently discussed.\n G. Template/Model for TBX Mapping wit h XLIFF v2.0 and Higher Version 1.0 (DavidF)\n https://l ists.oasis-open.org/archives/xliff/201411/msg00091.html\n Resolution: DavidF is in touch with stakeholders\; expect completion soon.\n L. ITS storage size restriction\n Fr edrik to propose slr profile for ITS storage size data categ ory\n N. Mistakes in the spec (Soroush)\n https://lists .oasis-open.org/archives/xliff/201502/msg00009.html\n 0. *N VDL for the core is updated (Soroush)\n https://lists.oa sis-open.org/archives/xliff/201503/msg00009.html\nIII Sub Co mmittee Report (0:45 - 0:55)\n\nIV Current and New Business (0:55 - )\nGroup: OASIS XML Localisation Interchange File F ormat (XLIFF) TC\nCreator: Bryan Schnabel URL:https://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=40298 UID:https://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=40298 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]