Given this in modelNames.xml
http://www.b2b.net/plants";>
sales
stocks
plants
clients
I am having problems with the following XQuery
xquery version "1.0";
declare namespace b2b = "http://www.b2b.net/plants";;
declare namespace xf="http://www.w3.org/2002/xforms";;
declare namespace ht
Achhh, didn't realise my replies weren't going to the list.
-- Forwarded message ------
From: Ihe Onwuka
Date: Fri, Jul 13, 2012 at 5:10 PM
Subject: Re: [xquery-talk] Simple (I thought) Xquery giving run-time error.
To: Josh Spiegel
Thats what I did before. Thats what I
move a /* either from the
> definition of $models or from the expression where it is used.
>
> Michael Kay
> Saxonica
>
>
> On 13/07/2012 15:41, Ihe Onwuka wrote:
>>
>> xquery version "1.0";
>>
>>
>> declare namespace b2b ="http:/
I'm running this on eXide, I'll try it on Saxon.
On Fri, Jul 13, 2012 at 5:48 PM, Michael Kay wrote:
>
> On 13/07/2012 17:35, Ihe Onwuka wrote:
>>
>> didn't want to tamper with the definition of $models as it is used
>> elsewhere (you are seeing a cu
It works on Saxon it's a bug in the eXist XQuery processor.
On Fri, Jul 13, 2012 at 5:55 PM, Ihe Onwuka wrote:
> I'm running this on eXide, I'll try it on Saxon.
>
> On Fri, Jul 13, 2012 at 5:48 PM, Michael Kay wrote:
>>
>> On 13/07/2012 17:35, Ihe
which I am told has now been fixed.
On Fri, Jul 13, 2012 at 6:44 PM, Ihe Onwuka wrote:
> It works on Saxon it's a bug in the eXist XQuery processor.
>
> On Fri, Jul 13, 2012 at 5:55 PM, Ihe Onwuka wrote:
>> I'm running this on eXide, I'll try it on Saxon.
>
Didn't use the right kind of comments and fell foul of this gotcha
http://en.wikibooks.org/wiki/XQuery/Gotchas#Comments
Except what I really want to do is comment a line in a direct
constructor and whichever type of comment I use it's going to appear
in the output and I don't want it to.
I vaguely remember reading somewhere that a preference for what I
would call axis notation has performance advantages over the
equivalent FLOWR code.
I certainly recall reading that XPath predicates perform better than
where clauses in FLOWR.
I would appreciate clarification, confirmation or cor
On Tue, Jul 31, 2012 at 5:25 PM, Ihe Onwuka wrote:
> I vaguely remember reading somewhere that a preference for what I
> would call axis notation has performance advantages over the
> equivalent FLOWR code.
>
> I certainly recall reading that XPath predicates perform better than
On Wed, Dec 19, 2012 at 2:54 PM, Robby Pelssers wrote:
> Ok...
>
> I managed to get something working. But not sure if it is such a smart
> idea... Any comments from the experts?
>
> http://robbypelssers.blogspot.nl/2012/12/using-options-in-xquery.html
>
Like most of the good things in Scala th
On Fri, Dec 21, 2012 at 1:08 PM, Michael Sokolov wrote:
> On 12/20/2012 11:00 AM, Michael Kay wrote:
>>
>>
>> Note that you haven't actually commented anything out. When you change the
>> content of an element constructor from
>>
>>
>>
>> to
>>
>> (::)
>
> So to achieve the intended effect
>
> Same story on the backend, when it comes to query flexible documents, XQuery
> has answered a lot of questions that the NoSQL community is only starting to
> discover and yet it seems that there is a cultural gap between the two
> communities.
>
Re NoSQL and a bit of a digression. but could sa
On Tue, May 21, 2013 at 1:56 PM, Michael Sokolov
wrote:
> On 05/21/2013 08:05 AM, Ihe Onwuka wrote:
>>>
>>> Same story on the backend, when it comes to query flexible documents,
>>> XQuery
>>> has answered a lot of questions that the NoSQL community is only
SICP - great book :)
Read Picturing Programs by Stephen Bloch. It is more likely to tax your
patience than your brain. If you find that too slow How to Design Programs.
Both of which are free on the web.
Casual observation. Every time I have bought a Functional Programmng book
that was written by
Has anybody tried this in XQuery or if I am so foolish (not yet but give me
time) would I be the courageous
http://www.youtube.com/watch?v=ik8JT2S-kBE early
adopter.
___
talk@x-query.com
http://x-query.com/mailman/listinfo/talk
elch wrote:
>
> It should be pretty trivial...
>
> On 31 Dec 2013 11:07, "Ihe Onwuka" wrote:
> >
> > Has anybody tried this in XQuery or if I am so foolish (not yet but give
> me time) would I be the courageous
> http://w
near algebra modulus written in XQUERY is expected to have performances
> performances 1000 X slower than its corresponding C++ or JAVA (you can
> measure it precisely). Any mathematician linear algebra modulus would
> probably trashed your modulus after the first test.
>
> Hope t
imizer
>
>
>
> This among other reasons (such as supporting json arrays) is why native
> array types that can nest are often supported as vendor extensions,
>
> and I belive are being considered by W3C as XQuery native types.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
The code below should (it's been edited) use map to create an element for A
B C D within the parent reviewData.
The call to local:getReview is expensive though, so to avoid calling it
twice I am returning a sequence as the content of the element constructor.
xquery version "3.0";
declare variabl
d FLOWR expressions after a ! like
>
>
>
> (1,2,3) ! ( for $a in . return . )
>
>
>
>
>
> *From:* talk-boun...@x-query.com [mailto:talk-boun...@x-query.com] *On
> Behalf Of *Ihe Onwuka
> *Sent:* Wednesday, January 01, 2014 2:03 AM
> *To:* talk@x-query.com
> *Subjec
yeah I was thinking that but y'know how it is when you go in all guns
blazing and claiming you've found a bug.. but now that you have
emboldened my keyboard I'm thinking of a subject heading like t will be
Bug. Fix it you b**ds.
On Thu, Jan 2, 2014 at 9:18 AM, Joe Wicentowski wrote:
> I
some contentsome content/
descendant::C[normalize-space(@score)]/
{,.}
Now look what Saxon 9.3.0.5 gives for the position attribute
and eXist 3.0
The idea was to have returned the position of the instance of C that was
found within it's parent. I'm not convinced either are doi
ng the items selected; it will always be an ascending sequence starting
> at 1.
>
> Michael Kay
> Saxonica
>
>
> On 2 Jan 2014, at 13:21, Ihe Onwuka wrote:
>
> some content />some content/
> descendant::C[normalize-space(@score)]/
> {,.}
If x is the document element of a document in a collection, is it the
sibling of y that is the document element of another document in the same
collection?
If not why not?
___
talk@x-query.com
http://x-query.com/mailman/listinfo/talk
eing
> "children" of a "parent" collection and thus "siblings"?
>
> On Sun, Jan 5, 2014 at 10:50 AM, Ihe Onwuka wrote:
> > If x is the document element of a document in a collection, is it the
> > sibling of y that is the document element of
in another collection - so that doesn't work.
The thing that seemed most natural to fix this was to supplement the
predicate to say there should be no sibling review by the same
reviews/@person.
On Sun, Jan 5, 2014 at 8:54 PM, Michael Kay wrote:
>
> On 5 Jan 2014, at 16:50,
Kay wrote:
> In XQuery 3.0
>
> for $review in collection($sp:reviewsColl)//review
> group by $review/@person
> where count($review) = 1
> return f:render($review)
>
> Michael Kay
> Saxonica
>
>
>
>
> On 6 Jan 2014, at 10:58, Ihe Onwuka wrote:
>
>
On Mon, Jan 6, 2014 at 12:21 PM, Andrew Welch wrote:
> On 6 January 2014 12:07, Ihe Onwuka wrote:
> > Thank you. I'm not wishing to sound uncharitable or rude, but I
> deliberately
> > didn't ask for a solution because I wanted to focus on the original
> > ques
On Mon, Jan 6, 2014 at 12:31 PM, Michael Kay wrote:
>
> On 6 Jan 2014, at 12:07, Ihe Onwuka wrote:
>
> > Thank you. I'm not wishing to sound uncharitable or rude, but I
> deliberately didn't ask for a solution because I wanted to focus on the
> original question
On Mon, Jan 6, 2014 at 2:30 PM, Andrew Welch wrote:
> This post:
>
> > I want to find all reviews written by people that only wrote 1 review. I
> > wrote
> >
> > collection($sp:reviewsColl)/descendant::reviews[not(review[2])]
> >
> > but reviews has a @person attribute and that person may have 1 o
Read it as "If you are still puzzled look at the original post of the
thread".
On Mon, Jan 6, 2014 at 3:09 PM, Joe Wicentowski wrote:
> Hi Ihe,
>
> > Still puzzled
>
> What are you still puzzled about? I thought your questions were all
> answered, no?
>
> Joe
>
xquery version "3.0";
The task is to display things in descending order of the number of times
they occur.
New Effort
import module namespace sp="urn:xx.com" at 'common.xqm';
{
for $thing in
subsequence(collection($sp:reviewsColl)/descendant::reviews[1]//thing,1,5)
group by $name:
>
> Michael Kay
> Saxonica
>
> On 7 Jan 2014, at 10:47, Ihe Onwuka wrote:
>
> xquery version "3.0";
> The task is to display things in descending order of the number of times
> they occur.
>
> New Effort
>
> import module namespace sp=&qu
On Tue, Jan 7, 2014 at 11:29 AM, Ihe Onwuka wrote:
> Tried that already but that will give me a let that follows a group by
> which is not allowed so I put the return back.
>
> When I moved the count up before the group by (still with no return) to
> counter that eXist gave me
&
oll)/descendant::reviews[1]//thing,1,5)
> group by $name:=$thing/@name
> order by count($thing) descending
>
> return }
>
>
>
>
> Michael Kay
> Saxonica
>
>
> On 7 Jan 2014, at 11:34, Ihe Onwuka wrote:
>
> {
> for $thing in
>
On Tue, Jan 7, 2014 at 12:39 PM, Michael Kay wrote:
>
> On 7 Jan 2014, at 12:30, Ihe Onwuka wrote:
>
> I am most distressed that this worked, firstly
>
> section 3.10.8 of the spec says
>
> An order by clause contains one or more ordering specifications, called
> or
That does not allow for an initial clause to follow an intermediate clause.
On Tue, Jan 7, 2014 at 12:45 PM, John Snelson wrote:
> On 07/01/14 12:39, Michael Kay wrote:
>
>> Yes, I was surprised to see that a "let" clause isn't allowed after an
>> order-by or group-by. I don't remember the reaso
Hang on I might have read that wrong ...not sure now.
On Tue, Jan 7, 2014 at 12:56 PM, Ihe Onwuka wrote:
> That does not allow for an initial clause to follow an intermediate clause.
>
>
> On Tue, Jan 7, 2014 at 12:45 PM, John Snelson
> wrote:
>
>> On 07/01/14
So the devil lies in the fact that an initial clause is an intermediate
clause.
Well eXist certainly doesn't allow the let.
unexpected token: let (while expecting closing tag for element constructor:
counts)
On Tue, Jan 7, 2014 at 12:59 PM, Ihe Onwuka wrote:
> Hang on I might have r
The definition of atomization in (for the avoidance of confusion that is
meant to be a link to section 2.4.2 of the XQuery 3.0 spec)
http://www.w3.org/TR/2013/WD-xquery-30-20130723/#id-atomization
looks to me to be saying the opposite of
http://books.google.co.uk/books?id=0Phv5N-cPg8C&pg=PA320&l
On Wed, Jan 8, 2014 at 7:10 AM, Ihe Onwuka wrote:
> The definition of atomization in (for the avoidance of confusion that is
> meant to be a link to section 2.4.2 of the XQuery 3.0 spec)
>
> http://www.w3.org/TR/2013/WD-xquery-30-20130723/#id-atomization
>
> looks to me to be s
On Wed, Jan 8, 2014 at 9:14 AM, Michael Kay wrote:
> Could you explain where you think these two definitions differ?
>
>
Your book says atomization is invoked implicitly when a SEQUENCE is used
where ATOMIC VALUES are expected.
The specification says Atomization is applied to a value when the V
On Wed, Jan 8, 2014 at 11:03 AM, David Carlisle wrote:
> On 08/01/2014 09:35, Ihe Onwuka wrote:
>
> >
>> > {$thing/@name}
>>
>>
> I can't begin to fathom the rationale for the exception or the value of
>> such an exception over
On Wed, Jan 8, 2014 at 11:44 AM, David Carlisle wrote:
> On 08/01/2014 11:36, Ihe Onwuka wrote:
>
>> No. I am saying that if the expression is an attrtibute constructor then
>> atomization should be atomic.
>>
>
>
> OK so I'm completely lost as I don'
On Wed, Jan 8, 2014 at 11:20 AM, David Carlisle wrote:
> On 08/01/2014 11:11, Ihe Onwuka wrote:
>
>>
>>
>>
>> On Wed, Jan 8, 2014 at 11:03 AM, David Carlisle > <mailto:dav...@nag.co.uk>> wrote:
>>
>> On 08/01/2014 09:35, Ihe Onwuka wr
On Wed, Jan 8, 2014 at 11:48 AM, David Carlisle wrote:
> On 08/01/2014 11:36, Ihe Onwuka wrote:
> > be good/{@cnt}
>
>> the expression inside is an attribute constructor.
>>
>
> No it's not an attribute constructor the attribute node is already
>
It's what I expected. I haven't seen a rational explanation to expect
anything different.
If it doesn't do that it's ok, but I wouldn't expect a language to give an
error where it could do something different.
The spec might say this will give you an error unless f you type it with
one hand while
On Wed, Jan 8, 2014 at 12:07 PM, David Carlisle wrote:
> On 08/01/2014 11:55, Ihe Onwuka wrote:
>
>>
>> for $t in things/thing group by $sex:=$t/@sex return
>> {$t/@sex}
>>
>> the effect of the group by turns {$t/@sex} into a sequence of
>> attribute nod
On Wed, Jan 8, 2014 at 12:26 PM, David Carlisle wrote:
> On 08/01/2014 12:17, Ihe Onwuka wrote:
> list of them, it is not weird at all.
>
>>
>> Furthermore atomizing it makes explicitly clear to the programmer whats
>> gone on whereas barfing about duplicate at
On Wed, Jan 8, 2014 at 12:32 PM, Ihe Onwuka wrote:
>
> On Wed, Jan 8, 2014 at 12:26 PM, David Carlisle wrote:
>
>> On 08/01/2014 12:17, Ihe Onwuka wrote:
>> list of them, it is not weird at all.
>>
>>>
>>> Furthermore atomizing it makes explici
On Wed, Jan 8, 2014 at 12:43 PM, David Carlisle wrote:
> On 08/01/2014 12:32, Ihe Onwuka wrote:
>
>> No I'm not. I want
>>
>> ___
talk@x-query.com
http://x-query.com/mailman/listinfo/talk
On Wed, Jan 8, 2014 at 1:04 PM, David Carlisle wrote:
> On 08/01/2014 12:55, Ihe Onwuka wrote:
>
>> Now thats me done. If it sounds weird to you , well the client doesn't
>> think so.
>>
>
> The client requirements are reasonable, but the code did not match
We were having an orthogonal conversation.
He didn't care about the effect and context of the resulting error message
and I didn't care about the distinction between attribute constructors and
attributes created as part of element constructors.
On Wed, Jan 8, 2014 at 1:59 PM, Andrew Welch wrote
a working
solution - maybe I should have just gotten on with my work.
Hopefully that only leaves the Chinese burn as possible source of confusion
for those who may have had a different cultural childhood. Better to give
than to receive.
On Wed, Jan 8, 2014 at 2:06 PM, Ihe Onwuka wrote:
On Wed, Jan 8, 2014 at 4:22 PM, David Carlisle wrote:
> On 08/01/2014 15:38, Ihe Onwuka wrote:
>
>> because it is going to end up (by whatever process) as an attribute
>> node.
>>
>
>
> That seems to be the cause of your confusion (and your misreading of the
and that referenced from section 2.4.2 where?
or was I supposed to have sussed that from seeing
-
Constructor expressions for various kinds of nodes
if I wasI guess it's my bad.
On Wed, Jan 8, 2014 at 4:29 PM, John Snelson wrote:
> On 08/01/14 16:25, Ihe Onwuka wrote:
&g
uot;.
>
> http://www.w3.org/TR/xquery-30/#id-content
>
> The XQuery spec is not always straight forward to read, but I think it's
> clear in this case. However the XQuery spec is not meant to be a tutorial
> in XQuery - there are better places to learn XQuery.
>
> John
I guess what I said about the error message didn't resonate.
On Wed, Jan 8, 2014 at 4:47 PM, David Carlisle wrote:
> On 08/01/2014 16:39, Ihe Onwuka wrote:
>
>> and that referenced from section 2.4.2 where?
>>
>> or was I supposed to have sussed that from seeing
ee with your critique but xquery != xml. In xquery anything is
> sequable, making it a powerful functional language. That the serialization
> will sometimes yield minor discrepancies is a known fact programmers deal
> with on daily basis.
>
> Thanks for the enlightening discuss
On Wed, Jan 8, 2014 at 5:13 PM, Andrew Welch wrote:
> On 8 January 2014 16:59, David Carlisle wrote:
> Like all gotchas you will get got until you know about them. The
> thing is, xquery has a load more, so if they are all played out like
> this it should be fun.
>
>
Not if I have anything to do
I am running through about a gigabyte worth of xml documents.
The ideal processing scenario is to offer each node in the sequence to
a list of filters and augment different XML documents (or different
branches of one encompassing document) based on the outcome of the
filter.
If anyone has seen
y.I find it so much easier to write and debug if I can
> work in small transformations and let the framework do the plumbing for me.
>
>
> Sent from my iPad (excuse the terseness)
> David A Lee
> d...@calldei.com
>
>
>> On Jan 13, 2014, at 11:12 AM, "Ihe Onwuka
On Mon, Jan 13, 2014 at 11:54 PM, David Lee wrote:
> If your running in exist then pure XQuery is probably as good or better then
> anything else.
> Could you expand on your problem ?
>
I have a collection. Suppose I have 10 different outputs I want and
the decision as to which output a node is
om
> http://www.xmlsh.org
>
>
> -----Original Message-
> From: Ihe Onwuka [mailto:ihe.onw...@gmail.com]
> Sent: Monday, January 13, 2014 4:19 PM
> To: David Lee
> Cc: talk@x-query.com
> Subject: Re: [xquery-talk] Multiple output via a stream of filters
>
> On Mon, Jan 13,
eturn true.
On Tue, Jan 14, 2014 at 12:38 AM, David Lee wrote:
> Could you define what you mean by "output" ?
>
>
> David A. Lee
> d...@calldei.com
> http://www.xmlsh.org
>
>
> -Original Message-
> From: Ihe O
>
> I suspect what your really after is to write multiple results to either
> documents or files.
> XQuery doesn't support this generically but XML Databases like eXist do so
> you might want to ask there.
>
> Or I may have completely misunderstood your question.
>
>
&
I only read the ginormous XML once... I apply the 7 filters to each
node read and it gets allocated to one of the 7 output buckets (hows
that for a semantically neutral term).
On Tue, Jan 14, 2014 at 3:50 AM, Ihe Onwuka wrote:
> Input ginormous xml document containing data relating t
Continuing on the them of recreating the limitations of the physical world.
where someNode does not exist in the document has no effect.
choice rather than something that flows naturally from the conceptual data
> model. It would be nice to have a model that hid this distinction, e.g. by
> m
On Sat, Jan 18, 2014 at 4:39 AM, G. Ken Holman
wrote:
> At 2014-01-17 18:14 +0000, Ihe Onwuka wrote:
>>
>> Continuing on the them of recreating the limitations of the physical
>> world.
>>
>>
>>
>> where someNode does not exist in the document has no
On Sat, Jan 18, 2014 at 9:19 AM, Michael Kay wrote:
>
> On 17 Jan 2014, at 18:14, Ihe Onwuka wrote:
>
>> Continuing on the them of recreating the limitations of the physical world.
>>
>>
>>
>> where someNode does not exist in the document has no effect.
&
On Sat, Jan 18, 2014 at 1:57 PM, Adam Retter wrote:
>>> You know full well that the design isn't going to be improved in a
>>> subsequent release unless there's an issue that's a real stopper, because
>>> people expect backwards compatibility.
>>
>> http://exist.2174344.n4.nabble.com/Signature-
sted in code samples showing the correct syntax for
> comments or explanations about the origins of whatever crazy comment syntax
> they came up with.
>
> One final note to anyone who tries to be helpful: Shove it!
>
> Sent from my iPhone
>
>> On Jan 18, 2014, at 11:02 AM,
the original post.
>
> Sent from my iPhone
>
>> On Jan 18, 2014, at 1:13 PM, Ihe Onwuka wrote:
>>
>> If getting code, syntax, solutions and help with writing your program
>> is your primary and sole objective I recommend StackOverflow.com.
>>
>>
>>
>
On Sat, Jan 18, 2014 at 6:35 PM, Joe Wicentowski wrote:
> In fact, while I (of course) was expecting you to read
>
before you started answering a question that was never asked.
___
talk@x-query.com
http://x-query.com/mailman/listinfo/talk
members of the XQuery Working Group and
may be used against you on a or the mailing list.
On Sat, Jan 18, 2014 at 6:47 PM, Andrew Welch wrote:
>
> He's being satirical.
>
> It's hard not to agree with his observations.
>
> On 18 Jan 2014 18:43, "Ihe Onwuka" wro
On Sat, Jan 18, 2014 at 7:17 PM, Joe Wicentowski wrote:
> Finally, someone understands my pure, noble intentions! I aim to advance the
> state of the field through the following tactics: lob questions phrased so
> vaguely and researched so lightly that rational, compassionate people feel no
>
On Sat, Jan 18, 2014 at 7:17 PM, Joe Wicentowski wrote:
> Finally, someone understands my pure, noble intentions! I aim to advance the
> state of the field through the following tactics: lob questions phrased so
> vaguely and researched so lightly that rational, compassionate people feel no
>
On Sat, Jan 18, 2014 at 8:23 PM, Adam Retter wrote:
> I do not think anyone has mocked you... until just a second ago.
If I hadn't seen it happen to others I wouldn't have mentioned it.
> I think the
> XQuery community and this mailing list are friendly and helpful. I have been
> a part of it fo
orning is dissipating
in the face of a simple query that turns into a runaway task
When the scheduler says terminating does that me... or
rather is it meant to stop saying terminating.
On Tue, Jan 14, 2014 at 11:49 AM, Ihe Onwuka wrote:
> So I killed it. and the bastard is no
/01/2014 10:03, Ihe Onwuka wrote:
>>
>>
>> http://www.biglist.com/cgi-bin/wilma/wilma_hiliter/xsl-l...@lists.mulberrytech.com/201212/msg00024.html?line=98#hilite
>> I also offered privately back then
>
>
> By "back then" do you mean 2012?? doc() is XPath 2 a
Just sharing something I've used to get by with a bash shell
transformation workflow. I have already been served a large portion
of "Why don't you use XPROC/xmlsh" and the answer is because I didn't
think of it at the outset.
The two "tricks" here are process substitution - a means of piping one
; manager and can work with calabash, which I want to try.
>
> Also, Stylus Studio has a great pipeline.
>
> -c
>
>> On Jan 22, 2014, at 10:16 AM, "Ihe Onwuka" wrote:
>>
>> Just sharing something I've used to get by with a bash shell
>> transform
So I have just written
if (@firstpage eq 0) then floor($totalPagesDecimal) else
ceiling($totalPagesDecimal)
but how close would
(floor,ceiling)[@firstpage + 1]($totalPagesDecimal) have been
I'm guessing I would at least have to put some function invoking
paraphenalia around the calls to floor
Then the right answer was very close no just joking.
Thanks - nice that you don't have to do any unnecessary function wrapping.
On Fri, Jan 24, 2014 at 1:26 PM, Christian Grün
wrote:
>> but how close would
>> (floor,ceiling)[@firstpage + 1]($totalPagesDecimal) have been
>
> Try this:
>
..are there any drawbacks to always using the general comparison form
thisThing = ('thatThing')
rather than
thisThing eq 'thatThing'
even when you know that you are dealing with a singleton sequence.
I am guessing this may be an implementation dependent issue.
_
On Sat, Jan 25, 2014 at 9:01 AM, Michael Kay wrote:
>
> The eq operator is easier to optimize because the type conversions it does
> are much simpler (in particular, exploiting indexes is more difficult).
> However, because 90% of the time people use "=", optimizers are likely to
> work hard at
it
downcasting) in effect here. What could be simpler than comparing to
0.
Verily twas a tough spot, I went through every other conditional in
the program first because it looked to me like the least likely
suspect.
On Fri, Jan 24, 2014 at 1:14 PM, Ihe Onwuka wrote:
> So I have just writ
; some pretty funny examples (see, eg [] + [], [] + {}, {} + {}, etc. -- none
> of them ends up being what you might expect).
>
> -Mike
>
>
> On 1/26/14 12:53 AM, Ihe Onwuka wrote:
>>
>> and it came to pass that the innocuous looking conditional in the if
>> stateme
As in ('','8')[.]
What is it called and where is it documented
___
talk@x-query.com
http://x-query.com/mailman/listinfo/talk
I get it... it's a filter expression. Like it.
On Mon, Jan 27, 2014 at 11:46 AM, Ihe Onwuka wrote:
> As in ('','8')[.]
>
> What is it called and where is it documented
___
talk@x-query.com
http://x-query.com/mailman/listinfo/talk
Having given it a bit more than a moments thought I prefer [.] because
it makes it explicit a filtering operation is going on .
I think any opacity is consequent on the syntax - not the semantic .
On Mon, Jan 27, 2014 at 3:18 PM, David Carlisle wrote:
> On 27/01/2014 15:14, David Lee wrote:
>>
I am using one transformation for two different data sources with two
different schemas.
One site may call a resoure readingMaterial another site may call the
same concept a publication, but they are otherwise similar and you may
want to treat them as such.
(xs:string(readingMaterial),xs:string(p
On Mon, Jan 27, 2014 at 3:08 PM, David Carlisle wrote:
> On 27/01/2014 14:55, Ihe Onwuka wrote:
>>
>> I am using one transformation for two different data sources with two
>> different schemas.
>>
>> One site may call a resoure readingMaterial another si
specified.
>
> I would do
>
>(xs:string(readingMaterial),xs:string(publication))[1]
> or just
> (readingMaterial,publication)[1]/string()
>
>
> which gives me readingMaterial if it exists, and if it doesnt exist then
> publication.
> but never both and alway
the zorba list?
https://groups.google.com/forum/#!forum/zorba-users
On Fri, Jan 31, 2014 at 9:37 AM, Hermann Stamm-Wilbrandt
wrote:
>
> Hi,
>
> I just joined this email list yesterday after being on xsl-list and
> xml-dev for quite some years.
>
> Searching markmail [1] for JSONiq [0] seems not
z
> Geschaeftsfuehrung: Dirk Wittkopp
> Sitz der Gesellschaft: Boeblingen
> Registergericht: Amtsgericht Stuttgart, HRB 243294
>
>
>
> From: Ihe Onwuka
>
> To: Hermann Stamm-Wilbrandt/Germany/IBM@IBMDE,
>
> Cc: "talk@x-query.com"
On Sat, Feb 1, 2014 at 11:33 PM, Hermann Stamm-Wilbrandt
wrote:
>
> Last Sylvester there was a thread on Matrix Multiplication in XQuery:
> http://markmail.org/message/7q7qnbbnjo7cljzv?q=list:com.x-query.talk+matrix
> +multiplication
>
> The biggest problem identified was that XQuery does not allo
On Mon, Jan 27, 2014 at 2:45 PM, Michael Kay wrote:
>
> I think the only case I've used in anger is probably count(tokenize($x, '
> ')[.]) which eliminates the zero-length tokens that can arise at the start
> and/or end of the sequence.
>
slight variation
tokenize($url,'/')[.][last()]
that ge
max((80,9)) -> 80
Probably works as designed but it does raise the question of the
utility of min and max in the presence of mixed content (i.e in the
case where you expect 9 because it is > than 8) - or are all bets off
if the content is mixed.
No - it is not an actual use case - I was actually
On Mon, Feb 10, 2014 at 8:17 AM, Michael Kay wrote:
>
> Remember, the M in XML stands for Markup. Markup is an annotation to text
> that can be removed without changing the meaning.
>
Cripes. It's not that far fetched that
8233
might mean
element b (total 8) consists of sub elements of d , e
1 - 100 of 254 matches
Mail list logo
