Our schemas for XLIFF 1.2 have been working fine for many developers. We abandoned the errata for XLIFF 1.2 because the procedures for publishing it were not worth the effort. This issue with the schemas still doesn’t make it worth in my opinion.
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Schnabel, Bryan S
Sent: Thursday, March 15, 2012 3:59 PM
To: Rodolfo M. Raya; email@example.com
Subject: RE: [xliff] problem with XLIFF 1.2 schemas: obsolete URL in our xml.xsd import (FW: xliffroundtriptool)
Thanks. Very good points. Regarding our obsolete include in the 1.2 schemas, not worthy of errata, in your opinion?
Jeroen should be using catalogs to resolve the location of the schema. His tools will not work without an Internet connection or if W3C moves the schema to a different location.
We are including an XML catalog in OASIS format with XLIFF 2.0 for connecting core schema with modules. Using catalogs with XLIFF 2.0 would continue being optional for tool vendors but would be more convenient than before.
While using my DITA-XLIFF roundtrip plug for the DITA Open Toolkit, Jeroen Boots discovered a problem with the XLIFF 1.2 Strict XML Schema. We import the W3C xml.xsd the following way:
<xsd:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/>
The correct URL is:
While all of the processing I do with XLIFF 1.2 works just fine. This causes a fatal error for Jeroen, though he's able to work-around the problem by updating the import as above.
I am not by any stretch of the imagination an expert on redirects. So I cannot explain why this error is forgiven in some environments (like all of mine), and not forgiven in others (like Jeroen's).
Any thoughts on causes or next steps regarding our XLIFF 1.2 schemas?
Not a problem, please go ahead and forward the issue. I am happy to contribute (even if it is in an insignificant manner).
I will do some more robust testing in the near future and if I run into trouble I will surely contact you.
Once again, appreciate your help Bryan, take care,
I'm happy that you were able to troubleshoot the problem. I am surprised that we have not seen this error with others. I guess the redirect is less fatal on some systems. Nonetheless I should look into this problem. I suspect I will need to bring this up with the XLIFF TC (not just a problem with my tool). Do you mind if I forward this to the XLIFF TC?
Thanks for giving me the opportunity to learn more about my tool. Any future questions or comments will be greatly appreciated.
Bryan, I appreciate your help. I was online when I ran the tool. I noticed the error about not being able to find the schema. When I copied & pasted the URL (http://www.w3.org/2001/xml.xsd) in my browser, it returned a Bad Gateway error. I checked with one of my developer friends who explained to me the process of forwarding the request from one location to the next. The physical file seems to reside in a different location. I found a likely hit on the internet, and tried that in the following file:
[changed …/2001/xml.xsd into …/2001/03/xml.xsd]
I ran your XLIFF file on my system and it worked perfectly. I zipped the results and added them to this note.
Looking at your error log, it seems the OT could not find the needed schemas. Were you by any chance not online when you ran the test? I've seen this before. If that is the case, could you please try to run the test while having access to the internet?
If that is not possible, another alternative would be to supply all of the schemas that the OT references. This might be difficult.
If you run the import again and still have the failure, or if that is not the cause, please let me know, and I will happily try more testing.
By the way, I really like your documentation.
Looking forward to hearing back from you.
Hi Bryan, that would be great! Thanks in advance.
I’m also enclosing a manual that describes the process, most of which is copied from your instructions. This may help understand the steps I took, as I cannot rule out that a mistake was made by me ;-)
I'm happy to troubleshoot this. I'll try to look into it this week.
My name is Jeroen Boots, I’m a Technical Writer from the Netherlands and I have heard about your DITA to XLIFF transformation tool.
I have downloaded and installed the tool and managed to create an XLIFF file, even got that translated, but on conversion from XLIFF to DITA, I get two errors which I cannot resolve.
Would it be possible for you to help me resolve this issue.
We are hoping to be able to use the xliffroundtriptool for our translation process.
I’m including the error message, and the translated xml document.
Your help is greatly appreciated!
6503 AB Nijmegen
6537 TL Nijmegen
T: +31 (0) 24 641 3135
F: +31 (0) 24 642 2942
Deze e-mail en alle bijlagen zijn slechts voor gebruik door de beoogde ontvanger. De e-mail kan intellectueel eigendom en/of vertrouwelijke informatie bevatten. De e-mail mag niet worden gekopieerd, openbaar worden gemaakt, worden bewaard of gebruikt door andere personen dan waarvoor deze e-mail bestemd is. Bent u niet de beoogde ontvanger,verwijdert u dan deze e-mail met alle bijlagen en kopieën onmiddellijk en informeer de afzender.
Denk aan het milieu voordat u deze e-mail print.