OASIS XML Localisation Interchange File Format (XLIFF) TC

 View Only

  • 1.  Schematron rules for 2.1 in XSLT

    Posted 05-12-2017 11:58
    Hi all,   While looking at handling the Schematron validation for 2.1 in Java, I found that one popular way to do this was to create an XSLT template corresponding to the Schematron rules and rule it against the file to validate. This may be a much easier way to provide validation for other implementations: They are much more implementations of XSLT than Schematron. It would be very helpful if the TC would provide such XSLT file as an official document. It seems they can be generated with a few Java Schematron implementation like Jing, and even oXygen appears to be able to do this.   Cheers, -yves   Yves Savourel Localization Solutions Architect ENLASO ® 4888 Pearl East Circle Suite 300E Boulder Colorado 80301 t: 303.945.3759 f: 303.516.1701 An ISO 9001:2015 certified company   Confidentiality Notice The information in this transmittal may be privileged and confidential and is intended only for the recipient(s) listed above. Any review, use, disclosure, distribution or copying of this transmittal, in any form, is prohibited except by or on behalf of the intended recipient. If you have received this transmittal in error, please notify me immediately by reply email and destroy all copies of the transmittal.  


  • 2.  Re: [xliff] Schematron rules for 2.1 in XSLT

    Posted 05-12-2017 15:12
    +1. Some schematron rules require an XSLT 2+ implementation, just fyi. Felix Felix Am 12.05.2017 13:57 schrieb "Yves Savourel" < ysavourel@enlaso.com >: Hi all,   While looking at handling the Schematron validation for 2.1 in Java, I found that one popular way to do this was to create an XSLT template corresponding to the Schematron rules and rule it against the file to validate. This may be a much easier way to provide validation for other implementations: They are much more implementations of XSLT than Schematron. It would be very helpful if the TC would provide such XSLT file as an official document. It seems they can be generated with a few Java Schematron implementation like Jing, and even oXygen appears to be able to do this.   Cheers, -yves   Yves Savourel Localization Solutions Architect ENLASO ® 4888 Pearl East Circle Suite 300E Boulder Colorado 80301 t: 303.945.3759 f: 303.516.1701 An ISO 9001:2015 certified company   Confidentiality Notice The information in this transmittal may be privileged and confidential and is intended only for the recipient(s) listed above. Any review, use, disclosure, distribution or copying of this transmittal, in any form, is prohibited except by or on behalf of the intended recipient. If you have received this transmittal in error, please notify me immediately by reply email and destroy all copies of the transmittal.  


  • 3.  RE: [xliff] Schematron rules for 2.1 in XSLT

    Posted 05-12-2017 15:29
    Good point Felix. Yes, I’ve noticed that one of the first line of the .sch file was queryBinding="xslt2". I guess it’s easier to find XSLT2 processors than Schematron one anyway…     Yves Savourel Localization Solutions Architect t: 303.951.4523 f: 303.516.1701 ENLASO ®   From: Felix Sasaki [mailto:felix@sasakiatcf.com] Sent: Friday, May 12, 2017 9:12 AM To: Yves Savourel <ysavourel@enlaso.com> Cc: XLIFF Main List <xliff@lists.oasis-open.org> Subject: Re: [xliff] Schematron rules for 2.1 in XSLT   +1. Some schematron rules require an XSLT 2+ implementation, just fyi.   Felix     Felix     Am 12.05.2017 13:57 schrieb "Yves Savourel" < ysavourel@enlaso.com >: Hi all,   While looking at handling the Schematron validation for 2.1 in Java, I found that one popular way to do this was to create an XSLT template corresponding to the Schematron rules and rule it against the file to validate. This may be a much easier way to provide validation for other implementations: They are much more implementations of XSLT than Schematron. It would be very helpful if the TC would provide such XSLT file as an official document. It seems they can be generated with a few Java Schematron implementation like Jing, and even oXygen appears to be able to do this.   Cheers, -yves   Yves Savourel Localization Solutions Architect ENLASO ® 4888 Pearl East Circle Suite 300E Boulder Colorado 80301 t: 303.945.3759 f: 303.516.1701 An ISO 9001:2015 certified company   Confidentiality Notice The information in this transmittal may be privileged and confidential and is intended only for the recipient(s) listed above. Any review, use, disclosure, distribution or copying of this transmittal, in any form, is prohibited except by or on behalf of the intended recipient. If you have received this transmittal in error, please notify me immediately by reply email and destroy all copies of the transmittal.  


  • 4.  Re: [xliff] Schematron rules for 2.1 in XSLT

    Posted 05-12-2017 16:35



    Hi all,


    Yes, the Schematron files can be compiled into XSLT and it is a common practice. I propose to produce one instance of XSLT with all namespaces included (core and modules) as TC reference. oXygen provides a pretty good compiler for this.


    Soroush.  








    On May 12, 2017, at 11:28 AM, Yves Savourel < ysavourel@enlaso.com > wrote:




    Good point Felix. Yes, I’ve noticed that one of the first line of the .sch file was queryBinding="xslt2".

    I guess it’s easier to find XSLT2 processors than Schematron one anyway…

     

     

    Yves Savourel  
    Localization Solutions Architect     t:   303.951.4523     f:   303.516.1701     ENLASO ®

     

    From:   Felix Sasaki [ mailto:felix@sasakiatcf.com ]  
    Sent:   Friday, May 12, 2017 9:12 AM
    To:   Yves Savourel < ysavourel@enlaso.com >
    Cc:   XLIFF Main List < xliff@lists.oasis-open.org >
    Subject:   Re: [xliff] Schematron rules for 2.1 in XSLT

     


    +1. Some schematron rules require an XSLT 2+ implementation, just fyi.


     



    Felix



     


     



    Felix



     





     


    Am 12.05.2017 13:57 schrieb "Yves Savourel" < ysavourel@enlaso.com >:




    Hi all,

     

    While looking at handling the Schematron validation for 2.1 in Java, I found that one popular way to do this was to create an XSLT template corresponding to the Schematron rules and rule it against the
    file to validate. This may be a much easier way to provide validation for other implementations: They are much more implementations of XSLT than Schematron.

    It would be very helpful if the TC would provide such XSLT file as an official document.

    It seems they can be generated with a few Java Schematron implementation like Jing, and even oXygen appears to be able to do this.

     

    Cheers,

    -yves

     

    Yves Savourel
    Localization Solutions Architect     ENLASO ®
    4888 Pearl East Circle     Suite 300E     Boulder     Colorado
    80301
    t:   303.945.3759     f:   303.516.1701
    An ISO 9001:2015 certified company

     

    Confidentiality Notice  
    The information in this transmittal may be privileged and confidential and is intended only for the recipient(s) listed above. Any review, use, disclosure, distribution or copying of this transmittal, in any form, is prohibited except by or on behalf of the
    intended recipient. If you have received this transmittal in error, please notify me immediately by reply email and destroy all copies of the transmittal.















  • 5.  RE: [xliff] Schematron rules for 2.1 in XSLT

    Posted 05-12-2017 17:05
    +1 for a single instance :)     Yves Savourel Localization Solutions Architect t: 303.951.4523 f: 303.516.1701 ENLASO ®   From: Soroush.Saadatfar [mailto:Soroush.Saadatfar@ul.ie] Sent: Friday, May 12, 2017 10:35 AM To: Yves Savourel <ysavourel@enlaso.com> Cc: Felix Sasaki <felix@sasakiatcf.com>; XLIFF Main List <xliff@lists.oasis-open.org> Subject: Re: [xliff] Schematron rules for 2.1 in XSLT   Hi all,   Yes, the Schematron files can be compiled into XSLT and it is a common practice. I propose to produce one instance of XSLT with all namespaces included (core and modules) as TC reference. oXygen provides a pretty good compiler for this.   Soroush.         On May 12, 2017, at 11:28 AM, Yves Savourel < ysavourel@enlaso.com > wrote:   Good point Felix. Yes, I’ve noticed that one of the first line of the .sch file was queryBinding="xslt2". I guess it’s easier to find XSLT2 processors than Schematron one anyway…     Yves Savourel   Localization Solutions Architect     t:   303.951.4523     f:   303.516.1701     ENLASO ®   From:   Felix Sasaki [ mailto:felix@sasakiatcf.com ]   Sent:   Friday, May 12, 2017 9:12 AM To:   Yves Savourel < ysavourel@enlaso.com > Cc:   XLIFF Main List < xliff@lists.oasis-open.org > Subject:   Re: [xliff] Schematron rules for 2.1 in XSLT   +1. Some schematron rules require an XSLT 2+ implementation, just fyi.   Felix     Felix     Am 12.05.2017 13:57 schrieb "Yves Savourel" < ysavourel@enlaso.com >: Hi all,   While looking at handling the Schematron validation for 2.1 in Java, I found that one popular way to do this was to create an XSLT template corresponding to the Schematron rules and rule it against the file to validate. This may be a much easier way to provide validation for other implementations: They are much more implementations of XSLT than Schematron. It would be very helpful if the TC would provide such XSLT file as an official document. It seems they can be generated with a few Java Schematron implementation like Jing, and even oXygen appears to be able to do this.   Cheers, -yves   Yves Savourel Localization Solutions Architect     ENLASO ® 4888 Pearl East Circle     Suite 300E     Boulder     Colorado 80301 t:   303.945.3759     f:   303.516.1701 An ISO 9001:2015 certified company   Confidentiality Notice   The information in this transmittal may be privileged and confidential and is intended only for the recipient(s) listed above. Any review, use, disclosure, distribution or copying of this transmittal, in any form, is prohibited except by or on behalf of the intended recipient. If you have received this transmittal in error, please notify me immediately by reply email and destroy all copies of the transmittal.  


Related Content