On 25 September 2016 at 20:56, Geert Josten
wrote:
> Hi Reece,
>
> Have you tried with a more regular qname? The docs give ‘validate as
> xs:boolean’ as example, not URIQualifiedName:
>
> http://docs.marklogic.com/guide/xquery/langoverview#id_55039
>
Yes, both 'validate as' and 'validate type' w
Hi Florent,
How about a sparql query that filters with regex(str(?s), Œxyz¹) or
something alike? There are several other str functions in sparql
available, and if necessary you can leverage fn functions as well..
Cheers,
Geert
On 9/25/16, 3:13 PM, "general-boun...@developer.marklogic.com on beha
Hi Reece,
Have you tried with a more regular qname? The docs give ‘validate as
xs:boolean’ as example, not URIQualifiedName:
http://docs.marklogic.com/guide/xquery/langoverview#id_55039
Keep in mind that MarkLogic does not cover the full XQuery 3 recommendation..
Cheers,
Geert
From:
mailto:g
Hi,
Given a string "xyz", I'd like to find all the IRIs in a subject
position in the triple index, so that the string appear anywhere in
the IRI after the last '/' or '#'. That is, for "xyz", I'd like to
have:
http://example.org/proj/component#xyz
http://example.org/proj/component#abc-xyz
http:/
Hi all,
I have found an issue in the MarkLogic support for XQuery 3.0 'validate
type' constructs on MarkLogic 6.0 - 8.0 (https://www.w3.org/TR/2014/
REC-xquery-30-20140408/#prod-xquery30-ValidateExpr).
Given:
xquery version "1.0-ml";
validate as Q{a}b { }
MarkLogic reports a parser err
