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

A. Admin

1- Roll call

Attendees: David, Phil, Robert, Chase, James, Soroush

Quorum reached with 6 out of 8 voters

2- Minutes from the last meeting 24 Jan 2017 

dF: I move that the following link is the official minutes of record for our previous meeting:

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

Robert: I second.

[no dissent]

dF: minutes approved

B. Material

1- XLIFF OM

dF: No progress due to XML Prague attendance, we can leave this item for the next meeting.

2- JLIFF

Robert: I did a basic a draft of JLIFF with some suggestions, however the work is still ongoing (the appliesTo property still not there for instance). Since keys [ids] define a different concept in JSON, they are represented by meta value pairs which can be now validated and is syntactically correct. We have it now in the updated schema and the examples can be validated against it. My suggestions on the following work would be to keep using “fragment” and also to define few default values for some of the properties and fields. Although, the issues around namespaces are unsolved. 

dF: We could go around it in JLIFF and define a Core and several metagroups, where the groups with freely created (not predefined) names serve as the generic extensibility mechanism and modules simply are those with predefined names and syntax

Chase: That might work. With metagroup embedded in JLIFF, module namespaces could be represented as keys, but isolation is the disadvantage, on the other hand. 

dF: It should at least work for simple modules like FS. But the real test will be express something as complex as SLR.

Chase: Maybe. I think the most valuable modules for us to concentrate is CTR, SLR and MTC.

dF: Since CTR and MTC use Core fields, they might be easier than SLR. Overall, a generic metacontainer for anything extended from Core could work. But it’s important to remember that modules, as standardized extensions, must be distinguished from generic extensions.

Robert: I think some more examples would help us to clear the way.

Chase: I agree, the next step is to use modules in examples, maybe the GLS. Phil and I have some ongoing discussion from the implementation perspective with the current focus on iterate core content and examining if they can handle polymorphism (segments and ignorables). We’re trying to streamline them to get rid of nested objects and also to have the result more JSON-like. I will report to the TC on our collaboration.

dF: Thank you all for the great progress and work. You can also have the conversations on the mailing list and have them thus captured on the persistent archive. Overall, we're definitely in the right direction. WRT the last issue of this topic, are we happy with the JLIFF acronym to be expanded as JSON Localization Interchange *Fragment* Format?

Chase: I think we should consider use cases here. I feel like it would be equally likely for fragment data to be passed within one or multiple units. On the other hand, we have a very limited metadata available at file level. It is more of a branding question and I am fine with it.

dF: We should consider both use case and logic of the inheritance in the data model. JSON would not represent the entire spectrum of use cases (like sending hundresds or hundreds of thousands of DITA topics in one big XLIFF file) and our main purpose is to represent unit. So, if no objections, it’s approved.

[no dissent]

3- TBX Mapping

dF: We just had a meeting with James before the TC meeting and did some progress on the mapping. We will continue our meetings regularly on the meeting day and keep reporting to the TC. I will be printing just in time for the meeting.

C. Other Topics

1- Date of next meeting

dF: If it is fine with everyone, we will hold our next meeting on Feb 28th 2017. I was in contact with Patrik and he might be able to return from his LOA shortly.

[short discussion if the time of the meeting could move earlier as of April to accommodate Patrik, this didn't seem to work for Chase]

2- Liaisons

dF: GALA TAPICC - officially launched last week under BSD 3-clause and CC-BY 2.0

(https://www.gala-global.org/sites/default/files/GALA%20TAPICC%20Project%20Charter.pdf)

Chase: I am interested in it and they need information and material from us WRT JLIFF and OM. Should I approach Klaus Fleischmann proactively?

dF: WRT TBX Steering Committee / ISO TC37/SC3, the first darft international standard is submitted now. The ISO publication probably to be expected in late 2017.

dF: Thanks to Chet the XLIFF 2.1 CSPRD02 launched on 10th February and will end by 25th February.

(https://www.oasis-open.org/news/announcements/public-review-for-xliff-v2-1-ends-february-24th,

http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd02/xliff-core-v2.1-csprd02.htmlv). You can review how each of the 20 issues of the 1st review resolved (https://issues.oasis-open.org/browse/XLIFF-14?jql=project%20%3D%20XLIFF%20AND%20status%20%3D%20Closed%20ORDER%20BY%20priority%20DESC). You can also subscribe to the comment list (https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=xliff) and send comments even if you’re not a member. You also may follow the CTR discussion (https://issues.oasis-open.org/browse/XLIFF-4)

3- Promotion

dF: Last week at XML Prague we announced the XLIFF 2.1 csprd02 and also mentioned the OMOS work on OM and JLIFF.

dF: We are considering to hold the next XLIFF Symposium in Barcelona in June or Silicon Vally in Nov. XLIFF TC members more inclined to the November event.

Chase, Robert: It would also be better and easier for us and American-based people to attend the one in November.

dF: also more comfortable wrt timing, so let's shoot for Nov Silicon Valley.

4- AOB

dF: If nothing to add, the meeting is adjourned. I hope to see you all in Silicon Valley in November and talk to you again on 28th Feb. 

A. Admin

1- Roll call

8 voters

5 needed for quorum

2- Minutes from the last meeting, 24 Jan 2017 

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

B. Material

1- XLIFF OM

modularity and extensions

2- JLIFF

- Decision on how to "officially" expand JLIFF

JSON Loclization Interchange *Fragment* Format

- Modularity and extensibility expressed in JSON

    - Idea from last time: use the mda method for all modules and extensions

3- TBX Mapping

Continue work on SVN: https://tools.oasis-open.org/version-control/browse/wsvn/xliff-omos/trunk/XLIFF-TBX/xliff-tbx-10.xml

Link to latest Editors' Draft of TBX mapping: https://tools.oasis-open.org/version-control/browse/wsvn/xliff-omos/trunk/XLIFF-TBX/xliff-tbx-v1.0.pdf

AI James and dF to schedule 1:1 editorial call for follow-up.  / PENDING

C. Other Topics

1- Date of next meeting?

• Normally on Feb 28, 2017.
• Robert can only attend from 5:15 GMT or so, this conflict until April or so
• Happy to accommodate Robert, we can start JLIFF stuff after Robert joins each time..

2- Liaisons

GALA TAPICC - officially launched last week BSD 3 clause and CC-BY 2.0

https://www.gala-global.org/sites/default/files/GALA%20TAPICC%20Project%20Charter.pdf

- dF connected Chase with Klaus Fleischmann (collecting metadata) ?? status

dF/James: TBX Steering Committee / ISO TC37/SC3 => Expect next TBX IS version in late 2017

dF/Yves: XLIFF TC - XLIFF 2.1 CSPRD02 launched on 10th February, will end by 25th February

https://www.oasis-open.org/news/announcements/public-review-for-xliff-v2-1-ends-february-24th

http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd02/xliff-core-v2.1-csprd02.html

You can review how each of the 20 1st public issues resolved

https://issues.oasis-open.org/browse/XLIFF-14?jql=project%20%3D%20XLIFF%20AND%20status%20%3D%20Closed%20ORDER%20BY%20priority%20DESC

Do subscribe to the comment list https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=xliff

if you're not a member of the XLIFF TC you can only comment through the comment list (if you have a subscription)

You may follow the CTR discussion here https://issues.oasis-open.org/browse/XLIFF-4

3- Promotion

XML Prague last week, we announced the XLIFF 2.1 csprd02 and also mentioned the OMOS work on OM and JLIFF

4- AOB

• OASIS Open (General Membership)
• General Public