Time and again I am amazed by the immediacy with which the BaseX team seizes
opportunities for instantaneous improvement. The obsessive idea of agility,
bugging ten-thousands of developing and managing heads, is dwarfed by the
practice of BaseX.
Am Donnerstag, 14. Februar 2019, 14:38:07 ME
> you may consider adding it explicitly to the Wiki example:
Contributions to our Wiki are welcome ;)
Februar 2019 14:38
> An: Zimmel, Daniel; George Sofianos
> Cc: basex-talk@mailman.uni-konstanz.de
> Betreff: Re: [basex-talk] Schema 1.1 validation and Xerces cta-full-xpath-
> checking?
>
> Hi Daniel, hi George,
>
> With the latest snapshot of BaseX, XSD validation feature
Hi Daniel, hi George,
With the latest snapshot of BaseX, XSD validation features can now be
specified [1,2]. In addition to that,
• I have removed the version argument. The most recent supported
version XML Schema will now be used by default.
• Two additional functions can be used to retrieve the
Hi Daniel,
I’ve added a little issue for your feature request [1].
Best,
Christian
[1] https://github.com/BaseXdb/basex/issues/1642
On Mon, Nov 19, 2018 at 5:07 PM Zimmel, Daniel wrote:
>
> Hi,
>
> is there any chance BaseX will support the cta-full-xpath-checking option
> (see https://xerc
Hi,
is there any chance BaseX will support the cta-full-xpath-checking option (see
https://xerces.apache.org/xerces2-j/features.html)? Without it, schema 1.1
validation is limited.
I could not find any switches to configure Xerces features, but did find
someone mentioning it from two years ago
6 matches
Mail list logo