OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff-omos message

[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 October 2018, 05:00pm to 06:00pm WET
Location: https://www.oasis-open.org/apps/org/workgroup/xliff-omos/members/action_item.php?action_item_id=3822
Description

See the private action item for dial in details

https://www.oasis-open.org/apps/org/workgroup/xliff-omos/members/action_item.php?action_item_id=3822


RSVP
This meeting counts towards voter eligibility.

Agenda

Agenda

 

 

A. Admin

1- Roll call

aprove/ammend minutes from 23rd Jan 2018

https://www.oasis-open.org/apps/org/workgroup/xliff-omos/email/archives/201801/msg00003.html

B. Material

1- XLIFF OM

In connection with finalizing the JLIFF structure with recursive subroups, dF modified the OM wiki

https://github.com/oasis-tcs/xliff-omos-om/wiki

See AI Robert to implement this in JLIFF schema

2- JLIFF

(https://github.com/oasis-tcs/xliff-omos-jliff)

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"

http://markmail.org/thread/75n3r6sxrbzohgkk

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

https://github.com/oasis-tcs/xliff-omos-jliff/commit/85e7c3e0e8d88539df5b2eb7519d6735f84256e9

 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

http://markmail.org/thread/qmvyp4yuihx76g6r

 

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

2- Liaisons

XLIFF 2.1 had to go for COS02, 

https://www.oasis-open.org/committees/ballot.php?id=3166

Special majority ballot closes tomorrow. Then a two weeks OASIS call for Consent.

3- Promotion

Will have good coverage on GALA Boston in March, as TAPICC Track 2 will be launched, building on JLIFF

4- AOB

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

 


Minutes

A. Admin

1- Roll call

? out of 5 voters

aprove minutes from 9th Jan 2018

http://markmail.org/thread/ohzqaonhfdvqenml

approved by CFD

B. Material

1- XLIFF OM

In connection with finalizing the JLIFF structure with recursive subroups, dF modified the OM wiki

https://github.com/oasis-tcs/xliff-omos-om/wiki

See AI Robert to implement this in JLIFF schema

2- JLIFF

(https://github.com/oasis-tcs/xliff-omos-jliff)

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.

AI Robert [DONE], 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

reviewed "element" extension points implemented as has map rather than an array in the latest commit https://github.com/oasis-tcs/xliff-omos-jliff/commit/85e7c3e0e8d88539df5b2eb7519d6735f84256e9

Discuss:

Use URI type of context or not?

AI Robert [DONE]:  To be reviewed

we have a good structure now, we just need to add subgroups as per previous minutes

Robert hesitant to add subgroups for lack of semantic difference. Discussed that offline with Cahse two weeks ago. Chase also thought that subgroups were unnecessary. 

see discussion of "root types"

http://markmail.org/thread/75n3r6sxrbzohgkk

The distinction between subgroups and subfiles is important for representing all possible root levels as well as ensuring interoperability, the original design was a property indicating the type of root. But the discussion ensued in the structural proposal that was more automation friendly. In general either the root type property or the strutural difference between subfiles and subgoups are needed to preserve the LIOM fragment level when exchanging between technologies.  

dF explained the difference between subfiles and subgroups. sublfiles are always top level, while subgroups can be not only in subfiles but also in other subgroups.

Robert agreed to implement and document that, so that we don't keep returning to the issue.

 

make context for 2.0 and 2.1

dF AI to make a PR for forking the 2.0 and 2.1 contexts

 

- Continue discussion on extension points, look at Robert's commit to introduce extension

https://github.com/oasis-tcs/xliff-omos-jliff/commit/85e7c3e0e8d88539df5b2eb7519d6735f84256e9

 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 [DONE]: 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, e.g. FAQ

http://markmail.org/thread/qmvyp4yuihx76g6r

 

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

2- Liaisons

XLIFF 2.1 had to go for COS02 -> OS Progress 

3- Promotion

Will have good coverage on GALA Boston in March, as TAPICC Track 2 will be launched, building on JLIFF

4- AOB

1- Date of next meeting

13th Feb and 27th Feb look good

 

2- Looking for a new secretary. Contact dF

 



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
  • Learn more about subscribing here.
  • View the OASIS XLIFF Object Model and Other Serializations (XLIFF OMOS) TC calendar here.
  • You may receive future notifications with updates to this event. Update the event on your calendar by accepting the changes.

Attachment: ical_47019.ics
Description: application/ics

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:20181023T140928Z
DTSTART;VALUE=DATE-TIME;TZID=Europe/Lisbon:20181030T170000
DTEND;VALUE=DATE-TIME;TZID=Europe/Lisbon:20181030T180000
SEQUENCE:16
SUMMARY:Exceptional 5th Tuesday XLIFF OMOS meeting (CANCELLED)
LAST-MODIFIED:20181023T140928Z
ORGANIZER:workgroup_mailer@lists.oasis-open.org
ATTENDEE;CUTYPE=GROUP:MAILTO:xliff-omos@lists.oasis-open.org
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=47010
RECURRENCE-ID;VALUE=DATE-TIME;TZID=Europe/Lisbon:20181030T170000
END:VEVENT
END:VCALENDAR


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]