Re: [basex-talk] from xquery:parse to data paths ...

Fine, Christian, I shall see what I can achieve. My interest is keen, as the validation of expressions embedded in configurations against XSDs has a potentially enormous value in the domain where I work. In fact, I had earlier begun to write a little XQuery parser myself for just this purpose

Re: [basex-talk] Header problems and xmlns

Hi, you need to handle the default nsmespace e.g. http://stackoverflow.com/questions/5261204/xquery-on-xml-file-with-namespace Or try querying with the * wildcard like //*:MY-ELEM Br, Max Am 20.02.2016 15:56 schrieb "Ana Victória Ladeira" : > > > > Good afternoon! > > I

[basex-talk] Odd Behavior from Ruby Client

I have my Ruby-based server-side commit hooks working but now I'm seeing a failure result I can't figure out yet. I have a large sample data set that I'm using for testing (https://hub.docker.com/r/ditacommunity/demo-content/). This content is non-trivial DITA and all the files are valid (e.g.,

[basex-talk] Header problems and xmlns

Good afternoon! I currently have a dataset with some files that use the following header (I will call it Header1): http://www.cnpq.br/2001/XSL/Lattes; NUMERO-IDENTIFICADOR="X" DATA-ATUALIZACAO="07122015" HORA-ATUALIZACAO="010008" xsi:schemaLocation=" http://www.cnpq.br/2014/XSD/Lattes/Versao1

Re: [basex-talk] from xquery:parse to data paths ...

Hi Hans-Jürgen, I’ll start from the end of your mail: > I would be prepared to embark upon an XQuery implementation of a data path > extractor, provided that you do not come to the conclusion that it would be > of very little. Awesome. The result will surely be interesting for others in the

Re: [basex-talk] from xquery:parse to data paths ...

Thank you very much for your thoughts, Christian! First, yes: you are right, the second outcome referred to the first XPath expression: /descendant::OutboundFlight[Status = 'Booked'][1]/FlightDeparture/DepartureTime => //OutboundFlight/FlightDeparture/DepartureTime, //OutboundFlight/Status But