Thanks Michael,
I cloned your repo and borrowed your .basex file. It did indeed allow me
to specify the page location. However, I'm not able to get it to find my
RESTXQ is my services. I added the out of the box BaseX ./bin to my PATH
and changed to a completely different directory. Attached
Gerrit and Liam,
Thanks for that background information and the recommendation for sponsoring
development. I tried adding rewriteSystem to the XML Catalog but it did not
help. The XML Catalog already uses systemSuffix. It is good to see that the
option for sponsoring development is available
On Fri, 2020-07-10 at 08:23 +0200, Imsieke, Gerrit, le-tex wrote:
> I’d like to warmly
> recommend paying him so that he can explore and fix the issue.
:-) Thank you for the recommendation!
The trick is to find the resolver output from setting verbose, as then
you will see the strings that
Hi Yasir,
The error XPST0051 is correct: If an item type is specified along with
“instance of”, its expanded QName must be defined as a generalized
atomic type (i.e., either an atomic type or a pure union type) [1].
Hope this helps,
Christian
[1]
Hello,
I ran the following query using BaseX 9.3.3 command-line client:
'hello' instance of xs:anyAtomicType
the result of the query is `true`.
But if I run this query:
'hello' instance of xs:anySimpleType
an error "[XPST0051] Unknown type: xs:anySimpleType" is returned
Similarly, for the
On 10.07.2020 08:23, Imsieke, Gerrit, le-tex wrote:
It may well be the case that our efforts to make DTD resolution
available to xslt:transform() only focused on supporting xsl:import and
xsl:include while not passing the resolver to the doc() function.
s/DTD resolution/catalog resolution/
Hi Vincent,
can you show us your catalog?
Since you mention that it chokes on finding the DTD, it might be that
you need rewriteSystem instead of rewriteURI for the DTD locations.
Also if you don't resolve by public ID and refer to the DTD by relative
path, this path will be made absolute
7 matches
Mail list logo
