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: RE: [xliff] Schematron rules for 2.1 in XSLT


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.

 



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