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


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

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

Subject: Modified: XLIFF TC Call

Submitter's message
minutes added, thanks to Lucía for scribing
-- Dr. David Filip
Event Title: XLIFF TC Call

Date: Tuesday, 20 February 2018, 11:00am to 12:00pm EST

Call details inside private AI:


This meeting counts towards voter eligibility.


I. Approve Jan 16 meeting minutes https://lists.oasis-open.org/archives/xliff/201801/msg00022.html

II. Congratulations on XLIFF 2.1 https://lists.oasis-open.org/archives/xliff/201802/msg00003.html

  A. Press release call https://lists.oasis-open.org/archives/xliff/201802/msg00009.html

III. Where do we go next?

  A. 2.2 vs. 3.0 https://lists.oasis-open.org/archives/xliff/201802/msg00010.html

IV. Subcommittee and sister TC reports

V. New business


Attendance: Bryan, Tom, David F. Lucia, Phil.

Regrets: Steven Loomis


I. Approve Jan 16 meeting minutes https://lists.oasis-open.org/archives/xliff/201801/msg00022.html

B: It was done through the mailing list.

D: Yes, it was done.



II. Congratulations on XLIFF 2.1 https://lists.oasis-open.org/archives/xliff/201802/msg00003.html

B: My sincere gratitude to the TC and specially to David.


A. Press release call https://lists.oasis-open.org/archives/xliff/201802/msg00009.html

B: We will have the opportunity to have a press release. The deadline is 23rd February. I will try to have other companies to give us quotes to include on the press release.

D: I will try to ask SDL again to have a quote from them.


III. Where do we go next?

A. 2.2 vs. 3.0 http://markmail.org/thread/rpllowohbou5jky7

B: I sent a proposal saying to include all the LISA standards as modules. We identified during the discussion of 2.1, a known issue with inline representation of change tracking that we said we would work on the new version.

D: We should again start the wiki to collect feature requests. We have two requests: one is the Change tracking module, that was dropped in 2.1.

P: We are interested in having it back.

D: Another standng request from ULI, the representation of segmentation rules. It will not be easy. But I believe that with people like Steven Loomis, we can work on it. We can start with these two features.

There was another feature mentioned, about plurals, but I think it is more related to extraction behavior.

I think we should stick to the process

Action Item for Bryan: create a space in the wiki for feature requests.

B: any other ideas?

D: adopting the LISA standards is basically covered as I explained in my response to Bryan. We actually should start working on the note explaining how to use XLIFF for TM exchange..

B: It seems that we have an agreement to replace TMX.

D: We have the Translation Candidates Module that covers that. That's why it is more urgent to push the note than start working on a new version. The minor versions are not attracting so much attention than the bigger ones.

B: We can try to increase the manpower this year.

D: the TBX mapping is in OMOS, this will be a standard. The work was stopped because TBX is on revision. The mapping is already defined. But the other thing, just before Christmas, we agreed on the note explaining how to use XLIFF instead of TMX for TM exchange. TMX cannot be extricated from ETSI. The only way is to use an XLIFF profile instead.

B: we can do the profile. I have a vision of something more structured than an XLIFF profile.

D: If you set up the feature request wiki. You can put the TMX replacement requirement in, and we can see if the discussion takes us further than the profile.

B: I will try to talk to past contributors in the past to see if we can have them back for the new features.

D: XLIFF 2.1 contains the media type registration. Robin has relaunched the registration, this time as permanent, In two months we can have it. We could not restart the registration before the spec got approved.


IV. Subcommittee and sister TC reports

D: The JLIFF has made a lot of progress, and now it is able to represent the core.  Phil has done a lot of progress with an experimental implementation.

P: I have been writing some code to keep up with the schema, my implementation was focusing on validation tests, one of the last things that we changed were the grouping mechanisms. I have reused one of the examples from Bryan’s book. It is coming together quite nicely.

D: we could use some more manpower. The OMOS is working on three projects at the same time. TAPICC (a GALA initiative) is working on XLIFF related projects. We are expecting to receive some contributions from them, they are working on XLIFF extraction recommendations. It will be a great contribution for us. The TAPICC is easy to participate as it does not require membership to participate, and also GALA has a great outreach.

The abstract data model is another project of OMOS. And the third project is the TBX mapping, this might be moving again as TBX is almost stable. IBM is also a member of the OMOS.


D: For promotion, I will talk on XLIFF 2.1 on an AMTA workshop in March.

B: Good news.

Df: we should try to have the next PL sc meeting on the first Tuesday of March. (6th March) The SC should also produce a report on the SOU. That would be worthy.

B: that seems good to me.

Df: we decided not to do either FESGILTT or XLIFF Symposium in Warsaw. Maybe it is time to skip one year. Also the colocation with LocWorld seems to be exhausted, LocWorld grows less technical every year.

L: I think it is a good idea. And it will give us more to time to prepare the next one better.

Df: We should prepare better for the next one. Engage with audience well in advance and make sure all are coming

B: I agree.

Df: We were thinking about other venues than LocWorld. We could consider other conferences like XML Prague. Or Unicode. We can discuss this in the next meeting. Another idea is ASLING, annual Translating and the Computer in London. I am on the PC. Please bring ideas for new venues and colocations to the next PL SC meeting.


V. New business

D: We should have new standing items for the 1) the TM prfile note and 2) for the 2.2 features.

We should also submit 2.1 again to ISO. It worked really well with 2.0 that has been published as ISO 21720. So we need another standing agenda item for that.

B: That sounds good.

D: we need to verify with ISO, it is not very clear the procedure if we need to change to ISO style. We need to repeat the steps: starting the ballot to submit it and then follow the steps.

B: Great, I will add those three points to the agenda.


B: Thank you very much. Meeting adjourned.

Owner: Bryan Schnabel
Group: OASIS XML Localisation Interchange File Format (XLIFF) TC
Sharing: This event is not shared to any other groups.
  • Learn more about subscribing here.
  • View the OASIS XML Localisation Interchange File Format (XLIFF) 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_47088.ics
Description: application/ics

PRODID:-//Kavi Corporation//NONSGML Kavi Groups//EN
DESCRIPTION:Call details inside private AI:\n\nhttps://www.oasis-open.or
 em_id=3663\n\nAgenda: I. Approve Jan 16 meeting minutes http
 \n\nII. Congratulations on XLIFF 2.1 https://lists.oasis-ope
 n.org/archives/xliff/201802/msg00003.html\n\n  A. Press rele
 ase call https://lists.oasis-open.org/archives/xliff/201802/
 msg00009.html\n\nIII. Where do we go next?\n\n  A. 2.2 vs. 3
 .0 https://lists.oasis-open.org/archives/xliff/201802/msg000
 10.html\n\nIV. Subcommittee and sister TC reports\n\nV. New 
 business\nGroup: OASIS XML Localisation Interchange File For
 mat (XLIFF) TC\nCreator: Bryan Schnabel

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