Validate module and catalogs

> On 02.09.2015, at 03:18, Lizzi, Vincent <Vincent.Lizzi at taylorandfrancis.com> wrote: > > It appears that the Validate module is not using catalogs. I’m working with XML that contains a DTD DOCTYPE declaration with a public identifier and a system identifier that contains the filename of the DTD, and I have set up a catalog that provides the DTD location. Here is a rough example: > > declare option db:chop 'false'; > declare option db:dtd 'true'; > declare option db:catfile 'schemas/catalog.xml'; > > let $xmlFile := ‘path/to/file.xml’ > let $parsed := doc($xmlFile) > let $report := validate:dtd-report($xmlFile) > return ($report, $parsed) > > This fails on the validate:dtd-report line. The error report indicates that BaseX is trying to find the DTD in the same folder as the XML file. > > I know the catalog is working because the doc() call is parsing the XML and populating default attributes, and if I remove the db:catfile option declaration the doc() call fails. > > If I add a path to the DTD in the second parameter in validate:dtd-report($xmlFile, ‘path/to/dtd.dtd’) the validation works. I’m not sure why this is needed because the XML contains a DOCTYPE and the catalog should be resolving the DTD location. > > Is this intentional? There are use cases to require that validation is done using a specific DTD and not simply any DTD that the XML happens to declare. In other cases however it is easier to validate using the DTD that is already identified in the DOCTYPE of the XML file. Is this a bug? > > Thanks, > Vincent

On Wed, Sep 2, 2015 at 3:18 AM, Lizzi, Vincent <Vincent.Lizzi at taylorandfrancis.com> wrote: > It appears that the Validate module is not using catalogs. I’m working with > XML that contains a DTD DOCTYPE declaration with a public identifier and a > system identifier that contains the filename of the DTD, and I have set up a > catalog that provides the DTD location. Here is a rough example: > > > > declare option db:chop 'false'; > > declare option db:dtd 'true'; > > declare option db:catfile 'schemas/catalog.xml'; > > > > let $xmlFile := ‘path/to/file.xml’ > > let $parsed := doc($xmlFile) > > let $report := validate:dtd-report($xmlFile) > > return ($report, $parsed) > > > > This fails on the validate:dtd-report line. The error report indicates that > BaseX is trying to find the DTD in the same folder as the XML file. > > > > I know the catalog is working because the doc() call is parsing the XML and > populating default attributes, and if I remove the db:catfile option > declaration the doc() call fails. > > > > If I add a path to the DTD in the second parameter in > validate:dtd-report($xmlFile, ‘path/to/dtd.dtd’) the validation works. I’m > not sure why this is needed because the XML contains a DOCTYPE and the > catalog should be resolving the DTD location. > > > > Is this intentional? There are use cases to require that validation is done > using a specific DTD and not simply any DTD that the XML happens to declare. > In other cases however it is easier to validate using the DTD that is > already identified in the DOCTYPE of the XML file. Is this a bug? > > > > Thanks, > > Vincent > >

-----Original Message----- From: Christian Grün [mailto:christian.gruen at gmail.com] Sent: Monday, September 14, 2015 6:41 AM To: Lizzi, Vincent <Vincent.Lizzi at taylorandfrancis.com> Cc: basex-talk at mailman.uni-konstanz.de Subject: Re: [basex-talk] Validate module and catalogs Hi Vincent, As you already found out, the catalog option is currently not applied when validating resources. Currently, it's only applied when parsing and importing XML documents [1]. As you have recently worked on Schematron validation (thanks again), maybe you already know how this is done in Java? If yes, I invite you to send me some Java code, and I will include it in our XQuery DTD (and maybe XSD) functions [2]. Thanks, Christian [1] https://github.com/BaseXdb/basex/blob/master/basex-core/src/main/java/org/basex/build/xml/SAXWrapper.java#L70-L71 [2] https://github.com/BaseXdb/basex/blob/master/basex-core/src/main/java/org/basex/query/func/validate/ On Wed, Sep 2, 2015 at 3:18 AM, Lizzi, Vincent <Vincent.Lizzi at taylorandfrancis.com> wrote: > It appears that the Validate module is not using catalogs. I’m working > with XML that contains a DTD DOCTYPE declaration with a public > identifier and a system identifier that contains the filename of the > DTD, and I have set up a catalog that provides the DTD location. Here is a rough example: > > > > declare option db:chop 'false'; > > declare option db:dtd 'true'; > > declare option db:catfile 'schemas/catalog.xml'; > > > > let $xmlFile := ‘path/to/file.xml’ > > let $parsed := doc($xmlFile) > > let $report := validate:dtd-report($xmlFile) > > return ($report, $parsed) > > > > This fails on the validate:dtd-report line. The error report indicates > that BaseX is trying to find the DTD in the same folder as the XML file. > > > > I know the catalog is working because the doc() call is parsing the > XML and populating default attributes, and if I remove the db:catfile > option declaration the doc() call fails. > > > > If I add a path to the DTD in the second parameter in > validate:dtd-report($xmlFile, ‘path/to/dtd.dtd’) the validation works. > I’m not sure why this is needed because the XML contains a DOCTYPE and > the catalog should be resolving the DTD location. > > > > Is this intentional? There are use cases to require that validation is > done using a specific DTD and not simply any DTD that the XML happens to declare. > In other cases however it is easier to validate using the DTD that is > already identified in the DOCTYPE of the XML file. Is this a bug? > > > > Thanks, > > Vincent > >