[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, 26 September 2017, 05:00pm to 06:00pm WEST
See the private action item for dial in details
This meeting counts towards voter eligibility.
This is to schedule the whole series, agenda will be posted for individual meetings
1- Roll call
7 Voters total
2- Minutes from the last quorum meeting 2017-07-23
1- XLIFF OM
check the wiki mapping
JLIFF unlike XLIFF has the capability to represent fragments at different logical levels -> need for a wrapper object in JLIFF at the top level
- what has to be on the logical root level?
list: srcLang / trgLang ...srcDir / trgDir .. whitespace handling (how?) more?
Following the OM discussion and the JLIFF capability to represent fragments from different logical levels
Consensus: JLIFF objects and arrays will be always wrapped with a top level object (thus necessarily nameless) indicating jliff version and other global properties of the fragment.
What can be inside / what is valid JLIFF content? :
files --- the top level object corresponds to XLIFF
groups | units --- the top level object corresponds to file
subunits --- the top level object corresponds to file
Issue: if content is units what's the corresponding XLIFF level? Could be group and could be file. This has potential to break roundtrip..
- what has to be on the wrapper level?
list: JLIFF version srcLang / trgLang ...srcDir / trgDir more?
In jliff the root object has no name and carries the global information such as jliff version.
To create JLIFF examples with each possible root.
- Continue discussion on qualified names
dolar sign "$"
- Look at JSON-LD? Use of context, no namespaces, but a way to shorten IRIs
Need to look into a prefix registration mechanism preferably indepnedent on the XLLIFF TC SVN?
The group consenus seems tending to identification of context for modules and registered extensions.
We can control via the registration mechanism that the first _ or : or $ or whatver the consenus is the separator of the qualifier.
Note that this leads to top level "pseudoobject" defining that context that JSON theorists don't seem to like. But we need that the capture the logical top level anyways.
- Using XLIFF 2 test suite to test JLIFF expressivity
wait for XLIFF 2.1 test suite
Ján Husarčík will submit new samples this week
3- TBX Mapping
Report from editorial 1-2-1 meeting [skipping until TC 37 meetings in Vienna late June]
Vienna aftermath report (dF/James)
TBX had good meeting in Vienna, strong consensus allowing for modernization of industry relevant profiles of TBX.
C- Otherr Topics
Where to place work on extraction reference guides? Seems industry want that..
Proposed that as TAPICC track inside Strand 1 Supply Chain Automation
TAPICC does not require GALA Membership. OMOS object model is linked to 2nd and 3rd tracks of TAPICC.
XLIFF TC - XLIFF Version 2.1 will progress to cos01
8th XLIFF Symposium CFP has been extended
The main conference is Nov 1-Nov 3, FEISGILTT will be held on Oct 31-Nov 1, 2017. Save the dates.
1- Date of next meeting
26th Sep, 10th Oct, 14th Nov, 28th Nov, 12th Dec. Which brings us to the end of 2017.
So that means I am also looking into a volunteer to chair 24th Oct, where I will be at tcworld Stuttgart and again unable to chair.
Both OMOS Secretaries had resigned at this point, so I am looking into volunteers for the secretary role.
Also we are looking into a backup maintainer for the OM Github repo
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
This event is part of a series with 13 more events. The next 4 events in this series:
Tuesday, 24 October 2017, 05:00pm to 06:00pm WEST
Tuesday, 28 November 2017, 05:00pm to 06:00pm WET
Tuesday, 26 December 2017, 05:00pm to 06:00pm WET
Tuesday, 23 January 2018, 05:00pm to 06:00pm WET
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:20170926T141916Z DTSTART;VALUE=DATE-TIME;TZID=Europe/Lisbon:20151222T170000 DTEND;VALUE=DATE-TIME;TZID=Europe/Lisbon:20151222T180000 SEQUENCE:10 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:20170926T141916Z ORGANIZER:email@example.com ATTENDEE;CUTYPE=GROUP:MAILTO:firstname.lastname@example.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: This is to schedu le the whole series\, agenda will be posted for individual m eetings\nGroup: OASIS XLIFF Object Model and Other Serializa tions (XLIFF OMOS) TC\nCreator: Dr. David Filip URL:https://www.oasis-open.org/apps/org/workgroup/xliff-omos/event.php?event_id=41676 UID:https://www.oasis-open.org/apps/org/workgroup/xliff-omos/event.php?event_id=41655 RRULE:FREQ=MONTHLY;BYDAY=4TU;COUNT=34 EXDATE;VALUE=DATE-TIME;TZID=Europe/Lisbon:20160126T170000,20160223T170000,20160322T170000,20160524T170000,20160628T170000,20160726T170000,20160823T170000,20160927T170000,20161025T170000,20161122T170000,20161227T170000,20170124T170000,20170228T170000,20170328T170000,20170425T170000,20170523T170000,20170627T170000,20170725T170000,20170822T170000 EXDATE;VALUE=DATE-TIME;TZID=Europe/Lisbon:20160126T170000 EXDATE;VALUE=DATE-TIME;TZID=Europe/Lisbon:20160223T170000 EXDATE;VALUE=DATE-TIME;TZID=Europe/Lisbon:20160322T170000 EXDATE;VALUE=DATE-TIME;TZID=Europe/Lisbon:20160524T170000 EXDATE;VALUE=DATE-TIME;TZID=Europe/Lisbon:20160628T170000 EXDATE;VALUE=DATE-TIME;TZID=Europe/Lisbon:20160726T170000 EXDATE;VALUE=DATE-TIME;TZID=Europe/Lisbon:20160823T170000 EXDATE;VALUE=DATE-TIME;TZID=Europe/Lisbon:20160927T170000 EXDATE;VALUE=DATE-TIME;TZID=Europe/Lisbon:20161025T170000 EXDATE;VALUE=DATE-TIME;TZID=Europe/Lisbon:20161122T170000 EXDATE;VALUE=DATE-TIME;TZID=Europe/Lisbon:20161227T170000 EXDATE;VALUE=DATE-TIME;TZID=Europe/Lisbon:20170124T170000 EXDATE;VALUE=DATE-TIME;TZID=Europe/Lisbon:20170228T170000 EXDATE;VALUE=DATE-TIME;TZID=Europe/Lisbon:20170328T170000 EXDATE;VALUE=DATE-TIME;TZID=Europe/Lisbon:20170425T170000 EXDATE;VALUE=DATE-TIME;TZID=Europe/Lisbon:20170523T170000 EXDATE;VALUE=DATE-TIME;TZID=Europe/Lisbon:20170627T170000 EXDATE;VALUE=DATE-TIME;TZID=Europe/Lisbon:20170725T170000 EXDATE;VALUE=DATE-TIME;TZID=Europe/Lisbon:20170822T170000 BEGIN:VALARM ACTION:DISPLAY DESCRIPTION:REMINDER TRIGGER;RELATED=START:-PT00H15M00S END:VALARM END:VEVENT END:VCALENDAR