[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Cancelled: Exceptional 5th Tuesday XLIFF OMOS meeting
Event Title: Exceptional 5th Tuesday XLIFF OMOS meeting
Date: Tuesday, 30 January 2018, 05:00pm to 06:00pm WET
See the private action item for dial in details
This meeting counts towards voter eligibility.
1- Roll call
aprove/ammend minutes from 23rd Jan 2018
1- XLIFF OM
In connection with finalizing the JLIFF structure with recursive subroups, dF modified the OM wiki
See AI Robert to implement this in JLIFF schema
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. [WIP, extension points?]
AI Robert [WIP]: restated
we have a good structure now, we just need to add subgroups as per previous minutes
subgroups type is the same as subfiles, both subgroups and a subfiles are arrays of oneOf group and unit objects
see discussion of "root types"
AI Chase [pending]: Chase temporarily out, need to fork the context files
make context for 2.0 and 2.1
AI Robert, 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
- Continue discussion on extension points, look at Robert's commit to introduce extension
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 [pending, dependency in XLIFF TC meeting]: 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
3- TBX Mapping
TBX-Basic mapping is in order, almost done on TBXInfo
@James, would you share the dev page, or is it released yet?
C- Other Topics
XLIFF 2.1 had to go for COS02,
Special majority ballot closes tomorrow. Then a two weeks OASIS call for Consent.
Will have good coverage on GALA Boston in March, as TAPICC Track 2 will be launched, building on JLIFF
1- Date of next meeting
Should consider 30 Jan (5th Tue), 13th Feb and 27th Feb look good
2- Looking for a new secretary. Contact dF
- Name is a uri (could be predefined or full external reference – discussing)
raised on XLIFF TC 16th Jan
Owner: Dr. David Filip
Group: OASIS XLIFF Object Model and Other Serializations (XLIFF OMOS) TC
Sharing: This event is not shared to any other groups.
BEGIN:VCALENDAR CALSCALE:GREGORIAN METHOD:CANCEL 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:CANCELLED TRANSP:OPAQUE DTSTAMP:20181129T123203Z DTSTART;VALUE=DATE-TIME;TZID=Europe/Lisbon:20180130T170000 DTEND;VALUE=DATE-TIME;TZID=Europe/Lisbon:20180130T180000 SEQUENCE:17 SUMMARY:Exceptional 5th Tuesday XLIFF OMOS meeting (CANCELLED) LAST-MODIFIED:20181129T123203Z ORGANIZER:firstname.lastname@example.org ATTENDEE;CUTYPE=GROUP:MAILTO:email@example.com URL:https://www.oasis-open.org/apps/org/workgroup/xliff-omos/event.php?event_id=47010 UID:https://www.oasis-open.org/apps/org/workgroup/xliff-omos/event.php?event_id=47010 END:VEVENT END:VCALENDAR