OASIS XML Localisation Interchange File Format (XLIFF) TC

Hi Tom, Bryan, all,   > One problem I'm running into is the slowness of the validation: > both loading the schema and performing the validation seem to > take a lot more time than expected. Maybe this is related to > fetching some default schema for the XML namespace?   I've finally resolved this speed issue by including the schema for the XML namespace along with the modules' schemas and changing the references in the files.   Now Lynx takes milliseconds instead of almost a minute to validate a document.   Maybe this is something we could do in the official copy too? After all the xml.xsd file is not going to change, and having it locally may help a lot with other validators too.   Cheers, -yves  

Yves, what do you mean with the official copy? Do you suggest that the xml schema is included in the official XLIFF schema folder? Thanks dF Dr. David Filip ======================= LRC CNGL LT-Web CSIS University of Limerick, Ireland telephone: +353-6120-2781 cellphone: +353-86-0222-158 facsimile: +353-6120-2734 mailto: david.filip@ul.ie On Sun, Oct 20, 2013 at 1:42 PM, Yves Savourel < ysavourel@enlaso.com > wrote: Hi Tom, Bryan, all,   > One problem I'm running into is the slowness of the validation: > both loading the schema and performing the validation seem to > take a lot more time than expected. Maybe this is related to > fetching some default schema for the XML namespace?   I've finally resolved this speed issue by including the schema for the XML namespace along with the modules' schemas and changing the references in the files.   Now Lynx takes milliseconds instead of almost a minute to validate a document.   Maybe this is something we could do in the official copy too? After all the xml.xsd file is not going to change, and having it locally may help a lot with other validators too.   Cheers, -yves  

> Yves, what do you mean with the official copy? > Do you suggest that the xml schema is included in > the official XLIFF schema folder? Yes. The W3C is throttling access to DTDs and schemas due to too much traffic. They recommend to not access those URI if it can be avoided. This blog entry explains the issue and recommend "Don't fetch stuff unless you actually need it": http://www.w3.org/blog/systeam/2008/02/08/w3c_s_excessive_dtd_traffic/ The schema for the XML namespace is frozen: There is no reason to not have a copy of it. In fact many XML validators have a local/hard-wired copy of it in their distribution. But the ones which do not--with our current schema--end up fetching the document on the W3C Web site and get throttled. Cheers, -ys

Thanks for clarification, Yves I think this needs a follow up with @Chet. I am afraid that we cannot bundle the W3C schema together with our schemas as it could create the false impression that the W3C schema is a part of our multipart product. But maybe there is a way how to include a copy while making clear that it is not a part of our deliverables.. Rgds dF Dr. David Filip ======================= LRC CNGL LT-Web CSIS University of Limerick, Ireland telephone: +353-6120-2781 cellphone: +353-86-0222-158 facsimile: +353-6120-2734 mailto: david.filip@ul.ie On Tue, Oct 22, 2013 at 1:44 PM, Yves Savourel < ysavourel@enlaso.com > wrote: > Yves, what do you mean with the official copy? > Do you suggest that the xml schema is included in > the official XLIFF schema folder? Yes. The W3C is throttling access to DTDs and schemas due to too much traffic. They recommend to not access those URI if it can be avoided. This blog entry explains the issue and recommend "Don't fetch stuff unless you actually need it": http://www.w3.org/blog/systeam/2008/02/08/w3c_s_excessive_dtd_traffic/ The schema for the XML namespace is frozen: There is no reason to not have a copy of it. In fact many XML validators have a local/hard-wired copy of it in their distribution. But the ones which do not--with our current schema--end up fetching the document on the W3C Web site and get throttled. Cheers, -ys

I am investigating for you. Will be back with a response shortly.  On Tue, Oct 22, 2013 at 1:43 PM, Dr. David Filip < David.Filip@ul.ie > wrote: Thanks for clarification, Yves I think this needs a follow up with @Chet. I am afraid that we cannot bundle the W3C schema together with our schemas as it could create the false impression that the W3C schema is a part of our multipart product. But maybe there is a way how to include a copy while making clear that it is not a part of our deliverables.. Rgds dF Dr. David Filip ======================= LRC CNGL LT-Web CSIS University of Limerick, Ireland telephone:  +353-6120-2781 cellphone: +353-86-0222-158 facsimile:  +353-6120-2734 mailto: david.filip@ul.ie On Tue, Oct 22, 2013 at 1:44 PM, Yves Savourel < ysavourel@enlaso.com > wrote: > Yves, what do you mean with the official copy? > Do you suggest that the xml schema is included in > the official XLIFF schema folder? Yes. The W3C is throttling access to DTDs and schemas due to too much traffic. They recommend to not access those URI if it can be avoided. This blog entry explains the issue and recommend "Don't fetch stuff unless you actually need it": http://www.w3.org/blog/systeam/2008/02/08/w3c_s_excessive_dtd_traffic/ The schema for the XML namespace is frozen: There is no reason to not have a copy of it. In fact many XML validators have a local/hard-wired copy of it in their distribution. But the ones which do not--with our current schema--end up fetching the document on the W3C Web site and get throttled. Cheers, -ys -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393  Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open