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
==========
Agenda:
A. Admin
1- Roll call
6 Voters total
aprove minutes from 12th Dec 2017
https://www.oasis-open.org/apps/org/workgroup/xliff-omos/email/archives/201712/msg00009.html
B. Material
1- XLIFF OM
(https://github.com/oasis-tcs/xliff-omos-om)
dF made some progress on prose
discussion on unsuported modules and extensions
http://markmail.org/thread/dw3equt7ae57h6xb
AI: Define requirements for crossing the XML/JSON boundary
In connection with finalizing the JLIFF structure with recursive subroups, dF modified the OM wiki
https://github.com/oasis-tcs/xliff-omos-om/wiki
2- JLIFF
(https://github.com/oasis-tcs/xliff-omos-jliff)
AI Chase [done]: commit the context file
xliff-omos-jliff/JLIFF-schema-draft/jliff-0.9.4.jsonld
Previous Consensus:
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]:
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 dsicussion of "root types"
http://markmail.org/thread/75n3r6sxrbzohgkk
AI Chase [pending]:
make context for 2.0 and 2.1
Discussion on extension points:
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..
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 ":"
Will try and address that on XLIFF TC 19th Dec.
[no time in that meeting]
3- TBX Mapping
Report from editorial 1-2-1 meeting [skipping until January 2018]
current editor's draft: https://tools.oasis-open.org/version-control/browse/wsvn/xliff-omos/trunk/XLIFF-TBX/xliff-tbx-v1.0.pdf
TBX-Basic mapping
C- Other Topics
2- Liaisons
New Extraction / Merge examples via TAPICC
https://github.com/GALAglobal/TAPICC/tree/master/extraction_examples
need bdi and bdo extraction examples
Traget to provide technically stable JLIFF 1.0 by GALA Boston March 2018.
XLIFF Version 2.1 COS01 review until 19th December 2017
http://bit.ly/XLIFF21COS01
3- Promotion
???
4- AOB
1- Date of next meeting
[skip Dec 26], 9th Jan 2018 and so on..
2- Looking for a new secretary. Contact dF
==========
Minutes:
A. Admin
1- Roll call
6 Voters total
Phil, Robert, Yves, dF
Steve - gained voting rights at the end of the meeting
aproved minutes from 12th Dec 2017 by CFD
https://www.oasis-open.org/apps/org/workgroup/xliff-omos/email/archives/201712/msg00009.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
2- JLIFF
(https://github.com/oasis-tcs/xliff-omos-jliff)
AI Chase [done]: commit the context file
xliff-omos-jliff/JLIFF-schema-draft/jliff-0.9.4.jsonld
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]:
make context for 2.0 and 2.1
Discussion on extension points:
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..
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
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 ":"
Will try and address that on XLIFF TC 16th Jan.
3- TBX Mapping
Skippe as James missing
TBX-Basic mapping is in order, almost done on TBXInfo
C- Other Topics
2- Liaisons
XLIFF 2.1 will have to go for COS02
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
23rd Jan looks good
2- Looking for a new secretary. Contact dF
Meeting adjourned
==========
Attendance:
| Meeting Statistics |
| Quorum rule |
51% of voting members
|
| Achieved quorum |
yes |
| Individual Attendance |
Contributing Members: 5 of 20 (25%)
Voting Members: 5 of 7 (71%) (used for quorum calculation)
|
| Company Attendance |
Contributing Companies: 5 of 15 (33%)
Voting Companies: 5 of 7 (71%)
|