OASIS Open

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

phil (minutes), yves, steven, robert, james, david
A Admin
Roll call 5 voters
approve minutes from 13th Feb

https://www.oasis-open.org/apps/org/workgroup/xliff-omos/email/archives/201802/msg00004.html.
rve: second minutes.
B Material
XLIFF OM
JLIFF
df: make 2.1 the primary branch ...walk us through changes
rve: had a conversation about schema to include modules not yet included: glossary and metadata in 0.95 ...3 modules remaining ...this version should conform to xliff 2.1 ...this is mostly based on 2.0 ...I matched the xliff descriptions and schema ...schema constraints are included as far as possible ...the schema constrains are pretty much equal to the xliff constraints ...in one case: matches the prefix is meaningless ...if we go the direction to use qualified modules then context has to be discussed ...changetrack and resourcedata ...for modules we could leave out namespaces ...we see prefixes within data of mrk
df: some attributes allow custom types
rve: basically not a QNAME | resolution mechanism? ...that's good news
df: the context files should match the different xliff versions with respect to the namespaces they include ...you should create 2.1 branch before changing the context file
rve: OK I will add the other modules ...new to add validation
df: sizerestriction is a complex one
rve: yes it will take more effort ...but not impossible
sl: not all validation can be done in the schema
df: in 2.0 we introduced a distinction between what is in processing requirements and constraints as opposed to the definitions that are all covered in the schema
sl: OK I see the distinction ...for jliff the intent is to keep the boundary the same?
df: so far we did not encounter any issues, everything was expressible in the schema ...in 2.1 we added schematron which is more powerful ...so jliff may also have custom validation ...good thing is you can use schematron 2.1 to validate xliff 2.0 ...segmentation has a lot of processing requirements
pr: I added more complete examples to my test suite ...based on xliff examples in yves xliff-lib project ...my code does lack the ability to translate between xliff and jliff and back ...I have done some experiments that haven't been very successful
ys: we did some work on a branch of the xliff-library ...we ran out of time to commit to the project ...acorn was teh basis for that
df: you also did work on representing its in json?
ys: yes but again work has not progressed ...it does some stuff but probably doesn't match the 0.95 schema
df: we want to see people in TAPICC using jliff ...we have a chance to generate some interest ...we should socialize the latest git branch with the TAPICC group
sl: I think there would be interest in extract|merge directly to jliff ...some workflows may only use jliff
df: we haven't really thought about it so far but it is interesting
ys: instead of concentrating on the format we should focus on the object model

dF: need to beef up the OM work it's currently only me
sl: I might be using jliff as a store
TBX Mapping
jh: TBX is currently out for ballot ...it should be really stable at this point ...I already made tag name changes ...TBX has two styles ...the mapping only currently addresses attributes mapping method

dF: let's add the tag style too and review the progress in 1-2-1 before the next meeting

jh: sure let's do that
C Other Topics
Liaisons
Promotion
AOB

Skipping 13th becuase of the GALA conference

Next meeting 27th March 2018 (phil will be travelling) dF and James to meet an hour ahead to discuss TBX mapping progress

A. Admin

1- Roll call

? out of 5 voters

aprove minutes from 13th Feb 2018

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

B. Material

1- XLIFF OM

OM wiki needs aligned with current JLIFF structure as per 0.9.5

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

2- JLIFF

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

Previous Consensus: restated

We agreed to work on 2.1 branch first and only then fork the 2.0

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?

make context for 2.0 and 2.1

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

https://github.com/oasis-tcs/xliff-omos-jliff/pull/5

[DONE, merged] 

- 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 walk us through the TBX Basic changes?

C- Other Topics

2- Liaisons

OS ballot closes today 23:59 UTC

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

https://www.oasis-open.org/apps/org/workgroup/voting/ballot.php?id=3171

3- Promotion

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

4- AOB

1- Date of next meeting

Will skip 13th March (GALA coneference), 27th March?

2- Looking for a new secretary. Contact dF

• OASIS Open (General Membership)
• General Public