< Return to Calendar

* XLIFF TC meeting (Conference Call)
Name * XLIFF TC meeting (Conference Call)
Time Tuesday, 19 November 2019, 08:00am to 09:00am EST
(Tuesday, 19 November 2019, 01:00pm to 02:00pm UTC)

New dial-in link at this action item.



Note, I will try to look into alternate dial in information - seems the chair is not able to use skype.


Attendance: Bryan, David F, Tom, Phil, Lucía.

B: Our time would be better spent if we think about recruiting. We can do a brainstorming section.

Df: we really need to restart the TC to start making progress on the technical work. We need to get more people coming.

Df: I am going to London to the ASLING T&C 41 conference this week, translators would be there.

B: we are missing also translation service providers. I can reach out to the ones that I work with. We have some strong presence from those companies before.

Df: We need to get people back. We need a coordinated effort to get more people on board.

Df: we need more representative to work on features. We need more people from the industry.

B: Exactly.

Tom: Just thinking out loud, in a virtual sense. What companies do we know of that should be using XLIFF, but aren't? What would they want to see in the standard to make it useful to them? And would they be willing to contribute resources to the TC's efforts?

Df: some people might join if they feel that something big might happen. I personally think that the rendering spec might be a good topic to get people’s attention. I can start doing the work but I do not feel like I am entitle to do it, we need more representativeness from the industry.

Df: we can publish the TAPPIC best practice as a TC Note. Once we publish XLIFF 2.1 at ISO TC 37/SC 5, we can also attract attention. So we can agree that we are not doing the symposium in the near term. What else can we do?

Df: Another important thing is that the schematron had bugs. It is natural as it was a huge delivery. Working on this issue would be a good addition.

B: Yes, we can work on this potential topic.

Df: I think the rendering would be a good thing, but tool makers might have their own ideas on how to render.

Df: TAPICC is working on track two, that deals on exchanging data at real time, and will use jliff that uses the same data model as xliff.

B: I wonder if standard committees are suffering the same as we are.

Df: I think it is normal. For example, the W3C they create working groups as there are needs, and they are closed as the complete the task. In our case, the critical mass seems to be around 6 or 7 people, if we get more people, we can work.

Df: I think there is interest in validation from the industry. We can work on conformance. Another thing, we are suffering from another current common issue: non technical people tend to think about standard formarts as less important becuase of AI, but it's actually the opposite..

Phil: XLIFF core is sufficient mature. Maybe the problem is with the modules as  tools might ignore them. 

Df: I believe that what needs to be done is to evangelise the core. Once you have ecosystem support for the core, we can start pushing the modules. There is some progress.

I wrote this article in Multilingual where I said that people might think that standards are not important because of AI.

XLIFF can be seen as a potential corpus format for bitext information, I presented it as such to JTC 1/SC 42 as ISO TC 37 liaison

I am chartering a new TC for lexicographical information data model. I think XLIFF as a bitext format has a great potential, also in this context

Phil: The CMS people would also be interested.

Df: I agree that CMS interoperability is a great issue. If would great to have people from the European Council. Simone Chiaretta has been working on an XLIFF extractor for Umbraco and also published a CMS agnostic tepate code for XLIFF extraction, BTW he works with the TAPICC best practice for extraction..

b: we can also concentrate on features that potential clients would need.

DF: the support is disconnected. People might be doing it, but they do not advertise it.

B: what is so difficult with the modules that people are not implementing it.

Df: we did good decisions on allowing extensibility. it would be ridiculous to have an XML format that wouldn't extend. But it is true it adds complexity. Module based namespaces are an advantage for advanced developers, but can be steep for novice developers.

B: Are we able to fix the errors in the schematron? Tom?

Tom: I haven't had a look at anything yet. Would need to come up to speed on Schematron a bit.

Df: I am teaching a module on that in Limerick. I can manage to do something. We can have a fix on the svn.

B: Meeting adjourned.


I. Administration
A. Welcome back! Where were we?

B. Approve meeting minutes
No minutes to approve this week.

C. Is this still a good time/day for our meeting? Meet 1 hour earlier?

II. Where do we go next?
A. XLIFF 2.X or 3.0 wiki space for new features (Bryan)

B. Rendering Requirements for XLIFF 2.2 - David

C. GALA TAPICC XLIFF Extraction and Merging Best Practice v1.0 Allison

D. Registration file - Yves

E. Invalid sample files identified by Rodolfo Raya

III. Subcommittee and sister TC reports
A. Promotion and Liaison SC
B. XOMOS - Sister TC

IV. New business

Submitter Bryan Schnabel
GroupOASIS XML Localisation Interchange File Format (XLIFF) TC
Access This event is visible to OASIS XML Localisation Interchange File Format (XLIFF) TC and shared with
  • OASIS Open (General Membership)
  • General Public