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

Submitter's message
no need for the 3rd meeting in January
-- Dr. David Filip
Event Title: Exceptional 5th Tuesday XLIFF OMOS meeting
Date: Tuesday, 30 January 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


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
aprove/amend minutes from 23rd Jan 2018
https://www.oasis-open.org/apps/org/workgroup/xliff- omos/email/archives/201801/msg00003.html
Approved
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"
Robert created groups and subgroups (committed) – commit 6e10946
Q SRL: is the version 0.9.4 recent or long standing?
A: Robert: long standing.
Robert: subfiles renamed to subgroups, user renamed to userdata.
David: Could make 0.9.5 as a copy of this, and then make incremental changes.
(This was Agreed) AI Robert


• Discussing extension points

- Name is a uri (could be predefined or full external reference – discussing)
- Content is an object (any content)
- Prior discussion is to remove the external URI and always require any custom
context to be inline
- AI: Robert will remove external schema from 0.9.5 ( from JSON-LD- context )
-
- Q:Should the top level JLIFF object allow better extensibility with top level userData?
- Issue is that JSON does not distinguish between attribute and element – adding
‘flexible element’ or ‘flexible attribute’ is the same thing at the top.
- Could add userData at the root level of JLIFF
- Have something at the file level, but may want the top level to have a container which
has specified semantics
- “userMetaData” since it is top level? Map to primitive values.
- XLIFF inline model currently has extensibility for modules but not arbitrary extensions –
constrained to the specific module namespaces (slr and fs). but annotation markers are extensible with arbitrary attributes as weel as user defined values.
- Discussing constraint on metadata
- Constraint on declaration on URI? (formal vs. operational constraints)
- URIs are fixed in the spec, not to be resolved at runtime – using URNs (mostly, except for W3C ITS)
- Could the prefixes be fixed (enumerated- "fs" and "slr")
- …
- Could be a regex to define property.
-

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 [done for element extensibility]
- 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 userData 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
http://markmail.org/thread/qmvyp4yuihx76g6r
 
3- TBX Mapping
TBX-Basic mapping is in order, almost done on TBXInfo

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 Tracks 2 and 3 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 not shared to any other groups.
  • 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_47010.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: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: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=47010
UID:https://www.oasis-open.org/apps/org/workgroup/xliff-omos/event.php?event_id=47010
END:VEVENT
END:VCALENDAR

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