XQuery Talk Mailing List

why do you care what other people think ?

Mon, 20 May 2013 09:51:20 GMT

Jim,

the yearly Digital Humanities Summer School in Oxford has a technical 
and hands-on focus on matters of XML-based text encoding and 
-transformation. They also have a dedicated Linked Data workshop this 
year (July)—although nothing specifically targeted at xQuery, so 
apologies if off-topic:

http://digital.humanities.ox.ac.uk/dhoxss/2013/workshops.html#humdata

Markus

On 5/20/13 10:08 AM, David Sewell wrote:
> Jim,
>
> The best two websites for general information on DH 
> organizations/events are probably:
>
> http://adho.org/
> http://dh2013.unl.edu/
>
> Also, the people within the DH community who are most interested in 
> XML from a theoretical perspective can usually be found at the 
> Balisage meetings: http://www.balisage.net/.
>
> David
>
> On Mon, 20 May 2013, James Fuller wrote:
>
>> Hello David,
>>
>> On Mon, May 20, 2013 at 3:46 PM, David Sewell  
>> wrote:
>> ...
>>> the oXygen editor/IDE). Even if the community of users is small by
>>> comparison with Javascript or Perl or whatever, the impact of 
>>> projects that
>>> rely on XQuery is, I suspect, much greater than people realize.
>>
>> Great to confirm Uche's reliable instincts.
>>
>> Wondering what are the top venues (conferences, training, etc) where
>> digital humanities folk 'live' ?
>>
>> I would also be interested in hearing what kind of problems these
>> folks are trying to solve.
>>
>> thx, Jim
>>
>


-- 
Markus Flatscher, Editorial and Technical Specialist
ROTUNDA, The University of Virginia Press
PO Box 400314, Charlottesville VA 22904, USA
Courier: 211 Emmet Street South, Charlottesville VA 22903, USA
Email: http://x-query.com/mailman/listinfo/talk
Web: http://rotunda.upress.virginia.edu/

why do you care what other people think ?

Mon, 20 May 2013 09:51:20 GMT

Jim,

the yearly Digital Humanities Summer School in Oxford has a technical 
and hands-on focus on matters of XML-based text encoding and 
-transformation. They also have a dedicated Linked Data workshop this 
year (July)—although nothing specifically targeted at xQuery, so 
apologies if off-topic:

http://digital.humanities.ox.ac.uk/dhoxss/2013/workshops.html#humdata

Markus

On 5/20/13 10:08 AM, David Sewell wrote:
> Jim,
>
> The best two websites for general information on DH 
> organizations/events are probably:
>
> http://adho.org/
> http://dh2013.unl.edu/
>
> Also, the people within the DH community who are most interested in 
> XML from a theoretical perspective can usually be found at the 
> Balisage meetings: http://www.balisage.net/.
>
> David
>
> On Mon, 20 May 2013, James Fuller wrote:
>
>> Hello David,
>>
>> On Mon, May 20, 2013 at 3:46 PM, David Sewell  
>> wrote:
>> ...
>>> the oXygen editor/IDE). Even if the community of users is small by
>>> comparison with Javascript or Perl or whatever, the impact of 
>>> projects that
>>> rely on XQuery is, I suspect, much greater than people realize.
>>
>> Great to confirm Uche's reliable instincts.
>>
>> Wondering what are the top venues (conferences, training, etc) where
>> digital humanities folk 'live' ?
>>
>> I would also be interested in hearing what kind of problems these
>> folks are trying to solve.
>>
>> thx, Jim
>>
>


-- 
Markus Flatscher, Editorial and Technical Specialist
ROTUNDA, The University of Virginia Press
PO Box 400314, Charlottesville VA 22904, USA
Courier: 211 Emmet Street South, Charlottesville VA 22903, USA
Email: http://x-query.com/mailman/listinfo/talk
Web: http://rotunda.upress.virginia.edu/

why do you care what other people think ?

Mon, 20 May 2013 07:08:04 GMT

Jim,

The best two websites for general information on DH organizations/events are 
probably:

http://adho.org/
http://dh2013.unl.edu/

Also, the people within the DH community who are most interested in XML from a 
theoretical perspective can usually be found at the Balisage meetings: 
http://www.balisage.net/.

David

On Mon, 20 May 2013, James Fuller wrote:

> Hello David,
>
> On Mon, May 20, 2013 at 3:46 PM, David Sewell  wrote:
> ...
>> the oXygen editor/IDE). Even if the community of users is small by
>> comparison with Javascript or Perl or whatever, the impact of projects that
>> rely on XQuery is, I suspect, much greater than people realize.
>
> Great to confirm Uche's reliable instincts.
>
> Wondering what are the top venues (conferences, training, etc) where
> digital humanities folk 'live' ?
>
> I would also be interested in hearing what kind of problems these
> folks are trying to solve.
>
> thx, Jim
>

-- 
David Sewell, Editorial and Technical Manager
ROTUNDA, The University of Virginia Press
PO Box 400314, Charlottesville, VA 22904-4314 USA
Email: http://x-query.com/mailman/listinfo/talk   Tel: +1 434 924 9973
Web: http://rotunda.upress.virginia.edu/

why do you care what other people think ?

Mon, 20 May 2013 07:08:04 GMT

Jim,

The best two websites for general information on DH organizations/events are 
probably:

http://adho.org/
http://dh2013.unl.edu/

Also, the people within the DH community who are most interested in XML from a 
theoretical perspective can usually be found at the Balisage meetings: 
http://www.balisage.net/.

David

On Mon, 20 May 2013, James Fuller wrote:

> Hello David,
>
> On Mon, May 20, 2013 at 3:46 PM, David Sewell  wrote:
> ...
>> the oXygen editor/IDE). Even if the community of users is small by
>> comparison with Javascript or Perl or whatever, the impact of projects that
>> rely on XQuery is, I suspect, much greater than people realize.
>
> Great to confirm Uche's reliable instincts.
>
> Wondering what are the top venues (conferences, training, etc) where
> digital humanities folk 'live' ?
>
> I would also be interested in hearing what kind of problems these
> folks are trying to solve.
>
> thx, Jim
>

-- 
David Sewell, Editorial and Technical Manager
ROTUNDA, The University of Virginia Press
PO Box 400314, Charlottesville, VA 22904-4314 USA
Email: http://x-query.com/mailman/listinfo/talk   Tel: +1 434 924 9973
Web: http://rotunda.upress.virginia.edu/

why do you care what other people think ?

Mon, 20 May 2013 06:58:37 GMT

Hello David,

On Mon, May 20, 2013 at 3:46 PM, David Sewell  wrote:
...
> the oXygen editor/IDE). Even if the community of users is small by
> comparison with Javascript or Perl or whatever, the impact of projects that
> rely on XQuery is, I suspect, much greater than people realize.

Great to confirm Uche's reliable instincts.

Wondering what are the top venues (conferences, training, etc) where
digital humanities folk 'live' ?

I would also be interested in hearing what kind of problems these
folks are trying to solve.

thx, Jim

why do you care what other people think ?

Mon, 20 May 2013 06:58:37 GMT

Hello David,

On Mon, May 20, 2013 at 3:46 PM, David Sewell  wrote:
...
> the oXygen editor/IDE). Even if the community of users is small by
> comparison with Javascript or Perl or whatever, the impact of projects that
> rely on XQuery is, I suspect, much greater than people realize.

Great to confirm Uche's reliable instincts.

Wondering what are the top venues (conferences, training, etc) where
digital humanities folk 'live' ?

I would also be interested in hearing what kind of problems these
folks are trying to solve.

thx, Jim

why do you care what other people think ?

Mon, 20 May 2013 06:46:57 GMT

On Sat, 18 May 2013, James Fuller wrote:

> Uche Ogbuji reminded us at last XML Prague to reach out to the digital
> humanities folks ... and I think this is an especially relevant group
> of people we should be trying to engage; librarians love this little
> language.

Speaking as someone in the digital humanities community, I am extremely grateful 
for the work that has been done on XQuery and on the entire suite of XML-related 
W3C technologies (XPath, XSLT, etc.) within the W3C working groups and by 
independent developers. As a self-taught programmer without a computer science 
background, I can't evaluate the theoretical arguments pro or against different 
styles of programming languages; all I know is that in the practical world, it 
is almost inconceivable that the projects I have worked on for the last decade 
could have been achieved as well as they have without XQuery and the tools built 
upon it (notably Saxon, MarkLogic, and the oXygen editor/IDE). Even if the 
community of users is small by comparison with Javascript or Perl or whatever, 
the impact of projects that rely on XQuery is, I suspect, much greater than 
people realize.

David

-- 
David Sewell, Editorial and Technical Manager
ROTUNDA, The University of Virginia Press
PO Box 400314, Charlottesville, VA 22904-4314 USA
Email: http://x-query.com/mailman/listinfo/talk   Tel: +1 434 924 9973
Web: http://rotunda.upress.virginia.edu/

why do you care what other people think ?

Mon, 20 May 2013 06:46:57 GMT

On Sat, 18 May 2013, James Fuller wrote:

> Uche Ogbuji reminded us at last XML Prague to reach out to the digital
> humanities folks ... and I think this is an especially relevant group
> of people we should be trying to engage; librarians love this little
> language.

Speaking as someone in the digital humanities community, I am extremely grateful 
for the work that has been done on XQuery and on the entire suite of XML-related 
W3C technologies (XPath, XSLT, etc.) within the W3C working groups and by 
independent developers. As a self-taught programmer without a computer science 
background, I can't evaluate the theoretical arguments pro or against different 
styles of programming languages; all I know is that in the practical world, it 
is almost inconceivable that the projects I have worked on for the last decade 
could have been achieved as well as they have without XQuery and the tools built 
upon it (notably Saxon, MarkLogic, and the oXygen editor/IDE). Even if the 
community of users is small by comparison with Javascript or Perl or whatever, 
the impact of projects that rely on XQuery is, I suspect, much greater than 
people realize.

David

-- 
David Sewell, Editorial and Technical Manager
ROTUNDA, The University of Virginia Press
PO Box 400314, Charlottesville, VA 22904-4314 USA
Email: http://x-query.com/mailman/listinfo/talk   Tel: +1 434 924 9973
Web: http://rotunda.upress.virginia.edu/

why do you care what other people think ?

Fri, 17 May 2013 23:42:10 GMT

On Sat, May 18, 2013 at 2:32 AM, daniela florescu  wrote:
> I have to apologize on this mailing list first for completely scaring one of
> potential XQuery's customers a couple of days back.
> (he never answered back... oups... I will always wonder if he solved his
> problem...)

reach out to him by email and ask ?

> This is not how science works.

XQuery is a unique, cool, interesting and great programming language,
it combines a query language with the power of a stored proc language
in one = GSD, it plays well with my other favorite tool xslt, XQuery
3.0 'fpness' gives me joy when I program (akin to when I spelunked
deeply in Perl) and joy in programming is a rare and wondrous thing.

Practically speaking, xquery generates career paths and with the
market now recognizing that data led decision making is better then
punditry, things look good for xquery (we should be positive about
that). We are living in a time where all the 'oxygen of choice' is
consumed by javascript ... it means we have to expend more energy to
get the word out about this incredibly productive little language.

With the data revolution going, we have a very good chance to
establish a grass roots foundation, which I think is where our efforts
are best focused versus the 'rocket science' end which I think you are
espousing ... we need materials for training (for students and
teachers), we need to tell students about the potential for a career
programming in xquery.

Uche Ogbuji reminded us at last XML Prague to reach out to the digital
humanities folks ... and I think this is an especially relevant group
of people we should be trying to engage; librarians love this little
language.

Daniela you've probably done more to try and make xquery used and
known within the academic community  (number of papers, advocation,
etc) then anyone; its a real achievement and I hear what you are
saying but I don't fully grok what you are proposing. From one angle,
I think your call for 'more science' could be construed as yet another
variation of the desire for 'wide spread adoption'; the book you read
taught you to ignore other people and yet you want more of these
people to use your favorite tool ?

Confused as to what you are concretely proposing, but interested and
will help 'pull the oar' once I understand.

Jim Fuller

why do you care what other people think ?

Fri, 17 May 2013 23:42:10 GMT

On Sat, May 18, 2013 at 2:32 AM, daniela florescu  wrote:
> I have to apologize on this mailing list first for completely scaring one of
> potential XQuery's customers a couple of days back.
> (he never answered back... oups... I will always wonder if he solved his
> problem...)

reach out to him by email and ask ?

> This is not how science works.

XQuery is a unique, cool, interesting and great programming language,
it combines a query language with the power of a stored proc language
in one = GSD, it plays well with my other favorite tool xslt, XQuery
3.0 'fpness' gives me joy when I program (akin to when I spelunked
deeply in Perl) and joy in programming is a rare and wondrous thing.

Practically speaking, xquery generates career paths and with the
market now recognizing that data led decision making is better then
punditry, things look good for xquery (we should be positive about
that). We are living in a time where all the 'oxygen of choice' is
consumed by javascript ... it means we have to expend more energy to
get the word out about this incredibly productive little language.

With the data revolution going, we have a very good chance to
establish a grass roots foundation, which I think is where our efforts
are best focused versus the 'rocket science' end which I think you are
espousing ... we need materials for training (for students and
teachers), we need to tell students about the potential for a career
programming in xquery.

Uche Ogbuji reminded us at last XML Prague to reach out to the digital
humanities folks ... and I think this is an especially relevant group
of people we should be trying to engage; librarians love this little
language.

Daniela you've probably done more to try and make xquery used and
known within the academic community  (number of papers, advocation,
etc) then anyone; its a real achievement and I hear what you are
saying but I don't fully grok what you are proposing. From one angle,
I think your call for 'more science' could be construed as yet another
variation of the desire for 'wide spread adoption'; the book you read
taught you to ignore other people and yet you want more of these
people to use your favorite tool ?

Confused as to what you are concretely proposing, but interested and
will help 'pull the oar' once I understand.

Jim Fuller

Is it possible to maintain a list of value in XQuery

Thu, 16 May 2013 05:56:41 GMT

On 05/16/2013 08:20 AM, David Lee wrote:
> -----------
>
> This is the "Promised Land of Milk and Honey" that I have been told about ...
>
>    
Look at what has been achieved with Java byte compilation, or -- 
Javascript to ASM ! -- who would have expected that in 1995?  Well, not 
me anyway.  I tend to think this has to do with adoption ... the 
interest in Javascript now is overwhelming, and it is embedded in every 
web application in the world, in possibly the most performance-sensitive 
part of it, so more attention gets paid to improving it.  Also it 
started with a low bar, so the improvement has been impressive.  I 
suspect that with a similar amount of incentive, XQuery would get 
optimized to take advantage of processor optimizations.
>   Adding the ability to "open a crack" from the functional to procedural
> allows users to achieve optimizations simply not practical by the optimizer.  Or atleast be able to write code that they can understand.    This is why I am seriously suggesting that  XQuery and XSLT (and MAYBE XPath ... but not so convinced on xpath) be opened up *philosophically* to non-functional paradigms.   Maybe not the whole floodgate, but bits.
>
>    
Part of the reason XQuery hasn't achieved wider acceptance, in my view, 
is the whole functional mindset.  Forget for a moment about 
performance.  People program in what they like to read and write (if 
they have a choice), preferably in a language that makes it easy to 
conceptualize a solution to a problem. People who take the trouble to 
learn how to program functionally generally come to appreciate it, but 
it doesn't seem to be the most natural idiom, and for the many 
programmers, it presents real difficulties.  One might suppose this is 
due to what is learned in school, but Scheme was the teaching language 
in vogue when I was learning, and still we bred a generation of C 
programmers.  Even XSLT I think presents a barrier of this sort, 
although somehow adoption is greater - perhaps because the 
pattern-matching rules engine fits another conceptual model?

Just stating the semi-obvious: not sure what that means for "the future 
of XQuery" or whatever.

-Mike

Is it possible to maintain a list of value in XQuery

Thu, 16 May 2013 05:56:41 GMT

On 05/16/2013 08:20 AM, David Lee wrote:
> -----------
>
> This is the "Promised Land of Milk and Honey" that I have been told about ...
>
>    
Look at what has been achieved with Java byte compilation, or -- 
Javascript to ASM ! -- who would have expected that in 1995?  Well, not 
me anyway.  I tend to think this has to do with adoption ... the 
interest in Javascript now is overwhelming, and it is embedded in every 
web application in the world, in possibly the most performance-sensitive 
part of it, so more attention gets paid to improving it.  Also it 
started with a low bar, so the improvement has been impressive.  I 
suspect that with a similar amount of incentive, XQuery would get 
optimized to take advantage of processor optimizations.
>   Adding the ability to "open a crack" from the functional to procedural
> allows users to achieve optimizations simply not practical by the optimizer.  Or atleast be able to write code that they can understand.    This is why I am seriously suggesting that  XQuery and XSLT (and MAYBE XPath ... but not so convinced on xpath) be opened up *philosophically* to non-functional paradigms.   Maybe not the whole floodgate, but bits.
>
>    
Part of the reason XQuery hasn't achieved wider acceptance, in my view, 
is the whole functional mindset.  Forget for a moment about 
performance.  People program in what they like to read and write (if 
they have a choice), preferably in a language that makes it easy to 
conceptualize a solution to a problem. People who take the trouble to 
learn how to program functionally generally come to appreciate it, but 
it doesn't seem to be the most natural idiom, and for the many 
programmers, it presents real difficulties.  One might suppose this is 
due to what is learned in school, but Scheme was the teaching language 
in vogue when I was learning, and still we bred a generation of C 
programmers.  Even XSLT I think presents a barrier of this sort, 
although somehow adoption is greater - perhaps because the 
pattern-matching rules engine fits another conceptual model?

Just stating the semi-obvious: not sure what that means for "the future 
of XQuery" or whatever.

-Mike

Is it possible to maintain a list of value in XQuery

Thu, 16 May 2013 05:37:10 GMT

Stop thinking like you only have one tool in your toolbox! Would you use a pliers to drive in a screw? I use many languages and XQuery is one of them. Each language has its strengths and weaknesses.

Sent from my iPhone

On May 16, 2013, at 7:20 AM, David Lee wrote:

>>> Liam

I'm not sure I'm failing to follow you incorrectly here.
------ Someone is failing somethign :)_

Yes, declarative languages, especially with referential transparency,
are often massively easier to optimize than procedural ones. Or rather,
the computer science and mathematics might be harder in some cases, but
the optimizations can be more far-reaching. The down side is that they
tend to start out slower, so it doesn't always balance out. *BUT* they
are also often more maintainable.
-----------

This is the "Promised Land of Milk and Honey" that I have been told about ...
And I can believe it in some cases.
What I boldly propose out of ignorance is that in reality its somewhat (mostly?) BS.
Like the class I took in collage about proving computer programs ... it only worked
if your program was about 3 lines or less beyond that it was *effectively* impossible.
I know many kinds of optimizations are possible (and yea have been achieved) with purely functional languages.
Query Optimization of SQL has some very deep proof of this and I suspect that may have been the rational
behind XQuery and XSLT. But in reality ... at least the reality I have absorbed by attending conferences,
reading papers, talking with implementers, and delving deeply into the guts of real world XQuery and XSLT processors ....
that reality has come up short from the promise. There are a huge range of *possible* optimizations that
simply never get achieved. Its *HARD* ... I am not blaming the implementers. There is Theory and then there is Engineering. (and lets not forget time and money).
One example is parallelism. A purely functional language should be able to be highly paralyzed automatically.
But what we have seen, is that few vendors do this at all, or very little.
I know from Mr Kay's papers he has had some success,
but largely by introducing vendor (and now some standard) specific "hints" into the language to allow for points where parallism can be recognized and he himself has stated that reality has not lived up to the ideal.
The comment about XQuery and cache hits I propose is theory not practice ... unless one implements XQuery in machine
language *directly* (the implementations I have seen are interpretive or late compiled to bytecode ... ),
then the illusion that xquery statements will actually fit snugly in cachelines is an illusion. Now if someone does write a direct XQuery to machine code compiler that might be valid ... maybe there is one, would love to see the paper at Balisage.
So what are the languages people write XQuery compilers in *really* ? What I have seen is C, C++ and Java. I am sure there are more. And *those* implementations are highly optimized using non-functional techniques. So in summary I just dont buy the "functional languages inherantly optimize better" angle. Maybe in theory ... and maybe in some select cases, but not globally in practice.
Global *mutable* variables are another example. To avoid them 100% can be very difficult and results in code that in theory should be optimized but in practice is often not. And can be very "ugly" by some standards.
Adding the ability to "open a crack" from the functional to procedural
allows users to achieve optimizations simply not practical by the optimizer. Or atleast be able to write code that they can understand. This is why I am seriously suggesting that XQuery and XSLT (and MAYBE XPath ... but not so convinced on xpath) be opened up *philosophically* to non-functional paradigms. Maybe not the whole floodgate, but bits.
The bits that vendors have found necessary to introduce ... Yes in theory this lets the cat out of the bag, and the camels nose in the tent and cats will sleep with dogs and the world will end .... But on the other hand maybe just a few carefully chosen idioms that "brake the shackles of pure functional programming" could be a good thing. For one maybe it would encourage vendors to switch over from their vendor specific holes and instead use the standard ones thus making XQuery and XSLT more portable do agree with a layered approach. You dont have to sink the entire ship with this, you can *document* where use of such a bastard might unduly affect the optimizer and let the user decide.
For Layered Approaches, XQuery scripting is one, xproc another, xmlsh another.
But I suggest the layer is too high. I suggest XQuery has grown in use to more complexity then possibly imagined at the beginning. Whole apps are being written in XQuery alone. So maybe the layer should be a little deeper *into* the language instead of above of. ( This is why I am shy of suggesting xpath itself break the mold of purely functional,
it might actually be the layer where pure functional ideology works).

I know from a standards committee perspective this is a nearly impossible task ... so instead I just rant on a mailing list. Maybe someone will see the view ... or intelligently disagree, or just think about it for a second before abandoning it as the ramblings of an insane apostate ... or maybe I will just be beat to a pulp.

All in all a good day :)

-David

_______________________________________________
http://x-query.com/mailman/listinfo/talk
http://x-query.com/mailman/listinfo/talk

Is it possible to maintain a list of value in XQuery

Thu, 16 May 2013 05:37:10 GMT

Stop thinking like you only have one tool in your toolbox! Would you use a pliers to drive in a screw? I use many languages and XQuery is one of them. Each language has its strengths and weaknesses.

Sent from my iPhone

On May 16, 2013, at 7:20 AM, David Lee wrote:

>>> Liam

I'm not sure I'm failing to follow you incorrectly here.
------ Someone is failing somethign :)_

All in all a good day :)

-David

_______________________________________________
http://x-query.com/mailman/listinfo/talk
http://x-query.com/mailman/listinfo/talk

Is it possible to maintain a list of value in XQuery

Thu, 16 May 2013 05:20:26 GMT

>>> Liam

I'm not sure I'm failing to follow you incorrectly here.
------ Someone is failing somethign :)_

All in all a good day :)

-David

Is it possible to maintain a list of value in XQuery

Thu, 16 May 2013 05:20:26 GMT

>>> Liam

I'm not sure I'm failing to follow you incorrectly here.
------ Someone is failing somethign :)_

All in all a good day :)

-David

Is it possible to maintain a list of value in XQuery

Thu, 16 May 2013 02:21:34 GMT

> Could you elaborate on the bigger picture? Are you running through a pile of
> data, trying to accumulate information along the way, and want to use that
> afterwards? Or is it something entirely different that you are trying to
> achieve?

It sounds like they want the equivalent of a TreeSet.... and there are
various ways to achieve that - such as appending to a sequence and
then using distinct-values() on the getter.



-- 
Andrew Welch
http://andrewjwelch.com

Is it possible to maintain a list of value in XQuery

Thu, 16 May 2013 02:21:34 GMT

> Could you elaborate on the bigger picture? Are you running through a pile of
> data, trying to accumulate information along the way, and want to use that
> afterwards? Or is it something entirely different that you are trying to
> achieve?

It sounds like they want the equivalent of a TreeSet.... and there are
various ways to achieve that - such as appending to a sequence and
then using distinct-values() on the getter.



-- 
Andrew Welch
http://andrewjwelch.com

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 22:39:09 GMT

On May 15, 2013, at 9:39 PM, Liam R E Quin wrote:

> On Thu, 2013-05-16 at 00:22 +0000, David Lee wrote:
>> I still am unconvinced that the theory that a purely functional
>> language would enable vastly better optimizations
>> has yet to be realized in the real world and may never be.
> 
> I'm not sure I'm failing to follow you incorrectly here.
> 
> Yes, declarative languages, especially with referential transparency,
> are often massively easier to optimize than procedural ones. Or rather,
> the computer science and mathematics might be harder in some cases, but
> the optimizations can be more far-reaching. The down side is that they
> tend to start out slower, so it doesn't always balance out. *BUT* they
> are also often more maintainable.

Really !? 100 lines of code are more maintainable then 20 (because this 1:5 is how it looks like when you
need to maintain a structure vs. when you have to FAKE like you don't need to update and  life is good and you are "just copying"
the data)

Really !??

Well, there is experimental evidence that says that bugs are linearly proportional with # lines of code.
(Let alone the nightmare that you put your optimizer through, trying to re-invent stuff that you already know, and you spent hours and days trying to hide.)

Great.

> 
> I started to write an essay on optimization of procedural languages and
> realised it was crazy and stopped.

Liam,

out of curiosity, other then writing an essay,  when is the last time you wrote a serious compiler/optimizer for either one !?
(Functional and/or procedural language !? And/or any combination of the above !?)

There are plenty of lessons that anyone can learn doing the "dirty" work. Dirty work is anything that is NOT pdf and slideshare.

Other then number of lines of code there is something else that counts.

 It's called experience.

> Maybe we should have a public XQuery optimization wiki, although I don't
> know how many vendors would be able to share their deep and wonderful
> secrets :)

Yes, such thing would be called a standard benchmark, and historically it triggers people to work on performance and/or publish
(or at least patent :-) their secret sauce.

I asked you for years to trigger W3C to work on this. Never heard back from it.

Thanks
Dana

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 22:39:09 GMT

On May 15, 2013, at 9:39 PM, Liam R E Quin wrote:

> On Thu, 2013-05-16 at 00:22 +0000, David Lee wrote:
>> I still am unconvinced that the theory that a purely functional
>> language would enable vastly better optimizations
>> has yet to be realized in the real world and may never be.
> 
> I'm not sure I'm failing to follow you incorrectly here.
> 
> Yes, declarative languages, especially with referential transparency,
> are often massively easier to optimize than procedural ones. Or rather,
> the computer science and mathematics might be harder in some cases, but
> the optimizations can be more far-reaching. The down side is that they
> tend to start out slower, so it doesn't always balance out. *BUT* they
> are also often more maintainable.

Really !? 100 lines of code are more maintainable then 20 (because this 1:5 is how it looks like when you
need to maintain a structure vs. when you have to FAKE like you don't need to update and  life is good and you are "just copying"
the data)

Really !??

Well, there is experimental evidence that says that bugs are linearly proportional with # lines of code.
(Let alone the nightmare that you put your optimizer through, trying to re-invent stuff that you already know, and you spent hours and days trying to hide.)

Great.

> 
> I started to write an essay on optimization of procedural languages and
> realised it was crazy and stopped.

Liam,

out of curiosity, other then writing an essay,  when is the last time you wrote a serious compiler/optimizer for either one !?
(Functional and/or procedural language !? And/or any combination of the above !?)

There are plenty of lessons that anyone can learn doing the "dirty" work. Dirty work is anything that is NOT pdf and slideshare.

Other then number of lines of code there is something else that counts.

 It's called experience.

> Maybe we should have a public XQuery optimization wiki, although I don't
> know how many vendors would be able to share their deep and wonderful
> secrets :)

Yes, such thing would be called a standard benchmark, and historically it triggers people to work on performance and/or publish
(or at least patent :-) their secret sauce.

I asked you for years to trigger W3C to work on this. Never heard back from it.

Thanks
Dana

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 21:39:42 GMT

On Thu, 2013-05-16 at 00:22 +0000, David Lee wrote:
> I still am unconvinced that the theory that a purely functional
> language would enable vastly better optimizations
> has yet to be realized in the real world and may never be.

I'm not sure I'm failing to follow you incorrectly here.

Yes, declarative languages, especially with referential transparency,
are often massively easier to optimize than procedural ones. Or rather,
the computer science and mathematics might be harder in some cases, but
the optimizations can be more far-reaching. The down side is that they
tend to start out slower, so it doesn't always balance out. *BUT* they
are also often more maintainable.

I started to write an essay on optimization of procedural languages and
realised it was crazy and stopped.

One minor note though, that applies to a great many languages where the
same code is run many times - logging the result of each conditional and
then rewriting the generated code to make the faster branch the more
common is a useful trick that only works in some environments. The speed
difference in a language like C or assembly is because one branch has to
do a jump (goto) to get to the else part, and jumps tend to stall the
CPU pipeline. But even in a language like XQuery you'll tend to get L2
cache performance benefits in such cases. I don't know how significant
they would be, and would be interested in hearing from implementors.

Maybe we should have a public XQuery optimization wiki, although I don't
know how many vendors would be able to share their deep and wonderful
secrets :)

Liam

-- 
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
Ankh: irc.sorcery.net irc.gnome.org freenode/#xml

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 21:39:42 GMT

On Thu, 2013-05-16 at 00:22 +0000, David Lee wrote:
> I still am unconvinced that the theory that a purely functional
> language would enable vastly better optimizations
> has yet to be realized in the real world and may never be.

I'm not sure I'm failing to follow you incorrectly here.

Yes, declarative languages, especially with referential transparency,
are often massively easier to optimize than procedural ones. Or rather,
the computer science and mathematics might be harder in some cases, but
the optimizations can be more far-reaching. The down side is that they
tend to start out slower, so it doesn't always balance out. *BUT* they
are also often more maintainable.

I started to write an essay on optimization of procedural languages and
realised it was crazy and stopped.

One minor note though, that applies to a great many languages where the
same code is run many times - logging the result of each conditional and
then rewriting the generated code to make the faster branch the more
common is a useful trick that only works in some environments. The speed
difference in a language like C or assembly is because one branch has to
do a jump (goto) to get to the else part, and jumps tend to stall the
CPU pipeline. But even in a language like XQuery you'll tend to get L2
cache performance benefits in such cases. I don't know how significant
they would be, and would be interested in hearing from implementors.

Maybe we should have a public XQuery optimization wiki, although I don't
know how many vendors would be able to share their deep and wonderful
secrets :)

Liam

-- 
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
Ankh: irc.sorcery.net irc.gnome.org freenode/#xml

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 17:22:57 GMT

I still am unconvinced that the theory that a purely functional language would enable vastly better optimizations
has yet to be realized in the real world and may never be.   It sounds good, and looks good on paper ... 
And maybe someday a genius will make it so ... and teach us peons how to do it Gods Way.
But in practice using non-functional semantics can produce vastly faster or simplier code sometimes  (or both	)....
Or why would every XQuery vendor put them in ?  They got tired of telling customers they were wrong.
And keeping a straight face ....

Of course this was the same argument for "register" and _asm in C ... and later had the back door "volatile" snuck in where
the assumptions of nothing sneaky happening in the back door were violated .... who knows what "volatile" really means nowadays in a multi-core multi layered cache line system ... The Compiler Knows :)

And yes adding scripting frameworks on top of XQuery is very powerful ... And Good. (why I wrote xmlsh ... ) ...
combining them is a very good mix.  But when your "stuck" with pure XQuery ... or XSLT for that matter no matter how many times the gurus tell you that its for your own good ... it seems more religion then fact ...
Thats my opinion and I'm sticking with it no matter how many facts you want to throw at me :)

----------------------------------------
David A. Lee
http://x-query.com/mailman/listinfo/talk
http://www.xmlsh.org

-----Original Message-----
From: Liam R E Quin [mailto:http://x-query.com/mailman/listinfo/talk] 
Sent: Wednesday, May 15, 2013 7:25 PM
To: David Lee
Cc: http://x-query.com/mailman/listinfo/talk
Subject: Re:  Is it possible to maintain a list of value in XQuery

On Wed, 2013-05-15 at 23:10 +0000, David Lee wrote:
[...]
> I boldly propose that perhaps as a group we step back and get off our
> high horse and admit that some procedural  aspects to XML processing
> be embraced instead of hidden in the dark corners of "vendor
> implementations"  that every single vendor has had to provide because
> pure functional programming  has simply not lived up to its promise.

I don't think it's about a high horse. The XQuery WG spent multiple
years trying to wrestle with adding procedural hooks to XQuery. Part of
the difficulty was that it was a group of people who did not share a
common goal. For example, some people thought it would be nice to offer
a sort of bait-and-switch language where the easy stuff was procedural
but anything hard was functional, a sort of gentle slope learning curve
followed by a cliff, instead of a very steep hill at the start. Others
needed synchronization and orchestration.

My own feeling is still that the scripting extensions would work better
as a framework rather like XProc, orchestrating functional chunks of
XQuery (and/or XSLT) at a higher level, with clearly-defined boundaries
for optimization & transactions. One problem with them as written today
is that it's easy to put a semicolon instead of a comma in places where
it's still legal, but has a different meaning, one which has the
side-effect (!) of effectively disabling a lot of optimization.

At any rate we ended up delaying XQuery 3 for a year or more while
working on the scripting extensions, without really coming to a good
consensus.

Maybe the long term answer is XQuery extensions to JavaScript.

Liam

-- 
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
Ankh: irc.sorcery.net irc.gnome.org freenode/#xml

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 17:22:57 GMT

I still am unconvinced that the theory that a purely functional language would enable vastly better optimizations
has yet to be realized in the real world and may never be.   It sounds good, and looks good on paper ... 
And maybe someday a genius will make it so ... and teach us peons how to do it Gods Way.
But in practice using non-functional semantics can produce vastly faster or simplier code sometimes  (or both	)....
Or why would every XQuery vendor put them in ?  They got tired of telling customers they were wrong.
And keeping a straight face ....

Of course this was the same argument for "register" and _asm in C ... and later had the back door "volatile" snuck in where
the assumptions of nothing sneaky happening in the back door were violated .... who knows what "volatile" really means nowadays in a multi-core multi layered cache line system ... The Compiler Knows :)

And yes adding scripting frameworks on top of XQuery is very powerful ... And Good. (why I wrote xmlsh ... ) ...
combining them is a very good mix.  But when your "stuck" with pure XQuery ... or XSLT for that matter no matter how many times the gurus tell you that its for your own good ... it seems more religion then fact ...
Thats my opinion and I'm sticking with it no matter how many facts you want to throw at me :)

----------------------------------------
David A. Lee
http://x-query.com/mailman/listinfo/talk
http://www.xmlsh.org

-----Original Message-----
From: Liam R E Quin [mailto:http://x-query.com/mailman/listinfo/talk] 
Sent: Wednesday, May 15, 2013 7:25 PM
To: David Lee
Cc: http://x-query.com/mailman/listinfo/talk
Subject: Re:  Is it possible to maintain a list of value in XQuery

On Wed, 2013-05-15 at 23:10 +0000, David Lee wrote:
[...]
> I boldly propose that perhaps as a group we step back and get off our
> high horse and admit that some procedural  aspects to XML processing
> be embraced instead of hidden in the dark corners of "vendor
> implementations"  that every single vendor has had to provide because
> pure functional programming  has simply not lived up to its promise.

I don't think it's about a high horse. The XQuery WG spent multiple
years trying to wrestle with adding procedural hooks to XQuery. Part of
the difficulty was that it was a group of people who did not share a
common goal. For example, some people thought it would be nice to offer
a sort of bait-and-switch language where the easy stuff was procedural
but anything hard was functional, a sort of gentle slope learning curve
followed by a cliff, instead of a very steep hill at the start. Others
needed synchronization and orchestration.

My own feeling is still that the scripting extensions would work better
as a framework rather like XProc, orchestrating functional chunks of
XQuery (and/or XSLT) at a higher level, with clearly-defined boundaries
for optimization & transactions. One problem with them as written today
is that it's easy to put a semicolon instead of a comma in places where
it's still legal, but has a different meaning, one which has the
side-effect (!) of effectively disabling a lot of optimization.

At any rate we ended up delaying XQuery 3 for a year or more while
working on the scripting extensions, without really coming to a good
consensus.

Maybe the long term answer is XQuery extensions to JavaScript.

Liam

-- 
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
Ankh: irc.sorcery.net irc.gnome.org freenode/#xml

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 17:21:14 GMT

On Wed, 2013-05-15 at 23:53 +0000, Eric Bloch wrote:
> 
> > 
> > Maybe the long term answer is XQuery extensions to JavaScript.
> > 
> 
> Are you suggesting a resurrection of E4X?

I wasn't, at least not directly, although E4X isn't as dead as you might
think (e.g. it's in Flash and Acrobat).

Liam

-- 
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
Ankh: irc.sorcery.net irc.gnome.org freenode/#xml

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 17:21:14 GMT

On Wed, 2013-05-15 at 23:53 +0000, Eric Bloch wrote:
> 
> > 
> > Maybe the long term answer is XQuery extensions to JavaScript.
> > 
> 
> Are you suggesting a resurrection of E4X?

I wasn't, at least not directly, although E4X isn't as dead as you might
think (e.g. it's in Flash and Acrobat).

Liam

-- 
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
Ankh: irc.sorcery.net irc.gnome.org freenode/#xml

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 16:53:46 GMT


> 
> Maybe the long term answer is XQuery extensions to JavaScript.
> 

Are you suggesting a resurrection of E4X?

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 16:53:46 GMT


> 
> Maybe the long term answer is XQuery extensions to JavaScript.
> 

Are you suggesting a resurrection of E4X?

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 16:25:25 GMT

On Wed, 2013-05-15 at 23:10 +0000, David Lee wrote:
[...]
> I boldly propose that perhaps as a group we step back and get off our
> high horse and admit that some procedural  aspects to XML processing
> be embraced instead of hidden in the dark corners of "vendor
> implementations"  that every single vendor has had to provide because
> pure functional programming  has simply not lived up to its promise.

I don't think it's about a high horse. The XQuery WG spent multiple
years trying to wrestle with adding procedural hooks to XQuery. Part of
the difficulty was that it was a group of people who did not share a
common goal. For example, some people thought it would be nice to offer
a sort of bait-and-switch language where the easy stuff was procedural
but anything hard was functional, a sort of gentle slope learning curve
followed by a cliff, instead of a very steep hill at the start. Others
needed synchronization and orchestration.

My own feeling is still that the scripting extensions would work better
as a framework rather like XProc, orchestrating functional chunks of
XQuery (and/or XSLT) at a higher level, with clearly-defined boundaries
for optimization & transactions. One problem with them as written today
is that it's easy to put a semicolon instead of a comma in places where
it's still legal, but has a different meaning, one which has the
side-effect (!) of effectively disabling a lot of optimization.

At any rate we ended up delaying XQuery 3 for a year or more while
working on the scripting extensions, without really coming to a good
consensus.

Maybe the long term answer is XQuery extensions to JavaScript.

Liam

-- 
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
Ankh: irc.sorcery.net irc.gnome.org freenode/#xml

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 16:25:25 GMT

On Wed, 2013-05-15 at 23:10 +0000, David Lee wrote:
[...]
> I boldly propose that perhaps as a group we step back and get off our
> high horse and admit that some procedural  aspects to XML processing
> be embraced instead of hidden in the dark corners of "vendor
> implementations"  that every single vendor has had to provide because
> pure functional programming  has simply not lived up to its promise.

I don't think it's about a high horse. The XQuery WG spent multiple
years trying to wrestle with adding procedural hooks to XQuery. Part of
the difficulty was that it was a group of people who did not share a
common goal. For example, some people thought it would be nice to offer
a sort of bait-and-switch language where the easy stuff was procedural
but anything hard was functional, a sort of gentle slope learning curve
followed by a cliff, instead of a very steep hill at the start. Others
needed synchronization and orchestration.

My own feeling is still that the scripting extensions would work better
as a framework rather like XProc, orchestrating functional chunks of
XQuery (and/or XSLT) at a higher level, with clearly-defined boundaries
for optimization & transactions. One problem with them as written today
is that it's easy to put a semicolon instead of a comma in places where
it's still legal, but has a different meaning, one which has the
side-effect (!) of effectively disabling a lot of optimization.

At any rate we ended up delaying XQuery 3 for a year or more while
working on the scripting extensions, without really coming to a good
consensus.

Maybe the long term answer is XQuery extensions to JavaScript.

Liam

-- 
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
Ankh: irc.sorcery.net irc.gnome.org freenode/#xml

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 13:32:04 GMT

On May 15, 2013, at 1:05 PM, David Lee wrote:

> Wow ... I really hoped our ivory tower was immune from personal attacks.... what's up with today a full moon crossing mars?

I just said the code is ugly and potentially slow.

I am attacking the coding style, not the author.  (and BTW, given the design of XQuery, there is no way to write it other way, so it's
definitely not the fault of the author. And by the way, a lot of the design of XQuery is my fault... so why would I complain?)

> If *anyone* on this list, or the entire world for that matter, knows about program optimization I would put Mike at the top of the list, higher than anyone I know personally and likely higher than anyone I know via Nth relation.

I can tell you the world is full of query optimizer experts, that probably know XQuery in and out, and SQL optimization in and out, and 
compiler technology in and out, and functional language compilation, and that you probably never met. 
Not everybody who knows something writes a lot of emails on public mailing lists, that's all.

There is a 30 years old history of optimizing SQL, or compiling functional languages, and lots of people did lots of things, even if you do 
not know about it.

( But I agree that nobody knows XML as well as Mike. I would defer all questions about the details of XML to him....)

> So could we stop that and get back to decency ?  XQuery itself is efficient or not based in the implementation, not the language.

>  And yes some optimizations are hard, possibly so hard they never get done or only done by 
> 

No, I am afraid you do not understand what I am trying to say.

Not that certain optimizations are HARD. Hard you can deal with. You just sit down and do it.

In optimization in general it is IMPOSSIBLE to get it PERFECT (and I have some 25 years of experience with compilers and query optimization, so I think
I know something about it).

An optimization is extremely rarely something that you apply and BOOM, your programs (all of them) are faster. Almost NONE are like this.

There is always a compromise to be made. For some programs that you make faster there are ALWAYS others that you make slower.

This is why optimization is the delicate art of choosing wisely a compromise that would work well IN AVERAGE (whatever that means..).

This is why you need heuristics, for the SPECIAL cases when the user knows better then the compiler -- and there are always cases like this--
and then he/she should have the possibility to say: "Here, I would like my program to be executed THIS way".

Most of the time you will trust a smart optimizer, but not always.

That's what an assignment is. A heuristic.

> As for the ugliness of XQuery code ... point taken.  XQuery is not always pretty ... but then it has many flavors. 
> I personally find it beautiful.
> 
> I am sure one could come up with prettier code.  Although I myself don't see any ugliness in the code  I wrote,
> and don't see how it would be prettier in a procedural fashion ... or why it matters to the poster ...
> Was subjective beauty part of the prerequisite ?
> 
> And the question was asked about XQuery, not XQuery + (Add feature X We are proud of but isn't XQuery)
> Might as well jump to C or Java or Haskell or 

Thanks for liking XQuery ! Given that it looks 90% as the language that bears my design (Quilt, with Jonathan Robie 
and Don Chamberlin) and that it is a functional language because of me (probably), I am certainly taking it as a compliment :-)))

So don't get me wrong, I like it too :-)

It's just that, like any other programming language, is not 100% perfect.

Best
Dana

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 13:32:04 GMT

On May 15, 2013, at 1:05 PM, David Lee wrote:

> Wow ... I really hoped our ivory tower was immune from personal attacks.... what's up with today a full moon crossing mars?

I just said the code is ugly and potentially slow.

I am attacking the coding style, not the author.  (and BTW, given the design of XQuery, there is no way to write it other way, so it's
definitely not the fault of the author. And by the way, a lot of the design of XQuery is my fault... so why would I complain?)

> If *anyone* on this list, or the entire world for that matter, knows about program optimization I would put Mike at the top of the list, higher than anyone I know personally and likely higher than anyone I know via Nth relation.

I can tell you the world is full of query optimizer experts, that probably know XQuery in and out, and SQL optimization in and out, and 
compiler technology in and out, and functional language compilation, and that you probably never met. 
Not everybody who knows something writes a lot of emails on public mailing lists, that's all.

There is a 30 years old history of optimizing SQL, or compiling functional languages, and lots of people did lots of things, even if you do 
not know about it.

( But I agree that nobody knows XML as well as Mike. I would defer all questions about the details of XML to him....)

> So could we stop that and get back to decency ?  XQuery itself is efficient or not based in the implementation, not the language.

>  And yes some optimizations are hard, possibly so hard they never get done or only done by 
> 

No, I am afraid you do not understand what I am trying to say.

Not that certain optimizations are HARD. Hard you can deal with. You just sit down and do it.

In optimization in general it is IMPOSSIBLE to get it PERFECT (and I have some 25 years of experience with compilers and query optimization, so I think
I know something about it).

An optimization is extremely rarely something that you apply and BOOM, your programs (all of them) are faster. Almost NONE are like this.

There is always a compromise to be made. For some programs that you make faster there are ALWAYS others that you make slower.

This is why optimization is the delicate art of choosing wisely a compromise that would work well IN AVERAGE (whatever that means..).

This is why you need heuristics, for the SPECIAL cases when the user knows better then the compiler -- and there are always cases like this--
and then he/she should have the possibility to say: "Here, I would like my program to be executed THIS way".

Most of the time you will trust a smart optimizer, but not always.

That's what an assignment is. A heuristic.

> As for the ugliness of XQuery code ... point taken.  XQuery is not always pretty ... but then it has many flavors. 
> I personally find it beautiful.
> 
> I am sure one could come up with prettier code.  Although I myself don't see any ugliness in the code  I wrote,
> and don't see how it would be prettier in a procedural fashion ... or why it matters to the poster ...
> Was subjective beauty part of the prerequisite ?
> 
> And the question was asked about XQuery, not XQuery + (Add feature X We are proud of but isn't XQuery)
> Might as well jump to C or Java or Haskell or 

Thanks for liking XQuery ! Given that it looks 90% as the language that bears my design (Quilt, with Jonathan Robie 
and Don Chamberlin) and that it is a functional language because of me (probably), I am certainly taking it as a compliment :-)))

So don't get me wrong, I like it too :-)

It's just that, like any other programming language, is not 100% perfect.

Best
Dana

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 13:12:08 GMT

Maps will most probably be added to XQuery 3.1, but there are already
some implementations available (e.g. check out Saxon [1] BaseX [2], or
eXist-db [3]). Note that the exact map syntax is still subject to
change.

[1] http://www.saxonica.com/documentation/index.html#!expressions/xpath30maps
[2] http://docs.basex.org/wiki/Map_Module
[3] http://atomic.exist-db.org/blogs/eXist/XQueryMap
___________________________

On Wed, May 15, 2013 at 9:42 PM, Adam Retter  wrote:
> Sure they will be in XQuery 3.0
>
> On 15 May 2013 20:38, "David Lee"  wrote:
>>
>> Has maps actually made it into xquery 3?  I thought they were xslt only so
>> far
>>
>> Sent from my iPhone
>>
>> On May 15, 2013, at 3:27 PM, "Michael Sokolov"
>>  wrote:
>>
>> > On 5/15/2013 10:47 AM, Kunal Chauhan wrote:
>> >> Hi,
>> >>
>> >> I want to maintain a list of value.
>> >>
>> >> for eg:
>> >> initially I have blank list and through some process I add values in to
>> >> the list.
>> >>
>> >> like (Apple,Banana,Cherry)
>> >>
>> >> now, when get Apple as an output 2nd time it will check into the list.
>> >> If present than don't add value into the list otherwise add it.
>> >> At last I will return the list.
>> >>
>> >> I don't know whether it's possible or not.
>> >> But this there any work around.
>> > You might want to look into maps, a new feature in XQuery 3.0, which
>> > provide a natural and (probably) efficient way to do this, but whether that
>> > is available to you will depend on which processor you are using.
>> >
>> > -Mike
>> > _______________________________________________
>> > http://x-query.com/mailman/listinfo/talk
>> > http://x-query.com/mailman/listinfo/talk
>>
>> _______________________________________________
>> http://x-query.com/mailman/listinfo/talk
>> http://x-query.com/mailman/listinfo/talk
>
>
> _______________________________________________
> http://x-query.com/mailman/listinfo/talk
> http://x-query.com/mailman/listinfo/talk

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 13:12:08 GMT

Maps will most probably be added to XQuery 3.1, but there are already
some implementations available (e.g. check out Saxon [1] BaseX [2], or
eXist-db [3]). Note that the exact map syntax is still subject to
change.

[1] http://www.saxonica.com/documentation/index.html#!expressions/xpath30maps
[2] http://docs.basex.org/wiki/Map_Module
[3] http://atomic.exist-db.org/blogs/eXist/XQueryMap
___________________________

On Wed, May 15, 2013 at 9:42 PM, Adam Retter  wrote:
> Sure they will be in XQuery 3.0
>
> On 15 May 2013 20:38, "David Lee"  wrote:
>>
>> Has maps actually made it into xquery 3?  I thought they were xslt only so
>> far
>>
>> Sent from my iPhone
>>
>> On May 15, 2013, at 3:27 PM, "Michael Sokolov"
>>  wrote:
>>
>> > On 5/15/2013 10:47 AM, Kunal Chauhan wrote:
>> >> Hi,
>> >>
>> >> I want to maintain a list of value.
>> >>
>> >> for eg:
>> >> initially I have blank list and through some process I add values in to
>> >> the list.
>> >>
>> >> like (Apple,Banana,Cherry)
>> >>
>> >> now, when get Apple as an output 2nd time it will check into the list.
>> >> If present than don't add value into the list otherwise add it.
>> >> At last I will return the list.
>> >>
>> >> I don't know whether it's possible or not.
>> >> But this there any work around.
>> > You might want to look into maps, a new feature in XQuery 3.0, which
>> > provide a natural and (probably) efficient way to do this, but whether that
>> > is available to you will depend on which processor you are using.
>> >
>> > -Mike
>> > _______________________________________________
>> > http://x-query.com/mailman/listinfo/talk
>> > http://x-query.com/mailman/listinfo/talk
>>
>> _______________________________________________
>> http://x-query.com/mailman/listinfo/talk
>> http://x-query.com/mailman/listinfo/talk
>
>
> _______________________________________________
> http://x-query.com/mailman/listinfo/talk
> http://x-query.com/mailman/listinfo/talk

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 13:05:53 GMT

Wow ... I really hoped our ivory tower was immune from personal attacks.... what's up with today a full moon crossing mars?
If *anyone* on this list, or the entire world for that matter, knows about program optimization I would put Mike at the top of the list, higher than anyone I know personally and likely higher than anyone I know via Nth relation.
So could we stop that and get back to decency ?  XQuery itself is efficient or not based in the implementation, not the language.  And yes some optimizations are hard, possibly so hard they never get done or only done by 

As for the ugliness of XQuery code ... point taken.  XQuery is not always pretty ... but then it has many flavors. 
I personally find it beautiful.

I am sure one could come up with prettier code.  Although I myself don't see any ugliness in the code  I wrote,
and don't see how it would be prettier in a procedural fashion ... or why it matters to the poster ...
Was subjective beauty part of the prerequisite ?

And the question was asked about XQuery, not XQuery + (Add feature X We are proud of but isn't XQuery)
Might as well jump to C or Java or Haskell or 


BUT ... if you want an answer to "Could I use another language instead of XQuery but is close enough to get on this list"
I of course recommend xmlsh ... it solves ALL problems and is prettier than any other language.
www.xmlsh.org



 ----------------------------------------
David A. Lee
http://x-query.com/mailman/listinfo/talk
http://www.xmlsh.org

-----Original Message-----
From: daniela florescu [mailto:http://x-query.com/mailman/listinfo/talk] 
Sent: Wednesday, May 15, 2013 2:24 PM
To: Michael Kay
Cc: http://x-query.com/mailman/listinfo/talk; David Lee; Kunal Chauhan
Subject: Re:  Is it possible to maintain a list of value in XQuery

> 
> No, if you are horrified by the inefficiency of this code then switch to an XQuery processor with a decent optimizer.

You know, Michael, I would mellow down a little bit if I were you.

Or at least try some benchmarks before hand (I did, and the results might surprise you ).

If you can strongly say such a statement, it either that you never understood how complicate of a problem 
optimization is (how many different cases, how to do a compromise between complexity of program vs. size of the data,
how to make sure that the optimization time stays reasonable, etc, etc,), or you are totally dishonest.

So, I don't know, a more mellow approach would be probably better.

=====

As a matter of fact,  I wasn't even talking about runtime when I wrote that email. (even though it applies to execution time, too).

I was horrified about HOW UGLY that code looked.

As a programmer, I would't like to write that.

Cheers
Dana

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 13:05:53 GMT

Wow ... I really hoped our ivory tower was immune from personal attacks.... what's up with today a full moon crossing mars?
If *anyone* on this list, or the entire world for that matter, knows about program optimization I would put Mike at the top of the list, higher than anyone I know personally and likely higher than anyone I know via Nth relation.
So could we stop that and get back to decency ?  XQuery itself is efficient or not based in the implementation, not the language.  And yes some optimizations are hard, possibly so hard they never get done or only done by 

As for the ugliness of XQuery code ... point taken.  XQuery is not always pretty ... but then it has many flavors. 
I personally find it beautiful.

I am sure one could come up with prettier code.  Although I myself don't see any ugliness in the code  I wrote,
and don't see how it would be prettier in a procedural fashion ... or why it matters to the poster ...
Was subjective beauty part of the prerequisite ?

And the question was asked about XQuery, not XQuery + (Add feature X We are proud of but isn't XQuery)
Might as well jump to C or Java or Haskell or 


BUT ... if you want an answer to "Could I use another language instead of XQuery but is close enough to get on this list"
I of course recommend xmlsh ... it solves ALL problems and is prettier than any other language.
www.xmlsh.org



 ----------------------------------------
David A. Lee
http://x-query.com/mailman/listinfo/talk
http://www.xmlsh.org

-----Original Message-----
From: daniela florescu [mailto:http://x-query.com/mailman/listinfo/talk] 
Sent: Wednesday, May 15, 2013 2:24 PM
To: Michael Kay
Cc: http://x-query.com/mailman/listinfo/talk; David Lee; Kunal Chauhan
Subject: Re:  Is it possible to maintain a list of value in XQuery

> 
> No, if you are horrified by the inefficiency of this code then switch to an XQuery processor with a decent optimizer.

You know, Michael, I would mellow down a little bit if I were you.

Or at least try some benchmarks before hand (I did, and the results might surprise you ).

If you can strongly say such a statement, it either that you never understood how complicate of a problem 
optimization is (how many different cases, how to do a compromise between complexity of program vs. size of the data,
how to make sure that the optimization time stays reasonable, etc, etc,), or you are totally dishonest.

So, I don't know, a more mellow approach would be probably better.

=====

As a matter of fact,  I wasn't even talking about runtime when I wrote that email. (even though it applies to execution time, too).

I was horrified about HOW UGLY that code looked.

As a programmer, I would't like to write that.

Cheers
Dana

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 12:42:20 GMT

Sure they will be in XQuery 3.0
On 15 May 2013 20:38, "David Lee"  wrote:

> Has maps actually made it into xquery 3?  I thought they were xslt only so
> far
>
> Sent from my iPhone
>
> On May 15, 2013, at 3:27 PM, "Michael Sokolov" <
> http://x-query.com/mailman/listinfo/talk> wrote:
>
> > On 5/15/2013 10:47 AM, Kunal Chauhan wrote:
> >> Hi,
> >>
> >> I want to maintain a list of value.
> >>
> >> for eg:
> >> initially I have blank list and through some process I add values in to
> the list.
> >>
> >> like (Apple,Banana,Cherry)
> >>
> >> now, when get Apple as an output 2nd time it will check into the list.
> >> If present than don't add value into the list otherwise add it.
> >> At last I will return the list.
> >>
> >> I don't know whether it's possible or not.
> >> But this there any work around.
> > You might want to look into maps, a new feature in XQuery 3.0, which
> provide a natural and (probably) efficient way to do this, but whether that
> is available to you will depend on which processor you are using.
> >
> > -Mike
> > _______________________________________________
> > http://x-query.com/mailman/listinfo/talk
> > http://x-query.com/mailman/listinfo/talk
>
> _______________________________________________
> http://x-query.com/mailman/listinfo/talk
> http://x-query.com/mailman/listinfo/talk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 12:42:20 GMT

Sure they will be in XQuery 3.0
On 15 May 2013 20:38, "David Lee"  wrote:

> Has maps actually made it into xquery 3?  I thought they were xslt only so
> far
>
> Sent from my iPhone
>
> On May 15, 2013, at 3:27 PM, "Michael Sokolov" <
> http://x-query.com/mailman/listinfo/talk> wrote:
>
> > On 5/15/2013 10:47 AM, Kunal Chauhan wrote:
> >> Hi,
> >>
> >> I want to maintain a list of value.
> >>
> >> for eg:
> >> initially I have blank list and through some process I add values in to
> the list.
> >>
> >> like (Apple,Banana,Cherry)
> >>
> >> now, when get Apple as an output 2nd time it will check into the list.
> >> If present than don't add value into the list otherwise add it.
> >> At last I will return the list.
> >>
> >> I don't know whether it's possible or not.
> >> But this there any work around.
> > You might want to look into maps, a new feature in XQuery 3.0, which
> provide a natural and (probably) efficient way to do this, but whether that
> is available to you will depend on which processor you are using.
> >
> > -Mike
> > _______________________________________________
> > http://x-query.com/mailman/listinfo/talk
> > http://x-query.com/mailman/listinfo/talk
>
> _______________________________________________
> http://x-query.com/mailman/listinfo/talk
> http://x-query.com/mailman/listinfo/talk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 12:36:40 GMT

Has maps actually made it into xquery 3?  I thought they were xslt only so far

Sent from my iPhone

On May 15, 2013, at 3:27 PM, "Michael Sokolov"  wrote:

> On 5/15/2013 10:47 AM, Kunal Chauhan wrote:
>> Hi,
>> 
>> I want to maintain a list of value.
>> 
>> for eg:
>> initially I have blank list and through some process I add values in to the list.
>> 
>> like (Apple,Banana,Cherry)
>> 
>> now, when get Apple as an output 2nd time it will check into the list.
>> If present than don't add value into the list otherwise add it.
>> At last I will return the list.
>> 
>> I don't know whether it's possible or not.
>> But this there any work around.
> You might want to look into maps, a new feature in XQuery 3.0, which provide a natural and (probably) efficient way to do this, but whether that is available to you will depend on which processor you are using.
> 
> -Mike
> _______________________________________________
> http://x-query.com/mailman/listinfo/talk
> http://x-query.com/mailman/listinfo/talk

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 12:36:40 GMT

Has maps actually made it into xquery 3?  I thought they were xslt only so far

Sent from my iPhone

On May 15, 2013, at 3:27 PM, "Michael Sokolov"  wrote:

> On 5/15/2013 10:47 AM, Kunal Chauhan wrote:
>> Hi,
>> 
>> I want to maintain a list of value.
>> 
>> for eg:
>> initially I have blank list and through some process I add values in to the list.
>> 
>> like (Apple,Banana,Cherry)
>> 
>> now, when get Apple as an output 2nd time it will check into the list.
>> If present than don't add value into the list otherwise add it.
>> At last I will return the list.
>> 
>> I don't know whether it's possible or not.
>> But this there any work around.
> You might want to look into maps, a new feature in XQuery 3.0, which provide a natural and (probably) efficient way to do this, but whether that is available to you will depend on which processor you are using.
> 
> -Mike
> _______________________________________________
> http://x-query.com/mailman/listinfo/talk
> http://x-query.com/mailman/listinfo/talk

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 12:26:22 GMT

On 5/15/2013 10:47 AM, Kunal Chauhan wrote:
> Hi,
>
> I want to maintain a list of value.
>
> for eg:
> initially I have blank list and through some process I add values in 
> to the list.
>
> like (Apple,Banana,Cherry)
>
> now, when get Apple as an output 2nd time it will check into the list.
> If present than don't add value into the list otherwise add it.
> At last I will return the list.
>
> I don't know whether it's possible or not.
> But this there any work around.
You might want to look into maps, a new feature in XQuery 3.0, which 
provide a natural and (probably) efficient way to do this, but whether 
that is available to you will depend on which processor you are using.

-Mike

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 12:26:22 GMT

On 5/15/2013 10:47 AM, Kunal Chauhan wrote:
> Hi,
>
> I want to maintain a list of value.
>
> for eg:
> initially I have blank list and through some process I add values in 
> to the list.
>
> like (Apple,Banana,Cherry)
>
> now, when get Apple as an output 2nd time it will check into the list.
> If present than don't add value into the list otherwise add it.
> At last I will return the list.
>
> I don't know whether it's possible or not.
> But this there any work around.
You might want to look into maps, a new feature in XQuery 3.0, which 
provide a natural and (probably) efficient way to do this, but whether 
that is available to you will depend on which processor you are using.

-Mike

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 11:23:42 GMT

> 
> No, if you are horrified by the inefficiency of this code then switch to an XQuery processor with a decent optimizer.

You know, Michael, I would mellow down a little bit if I were you.

Or at least try some benchmarks before hand (I did, and the results might surprise you ).

If you can strongly say such a statement, it either that you never understood how complicate of a problem 
optimization is (how many different cases, how to do a compromise between complexity of program vs. size of the data,
how to make sure that the optimization time stays reasonable, etc, etc,), or you are totally dishonest.

So, I don't know, a more mellow approach would be probably better.

=====

As a matter of fact,  I wasn't even talking about runtime when I wrote that email. (even though it applies to execution time, too).

I was horrified about HOW UGLY that code looked.

As a programmer, I would't like to write that.

Cheers
Dana

Is it possible to maintain a list of value in XQuery

Wed, 15 May 2013 11:23:42 GMT

> 
> No, if you are horrified by the inefficiency of this code then switch to an XQuery processor with a decent optimizer.

You know, Michael, I would mellow down a little bit if I were you.

Or at least try some benchmarks before hand (I did, and the results might surprise you ).

If you can strongly say such a statement, it either that you never understood how complicate of a problem 
optimization is (how many different cases, how to do a compromise between complexity of program vs. size of the data,
how to make sure that the optimization time stays reasonable, etc, etc,), or you are totally dishonest.

So, I don't know, a more mellow approach would be probably better.

=====

As a matter of fact,  I wasn't even talking about runtime when I wrote that email. (even though it applies to execution time, too).

I was horrified about HOW UGLY that code looked.

As a programmer, I would't like to write that.

Cheers
Dana

Fuctions and variables in replacement string of fn:replace()

Wed, 01 May 2013 06:43:00 GMT

Thanks, Michael, for the clarification. I'm aware that fn:analyze-string is 
(with XPath 3.0) the right tool for this kind of job, I was just confused about 
the extent to which fn:replace() was capable of being a poor-man's equivalent. 
The answer then is "not much".

David

On Wed, 1 May 2013, Michael Kay wrote:

>
> On 1 May 2013, at 04:14, Liam R E Quin wrote:
>
>> On Tue, 2013-04-30 at 23:01 -0400, David Sewell wrote:
>>> When using fn:replace(), is it kosher or illegal to construct the
>>> replacement string dynamically using a function?
>
> Yes. XQuery is an orthogonal language, any expression can be replaced by a different expression that returns the same value.
>
>>> In some cases this
>>> seems to work (tested in Saxon and MarkLogic):
>>>
>>> xquery version "1.0";
>>> let $string := "Now, let's SEND OUT for QUICHE!!"
>>> let $match := "[A-Z][A-Z]+"
>>> return replace($string, $match, concat("$0","$0"))
>>> ==> Now, let's SENDSEND OUTOUT for QUICHEQUICHE!!
>>>
>>> but in other cases it doesn't. For example, lower-case("$0") has no
>>> effect.
>
> It should have no effect. It's the same as replace($string, $match, '$0') which replaces every string that matches $match with itself.
>
>>> And substring("$0", 1, 1) throws an error.
>
> Because '$' is not a valid replacement string.
>
> OK, I think I've understood what you wanted (maybe!). You didn't want to construct the replacement string using a function, you wanted to apply a function to the matching substrings found by the matching operation: you want a higher-order replace(). Saxon has such a thing in the form of saxon:analyze-string (see http://www.saxonica.com/documentation/#!functions/saxon/analyze-string) but in 3.0 the WG took a different direction in its definition of fn:analyze-string(), which is probably easier for ordinary mortals to cope with: http://www.w3.org/TR/xpath-functions-30/#func-analyze-string
>>
> Michael Kay
> Saxonica
>
>
> _______________________________________________
> http://x-query.com/mailman/listinfo/talk
> http://x-query.com/mailman/listinfo/talk
>

-- 
David Sewell, Editorial and Technical Manager
ROTUNDA, The University of Virginia Press
PO Box 400314, Charlottesville, VA 22904-4314 USA
Email: http://x-query.com/mailman/listinfo/talk   Tel: +1 434 924 9973
Web: http://rotunda.upress.virginia.edu/

Fuctions and variables in replacement string of fn:replace()

Wed, 01 May 2013 06:43:00 GMT

Thanks, Michael, for the clarification. I'm aware that fn:analyze-string is 
(with XPath 3.0) the right tool for this kind of job, I was just confused about 
the extent to which fn:replace() was capable of being a poor-man's equivalent. 
The answer then is "not much".

David

On Wed, 1 May 2013, Michael Kay wrote:

>
> On 1 May 2013, at 04:14, Liam R E Quin wrote:
>
>> On Tue, 2013-04-30 at 23:01 -0400, David Sewell wrote:
>>> When using fn:replace(), is it kosher or illegal to construct the
>>> replacement string dynamically using a function?
>
> Yes. XQuery is an orthogonal language, any expression can be replaced by a different expression that returns the same value.
>
>>> In some cases this
>>> seems to work (tested in Saxon and MarkLogic):
>>>
>>> xquery version "1.0";
>>> let $string := "Now, let's SEND OUT for QUICHE!!"
>>> let $match := "[A-Z][A-Z]+"
>>> return replace($string, $match, concat("$0","$0"))
>>> ==> Now, let's SENDSEND OUTOUT for QUICHEQUICHE!!
>>>
>>> but in other cases it doesn't. For example, lower-case("$0") has no
>>> effect.
>
> It should have no effect. It's the same as replace($string, $match, '$0') which replaces every string that matches $match with itself.
>
>>> And substring("$0", 1, 1) throws an error.
>
> Because '$' is not a valid replacement string.
>
> OK, I think I've understood what you wanted (maybe!). You didn't want to construct the replacement string using a function, you wanted to apply a function to the matching substrings found by the matching operation: you want a higher-order replace(). Saxon has such a thing in the form of saxon:analyze-string (see http://www.saxonica.com/documentation/#!functions/saxon/analyze-string) but in 3.0 the WG took a different direction in its definition of fn:analyze-string(), which is probably easier for ordinary mortals to cope with: http://www.w3.org/TR/xpath-functions-30/#func-analyze-string
>>
> Michael Kay
> Saxonica
>
>
> _______________________________________________
> http://x-query.com/mailman/listinfo/talk
> http://x-query.com/mailman/listinfo/talk
>

-- 
David Sewell, Editorial and Technical Manager
ROTUNDA, The University of Virginia Press
PO Box 400314, Charlottesville, VA 22904-4314 USA
Email: http://x-query.com/mailman/listinfo/talk   Tel: +1 434 924 9973
Web: http://rotunda.upress.virginia.edu/

Fuctions and variables in replacement string of fn:replace()

Wed, 01 May 2013 01:32:38 GMT

Or switch to xsl:analyze-string..

;-)

> -----Oorspronkelijk bericht-----
> Van: http://x-query.com/mailman/listinfo/talk [mailto:http://x-query.com/mailman/listinfo/talk]
> Namens Michael Kay
> Verzonden: woensdag 1 mei 2013 10:02
> Aan: http://x-query.com/mailman/listinfo/talk
> CC: XQuery Talk; David Sewell
> Onderwerp: Re:  Fuctions and variables in replacement
string
> of fn:replace()
>
>
> On 1 May 2013, at 04:14, Liam R E Quin wrote:
>
> > On Tue, 2013-04-30 at 23:01 -0400, David Sewell wrote:
> >> When using fn:replace(), is it kosher or illegal to construct the
> >> replacement string dynamically using a function?
>
> Yes. XQuery is an orthogonal language, any expression can be replaced by
a
> different expression that returns the same value.
>
> >> In some cases this
> >> seems to work (tested in Saxon and MarkLogic):
> >>
> >> xquery version "1.0";
> >> let $string := "Now, let's SEND OUT for QUICHE!!"
> >> let $match := "[A-Z][A-Z]+"
> >> return replace($string, $match, concat("$0","$0"))
> >> ==> Now, let's SENDSEND OUTOUT for QUICHEQUICHE!!
> >>
> >> but in other cases it doesn't. For example, lower-case("$0") has no
> >> effect.
>
> It should have no effect. It's the same as replace($string, $match,
'$0')
> which replaces every string that matches $match with itself.
>
> >> And substring("$0", 1, 1) throws an error.
>
> Because '$' is not a valid replacement string.
>
> OK, I think I've understood what you wanted (maybe!). You didn't want to
> construct the replacement string using a function, you wanted to apply a
> function to the matching substrings found by the matching operation: you
> want a higher-order replace(). Saxon has such a thing in the form of
> saxon:analyze-string (see
> http://www.saxonica.com/documentation/#!functions/saxon/analyze-
> string) but in 3.0 the WG took a different direction in its definition
of
> fn:analyze-string(), which is probably easier for ordinary mortals to
cope
> with: http://www.w3.org/TR/xpath-functions-30/#func-analyze-string
> >
> Michael Kay
> Saxonica
>
>
> _______________________________________________
> http://x-query.com/mailman/listinfo/talk
> http://x-query.com/mailman/listinfo/talk

Fuctions and variables in replacement string of fn:replace()

Wed, 01 May 2013 01:32:38 GMT

Or switch to xsl:analyze-string..

;-)

> -----Oorspronkelijk bericht-----
> Van: http://x-query.com/mailman/listinfo/talk [mailto:http://x-query.com/mailman/listinfo/talk]
> Namens Michael Kay
> Verzonden: woensdag 1 mei 2013 10:02
> Aan: http://x-query.com/mailman/listinfo/talk
> CC: XQuery Talk; David Sewell
> Onderwerp: Re:  Fuctions and variables in replacement
string
> of fn:replace()
>
>
> On 1 May 2013, at 04:14, Liam R E Quin wrote:
>
> > On Tue, 2013-04-30 at 23:01 -0400, David Sewell wrote:
> >> When using fn:replace(), is it kosher or illegal to construct the
> >> replacement string dynamically using a function?
>
> Yes. XQuery is an orthogonal language, any expression can be replaced by
a
> different expression that returns the same value.
>
> >> In some cases this
> >> seems to work (tested in Saxon and MarkLogic):
> >>
> >> xquery version "1.0";
> >> let $string := "Now, let's SEND OUT for QUICHE!!"
> >> let $match := "[A-Z][A-Z]+"
> >> return replace($string, $match, concat("$0","$0"))
> >> ==> Now, let's SENDSEND OUTOUT for QUICHEQUICHE!!
> >>
> >> but in other cases it doesn't. For example, lower-case("$0") has no
> >> effect.
>
> It should have no effect. It's the same as replace($string, $match,
'$0')
> which replaces every string that matches $match with itself.
>
> >> And substring("$0", 1, 1) throws an error.
>
> Because '$' is not a valid replacement string.
>
> OK, I think I've understood what you wanted (maybe!). You didn't want to
> construct the replacement string using a function, you wanted to apply a
> function to the matching substrings found by the matching operation: you
> want a higher-order replace(). Saxon has such a thing in the form of
> saxon:analyze-string (see
> http://www.saxonica.com/documentation/#!functions/saxon/analyze-
> string) but in 3.0 the WG took a different direction in its definition
of
> fn:analyze-string(), which is probably easier for ordinary mortals to
cope
> with: http://www.w3.org/TR/xpath-functions-30/#func-analyze-string
> >
> Michael Kay
> Saxonica
>
>
> _______________________________________________
> http://x-query.com/mailman/listinfo/talk
> http://x-query.com/mailman/listinfo/talk

Fuctions and variables in replacement string of fn:replace()

Wed, 01 May 2013 01:02:07 GMT

On 1 May 2013, at 04:14, Liam R E Quin wrote:

> On Tue, 2013-04-30 at 23:01 -0400, David Sewell wrote:
>> When using fn:replace(), is it kosher or illegal to construct the
>> replacement string dynamically using a function?

Yes. XQuery is an orthogonal language, any expression can be replaced by a different expression that returns the same value.

>> In some cases this
>> seems to work (tested in Saxon and MarkLogic):
>> 
>> xquery version "1.0";
>> let $string := "Now, let's SEND OUT for QUICHE!!"
>> let $match := "[A-Z][A-Z]+"
>> return replace($string, $match, concat("$0","$0"))
>> ==> Now, let's SENDSEND OUTOUT for QUICHEQUICHE!!
>> 
>> but in other cases it doesn't. For example, lower-case("$0") has no
>> effect.

It should have no effect. It's the same as replace($string, $match, '$0') which replaces every string that matches $match with itself.

>> And substring("$0", 1, 1) throws an error.

Because '$' is not a valid replacement string.

OK, I think I've understood what you wanted (maybe!). You didn't want to construct the replacement string using a function, you wanted to apply a function to the matching substrings found by the matching operation: you want a higher-order replace(). Saxon has such a thing in the form of saxon:analyze-string (see http://www.saxonica.com/documentation/#!functions/saxon/analyze-string) but in 3.0 the WG took a different direction in its definition of fn:analyze-string(), which is probably easier for ordinary mortals to cope with: http://www.w3.org/TR/xpath-functions-30/#func-analyze-string
> 
Michael Kay
Saxonica

Fuctions and variables in replacement string of fn:replace()

Wed, 01 May 2013 01:02:07 GMT

On 1 May 2013, at 04:14, Liam R E Quin wrote:

> On Tue, 2013-04-30 at 23:01 -0400, David Sewell wrote:
>> When using fn:replace(), is it kosher or illegal to construct the
>> replacement string dynamically using a function?

Yes. XQuery is an orthogonal language, any expression can be replaced by a different expression that returns the same value.

>> In some cases this
>> seems to work (tested in Saxon and MarkLogic):
>> 
>> xquery version "1.0";
>> let $string := "Now, let's SEND OUT for QUICHE!!"
>> let $match := "[A-Z][A-Z]+"
>> return replace($string, $match, concat("$0","$0"))
>> ==> Now, let's SENDSEND OUTOUT for QUICHEQUICHE!!
>> 
>> but in other cases it doesn't. For example, lower-case("$0") has no
>> effect.

It should have no effect. It's the same as replace($string, $match, '$0') which replaces every string that matches $match with itself.

>> And substring("$0", 1, 1) throws an error.

Because '$' is not a valid replacement string.

OK, I think I've understood what you wanted (maybe!). You didn't want to construct the replacement string using a function, you wanted to apply a function to the matching substrings found by the matching operation: you want a higher-order replace(). Saxon has such a thing in the form of saxon:analyze-string (see http://www.saxonica.com/documentation/#!functions/saxon/analyze-string) but in 3.0 the WG took a different direction in its definition of fn:analyze-string(), which is probably easier for ordinary mortals to cope with: http://www.w3.org/TR/xpath-functions-30/#func-analyze-string
> 
Michael Kay
Saxonica

Fuctions and variables in replacement string of fn:replace()

Tue, 30 Apr 2013 20:14:27 GMT

On Tue, 2013-04-30 at 23:01 -0400, David Sewell wrote:
> When using fn:replace(), is it kosher or illegal to construct the
> replacement string dynamically using a function? In some cases this
> seems to work (tested in Saxon and MarkLogic):
> 
> xquery version "1.0";
> let $string := "Now, let's SEND OUT for QUICHE!!"
> let $match := "[A-Z][A-Z]+"
> return replace($string, $match, concat("$0","$0"))
> ==> Now, let's SENDSEND OUTOUT for QUICHEQUICHE!!
> 
> but in other cases it doesn't. For example, lower-case("$0") has no
> effect. And substring("$0", 1, 1) throws an error.

In your first example,
return replace($string, $match, concat("$0","$0"))
the replace function gets called with 3 arguments:
    replace(
      "Now, let's SEND OUT for QUICHE!!",
      "[A-Z][A-Z]+",
      "$0$0"
    )

Now, replace() treats $0 as whatever matched - it is not a variable
reference, even though it looks like one. Th $ sign is special to
replace().

However, lower-case("$0") will return "$0" since neither $ nor 0 is an
upper case letter.

substring("$0", 1, 1) ought to return a $ sign, and if you use that as
an argument to replace(0 you'll get an error, because replace() wants
dollar signs to be followed by digits.

Hope that helps.

Liam

-- 
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
Ankh: irc.sorcery.net irc.gnome.org freenode/#xml

Fuctions and variables in replacement string of fn:replace()

Tue, 30 Apr 2013 20:14:27 GMT

On Tue, 2013-04-30 at 23:01 -0400, David Sewell wrote:
> When using fn:replace(), is it kosher or illegal to construct the
> replacement string dynamically using a function? In some cases this
> seems to work (tested in Saxon and MarkLogic):
> 
> xquery version "1.0";
> let $string := "Now, let's SEND OUT for QUICHE!!"
> let $match := "[A-Z][A-Z]+"
> return replace($string, $match, concat("$0","$0"))
> ==> Now, let's SENDSEND OUTOUT for QUICHEQUICHE!!
> 
> but in other cases it doesn't. For example, lower-case("$0") has no
> effect. And substring("$0", 1, 1) throws an error.

In your first example,
return replace($string, $match, concat("$0","$0"))
the replace function gets called with 3 arguments:
    replace(
      "Now, let's SEND OUT for QUICHE!!",
      "[A-Z][A-Z]+",
      "$0$0"
    )

Now, replace() treats $0 as whatever matched - it is not a variable
reference, even though it looks like one. Th $ sign is special to
replace().

However, lower-case("$0") will return "$0" since neither $ nor 0 is an
upper case letter.

substring("$0", 1, 1) ought to return a $ sign, and if you use that as
an argument to replace(0 you'll get an error, because replace() wants
dollar signs to be followed by digits.

Hope that helps.

Liam

-- 
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
Ankh: irc.sorcery.net irc.gnome.org freenode/#xml

Fuctions and variables in replacement string of fn:replace()

Tue, 30 Apr 2013 20:01:01 GMT

When using fn:replace(), is it kosher or illegal to construct the
replacement string dynamically using a function? In some cases this
seems to work (tested in Saxon and MarkLogic):

xquery version "1.0";
let $string := "Now, let's SEND OUT for QUICHE!!"
let $match := "[A-Z][A-Z]+"
return replace($string, $match, concat("$0","$0"))
==> Now, let's SENDSEND OUTOUT for QUICHEQUICHE!!

but in other cases it doesn't. For example, lower-case("$0") has no
effect. And substring("$0", 1, 1) throws an error.

DS

-- 
David Sewell, Editorial and Technical Manager
ROTUNDA, The University of Virginia Press
PO Box 400314, Charlottesville, VA 22904-4314 USA
Email: http://x-query.com/mailman/listinfo/talk   Tel: +1 434 924 9973
Web: http://rotunda.upress.virginia.edu/

Fuctions and variables in replacement string of fn:replace()

Tue, 30 Apr 2013 20:01:01 GMT

When using fn:replace(), is it kosher or illegal to construct the
replacement string dynamically using a function? In some cases this
seems to work (tested in Saxon and MarkLogic):

xquery version "1.0";
let $string := "Now, let's SEND OUT for QUICHE!!"
let $match := "[A-Z][A-Z]+"
return replace($string, $match, concat("$0","$0"))
==> Now, let's SENDSEND OUTOUT for QUICHEQUICHE!!

but in other cases it doesn't. For example, lower-case("$0") has no
effect. And substring("$0", 1, 1) throws an error.

DS

-- 
David Sewell, Editorial and Technical Manager
ROTUNDA, The University of Virginia Press
PO Box 400314, Charlottesville, VA 22904-4314 USA
Email: http://x-query.com/mailman/listinfo/talk   Tel: +1 434 924 9973
Web: http://rotunda.upress.virginia.edu/

Xquery and API documentation

Wed, 24 Apr 2013 06:21:51 GMT

Hi Jakob,

I also recently saw Swagger and was very impressed and was considering
doing something with it at some point.

The XQuery 3.0 annotations for defining a REST API are known as RESTXQ.

If the platform you are using supports RESTXQ and introspection, then
you could probably quite easily write a small XQuery script to find
the annotated functions and create the JSON file for Swagger. If your
on eXist you could probably even write the function as a RESTXQ
function, making the api-doc a REST API function too :-)
Another option would be if you have RESTXQ support but no
introspection, to use rest:resource-functions() function to get the
details of the annotated functions and then create JSON from that.

Cheers Adam.

On 24 April 2013 13:40, Jakob Fix  wrote:
> Hi,
>
> I'm looking for ways to generate API documentation from our Xquery code. Of
> course, there is Xqdoc, but I'm looking to get something that is a) a bit
> better-looking and more importantly, b) usable by the developer who wants to
> try out the API.
>
> I've been looking at Swagger [1] which seems to do what I want. It expects a
> JSON file that would need to be generated from the Xquery code. I think I
> remember Adam Retter giving a talk on how to use 3.0 annotations for
> defining the API in Prague a couple of years ago.
>
> Are there already efforts underway to get something like this going?
>
> I would be most interested,
> Jakob.
>
> [1] https://developers.helloreverb.com/swagger/
>
>
> _______________________________________________
> http://x-query.com/mailman/listinfo/talk
> http://x-query.com/mailman/listinfo/talk

-- 
Adam Retter

skype: adam.retter
tweet: adamretter
http://www.adamretter.org.uk

Xquery and API documentation

Wed, 24 Apr 2013 06:21:51 GMT

Hi Jakob,

I also recently saw Swagger and was very impressed and was considering
doing something with it at some point.

The XQuery 3.0 annotations for defining a REST API are known as RESTXQ.

If the platform you are using supports RESTXQ and introspection, then
you could probably quite easily write a small XQuery script to find
the annotated functions and create the JSON file for Swagger. If your
on eXist you could probably even write the function as a RESTXQ
function, making the api-doc a REST API function too :-)
Another option would be if you have RESTXQ support but no
introspection, to use rest:resource-functions() function to get the
details of the annotated functions and then create JSON from that.

Cheers Adam.

On 24 April 2013 13:40, Jakob Fix  wrote:
> Hi,
>
> I'm looking for ways to generate API documentation from our Xquery code. Of
> course, there is Xqdoc, but I'm looking to get something that is a) a bit
> better-looking and more importantly, b) usable by the developer who wants to
> try out the API.
>
> I've been looking at Swagger [1] which seems to do what I want. It expects a
> JSON file that would need to be generated from the Xquery code. I think I
> remember Adam Retter giving a talk on how to use 3.0 annotations for
> defining the API in Prague a couple of years ago.
>
> Are there already efforts underway to get something like this going?
>
> I would be most interested,
> Jakob.
>
> [1] https://developers.helloreverb.com/swagger/
>
>
> _______________________________________________
> http://x-query.com/mailman/listinfo/talk
> http://x-query.com/mailman/listinfo/talk

-- 
Adam Retter

skype: adam.retter
tweet: adamretter
http://www.adamretter.org.uk

Xquery and API documentation

Wed, 24 Apr 2013 05:57:55 GMT

Try xquerydoc, which can extract XQDoc comments and style them in HTML and markdown. It's written in pure XQuery 1.0, with a small amount of XProc to drive the initial execution.

https://github.com/xquery/xquerydoc

John

On 24 Apr 2013, at 13:40, Jakob Fix 
 wrote:

> Hi,
> 
> I'm looking for ways to generate API documentation from our Xquery code. Of course, there is Xqdoc, but I'm looking to get something that is a) a bit better-looking and more importantly, b) usable by the developer who wants to try out the API.
> 
> I've been looking at Swagger [1] which seems to do what I want. It expects a JSON file that would need to be generated from the Xquery code. I think I remember Adam Retter giving a talk on how to use 3.0 annotations for defining the API in Prague a couple of years ago.
> 
> Are there already efforts underway to get something like this going?
> 
> I would be most interested,
> Jakob.
> 
> [1] https://developers.helloreverb.com/swagger/
> 
> _______________________________________________
> http://x-query.com/mailman/listinfo/talk
> http://x-query.com/mailman/listinfo/talk

Xquery and API documentation

Wed, 24 Apr 2013 05:57:55 GMT

Try xquerydoc, which can extract XQDoc comments and style them in HTML and markdown. It's written in pure XQuery 1.0, with a small amount of XProc to drive the initial execution.

https://github.com/xquery/xquerydoc

John

On 24 Apr 2013, at 13:40, Jakob Fix 
 wrote:

> Hi,
> 
> I'm looking for ways to generate API documentation from our Xquery code. Of course, there is Xqdoc, but I'm looking to get something that is a) a bit better-looking and more importantly, b) usable by the developer who wants to try out the API.
> 
> I've been looking at Swagger [1] which seems to do what I want. It expects a JSON file that would need to be generated from the Xquery code. I think I remember Adam Retter giving a talk on how to use 3.0 annotations for defining the API in Prague a couple of years ago.
> 
> Are there already efforts underway to get something like this going?
> 
> I would be most interested,
> Jakob.
> 
> [1] https://developers.helloreverb.com/swagger/
> 
> _______________________________________________
> http://x-query.com/mailman/listinfo/talk
> http://x-query.com/mailman/listinfo/talk

Need xquery function for "number of days between two dates"

Fri, 12 Apr 2013 10:25:01 GMT

sudheshna iyer wrote:

> I need a xquery function which takes two dates and return number of days
> that lapsed between these two dates. Input to this function can be a 2
> strings of type "mm/dd/yyyy 00:00:00".
>
> Can any of you have a function handy to do this?

Well there is an xs:dateTime data type supporting this:

days-from-duration(current-dateTime() - xs:dateTime('2013-01-01T00:00:00'))

You would first need to convert your date time format to the xs:dateTime 
format of yyyy-mm-ddThh:mm:ss respectively construct xs:dateTime values 
from your format.

Need xquery function for "number of days between two dates"

Fri, 12 Apr 2013 10:25:01 GMT

sudheshna iyer wrote:

> I need a xquery function which takes two dates and return number of days
> that lapsed between these two dates. Input to this function can be a 2
> strings of type "mm/dd/yyyy 00:00:00".
>
> Can any of you have a function handy to do this?

Well there is an xs:dateTime data type supporting this:

days-from-duration(current-dateTime() - xs:dateTime('2013-01-01T00:00:00'))

You would first need to convert your date time format to the xs:dateTime 
format of yyyy-mm-ddThh:mm:ss respectively construct xs:dateTime values 
from your format.

XQuery Update vs. Perl

Thu, 04 Apr 2013 20:12:40 GMT

OK, I figured out how to do most of it:
copy $c := doc("zaokeng.kml")
modify (
  for $d in $c//*:Point
  return insert node (
  1,
  relativeToGround
		)  before $d/*:coordinates
)
return $c

As far as inserting things into the text of a node,
well as you can see in
http://www.mail-archive.com/basex-talk%40mailman.uni-konstanz.de/msg02434.html
if I let basex's doc() get its hands on it my significant whitespace
gets zapped anyway...

XQuery Update vs. Perl

Thu, 04 Apr 2013 04:04:41 GMT

Gentlemen, though I read
http://docs.basex.org/wiki/XQuery_Update
http://docs.oracle.com/cd/E17276_01/html/gsg_xml/cxx/modifydocument.html
it seems nothing can beat
#!/usr/bin/perl
while(<>){
    s!!$&1relativeToGround!;
    print;
}
for simply inserting nodes ___and getting the whole modified document
back, and not just the modified Point nodes___.

How can I do
$ perl above_program.pl < input > output
but instead e.g., with basex etc.?

P.S., I also want to change all the
	  120.8663222,24.1810570
	  120.8666897,24.1811994
	  120.8661032,24.1812131
to
	  120.8663222,24.1810570,10
	  120.8666897,24.1811994,10
	  120.8661032,24.1812131,10
I bet it is 1000 times easier with perl.

To see the source I want to modify, do
$ wget http://jidanni.org/location/zaokeng.kmz
$ unzip zaokeng.kmz

First draft of the Web Application spec

Wed, 03 Apr 2013 10:54:01 GMT

  Hi,

  I thought you might be interested in the following announce, as
it is about a spec for writing XQuery main modules and libraries
(among other technologies) to implement server-side response to
HTTP requests.

  Regards,

-- 
Florent Georges
http://fgeorges.org/
http://h2oconsulting.be/


  Hi,

  I am very pleased to announce the first public draft of the
"Web Application" spec from the W3C EXPath CG.  It is available
at:

    http://expath.org/spec/webapp

  The goal is to define a general purpose binding to HTTP, on the
server side.  The spec defines how components are passed the HTTP
request information, how they return the HTTP response to send
back, and how requests are dispatched to which components.

  Components can be XSLT, XQuery and/or XProc components.  The
can be used to serve resources (or web pages), to create filters,
and to implement specific error handlers.

  Servlex is an open-source implementation of this specification.
See the following links for more information on the EXPath
initiative, on the W3C EXPath CG, and on Servlex:

    http://expath.org/
    http://w3.org/community/expath/
    http://github.com/fgeorges/servlex

  Comments welcome!

  Regards,

-- 
Florent Georges
http://fgeorges.org/
http://h2oconsulting.be/

let's comment out a line in XQuery

Tue, 02 Apr 2013 10:28:19 GMT

MS> IIRC he's all het up about {} ...
Yes something like that.
Anyway there's no point in discussing it again.
I just want to say "doctors have proven that the most one can remember
is (: and :)."

let's comment out a line in XQuery

Tue, 02 Apr 2013 10:27:12 GMT

XQuery comments are (: trivial :)

Where exactly they work is complicated ... until you understand XQuery then its trivial. 


----------------------------------------
David A. Lee
http://x-query.com/mailman/listinfo/talk
http://www.xmlsh.org

-----Original Message-----
From: http://x-query.com/mailman/listinfo/talk [mailto:http://x-query.com/mailman/listinfo/talk] On Behalf Of Michael Sokolov
Sent: Tuesday, April 02, 2013 2:23 PM
To: Florent Georges
Cc: http://x-query.com/mailman/listinfo/talk; http://x-query.com/mailman/listinfo/talk
Subject: Re:  let's comment out a line in XQuery

On 04/02/2013 01:34 PM, Florent Georges wrote:
> http://x-query.com/mailman/listinfo/talk wrote:
>
>    
>> there is no way for me to remember the xquery complex full
>> comment syntax for more than one month.
>>      
>    The "smiley syntax", complex?  Really?
>
>    
IIRC he's all het up about {} not being syntactically valid, preventing 
{(: $expression :)}.

-- 
Michael Sokolov
Senior Architect
Safari Books Online

_______________________________________________
http://x-query.com/mailman/listinfo/talk
http://x-query.com/mailman/listinfo/talk

let's comment out a line in XQuery

Tue, 02 Apr 2013 10:23:24 GMT

On 04/02/2013 01:34 PM, Florent Georges wrote:
> http://x-query.com/mailman/listinfo/talk wrote:
>
>    
>> there is no way for me to remember the xquery complex full
>> comment syntax for more than one month.
>>      
>    The "smiley syntax", complex?  Really?
>
>    
IIRC he's all het up about {} not being syntactically valid, preventing 
{(: $expression :)}.

-- 
Michael Sokolov
Senior Architect
Safari Books Online

let's comment out a line in XQuery

Tue, 02 Apr 2013 09:34:13 GMT

http://x-query.com/mailman/listinfo/talk wrote:

> there is no way for me to remember the xquery complex full
> comment syntax for more than one month.

  The "smiley syntax", complex?  Really?

-- 
Florent Georges
http://fgeorges.org/
http://h2oconsulting.be/

let's comment out a line in XQuery

Mon, 01 Apr 2013 21:20:04 GMT

I'm back, and it's proven!: there is no way for me to remember the
xquery complex full comment syntax for more than one month. Solution.
put comments into a separate file. OK.

where clause

Thu, 28 Mar 2013 23:54:06 GMT

It's not just the WHERE clause, of course: ORDER BY and GROUP BY also affect the strategy.

In XQuery 1.0 nearly every FLWOR expression could be rewritten as an expression on sequences of items (rather than tuples). The only exception was a rather weird and rare case involving ORDER BY where the order of tuples couldn't be reduced to an ordering of items in the input sequences. Saxon reduced everything to sequence operations, handling this special case with a bit of custom code that essentially wrapped the tuple as a map-like item.

In XQuery 3.0 there are many more FLWOR expressions that can't be rewritten in terms of operations on item sequences, and native support for tuple streams in the run-time engine becomes almost unavoidable. Once you have that support, there's not necessarily any benefit in eliminating the WHERE clauses (though Saxon still attempts to do so, mainly to take advantage of the other optimisations available for filter expressions). The important thing is to promote each conjunctive term of the WHERE clause up the pipeline to the earliest place where it can be evaluated; whether it is then turned into a filter expression is relatively unimportant.

Michael Kay
Saxonica

On 29 Mar 2013, at 07:35, Liam R E Quin wrote:

> 
> On Wed, 2013-03-27 at 13:26 +0000, deBakker, Bas wrote:
>> Wouldn't that be equivalent to
>> 
>>    for $a in expr1, $b in expr2, $c in expr3[$a = $b + .]
>>    return $a
> 
> I notice that BaseX does exactly that rewrite.
> 
> In SQL with a WHERE clause some of the values may be NULL, but that
> can't occur in XQuery today; if it could, there might be tuples without
> a value for $c, in which case the rewrite wouldn't work.
> 
> A smart optimizer with knowledge of the input could rewrite at runtime
> to put the [predicate] on the expression likely to have the fewest
> nodes, or could rewrite to say, for $a in expr1[. ge min($b) + min($c)];
> this sort of rewrite can turn a theoretically O(n^3) operation into O(n)
> in practice.
> 
> I think the answer is, use "where" when it makes the query more
> readable, or if there are positional or grouping clauses. Some
> implementatins do more optimizatoins than others, though, so sometimes
> readability ends up second to speed.
> 
> Liam
> 
> -- 
> Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
> Pictures from old books: http://fromoldbooks.org/
> Ankh: irc.sorcery.net irc.gnome.org freenode/#xml
> 
> _______________________________________________
> http://x-query.com/mailman/listinfo/talk
> http://x-query.com/mailman/listinfo/talk

where clause

Thu, 28 Mar 2013 23:35:38 GMT

On Wed, 2013-03-27 at 13:26 +0000, deBakker, Bas wrote:
> Wouldn't that be equivalent to
> 
>     for $a in expr1, $b in expr2, $c in expr3[$a = $b + .]
>     return $a

I notice that BaseX does exactly that rewrite.

In SQL with a WHERE clause some of the values may be NULL, but that
can't occur in XQuery today; if it could, there might be tuples without
a value for $c, in which case the rewrite wouldn't work.

A smart optimizer with knowledge of the input could rewrite at runtime
to put the [predicate] on the expression likely to have the fewest
nodes, or could rewrite to say, for $a in expr1[. ge min($b) + min($c)];
this sort of rewrite can turn a theoretically O(n^3) operation into O(n)
in practice.

I think the answer is, use "where" when it makes the query more
readable, or if there are positional or grouping clauses. Some
implementatins do more optimizatoins than others, though, so sometimes
readability ends up second to speed.

Liam

-- 
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
Ankh: irc.sorcery.net irc.gnome.org freenode/#xml

where clause

Thu, 28 Mar 2013 11:08:13 GMT

I see - nice!  Still trying to wrap my head around it to generalize, but 
I see your point.

-Mike

On 03/28/2013 02:22 PM, daniela florescu wrote:
> Not in the general case of such pattern -- because of cardinality.
> (I told you XQuery is twisted :-)
>
> Imagine that the function would have looked like this instead of the one I wrote:
>
>
> declare function foo($x)
> {
>     if ($x/@a) then ($x, $x) else
> };
>
> then count(...) of the total result  is different  !
>
> :-)
>
> Dana
>
>
>
>    
>>>
>>>        
>> Yes, that is twisted for sure.  But isn't it also equivalent to:
>>
>> for $x in Blah1
>> for $y in Blah2
>> for $z in foo($y)[. is .]
>> return $x
>>
>> ?
>>
>> not that that really makes any difference, in some sense, but given the problem as stated, I don't think a where clause is required
>>
>> -- 
>> Michael Sokolov
>> Senior Architect
>> Safari Books Online
>>
>> _______________________________________________
>> http://x-query.com/mailman/listinfo/talk
>> http://x-query.com/mailman/listinfo/talk
>>      
>    


-- 
Michael Sokolov
Senior Architect
Safari Books Online

where clause

Thu, 28 Mar 2013 10:22:08 GMT

Not in the general case of such pattern -- because of cardinality. (I told you XQuery is twisted :-) Imagine that the function would have looked like this instead of the one I wrote: declare function foo($x) { if ($x/@a) then ($x, $x) else }; then count(...) of the total result is different ! :-) Dana >> >> > Yes, that is twisted for sure. But isn't it also equivalent to: > > for $x in Blah1 > for $y in Blah2 > for $z in foo($y)[. is .] > return $x > > ? > > not that that really makes any difference, in some sense, but given the problem as stated, I don't think a where clause is required > > -- > Michael Sokolov > Senior Architect > Safari Books Online > > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk

where clause

Thu, 28 Mar 2013 10:15:20 GMT

On 03/28/2013 12:23 PM, daniela florescu wrote: > Michael, > > in addition to the queries I already gave you with count and groupby, here is another one in > pure XQuery 1.0 that cannot be reduced > > declare function foo($x) > { > if ($x/@a) then $x else > }; > > > for $x in Blah1 > for $y in Blah2 > let $z := foo($y) > where $z is $z > return $x > > > (variable $z cannot be unfolded because of the generation of new nodes, and then the where cannot be move up because > of the let) > > > Sorry, I felt like being twisted minded this morning :-) > > XQuery is wicked :-) > Yes, that is twisted for sure. But isn't it also equivalent to: for $x in Blah1 for $y in Blah2 for $z in foo($y)[. is .] return $x ? not that that really makes any difference, in some sense, but given the problem as stated, I don't think a where clause is required -- Michael Sokolov Senior Architect Safari Books Online

where clause

Thu, 28 Mar 2013 08:23:02 GMT

Michael, in addition to the queries I already gave you with count and groupby, here is another one in pure XQuery 1.0 that cannot be reduced declare function foo($x) { if ($x/@a) then $x else }; for $x in Blah1 for $y in Blah2 let $z := foo($y) where $z is $z return $x (variable $z cannot be unfolded because of the generation of new nodes, and then the where cannot be move up because of the let) Sorry, I felt like being twisted minded this morning :-) XQuery is wicked :-) Best Dana On Mar 27, 2013, at 7:10 PM, Michael Sokolov wrote: > (forwarding Daniela's message) > > Michael, > > I think the ones with grouby and a where after the groupby are impossible to rewrite > in general (remember this from my optimizing SQL days). In this case the WHERE is the good old > HAVING clause of SQL. > > Something along the lines of > > for $x in blah > for $y in blah > group by $z:= $x/a, $t:= $y/b > where $z+$t >25 > return $z > > I am putting an informal syntax, obviously. > > Another case is when the COUNT clause exists. You cannot move the where up and down in the tuple stream in > such a case. > > for $x in Blah1 > for $y in Blah2 > count $i > where $x/a eq $y/b > return something using $i > > > HTH > Dana > > > On Mar 27, 2013, at 5:31 AM, Michael Sokolov wrote: > >> I'm trying to come up with examples in which "where" clauses cannot be rewritten as XPath predicates. So far, the ones I have all involve an "at" counter. Are there others? >> >> -- >> Michael Sokolov >> Senior Architect >> Safari Books Online >> >> _______________________________________________ >> http://x-query.com/mailman/listinfo/talk >> http://x-query.com/mailman/listinfo/talk > > > > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk

[ANN] Pascal XQuery 1 engine now with JSONiq

Thu, 28 Mar 2013 04:15:50 GMT

Hi, there is now a new release of my Pascal-based XQuery engine which adds JSONiq support. (not JSONiq Update through, but there is an old global variable extension, which can be used to update some (but not all) object properties without involving snapshots ) The XQuery part supports everything of XQuery 1 except xml schemas, and static type checking, with some extensions like pattern matching, global variables or a XPath 2-restricted mode. Main library page:http://www.benibela.de/sources_en.html#internettools Online XQuery tester: http://videlibri.sourceforge.net/cgi-bin/xidelcgi?extract-kind=xquery Command Line Tool: http://videlibri.sourceforge.net/xidel.html XQTS Results: http://www.benibela.de/documentation/internettools/internettoolsxqts.html (skipping invalid inputs) Benito

Fwd: Re: where clause

Wed, 27 Mar 2013 18:10:35 GMT

(forwarding Daniela's message) Michael, I think the ones with grouby and a where after the groupby are impossible to rewrite in general (remember this from my optimizing SQL days). In this case the WHERE is the good old HAVING clause of SQL. Something along the lines of for $x in blah for $y in blah group by $z:= $x/a, $t:= $y/b where $z+$t >25 return $z I am putting an informal syntax, obviously. Another case is when the COUNT clause exists. You cannot move the where up and down in the tuple stream in such a case. for $x in Blah1 for $y in Blah2 count $i where $x/a eq $y/b return something using $i HTH Dana On Mar 27, 2013, at 5:31 AM, Michael Sokolov wrote: > I'm trying to come up with examples in which "where" clauses cannot be rewritten as XPath predicates. So far, the ones I have all involve an "at" counter. Are there others? > > -- > Michael Sokolov > Senior Architect > Safari Books Online > > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk

where clause

Wed, 27 Mar 2013 17:09:58 GMT

On 3/27/13 8:31 AM, Michael Sokolov wrote: > I'm trying to come up with examples in which "where" clauses cannot be > rewritten as XPath predicates. So far, the ones I have all involve an > "at" counter. Are there others? > OK - thanks, Ken, Michael, Daniela - I'll just summarize: in XQuery 1.0 (I didn't say, but that's my current target) the only examples we have are those with "at" - Bas and Michael demonstrated that most expressions can be rewritten, including Ken's, even if with some difficulty. Daniela's examples (group by, count) are from XQuery 3.0 - they look irreducible. Thanks again -Mike Sokolov

where clause

Wed, 27 Mar 2013 14:43:28 GMT

On 27/03/2013 12:31, Michael Sokolov wrote: > I'm trying to come up with examples in which "where" clauses cannot be > rewritten as XPath predicates. So far, the ones I have all involve an > "at" counter. Are there others? > The ones that are trickiest to rewrite are those that reference the context. For example $y/(for $x in //item where $x/@status = . return $x) To translate this into a predicate you need to introduce a variable: $y/(let $z := . return //item[@status = $z]) Michael Kay Saxonica

where clause

Wed, 27 Mar 2013 07:01:31 GMT

At 2013-03-27 13:26 +0000, deBakker, Bas wrote: >Wouldn't that be equivalent to > > for $a in expr1, $b in expr2, $c in expr3[$a = $b + .] > return $a Thank you, Bas, yes I grant that your expression is equivalent to mine. I failed to acknowledge that tuples are only created when there is a binding value for every member of the tuple. I appreciate the clarification. . . . . . . . . Ken >Bas > >-----Original Message----- >From: http://x-query.com/mailman/listinfo/talk [mailto:http://x-query.com/mailman/listinfo/talk] On >Behalf Of G. Ken Holman >Sent: Wednesday, March 27, 2013 14:19 >To: http://x-query.com/mailman/listinfo/talk >Subject: Re: where clause > >At 2013-03-27 08:31 -0400, Michael Sokolov wrote: > >I'm trying to come up with examples in which "where" clauses cannot be > >rewritten as XPath predicates. So far, the ones I have all involve an > >"at" counter. Are there others? > >I can see no difference off hand when creating 1-tuples, as a >1-tuple is essentially just a sequence. > >However, when creating n-tuples (either with the "at" keyword as you >say or with other bound variables in your expression), the where >clause acts on the tuple, not just on a set of values. Here is a >3-tuple expression example: > > for $a in expr1, $b in expr2, $c in expr3 > where $a=$b+$c > return $a > >I hope this is helpful. > >. . . . . . . . Ken -- Public XSLT, XSL-FO, UBL and code list classes in Europe -- Apr 2013 | Contact us for world-wide XML consulting and instructor-led training | Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm | Crane Softwrights Ltd. http://www.CraneSoftwrights.com/m/ | G. Ken Holman mailto:http://x-query.com/mailman/listinfo/talk | Google+ profile: https://plus.google.com/116832879756988317389/about | Legal business disclaimers: http://www.CraneSoftwrights.com/legal |

where clause

Wed, 27 Mar 2013 05:26:52 GMT

Wouldn't that be equivalent to for $a in expr1, $b in expr2, $c in expr3[$a = $b + .] return $a Bas -----Original Message----- From: http://x-query.com/mailman/listinfo/talk [mailto:http://x-query.com/mailman/listinfo/talk] On Behalf Of G. Ken Holman Sent: Wednesday, March 27, 2013 14:19 To: http://x-query.com/mailman/listinfo/talk Subject: Re: where clause At 2013-03-27 08:31 -0400, Michael Sokolov wrote: >I'm trying to come up with examples in which "where" clauses cannot be >rewritten as XPath predicates. So far, the ones I have all involve an >"at" counter. Are there others? I can see no difference off hand when creating 1-tuples, as a 1-tuple is essentially just a sequence. However, when creating n-tuples (either with the "at" keyword as you say or with other bound variables in your expression), the where clause acts on the tuple, not just on a set of values. Here is a 3-tuple expression example: for $a in expr1, $b in expr2, $c in expr3 where $a=$b+$c return $a I hope this is helpful. . . . . . . . . Ken -- Public XSLT, XSL-FO, UBL and code list classes in Europe -- Apr 2013 | Contact us for world-wide XML consulting and instructor-led training | Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm | Crane Softwrights Ltd. http://www.CraneSoftwrights.com/q/ | G. Ken Holman mailto:http://x-query.com/mailman/listinfo/talk | Google+ profile: https://plus.google.com/116832879756988317389/about | Legal business disclaimers: http://www.CraneSoftwrights.com/legal | _______________________________________________ http://x-query.com/mailman/listinfo/talk http://x-query.com/mailman/listinfo/talk

where clause

Wed, 27 Mar 2013 05:18:41 GMT

At 2013-03-27 08:31 -0400, Michael Sokolov wrote: >I'm trying to come up with examples in which "where" clauses cannot >be rewritten as XPath predicates. So far, the ones I have all >involve an "at" counter. Are there others? I can see no difference off hand when creating 1-tuples, as a 1-tuple is essentially just a sequence. However, when creating n-tuples (either with the "at" keyword as you say or with other bound variables in your expression), the where clause acts on the tuple, not just on a set of values. Here is a 3-tuple expression example: for $a in expr1, $b in expr2, $c in expr3 where $a=$b+$c return $a I hope this is helpful. . . . . . . . . Ken -- Public XSLT, XSL-FO, UBL and code list classes in Europe -- Apr 2013 | Contact us for world-wide XML consulting and instructor-led training | Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm | Crane Softwrights Ltd. http://www.CraneSoftwrights.com/q/ | G. Ken Holman mailto:http://x-query.com/mailman/listinfo/talk | Google+ profile: https://plus.google.com/116832879756988317389/about | Legal business disclaimers: http://www.CraneSoftwrights.com/legal |

where clause

Wed, 27 Mar 2013 04:31:40 GMT

I'm trying to come up with examples in which "where" clauses cannot be rewritten as XPath predicates. So far, the ones I have all involve an "at" counter. Are there others? -- Michael Sokolov Senior Architect Safari Books Online

XQuery 3.0 test suite - Call for implementations of XQuery 3

Sun, 10 Mar 2013 11:01:57 GMT

Liam, thanks for the reminder! We are working on the finalization of XQuery 3.0, and we will submit our results as soon as we are approximating 100%. Yoshi OKAMOTO san: our implementation of format-integer() still needs to be adjusted to the latest version of the specification. I can just confirm that many results of this function will be somewhat unexpected. Best, Christian ___________________________ > The XQuery 3.0 specification is currently a W3C "Candidate > Recommendation", meaning we (W3C) are waiting to know that it can be > implemented by multiple people such that people can move queries from > one implementation to another reasonably easily. > > If you have made an XQuery 3 implementation, please run the test suite > at [1] and send us the results. We can publish them anonymously if you > prefer (email me directly for instructions). > > Thank you for helping XQuery 3.0 move forward, and helping with this > work! > > > [1] http://dev.w3.org/2011/QT3-test-suite/ > > -- > Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ > Pictures from old books: http://fromoldbooks.org/ > Ankh: irc.sorcery.net irc.gnome.org freenode/#xml > > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk

XQuery 3.0: formatting integers

Sun, 10 Mar 2013 10:08:22 GMT

There has been quite a bit of tightening up of the format-integer specification over successive drafts. The Candidate Recommendation says this: If the primary format token contains at least one Unicode digit then it is taken as a decimal digit pattern, and in this case it must match the regular expression ^((\p{Nd}|#|[^\p{N}\p{L}])+?)$. If it contains a digit but does not match this pattern, a dynamic error is raised [err:FODF1310]. which makes it pretty clear that in your example, the picture is an error (because it contains a "."). >I assume that Michael Kay's Saxon processor is probably the implementation to trust most? No, because the specification has been changed since Saxon 9.4 was released. At this stage of the game, while the specification is still a draft, differences between implementations - especially in edge cases - are to be expected. Michael Kay Saxonica

XQuery 3.0 test suite - Call for implementations of XQuery 3

Sun, 10 Mar 2013 09:23:42 GMT

The XQuery 3.0 specification is currently a W3C "Candidate Recommendation", meaning we (W3C) are waiting to know that it can be implemented by multiple people such that people can move queries from one implementation to another reasonably easily. If you have made an XQuery 3 implementation, please run the test suite at [1] and send us the results. We can publish them anonymously if you prefer (email me directly for instructions). Thank you for helping XQuery 3.0 move forward, and helping with this work! [1] http://dev.w3.org/2011/QT3-test-suite/ -- Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.org/ Ankh: irc.sorcery.net irc.gnome.org freenode/#xml

XQuery 3.0: formatting integers (2)

Sun, 10 Mar 2013 09:11:19 GMT

On Sun, 2013-03-10 at 16:43 +0000, Yoshi Okamoto wrote: > Dear readers (2), > > my impression is that it may be too early to test fn:format-integer(), > because the returned values of all implementations I have tested so > far seem to remain unpredictable. It might mean that our test suite needs to be improved in this area, and we'd really welcome contributions,,, For moving XQuery 3.0 to a W3C Recommendation, we need to show good interoperability. There's a test suite at http://dev.w3.org/2011/QT3-test-suite/ which includes a link to a page about submitting test cases. Liam -- Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.org/ Ankh: irc.sorcery.net irc.gnome.org freenode/#xml

XQuery 3.0: formatting integers (2)

Sun, 10 Mar 2013 08:43:51 GMT

Dear readers (2), my impression is that it may be too early to test fn:format-integer(), because the returned values of all implementations I have tested so far seem to remain unpredictable. Indeed, I believe I have managed to bring the tested implementations together in all possible combinations! Two other examples that I want to present: Query 1: format-integer(-1, '1;o') The results are: * xMLPrime: -1st * Saxon, BaseX, Zorba: error I believe that XMLPrime's result is correct (?). Query 2: format-integer(-1, '1o') The results are: * xMLPrime, Saxon: -1 * BaseX, Zorba: -1st Here, I would have expected an error, because, following the specification, the string contains no semicolon, and '1o' does not match the pattern '^((\p{Nd}|#|[^\p{N}\p{L}])+?)$'. But I am afraid I may be so wrong? Yoshi OKAMOTO

XQuery 3.0: formatting integers

Sun, 10 Mar 2013 07:31:52 GMT

Dear readers, I have a question regarding the new fn:format-integer() function of XQuery. I noticed that the implementations I tried give me different results for various queries. This is one example: format-integer(-1, '#####12.3') The results are: * Saxon: -0.0.1 * BaseX, XMLPrime: -00.1 * Zorba: -1 Does someone know what is the correct result? I spent about one hour in the Functions and Operators 3.0 specification to finally confess that I did not manage to sort out the relevant details. This is the text I read: http://www.w3.org/TR/xpath-functions-30/#func-format-integer Maybe someone in the community is faster than me? Maybe someone even know the answer by heart? Maybe I should try more implementations? I assume that Michael Kay's Saxon processor is probably the implementation to trust most? Thank you for reading this, and thank your for sharing your time, Best regards Yoshi OKAMOTO

[ANN] BaseX 7.6: The XMLPrague Edition

Tue, 05 Feb 2013 13:24:12 GMT

Hi all, we are excited to announce Version 7.6 of BaseX, which provides some fresh new features that will further boost your productivity: DATABASE LOCKING: - updates on different databases can now be executed in parallel and won't lock your read-only queries anymore: http://docs.basex.org/wiki/Transaction_Management XQUERY: - when errors are raised, the full stack trace is now returned - the EXPath Geo Module, Fetch Module and HTML Module have been added: http://docs.basex.org/wiki/Module_Library - the Validation, XSLT, Database and Profiling Module have been updated GUI: - error messages are now clickable and linked with the text editor - trace/profiling output is redirected to the info view in realtime Have fun with our new release! It is available at: http://basex.org/products/download/ Looking forward to your feedback, and seeing some of you in Prague, Christian BaseX Team, 2013

Looking for an example - calling XQuery 3.0 function module from XSLT 3.0

Mon, 04 Feb 2013 01:23:15 GMT

Here's a very simple test case from my test suite (though it uses XSLT 2.0 and XQuery 1.0): test.xsl test.xq: xquery version "1.0"; module namespace qf = "library.uri"; declare function qf:distinct-countries($root as document-node()) as xs:string* { distinct-values($root//city/@country) }; One word of advice, I would advise avoiding use of global variables in the query library. There are some unresolved bugs relating to use of global variables in separately compiled query libraries. I would also suggest, if you're having problems, it's best to say what you are doing and how it is failing. That way, it's easier to see where you are stuck and what information you need to help you move forward. It's even possible you've hit a bug - you're a little off-piste when you use extensions like this, so the risk of finding bugs is greater. Michael Kay Saxonica On 01/02/2013 15:10, Loren Cahlander wrote: > Hello folks, > > I am playing with the latest version of Saxon from Saxonica and am looking for an example of calling a function from an XQuery 3.0 function module from XSLT 3.0. Has anyone out there done this yet? > > Thanks, > Loren > > > > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk >

Looking for an example - calling XQuery 3.0 function module from XSLT 3.0

Fri, 01 Feb 2013 07:10:09 GMT

Hello folks, I am playing with the latest version of Saxon from Saxonica and am looking for an example of calling a function from an XQuery 3.0 function module from XSLT 3.0. Has anyone out there done this yet? Thanks, Loren

XQuery file naming conventions (xq, xqy, xql, xqm, xquery, etc.)

Tue, 22 Jan 2013 15:35:50 GMT

Maybe its Xquery Update... whatever that would mean standalone?!? On 22 January 2013 23:21, Joe Wicentowski wrote: > Hi all, > > I just noticed a new one: .xu. This extension appears in oXygen's > File > Save dialog in Windows when you are saving an XQuery file: > > Save as type: XQUERY, XQ, XQL, XQM, XQY, XU > > Hadn't seen that one before. What could it mean? XUpdate? But > XUpdate isn't XQuery... > > Maybe we should adopt it so that we can pronounce our files' > extensions as "dot zoo"! > > Joe > > On Fri, Jan 11, 2013 at 4:55 PM, Joe Wicentowski wrote: >> Thanks to all for your responses! There's merit in all of the >> approaches that were shared. >> >> I'm sympathetic to the idea that we shouldn't have to use file >> extensions to distinguish between library and main modules. Maybe >> ".xq" (or ".xquery") across the board makes sense. >> >> One thing does bug me about the "module" terminology in the spec. If >> the spec distinguishes between "library" and "main" modules, why do >> *only* library modules begin with the "module namespace" construction? >> Shouldn't *all* modules begin with "module namespace ..."? Or if >> that's overkill, shouldn't it be "library module namespace ..." >> instead (as opposed to "main module namespace ...")? >> >> In retrospect, I think this "module namespace..." construction is >> responsible for many of us thinking that a module *is* a library >> module. I never thought of library vs. main modules. I always >> thought of "modules" vs. "scripts." If I'd been there on the >> committee, I think I would've advocated doing away with "module" >> altogether, and instead promoting "library" and "script". >> >> But we've got library and main module, and I guess that's okay. And >> using file extensions to distinguish between the two, or only using a >> single extension for all xquery files, are both okay too. >> >> Have a good weekend, all >> Joe -- Adam Retter skype: adam.retter tweet: adamretter http://www.adamretter.org.uk

XQuery file naming conventions (xq, xqy, xql, xqm, xquery, etc.)

Tue, 22 Jan 2013 15:21:24 GMT

Hi all, I just noticed a new one: .xu. This extension appears in oXygen's File > Save dialog in Windows when you are saving an XQuery file: Save as type: XQUERY, XQ, XQL, XQM, XQY, XU Hadn't seen that one before. What could it mean? XUpdate? But XUpdate isn't XQuery... Maybe we should adopt it so that we can pronounce our files' extensions as "dot zoo"! Joe On Fri, Jan 11, 2013 at 4:55 PM, Joe Wicentowski wrote: > Thanks to all for your responses! There's merit in all of the > approaches that were shared. > > I'm sympathetic to the idea that we shouldn't have to use file > extensions to distinguish between library and main modules. Maybe > ".xq" (or ".xquery") across the board makes sense. > > One thing does bug me about the "module" terminology in the spec. If > the spec distinguishes between "library" and "main" modules, why do > *only* library modules begin with the "module namespace" construction? > Shouldn't *all* modules begin with "module namespace ..."? Or if > that's overkill, shouldn't it be "library module namespace ..." > instead (as opposed to "main module namespace ...")? > > In retrospect, I think this "module namespace..." construction is > responsible for many of us thinking that a module *is* a library > module. I never thought of library vs. main modules. I always > thought of "modules" vs. "scripts." If I'd been there on the > committee, I think I would've advocated doing away with "module" > altogether, and instead promoting "library" and "script". > > But we've got library and main module, and I guess that's okay. And > using file extensions to distinguish between the two, or only using a > single extension for all xquery files, are both okay too. > > Have a good weekend, all > Joe

treat as

Mon, 21 Jan 2013 10:59:26 GMT

David - I've run across them in a somewhat obscure context, I guess. I've written an XQuery processor that rewrites queries originally parsed by Saxon, basically serializing them in the process. All I can tell you is that Saxon generates an internal expression (ItemChecker) that is documented as corresponding to "treat as" in some cases where there was no "treat as" in the original supplied expression. > > I think this happens, eg, if you declare a variable with a certain > type (so the type will be checked dynamically when the assignment is > done), but later references to the variable's value can be wrapped in > a "treat as" so that the compiler can assume that the variable has the > declared type and perform suitable automatic type inferencing. But > that's just a guess :) > > -Mike "treat as" is basically a dynamic type check. Saxon does optimistic static typing, which basically means that it automatically inserts "treat as" expressions into the expression tree whenever it finds a construct that isn't statically type safe. So if you write $a/child::node() and the type of $a isn't statically known, Saxon rewrites it as ($a treat as node()*)/child::node() which is what you would have to write yourself in a system with pessimistic type checking (either that, or you would add a type declaration to the declaration of variable $a). Michael Kay Saxonica

Conditional use of fn:error() ?

Mon, 21 Jan 2013 03:45:56 GMT

Dear Michael Kay, this was a quick and excellent reply, which answered all my open questions. Best regards Yoshi OKAMOTO ----- Original Message ----- From: Michael Kay To: http://x-query.com/mailman/listinfo/talk Cc: Sent: Monday, January 21, 2013 12:24 PM Subject: Re: Conditional use of fn:error() ? For all these queries, implementations have the option whether to evaluate the base expression (error()) before or after evaluating the predicate. If the value of a predicate doesn't depend on the focus, rewriting A[B] as "if (B) then A else ()" is a good thing to do, so many processors will do it. The only reliable way to generate an error conditionally is to use if/then/else (or typeswitch): if (contains('http:...', 'details')) then error() else ... There are specific rules for conditional expressions that prevent optimizers evaluating the then/else branch unless the condition is true/false. Michael Kay Saxonica On 21/01/2013 11:07, Yoshi Okamoto wrote: > Dear list subscribers, > > I noticed that different XQuery processors (BaseX, > Saxon, XMLPrime, Zorba) return different results for the following queries: > > Query A: > fn:error()[false()] > > > Query B: > error(())[contains('http://....', 'details')] > Query C: > let $url := ... > where contains($url, 'details') > return error(()) > > > All except for XMLPrime return an empty sequence. > > > Query D: > let $url := ... > return error(())[contains($url, 'details')] > > All except for Zorba return an error. > > > My original intention was to raise an error whenever a certain condition is true. My questions would be: > > - what are the correct results for Query A-D? > > - XMLPrime is the implementation that always raises an error. If this behavior should be correct, how would I proceed to only raise errors under a certain condition? > > > Thank you for your attention and patience. > > Best regards > Yoshi OKAMOTO > > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk > _______________________________________________ http://x-query.com/mailman/listinfo/talk http://x-query.com/mailman/listinfo/talk

Conditional use of fn:error() ?

Mon, 21 Jan 2013 03:24:09 GMT

For all these queries, implementations have the option whether to evaluate the base expression (error()) before or after evaluating the predicate. If the value of a predicate doesn't depend on the focus, rewriting A[B] as "if (B) then A else ()" is a good thing to do, so many processors will do it. The only reliable way to generate an error conditionally is to use if/then/else (or typeswitch): if (contains('http:...', 'details')) then error() else ... There are specific rules for conditional expressions that prevent optimizers evaluating the then/else branch unless the condition is true/false. Michael Kay Saxonica On 21/01/2013 11:07, Yoshi Okamoto wrote: > Dear list subscribers, > > I noticed that different XQuery processors (BaseX, > Saxon, XMLPrime, Zorba) return different results for the following queries: > > Query A: > fn:error()[false()] > > > Query B: > error(())[contains('http://....', 'details')] > Query C: > let $url := ... > where contains($url, 'details') > return error(()) > > > All except for XMLPrime return an empty sequence. > > > Query D: > let $url := ... > return error(())[contains($url, 'details')] > > All except for Zorba return an error. > > > My original intention was to raise an error whenever a certain condition is true. My questions would be: > > - what are the correct results for Query A-D? > > - XMLPrime is the implementation that always raises an error. If this behavior should be correct, how would I proceed to only raise errors under a certain condition? > > > Thank you for your attention and patience. > > Best regards > Yoshi OKAMOTO > > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk >

Conditional use of fn:error() ?

Mon, 21 Jan 2013 03:07:36 GMT

Dear list subscribers, I noticed that different XQuery processors (BaseX, Saxon, XMLPrime, Zorba) return different results for the following queries: Query A: fn:error()[false()] Query B: error(())[contains('http://....', 'details')] Query C: let $url := ... where contains($url, 'details') return error(()) All except for XMLPrime return an empty sequence. Query D: let $url := ... return error(())[contains($url, 'details')] All except for Zorba return an error. My original intention was to raise an error whenever a certain condition is true. My questions would be: - what are the correct results for Query A-D? - XMLPrime is the implementation that always raises an error. If this behavior should be correct, how would I proceed to only raise errors under a certain condition? Thank you for your attention and patience. Best regards Yoshi OKAMOTO

XQuery file naming conventions (xq, xqy, xql, xqm, xquery, etc.)

Fri, 11 Jan 2013 13:55:33 GMT

Thanks to all for your responses! There's merit in all of the approaches that were shared. I'm sympathetic to the idea that we shouldn't have to use file extensions to distinguish between library and main modules. Maybe ".xq" (or ".xquery") across the board makes sense. One thing does bug me about the "module" terminology in the spec. If the spec distinguishes between "library" and "main" modules, why do *only* library modules begin with the "module namespace" construction? Shouldn't *all* modules begin with "module namespace ..."? Or if that's overkill, shouldn't it be "library module namespace ..." instead (as opposed to "main module namespace ...")? In retrospect, I think this "module namespace..." construction is responsible for many of us thinking that a module *is* a library module. I never thought of library vs. main modules. I always thought of "modules" vs. "scripts." If I'd been there on the committee, I think I would've advocated doing away with "module" altogether, and instead promoting "library" and "script". But we've got library and main module, and I guess that's okay. And using file extensions to distinguish between the two, or only using a single extension for all xquery files, are both okay too. Have a good weekend, all Joe

XQuery file naming conventions (xq, xqy, xql, xqm, xquery, etc.)

Tue, 08 Jan 2013 04:29:59 GMT

>>However, I would note that David's suggestion to use .x could be >>problematic. As .x is already used for DirectX model files. FYI: this was a "Reductio ad Absurdum" joke ... Back in "The Old Days" on mainframe type systems files had actual "types" independent from their extension - if any. Unix in its ideal simplicity got rid of that. And instead used file extensions ... and magic numbers. "See no types up my sleeves ! " -David

XQuery file naming conventions (xq, xqy, xql, xqm, xquery, etc.)

Tue, 08 Jan 2013 01:19:49 GMT

Joe, I currently do the opposite to you, I adopted this because some eXist folks were doing it before me. i.e. .xql for main modules (XQuery Language) and .xqm for library modules (XQuery Module). However now I think about it, it does not make as much sense as your proposal of reversing it. I think as David says, we first have to think about whether there should be a distinction in the naming between main modules and library modules. However, I would note that David's suggestion to use .x could be problematic. As .x is already used for DirectX model files. On 7 January 2013 21:33, Joe Wicentowski wrote: > Hi all, > > There is quite a profusion of file extensions for XQuery: .xq, .xqy, > .xql, .xqm, and .xquery. Perhaps this profusion has happened the spec > doesn't say anything about the file extensions. This has opened up > the choice to each implementation and each community/project. I'd be > interested to know which communities use which file naming > conventions, and if there is any consensus? What do you use, and why? > > My experience: When I first started learning XQuery I used .xq for > everything -- I guess because it's short. oXygen uses .xquery as its > default file extension for XQuery files but recognizes all of the > above as XQuery files. The MarkLogic community seems to use .xqy. > When I started to write library modules I started to use .xqm, with > the 'm' indicating module. I saw yet others in the eXist-db community > using .xql, though it allows all of the above. Github doesn't > currently recognize .xql or .xqm as XQuery [1]. Diversity is fine, > but the downside is that newcomers are certainly confused, and anytime > we share code there is no reliable way to know whether a file is a > library or main module without opening it up. > > The spec does make a distinction that seems to apply to XQuery files. > It states that there are two kinds of modules: *library* modules and > *main* modules. The distinction is that library modules contain only > functions, whereas main modules contain a single main routine (though > can also contain function declarations). (See these two terms defined > in the spec at http://www.w3.org/TR/xquery/#dt-library-module and > http://www.w3.org/TR/xquery/#dt-main-module.) > > It seems to me that any good XQuery file naming convention should > reflect this distinction between *library* and *main* modules. > > After thinking about this, I think .xql and .xqm make good candidates > for a file naming convention, since they mnemonically reflect the > distinction between library (L) and main (M). Where does that leave > .xq, .xqy, or .xquery? I guess they're acceptable alternatives to .xq > for main modules, but in my own new projects I think I'm going to go > with .xql and .xqm. > > What practices do you use? What do you think? Does your > implementation/community document your practice? > > Joe > > [1] https://github.com/github/linguist/blob/master/lib/linguist/languages.yml. > I've submitted a pull request to add .xql and .xqm, > https://github.com/github/linguist/pull/338. > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk -- Adam Retter skype: adam.retter tweet: adamretter http://www.adamretter.org.uk

XQuery file naming conventions (xq, xqy, xql, xqm, xquery, etc.)

Mon, 07 Jan 2013 13:49:44 GMT

Hi Joe, in BaseX, .xq is used for main modules and .xqm for library modules (including RESTXQ modules). The main motivation for this was similar to yours: .xq is short, there was some need to distinguish between main and library modules, and there was no convention what would be the best choice. The current solution seems quite intuitive to most of our users, but I agree that your convention makes some sense, and is closer to the terminology of the XQuery spec. Best, Christian ___________________________ On Mon, Jan 7, 2013 at 10:33 PM, Joe Wicentowski wrote: > Hi all, > > There is quite a profusion of file extensions for XQuery: .xq, .xqy, > .xql, .xqm, and .xquery. Perhaps this profusion has happened the spec > doesn't say anything about the file extensions. This has opened up > the choice to each implementation and each community/project. I'd be > interested to know which communities use which file naming > conventions, and if there is any consensus? What do you use, and why? > > My experience: When I first started learning XQuery I used .xq for > everything -- I guess because it's short. oXygen uses .xquery as its > default file extension for XQuery files but recognizes all of the > above as XQuery files. The MarkLogic community seems to use .xqy. > When I started to write library modules I started to use .xqm, with > the 'm' indicating module. I saw yet others in the eXist-db community > using .xql, though it allows all of the above. Github doesn't > currently recognize .xql or .xqm as XQuery [1]. Diversity is fine, > but the downside is that newcomers are certainly confused, and anytime > we share code there is no reliable way to know whether a file is a > library or main module without opening it up. > > The spec does make a distinction that seems to apply to XQuery files. > It states that there are two kinds of modules: *library* modules and > *main* modules. The distinction is that library modules contain only > functions, whereas main modules contain a single main routine (though > can also contain function declarations). (See these two terms defined > in the spec at http://www.w3.org/TR/xquery/#dt-library-module and > http://www.w3.org/TR/xquery/#dt-main-module.) > > It seems to me that any good XQuery file naming convention should > reflect this distinction between *library* and *main* modules. > > After thinking about this, I think .xql and .xqm make good candidates > for a file naming convention, since they mnemonically reflect the > distinction between library (L) and main (M). Where does that leave > .xq, .xqy, or .xquery? I guess they're acceptable alternatives to .xq > for main modules, but in my own new projects I think I'm going to go > with .xql and .xqm. > > What practices do you use? What do you think? Does your > implementation/community document your practice? > > Joe > > [1] https://github.com/github/linguist/blob/master/lib/linguist/languages.yml. > I've submitted a pull request to add .xql and .xqm, > https://github.com/github/linguist/pull/338. > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk

XQuery file naming conventions (xq, xqy, xql, xqm, xquery, etc.)

Mon, 07 Jan 2013 13:43:19 GMT

My opinion. First, just like C and Java etc ... I dont see a need to seperate Libraries and Modules and Mains with extensions. The extension (should, IMHO) apply to the source language not to the use its applied. A single extension should do, and its main job is to load the right editor (for GUI systems ),and for non-gui systems is useful for simply telling apart languages like .xslt and .xquery Hey what do people use for .xslt ? .xsl ? .xs ? How about just .x and let the first line dictate !!!! Whenever I am by myself I use .xquery ... it just makes sense ! When I joined MarkLogic I adopted their convention for any code I write to be shipped with ML and use .xqy But for anything personal I still use .xquery I dont see the need for any more but hey, like standards the fun is that there are so many ! ---------------------------------------- David A. Lee http://x-query.com/mailman/listinfo/talk http://www.xmlsh.org -----Original Message----- From: http://x-query.com/mailman/listinfo/talk [mailto:http://x-query.com/mailman/listinfo/talk] On Behalf Of Joe Wicentowski Sent: Monday, January 07, 2013 4:33 PM To: XQuery Talk Subject: XQuery file naming conventions (xq, xqy, xql, xqm, xquery, etc.) Hi all, There is quite a profusion of file extensions for XQuery: .xq, .xqy, .xql, .xqm, and .xquery. Perhaps this profusion has happened the spec doesn't say anything about the file extensions. This has opened up the choice to each implementation and each community/project. I'd be interested to know which communities use which file naming conventions, and if there is any consensus? What do you use, and why? My experience: When I first started learning XQuery I used .xq for everything -- I guess because it's short. oXygen uses .xquery as its default file extension for XQuery files but recognizes all of the above as XQuery files. The MarkLogic community seems to use .xqy. When I started to write library modules I started to use .xqm, with the 'm' indicating module. I saw yet others in the eXist-db community using .xql, though it allows all of the above. Github doesn't currently recognize .xql or .xqm as XQuery [1]. Diversity is fine, but the downside is that newcomers are certainly confused, and anytime we share code there is no reliable way to know whether a file is a library or main module without opening it up. The spec does make a distinction that seems to apply to XQuery files. It states that there are two kinds of modules: *library* modules and *main* modules. The distinction is that library modules contain only functions, whereas main modules contain a single main routine (though can also contain function declarations). (See these two terms defined in the spec at http://www.w3.org/TR/xquery/#dt-library-module and http://www.w3.org/TR/xquery/#dt-main-module.) It seems to me that any good XQuery file naming convention should reflect this distinction between *library* and *main* modules. After thinking about this, I think .xql and .xqm make good candidates for a file naming convention, since they mnemonically reflect the distinction between library (L) and main (M). Where does that leave .xq, .xqy, or .xquery? I guess they're acceptable alternatives to .xq for main modules, but in my own new projects I think I'm going to go with .xql and .xqm. What practices do you use? What do you think? Does your implementation/community document your practice? Joe [1] https://github.com/github/linguist/blob/master/lib/linguist/languages.yml. I've submitted a pull request to add .xql and .xqm, https://github.com/github/linguist/pull/338. _______________________________________________ http://x-query.com/mailman/listinfo/talk http://x-query.com/mailman/listinfo/talk

XQuery file naming conventions (xq, xqy, xql, xqm, xquery, etc.)

Mon, 07 Jan 2013 13:33:22 GMT

Hi all, There is quite a profusion of file extensions for XQuery: .xq, .xqy, .xql, .xqm, and .xquery. Perhaps this profusion has happened the spec doesn't say anything about the file extensions. This has opened up the choice to each implementation and each community/project. I'd be interested to know which communities use which file naming conventions, and if there is any consensus? What do you use, and why? My experience: When I first started learning XQuery I used .xq for everything -- I guess because it's short. oXygen uses .xquery as its default file extension for XQuery files but recognizes all of the above as XQuery files. The MarkLogic community seems to use .xqy. When I started to write library modules I started to use .xqm, with the 'm' indicating module. I saw yet others in the eXist-db community using .xql, though it allows all of the above. Github doesn't currently recognize .xql or .xqm as XQuery [1]. Diversity is fine, but the downside is that newcomers are certainly confused, and anytime we share code there is no reliable way to know whether a file is a library or main module without opening it up. The spec does make a distinction that seems to apply to XQuery files. It states that there are two kinds of modules: *library* modules and *main* modules. The distinction is that library modules contain only functions, whereas main modules contain a single main routine (though can also contain function declarations). (See these two terms defined in the spec at http://www.w3.org/TR/xquery/#dt-library-module and http://www.w3.org/TR/xquery/#dt-main-module.) It seems to me that any good XQuery file naming convention should reflect this distinction between *library* and *main* modules. After thinking about this, I think .xql and .xqm make good candidates for a file naming convention, since they mnemonically reflect the distinction between library (L) and main (M). Where does that leave .xq, .xqy, or .xquery? I guess they're acceptable alternatives to .xq for main modules, but in my own new projects I think I'm going to go with .xql and .xqm. What practices do you use? What do you think? Does your implementation/community document your practice? Joe [1] https://github.com/github/linguist/blob/master/lib/linguist/languages.yml. I've submitted a pull request to add .xql and .xqm, https://github.com/github/linguist/pull/338.

Basex: using all of -i, -c and -q

Thu, 27 Dec 2012 02:03:59 GMT

I tried to use all of -i, -c, and -q, but in the end the only thing for me that worked was $ basex -q 'declare option db:parser "html"; doc("bla.html")' so maybe it is not possible. P.S., I tried to send this to the right list, alas, : host cytosin.uni-konstanz.de[134.34.240.61] said: 550 #5.1.0 Address rejected. (in reply to RCPT TO command)

let's comment out a line in XQuery

Sat, 22 Dec 2012 15:09:58 GMT

>>>>> "MK" == Michael Kay writes: MK> The use of /text() in this way is generally a bad habit. Thanks! I removed them and my program worked just as fine! (Not Cc'd so didn't notice your comment until now.)

Join my network on LinkedIn

Fri, 21 Dec 2012 15:39:06 GMT

LinkedIn ------------ Christian Grün has indicated you are a Friend ------------------------------------------ Since you are a person I trust, I wanted to invite you to join my network on LinkedIn. Accept invitation from Christian Grün http://www.linkedin.com/e/xnupbm-hazynsqq-6d/kDd-YG5BG4ZUACXjkyk-G9jZp24/blk/I384377797_12/3wOtCVFbmdxnSVFbm8JrnpKqlZJrmZzbmNJpjRQnOpBtn9QfmhBt71BoSd1p65Lr6lOfP8NnPsVdPsTcPgUcQALhRhbi2RKp6YLd3cNc3oTdPgNc34LrCBxbOYWrSlI/eml-comm_invm-b-in_ac-inv28/?hs=false&tok=3xGq4sF4XHUlw1 View profile of Christian Grün http://www.linkedin.com/e/xnupbm-hazynsqq-6d/rso/1401638/j1Xp/name/94457480_I384377797_12/?hs=false&tok=0NJzgrz23HUlw1 ------------------------------------------ You are receiving Invitation emails. This email was intended for Ihe Onwuka. Learn why this is included: http://www.linkedin.com/e/xnupbm-hazynsqq-6d/plh/http%3A%2F%2Fhelp%2Elinkedin%2Ecom%2Fapp%2Fanswers%2Fdetail%2Fa_id%2F4788/-GXI/?hs=false&tok=0vplFFC6XHUlw1 (c) 2012, LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA. -------------- next part -------------- An HTML attachment was scrubbed... URL:

let's comment out a line in XQuery

Fri, 21 Dec 2012 07:11:09 GMT

On 12/21/2012 09:40 AM, David Lee wrote: > in XQuery > > declare function foo() {} > > is bad for precisely the same reason as functions *always* have a return type. > (no void). But what should it be ? > Again, empty-sequence() is the only logical choice. Better than an error in my book.

[ANN] BaseX 7.5 -- The BaseXMas Edition

Fri, 21 Dec 2012 06:55:47 GMT

Dear all, we are excited to announce the release of BaseX 7.5, aka the BaseXMas Edition: http://basex.org/downloads The latest features and changes are as follows: XQUERY UPDATE - bulk updates are now much faster than before - insert and replace operations take much less memory - databases can now be created via XQuery and db:create() GUI TEXT EDITOR - a fast and flexible search/replace panel has been added - error highlighting has been extended to XML files - the editor was improved for editing arbitrary text files XQUERY 3.0 - the code has been aligned with latest changes in the specs - HTML5 support has been updated WEB APPLICATIONS - new modules have been added: Request, Session, Sessions - logging has been revised and extended to HTTP requests - SSL support added, switched to Jetty 8 - all operation modes have been unified and simplified - RESTXQ elements added to simplify forwarding and redirects CORE FEATURES - improved stability of concurrent read/write operations - the INSPECT command performs database sanity checks - EXECUTE triggers the execution of command scripts Numerous other updates can be found in our documentation (http://docs.basex.org). Your feedback is welcome. Christian BaseX Team 2012 PS: We hope to see you all on the XMLPrague Conference 2013! If you haven’t registered yet, you are invited to join our BaseX User Meeting: http://lanyrd.com/2013/basex-users-meetup-xml-prague

let's comment out a line in XQuery

Fri, 21 Dec 2012 06:49:53 GMT

... whether there is any good reason plain {} doesn't generate () (an empty sequence)? I'm not aware that the idea has ever been proposed and discussed in the WG. I've no idea whether it would find favour. Probably not; minor tweaking for minor usability benefits doesn't usually attract much enthusiasm. You might find someone in the WG has grand ideas to use the same syntax for something else, like an empty map or array, and wants to hold it in reserve for that, and on past experience that would probably win the argument. Michael Kay Saxonica

let's comment out a line in XQuery

Fri, 21 Dec 2012 06:43:18 GMT

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 (no nodes where is, not even a > comment node), one would need: > > {(::)()} > > ? That's a lot of punctuation. > > I think this has been batted around here before, http://www.stylusstudio.com/xquerytalk/201207/003932.html

let's comment out a line in XQuery

Fri, 21 Dec 2012 06:40:55 GMT

------------- Actually my compiler allows "void foo () { }" - why not? A function that does nothing could be very useful sometimes. "foo () { }" is bad because implicitly it is declared as returning int, yet does not return anything. ----------- Which is why I used as an example foo() {} which in K&R C means int foo() {} not void foo() {} in XQuery declare function foo() {} is bad for precisely the same reason as functions *always* have a return type. (no void). But what should it be ? ----------------------------------------------------------------------------- David Lee Lead Engineer MarkLogic Corporation http://x-query.com/mailman/listinfo/talk Phone: +1 812-482-5224 Cell: +1 812-630-7622 www.marklogic.com

let's comment out a line in XQuery

Fri, 21 Dec 2012 06:38:09 GMT

On 12/21/2012 09:32 AM, David Lee wrote: > ------------------ > I think this has been batted around here before, but would somebody mind > refreshing us as to whether there is any good reason plain {} doesn't > generate () (an empty sequence)? > --------------- > > If you want historical rationality you will have to ask someone else. > > > If you want deductive logic ... > > { expr } parses expr ... it returns whatever expr is. If there is nothing there then thats nothing. () is not nothing, its something. So it would be silly and inconsistent if {} produced something rather than nothing. > Actually I think () is the closest we have to null and void in xquery, so it seems consistent and logical to me :) > Also there is the other use of {} which is in functions > > declare function x () { }; > > > Which is rightfully an error because there is no expression and should be. > Although one could argue that it should be treated as > declare function x () { ()}; > Yes I would > But then one could argue that in C > > foo() { } > > should be treated as > foo() { return NULL ; } > > But that would be silly now wouldn't it ? > > Actually my compiler allows "void foo () { }" - why not? A function that does nothing could be very useful sometimes. "foo () { }" is bad because implicitly it is declared as returning int, yet does not return anything.

let's comment out a line in XQuery

Fri, 21 Dec 2012 06:32:28 GMT

------------------ I think this has been batted around here before, but would somebody mind refreshing us as to whether there is any good reason plain {} doesn't generate () (an empty sequence)? --------------- If you want historical rationality you will have to ask someone else. If you want deductive logic ... { expr } parses expr ... it returns whatever expr is. If there is nothing there then thats nothing. () is not nothing, its something. So it would be silly and inconsistent if {} produced something rather than nothing. The only time that I can see that it is actually inconvenient ("annoying"?) that {} produces nothing rather then something is in this particular case with comments embedded within literal constructors. Buy why single out () as the something it should produce ? There is nothing special about the empty sequence that makes it the best candidate for a fillin for nothing. Also there is the other use of {} which is in functions declare function x () { }; Which is rightfully an error because there is no expression and should be. Although one could argue that it should be treated as declare function x () { ()}; But then one could argue that in C foo() { } should be treated as foo() { return NULL ; } But that would be silly now wouldn't it ? In the end I am not going to try to justify this rule in XQuery ... it just is the way it is. ----------------------------------------------------------------------------- David Lee Lead Engineer MarkLogic Corporation http://x-query.com/mailman/listinfo/talk Phone: +1 812-482-5224 Cell: +1 812-630-7622 www.marklogic.com

let's comment out a line in XQuery

Fri, 21 Dec 2012 05:08:35 GMT

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 (no nodes where is, not even a comment node), one would need: {(::)()} ? That's a lot of punctuation. I think this has been batted around here before, but would somebody mind refreshing us as to whether there is any good reason plain {} doesn't generate () (an empty sequence)? -Mike

let's comment out a line in XQuery

Thu, 20 Dec 2012 08:47:05 GMT

OK, I will try various combinations of these in various situations. I just wish Google searches wouldn't always just come up with (: :) when in fact one often needs "the heavy pliers" instead. DL> its actually quite easy once you learn the syntax. I'm sure it must be, but I just want to... http://www.google.com/search?q=Big+Daddy+Kane+I+get+the+job+done get the job done.

let's comment out a line in XQuery

Thu, 20 Dec 2012 08:25:33 GMT

Sorry, you need to make a bit more room in your brain. The proper syntax is context specific. And I made a mistake in my example. double bad :) inside an element constructor you need this: {()(:comment:)} other places you use (: comment :) but realize that produces nothing, not the empty sequence so some places it wont work and you might need ()(:comment:) its actually quite easy once you learn the syntax. ---------------------------------------- David A. Lee http://x-query.com/mailman/listinfo/talk http://www.xmlsh.org -----Original Message----- From: http://x-query.com/mailman/listinfo/talk [mailto:http://x-query.com/mailman/listinfo/talk] Sent: Thursday, December 20, 2012 11:12 AM To: David Lee Cc: http://x-query.com/mailman/listinfo/talk; http://x-query.com/mailman/listinfo/talk Subject: Re: let's comment out a line in XQuery OK. In my brain (which only has room for one comment syntax per language) I will now try to remember {(: comment :)()} as the REAL XQuery comment syntax (the one that is guaranteed not to fail, the one that gets even tough stains out), and any simplifications thereof e.g., (: comment :) as mere shortcuts that will sometimes fail. I hope that is fair, assuming I only want to remember one comment syntax. (No I don't want to use as that ends up in the laundry.)

let's comment out a line in XQuery

Thu, 20 Dec 2012 08:12:25 GMT

OK. In my brain (which only has room for one comment syntax per language) I will now try to remember {(: comment :)()} as the REAL XQuery comment syntax (the one that is guaranteed not to fail, the one that gets even tough stains out), and any simplifications thereof e.g., (: comment :) as mere shortcuts that will sometimes fail. I hope that is fair, assuming I only want to remember one comment syntax. (No I don't want to use as that ends up in the laundry.)

let's comment out a line in XQuery

Thu, 20 Dec 2012 08:00:09 GMT

Your problem is the call concat($f/*:Placemark[$c]//*:coordinates/text(), ... The first argument selects more than one text node, but the arguments to concat() must be single items. Note that you haven't actually commented anything out. When you change the content of an element constructor from to (::) the content of the element will be a text node containing " (:", an empty b element, a text node containing ":) ", an empty element, and possibly (depending on boundary-space settings) a text node containing a single space. This is because comment delimiters are not recognized inside literal element content. The use of /text() in this way is generally a bad habit. Normally if you want the value of the coordinates element, it's best just to atomize the element. You should only use text() if you want to pick out the text nodes from among the other children of the element. Michael Kay Saxonica On 20/12/2012 15:39, http://x-query.com/mailman/listinfo/talk wrote: > I don't have a Senior Secondary Certificate of Education :-) but here > goes anyway. basex: Debian's 7.3-1. > $ basex noise0.xq |wc > Stopped at line 26, column 46 in /home/jidanni/mapping/kml/noise0.xq: > [XPTY0004] Single item expected, ( ALLOW ME TO COMMENT OUT THIS LINE, ...) found. > 0 0 0 > $ cat noise0.xq > (: > # Make a map of noisy neighbors, Xquery version. > # Copyright : http://www.fsf.org/copyleft/gpl.html > # Author : Dan Jacobson -- http://jidanni.org/ > # Created On : Sat Jan 29 17:28:12 2011 > # Last Modified On: Thu Dec 20 23:29:24 2012 > # Update Count : 122 > :) > declare option output:omit-xml-declaration "no"; > declare function local:fol($f){ > (: just adds lines between the first point and the rest :) > > {$f/*} > > (lines) > 0 > { > for $p at $c in $f/*:Placemark > where $c > 1 > return > > {concat($f/*:Placemark[$c]//*:name/text()," to ", > $f/*:Placemark[ 1]//*:name/text())} > > {concat($f/*:Placemark[$c]//*:coordinates/text()," ", > $f/*:Placemark[ 1]//*:coordinates/text())} > > > } > } > ; > > {comment {"Made by noise.xq, will get OVERWRITTEN"}} > > > 噪音 Noise > http://jidanni.org/me/quiet.html > {local:fol( > > 慶福街 1-3 Qingfu St. > > 1-3 > > (: ALLOW ME TO COMMENT OUT THIS LINE :) > 120.865201,24.181712 (: 2012/12 Google satellite :) > > > > Luo Yuntian > > 120.868205,24.176483 > > > > Zhong Guilin > > 120.866934,24.152642 > > > > Maan Nong Zhuang > > 120.84368,24.17268 (: 東勢區慶福里007鄰-東關路１４７號 :) > > > )} > {local:fol( > > 慶福街 1-6 Qingfu St. > > 1-6 > > 120.866215,24.181668 > > > > Liu Shiqing > > 120.86981,24.19667 (: Approx :) > > > > Wu Yuxuan > > 120.86981,24.18811 > > > > Chen Chunlai > > 120.877008,24.187393 > > > > Chen Zhenfeng > > 120.87456,24.18333 > > > > Dazhong > > 120.872499,24.200025 > > > > Liu Jinxing > > 120.874624,24.193282 > > > > Zeng Pingzhu > > 120.868530,24.183716 > > > )} > > > > > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk

let's comment out a line in XQuery

Thu, 20 Dec 2012 07:47:05 GMT

As per the mailing list archive link I sent yesterday. Use this to comment out data inside XML literal constructors { (: ALLOW ME TO COMMENT OUT THIS LINE :) } ... ---------------------------------------- David A. Lee http://x-query.com/mailman/listinfo/talk http://www.xmlsh.org -----Original Message----- From: http://x-query.com/mailman/listinfo/talk [mailto:http://x-query.com/mailman/listinfo/talk] On Behalf Of http://x-query.com/mailman/listinfo/talk Sent: Thursday, December 20, 2012 10:39 AM To: http://x-query.com/mailman/listinfo/talk Cc: http://x-query.com/mailman/listinfo/talk Subject: Re: let's comment out a line in XQuery I don't have a Senior Secondary Certificate of Education :-) but here goes anyway. basex: Debian's 7.3-1. $ basex noise0.xq |wc Stopped at line 26, column 46 in /home/jidanni/mapping/kml/noise0.xq: [XPTY0004] Single item expected, ( ALLOW ME TO COMMENT OUT THIS LINE, ...) found. 0 0 0 $ cat noise0.xq (: # Make a map of noisy neighbors, Xquery version. # Copyright : http://www.fsf.org/copyleft/gpl.html # Author : Dan Jacobson -- http://jidanni.org/ # Created On : Sat Jan 29 17:28:12 2011 # Last Modified On: Thu Dec 20 23:29:24 2012 # Update Count : 122 :) declare option output:omit-xml-declaration "no"; declare function local:fol($f){ (: just adds lines between the first point and the rest :) {$f/*} (lines) 0 { for $p at $c in $f/*:Placemark where $c > 1 return {concat($f/*:Placemark[$c]//*:name/text()," to ", $f/*:Placemark[ 1]//*:name/text())} {concat($f/*:Placemark[$c]//*:coordinates/text()," ", $f/*:Placemark[ 1]//*:coordinates/text())} } } ; {comment {"Made by noise.xq, will get OVERWRITTEN"}} 噪音 Noise http://jidanni.org/me/quiet.html {local:fol( 慶福街 1-3 Qingfu St. 1-3 (: ALLOW ME TO COMMENT OUT THIS LINE :) 120.865201,24.181712 (: 2012/12 Google satellite :) Luo Yuntian 120.868205,24.176483 Zhong Guilin 120.866934,24.152642 Maan Nong Zhuang 120.84368,24.17268 (: 東勢區慶福里007鄰-東關路１４７號 :) )} {local:fol( 慶福街 1-6 Qingfu St. 1-6 120.866215,24.181668 Liu Shiqing 120.86981,24.19667 (: Approx :) Wu Yuxuan 120.86981,24.18811 Chen Chunlai 120.877008,24.187393 Chen Zhenfeng 120.87456,24.18333 Dazhong 120.872499,24.200025 Liu Jinxing 120.874624,24.193282 Zeng Pingzhu 120.868530,24.183716 )} _______________________________________________ http://x-query.com/mailman/listinfo/talk http://x-query.com/mailman/listinfo/talk

let's comment out a line in XQuery

Thu, 20 Dec 2012 07:39:22 GMT

I don't have a Senior Secondary Certificate of Education :-) but here goes anyway. basex: Debian's 7.3-1. $ basex noise0.xq |wc Stopped at line 26, column 46 in /home/jidanni/mapping/kml/noise0.xq: [XPTY0004] Single item expected, ( ALLOW ME TO COMMENT OUT THIS LINE, ...) found. 0 0 0 $ cat noise0.xq (: # Make a map of noisy neighbors, Xquery version. # Copyright : http://www.fsf.org/copyleft/gpl.html # Author : Dan Jacobson -- http://jidanni.org/ # Created On : Sat Jan 29 17:28:12 2011 # Last Modified On: Thu Dec 20 23:29:24 2012 # Update Count : 122 :) declare option output:omit-xml-declaration "no"; declare function local:fol($f){ (: just adds lines between the first point and the rest :) {$f/*} (lines) 0 { for $p at $c in $f/*:Placemark where $c > 1 return {concat($f/*:Placemark[$c]//*:name/text()," to ", $f/*:Placemark[ 1]//*:name/text())} {concat($f/*:Placemark[$c]//*:coordinates/text()," ", $f/*:Placemark[ 1]//*:coordinates/text())} } } ; {comment {"Made by noise.xq, will get OVERWRITTEN"}} 噪音 Noise http://jidanni.org/me/quiet.html {local:fol( 慶福街 1-3 Qingfu St. 1-3 (: ALLOW ME TO COMMENT OUT THIS LINE :) 120.865201,24.181712 (: 2012/12 Google satellite :) Luo Yuntian 120.868205,24.176483 Zhong Guilin 120.866934,24.152642 Maan Nong Zhuang 120.84368,24.17268 (: 東勢區慶福里007鄰-東關路１４７號 :) )} {local:fol( 慶福街 1-6 Qingfu St. 1-6 120.866215,24.181668 Liu Shiqing 120.86981,24.19667 (: Approx :) Wu Yuxuan 120.86981,24.18811 Chen Chunlai 120.877008,24.187393 Chen Zhenfeng 120.87456,24.18333 Dazhong 120.872499,24.200025 Liu Jinxing 120.874624,24.193282 Zeng Pingzhu 120.868530,24.183716 )}

let's comment out a line in XQuery

Thu, 20 Dec 2012 04:19:55 GMT

Arg so tired I can't copy/paste sorry http://markmail.org/thread/cd2nyugalcffjf3o -----Original Message----- From: http://x-query.com/mailman/listinfo/talk [mailto:http://x-query.com/mailman/listinfo/talk] On Behalf Of David Lee Sent: Thursday, December 20, 2012 7:18 AM To: Michael Kay; http://x-query.com/mailman/listinfo/talk Subject: Re: let's comment out a line in XQuery Since I am tired this morning :) Try perusing this tread for a lively discussion on XQuery comments arkmail.org/thread/cd2nyugalcffjf3o -----Original Message----- From: http://x-query.com/mailman/listinfo/talk [mailto:http://x-query.com/mailman/listinfo/talk] On Behalf Of Michael Kay Sent: Thursday, December 20, 2012 3:30 AM To: http://x-query.com/mailman/listinfo/talk Subject: Re: let's comment out a line in XQuery Clearly there are contexts in which commenting out a line of code will leave a query that is syntactically or semantically invalid. Why do you find this strange? Why do you expect us to be able to tell you why the remaining query throws an error, when you haven't shown us this query? Or is this a Christmas quiz: invent a query such that removing line 26 will cause this error? Michael Kay Saxonica On 20/12/2012 05:45, http://x-query.com/mailman/listinfo/talk wrote: > Geez, all I wanted to do was comment out a line: > (: 120.865225,24.181802 :) But now I have > to make it > (: 120.865225,24.181802 :) > or else I get > $ basex noise.xq > noise.kml > Stopped at line 26, column 46 in /home/jidanni/mapping/kml/noise.xq: > [XPTY0004] Single item expected, (120.865225,24.181802, 120.865201,24.181712) found. > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk > _______________________________________________ http://x-query.com/mailman/listinfo/talk http://x-query.com/mailman/listinfo/talk _______________________________________________ http://x-query.com/mailman/listinfo/talk http://x-query.com/mailman/listinfo/talk

let's comment out a line in XQuery

Thu, 20 Dec 2012 04:18:26 GMT

Since I am tired this morning :) Try perusing this tread for a lively discussion on XQuery comments arkmail.org/thread/cd2nyugalcffjf3o -----Original Message----- From: http://x-query.com/mailman/listinfo/talk [mailto:http://x-query.com/mailman/listinfo/talk] On Behalf Of Michael Kay Sent: Thursday, December 20, 2012 3:30 AM To: http://x-query.com/mailman/listinfo/talk Subject: Re: let's comment out a line in XQuery Clearly there are contexts in which commenting out a line of code will leave a query that is syntactically or semantically invalid. Why do you find this strange? Why do you expect us to be able to tell you why the remaining query throws an error, when you haven't shown us this query? Or is this a Christmas quiz: invent a query such that removing line 26 will cause this error? Michael Kay Saxonica On 20/12/2012 05:45, http://x-query.com/mailman/listinfo/talk wrote: > Geez, all I wanted to do was comment out a line: > (: 120.865225,24.181802 :) But now I have > to make it > (: 120.865225,24.181802 :) > or else I get > $ basex noise.xq > noise.kml > Stopped at line 26, column 46 in /home/jidanni/mapping/kml/noise.xq: > [XPTY0004] Single item expected, (120.865225,24.181802, 120.865201,24.181712) found. > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk > _______________________________________________ http://x-query.com/mailman/listinfo/talk http://x-query.com/mailman/listinfo/talk

let's comment out a line in XQuery

Thu, 20 Dec 2012 00:29:33 GMT

Clearly there are contexts in which commenting out a line of code will leave a query that is syntactically or semantically invalid. Why do you find this strange? Why do you expect us to be able to tell you why the remaining query throws an error, when you haven't shown us this query? Or is this a Christmas quiz: invent a query such that removing line 26 will cause this error? Michael Kay Saxonica On 20/12/2012 05:45, http://x-query.com/mailman/listinfo/talk wrote: > Geez, all I wanted to do was comment out a line: > (: 120.865225,24.181802 :) > But now I have to make it > (: 120.865225,24.181802 :) > or else I get > $ basex noise.xq > noise.kml > Stopped at line 26, column 46 in /home/jidanni/mapping/kml/noise.xq: > [XPTY0004] Single item expected, (120.865225,24.181802, 120.865201,24.181712) found. > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk >

let's comment out a line in XQuery

Wed, 19 Dec 2012 23:41:05 GMT

Hi jidanni, Your particular line does not cause an error here. Tried it with the BaseX live demo (online). Your query indicates it consists of at least 26 lines, could you provide the whole query, or even better an ssce? We are using comments in XQuery on a day to basis, so I hope you're only provided with a misleading error message :-) Best Michael Am 20.12.2012 um 06:45 schrieb http://x-query.com/mailman/listinfo/talk: > Geez, all I wanted to do was comment out a line: > (: 120.865225,24.181802 :) > But now I have to make it > (: 120.865225,24.181802 :) > or else I get > $ basex noise.xq > noise.kml > Stopped at line 26, column 46 in /home/jidanni/mapping/kml/noise.xq: > [XPTY0004] Single item expected, (120.865225,24.181802, 120.865201,24.181712) found. > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk

let's comment out a line in XQuery

Wed, 19 Dec 2012 21:45:37 GMT

Geez, all I wanted to do was comment out a line: (: 120.865225,24.181802 :) But now I have to make it (: 120.865225,24.181802 :) or else I get $ basex noise.xq > noise.kml Stopped at line 26, column 46 in /home/jidanni/mapping/kml/noise.xq: [XPTY0004] Single item expected, (120.865225,24.181802, 120.865201,24.181712) found.

static error [err:XPST0051]: "xs:anySimpleType": not defined as atomic type

Wed, 19 Dec 2012 07:40:37 GMT

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 this originated in Standard ML (and anybody wondering whether learning Standard ML would short circuit their Scala learning curve would IMHO be right). http://www.standardml.org/Basis/option.html PS I am not an expert.

static error [err:XPST0051]: "xs:anySimpleType": not defined as atomic type

Wed, 19 Dec 2012 06:54:28 GMT

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 Cheers, Robby -----Original Message----- From: Robby Pelssers Sent: Wednesday, December 19, 2012 3:21 PM To: http://x-query.com/mailman/listinfo/talk; Robby Pelssers Subject: static error [err:XPST0051]: "xs:anySimpleType": not defined as atomic type Hi all, I was experimenting a bit to make my code more robust but I don't fully understand why the code below complains about the local:getOrElse function. Can someone shed some light on this matter? Thx in advance, Robby (: Taken the same approach as Scala we return options which are either none or some Example of a lookup map represented in XML SOT669 SOT78B SOT404 :) declare function local:getOrElse($map as element(map), $key as xs:string, $else as xs:anySimpleType) as xs:anySimpleType { let $option := local:get($map, $key) return (if (empty($option/some)) then $else else data($option/some)) }; declare function local:get($map as element(map), $key as xs:string) as element(option) { return (if (empty($map/entry[key=$key])) then else ) }; let $map := SOT669 SOT78B SOT404 return {local:getOrElse($map, "PH3330L", "test1")} {local:getOrElse($map, "INVALID", "test1")}

static error [err:XPST0051]: "xs:anySimpleType": not defined as atomic type

Wed, 19 Dec 2012 06:21:21 GMT

Hi all, I was experimenting a bit to make my code more robust but I don't fully understand why the code below complains about the local:getOrElse function. Can someone shed some light on this matter? Thx in advance, Robby (: Taken the same approach as Scala we return options which are either none or some Example of a lookup map represented in XML SOT669 SOT78B SOT404 :) declare function local:getOrElse($map as element(map), $key as xs:string, $else as xs:anySimpleType) as xs:anySimpleType { let $option := local:get($map, $key) return (if (empty($option/some)) then $else else data($option/some)) }; declare function local:get($map as element(map), $key as xs:string) as element(option) { return (if (empty($map/entry[key=$key])) then else ) }; let $map := SOT669 SOT78B SOT404 return {local:getOrElse($map, "PH3330L", "test1")} {local:getOrElse($map, "INVALID", "test1")}

The value does not conform to the lexical constraints defined for the xs:anyURI type

Wed, 19 Dec 2012 04:11:12 GMT

>> http://www.w3.org/2011/04/XMLSchema/TypeLibrary-IRI-RFC3987.xsd So the newest regex is the union of ((([A-Za-z])[A-Za-z0-9+\-\.]*):((//(((([A-Za-z0-9\-\._~ -퟿豈-﷏ﷰ-￯��- ��-��-��-��-��-��-��-��-��-��-��-��- ��-��!$&'()*+,;=:]|(%[0-9A-Fa-f][0-9A-Fa-f]))*@))?((\[((((([0-9A-Fa-f]{0,4}:)){6}(([0-9A-Fa-f]{0,4}:[0-9A-Fa-f]{0,4})|(([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5])))))|(::(([0-9A-Fa-f]{0,4}:)){5}(([0-9A-Fa-f]{0,4}:[0-9A-Fa-f]{0,4})|(([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5])))))|(([0-9A-Fa-f]{0,4})?::(([0-9A-Fa-f]{0,4}:)){4}(([0-9A-Fa-f]{0,4}:[0-9A-Fa-f]{0,4})|(([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5])))))|((((([0-9A-Fa-f]{0,4}:))?[0-9A-Fa-f]{0,4}))?::(([0-9A-Fa-f]{0,4}:)){3}(([0-9A-Fa-f]{0,4}:[0-9A-Fa-f]{0,4})|(([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5])))))|((((([0-9A-Fa-f]{0,4}:)){0,2}[0-9A-Fa-f]{0,4}))?::(([0-9A-Fa-f]{0,4}:)){2}(([0-9A-Fa-f]{0,4}:[0-9A-Fa-f]{0,4})|(([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5])))))|((((([0-9A-Fa-f]{0,4}:)){0,3}[0-9A-Fa-f]{0,4}))?::[0-9A-Fa-f]{0,4}:(([0-9A-Fa-f]{0,4}:[0-9A-Fa-f]{0,4})|(([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5])))))|((((([0-9A-Fa-f]{0,4}:)){0,4}[0-9A-Fa-f]{0,4}))?::(([0-9A-Fa-f]{0,4}:[0-9A-Fa-f]{0,4})|(([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5])))))|((((([0-9A-Fa-f]{0,4}:)){0,5}[0-9A-Fa-f]{0,4}))?::[0-9A-Fa-f]{0,4})|((((([0-9A-Fa-f]{0,4}:)){0,6}[0-9A-Fa-f]{0,4}))?::))|(v[0-9A-Fa-f]+\.[A-Za-z0-9\-\._~!$&'()*+,;=:]+))\])|(([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5])))|(([A-Za-z0-9\-\._~ -퟿豈-﷏ﷰ-￯��-��-��-��-��-��-��-��-��-��-��-��- ��-��-��]|(%[0-9A-Fa-f][0-9A-Fa-f])|[!$&'()*+,;=]))*)((:[0-9]*))?)((/(([A-Za-z0-9\-\._~ -퟿豈-﷏ﷰ-￯��-��-��-��-��-��-��-��-��-��-��-��- ��-��-��]|(%[0-9A-Fa-f][0-9A-Fa-f])|[!$&'()*+,;=:@]))*))*)|(/(((([A-Za-z0-9\-\._~ -퟿豈-﷏ﷰ-￯��-��-��-��-��-��-��-��-��-��-��-��- ��-��-��]|(%[0-9A-Fa-f][0-9A-Fa-f])|[!$&'()*+,;=:@]))+((/(([A-Za-z0-9\-\._~ -퟿豈-﷏ﷰ-￯��-��-��-��-��-��-��-��-��-��-��-��- ��-��-��]|(%[0-9A-Fa-f][0-9A-Fa-f])|[!$&'()*+,;=:@]))*))*))?)|((([A-Za-z0-9\-\._~ -퟿豈-﷏ﷰ-￯��-��-��-��-��-��-��-��-��-��-��-��- ��-��-��]|(%[0-9A-Fa-f][0-9A-Fa-f])|[!$&'()*+,;=:@]))+((/(([A-Za-z0-9\-\._~ -퟿豈-﷏ﷰ-￯��-��-��-��-��-��-��-��-��-��-��-��- ��-��-��]|(%[0-9A-Fa-f][0-9A-Fa-f])|[!$&'()*+,;=:@]))*))*)|)((\?(([A-Za-z0-9\-\._~ -퟿豈-﷏ﷰ-￯��-��-��-��-��-��-��-��-��-��-��-��- ��-��-��]|(%[0-9A-Fa-f][0-9A-Fa-f])|[!$&'()*+,;=:@])|[-��-��-��/?])*))?((#((([A-Za-z0-9\-\._~ -퟿豈-﷏ﷰ-￯��-��-��-��-��-��-��-��-��-��-��-��- ��-��-��]|(%[0-9A-Fa-f][0-9A-Fa-f])|[!$&'()*+,;=:@])|/|\?))*))?) and (((//(((([A-Za-z0-9\-\._~ -퟿豈-﷏ﷰ-￯��-��-��-��-��-��-��- ��-��-��-��-��-��- ��-��!$&'()*+,;=:]|(%[0-9A-Fa-f][0-9A-Fa-f]))*@))?((\[((((([0-9A-Fa-f]{0,4}:)){6}(([0-9A-Fa-f]{0,4}:[0-9A-Fa-f]{0,4})|(([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5])))))|(::(([0-9A-Fa-f]{0,4}:)){5}(([0-9A-Fa-f]{0,4}:[0-9A-Fa-f]{0,4})|(([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5])))))|(([0-9A-Fa-f]{0,4})?::(([0-9A-Fa-f]{0,4}:)){4}(([0-9A-Fa-f]{0,4}:[0-9A-Fa-f]{0,4})|(([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5])))))|((((([0-9A-Fa-f]{0,4}:))?[0-9A-Fa-f]{0,4}))?::(([0-9A-Fa-f]{0,4}:)){3}(([0-9A-Fa-f]{0,4}:[0-9A-Fa-f]{0,4})|(([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5])))))|((((([0-9A-Fa-f]{0,4}:)){0,2}[0-9A-Fa-f]{0,4}))?::(([0-9A-Fa-f]{0,4}:)){2}(([0-9A-Fa-f]{0,4}:[0-9A-Fa-f]{0,4})|(([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5])))))|((((([0-9A-Fa-f]{0,4}:)){0,3}[0-9A-Fa-f]{0,4}))?::[0-9A-Fa-f]{0,4}:(([0-9A-Fa-f]{0,4}:[0-9A-Fa-f]{0,4})|(([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5])))))|((((([0-9A-Fa-f]{0,4}:)){0,4}[0-9A-Fa-f]{0,4}))?::(([0-9A-Fa-f]{0,4}:[0-9A-Fa-f]{0,4})|(([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5])))))|((((([0-9A-Fa-f]{0,4}:)){0,5}[0-9A-Fa-f]{0,4}))?::[0-9A-Fa-f]{0,4})|((((([0-9A-Fa-f]{0,4}:)){0,6}[0-9A-Fa-f]{0,4}))?::))|(v[0-9A-Fa-f]+\.[A-Za-z0-9\-\._~!$&'()*+,;=:]+))\])|(([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5]))\.([0-9]|([1-9][0-9])|(1([0-9]){2})|(2[0-4][0-9])|(25[0-5])))|(([A-Za-z0-9\-\._~ -퟿豈-﷏ﷰ-￯��-��-��-��-��-��-��-��-��-��-��-��- ��-��-��]|(%[0-9A-Fa-f][0-9A-Fa-f])|[!$&'()*+,;=]))*)((:[0-9]*))?)((/(([A-Za-z0-9\-\._~ -퟿豈-﷏ﷰ-￯��-��-��-��-��-��-��-��-��-��-��-��- ��-��-��]|(%[0-9A-Fa-f][0-9A-Fa-f])|[!$&'()*+,;=:@]))*))*)|(/(((([A-Za-z0-9\-\._~ -퟿豈-﷏ﷰ-￯��-��-��-��-��-��-��-��-��-��-��-��- ��-��-��]|(%[0-9A-Fa-f][0-9A-Fa-f])|[!$&'()*+,;=:@]))+((/(([A-Za-z0-9\-\._~ -퟿豈-﷏ﷰ-￯��-��-��-��-��-��-��-��-��-��-��-��- ��-��-��]|(%[0-9A-Fa-f][0-9A-Fa-f])|[!$&'()*+,;=:@]))*))*))?)|(([A-Za-z0-9\-\._~ -퟿豈-﷏ﷰ-￯��-��-��-��-��-��-��-��-��-��-��-��- ��-��-��!$&'()*+,;=@]|(%[0-9A-Fa-f][0-9A-Fa-f]))+((/(([A-Za-z0-9\-\._~ -퟿豈-﷏ﷰ-￯��-��-��-��-��-��-��-��-��-��-��-��- ��-��-��]|(%[0-9A-Fa-f][0-9A-Fa-f])|[!$&'()*+,;=:@]))*))*))?((\?(([A-Za-z0-9\-\._~ -퟿豈-﷏ﷰ-￯��-��-��-��-��-��-��-��-��-��-��-��- ��-��-��]|(%[0-9A-Fa-f][0-9A-Fa-f])|[!$&'()*+,;=:@])|[-��-��-��/?])*))?((#((([A-Za-z0-9\-\._~ -퟿豈-﷏ﷰ-￯��-��-��-��-��-��-��-��-��-��-��-��- ��-��-��]|(%[0-9A-Fa-f][0-9A-Fa-f])|[!$&'()*+,;=:@])|/|\?))*))?) But that is even worse! Benito On 12/19/2012 12:41 PM, Michael Kay wrote:> Michael Sperberg-McQueen has defined types that match> different flavours of URI in>> http://www.w3.org/2011/04/XMLSchema/TypeLibrary-URI-RFC3986.xsd>> and>> http://www.w3.org/2011/04/XMLSchema/TypeLibrary-IRI-RFC3987.xsd>> To see the way these complex regular expressions are constructed, view> these documents at the raw XML level using (for example) curl.>> Michael Kay> Saxonica>>> On 19/12/2012 11:13, Benito van der Zander wrote:>> Hi,>>>> btw. has anyone a regular expression matching exactly the allowed >> anyURIs of XSD 1.0?>>>> I tried to make one by translating the BNF in RFC 2396 and 2732 to >> regex, by having a regex for every token, and substituting them >> everywhere the token is used in the BNF.>>>> But the resulting regex:>>>> ((((([a-zA-Z][a-zA-Z0-9+-.]*:)?((//(((([a-zA-Z0-9-_.!~*''();:&=+$,]|%[a-fA-F0-9]{2})*@)?((([a-zA-Z0-9]([-a-zA-Z0-9]*[a-zA-Z0-9])?.)*[a-zA-Z]([-a-zA-Z0-9]*[a-zA-Z0-9])?.?)|([0-9]+(.[0-9]+){3})|\[(([0-9a-fA-F]{1,4}(:[0-9a-fA-F]{1,4})*)?|([0-9a-fA-F]{1,4}(:[0-9a-fA-F]{1,4})*)?::([0-9a-fA-F]{1,4}(:[0-9a-fA-F]{1,4})*)?)(:[0-9]{1,3}(.[0-9]{1,3}){3})?\])(:[0-9]*)?)?|([a-zA-Z0-9-_.!~*''()$,;:@&=+]|%[a-fA-F0-9]{2})+)(/([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*(;([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*)*(/([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*(;([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*)*)*)?)|(/([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*(;([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*)*(/([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*(;([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*)*)*)))|(([a-zA-Z0-9-_.!~*''();@&=+$,]|%[a-fA-F0-9]{2})+(/([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*(;([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*)*(/([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*(;([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*)*)*)?))([?]([;/?:@&=+$,\][a-zA-Z0-9-_.!~*''()]|%[a-fA-F0-9]{2})*)?)|([a-zA-Z][a-zA-Z0-9+-.]*:([a-zA-Z0-9-_.!~*''();?:@&=+$,]|%[a-fA-F0-9]{2})(([;/?:@&=+$,\][a-zA-Z0-9-_.!~*''()]|%[a-fA-F0-9]{2}))*))?(#(([;/?:@&=+$,\][a-zA-Z0-9-_.!~*''()]|%[a-fA-F0-9]{2})*))? >>>>>> is just horrible.>> (and it might not even work so well with unicode)>>>> Benito>>>>>> On 12/19/2012 10:31 AM, Michael Kay wrote:>>> The validation rules for xs:anyURI in the XSD 1.0 specification are >>> notoriously troublesome, and it is not surprising that different >>> implementors interpret them differently.>>>>>> This is what XSD 1.0 says:>>>>>> >>> The ·lexical space· of anyURI is finite-length character sequences >>> which, when the algorithm defined in Section 5.4 of [XML Linking >>> Language] is applied to them, result in strings which are legal URIs >>> according to [RFC 2396], as amended by [RFC 2732].>>>>>> Note: Spaces are, in principle, allowed in the ·lexical space· of >>> anyURI, however, their use is highly discouraged (unless they are >>> encoded by %20).>>> >>>>>> The "Note" here suggests that Sedna is wrong to reject the value (it >>> also suggests that your query is wrong to supply it, but that you >>> should be able to get away with it).>>>>>> The "algorithm" referred to in this rule is basically the escaping >>> of special characters such as space.>>>>>> Note that in XSD 1.1, the spec gives up trying to define what's >>> valid in an xs:anyURI and what isn't - all strings are now valid in >>> the lexical space of xs:anyURI.>>>>>> Michael Kay>>> Saxonica>>>>>> On 19/12/2012 09:11, Robby Pelssers wrote:>>>> Hi all,>>>>>>>>>>>> I tested following Xquery with Sedna and Zorba:>>>>>>>> declare function local:getPipUri($id as xs:string) as xs:anyURI {>>>> xs:anyURI(concat("http://www.nxp.com/pip/", $id))>>>> };>>>>>>>> local:getPipUri("CX24483 14LZ")>>>>>>>>>>>> Sedna throws an exception:>>>> 2012/12/19 10:07:09 database query/update failed (SEDNA Message: >>>> ERROR FORG0001>>>> Invalid value for cast/constructor.>>>> Details: The value does not conform to the lexical constraints >>>> defined for the xs:anyURI type.>>>> Query line: 6, column:4>>>> )>>>>>>>>>>>> http://www.zorba-xquery.com/html/demo happy returns >>>> "http://www.nxp.com/pip/CX24483 14LZ">>>>>>>> So how does the xs:anyURI cast work? Is the developer supposed to >>>> encode the String before passing it to xs:anyURI or is the anyURI >>>> function supposed to do this?>>>>>>>> Thx in advance,>>>> Robby>>>>>>>> _______________________________________________>>>> http://x-query.com/mailman/listinfo/talk>>>> http://x-query.com/mailman/listinfo/talk>>>>>>>>>> _______________________________________________>>> http://x-query.com/mailman/listinfo/talk>>> http://x-query.com/mailman/listinfo/talk>>>>>>>>>>> _______________________________________________>> http://x-query.com/mailman/listinfo/talk>> http://x-query.com/mailman/listinfo/talk>>>>>> _______________________________________________> http://x-query.com/mailman/listinfo/talk> http://x-query.com/mailman/listinfo/talk>

The value does not conform to the lexical constraints defined for the xs:anyURI type

Wed, 19 Dec 2012 03:41:17 GMT

Michael Sperberg-McQueen has defined types that match different flavours of URI in http://www.w3.org/2011/04/XMLSchema/TypeLibrary-URI-RFC3986.xsd and http://www.w3.org/2011/04/XMLSchema/TypeLibrary-IRI-RFC3987.xsd To see the way these complex regular expressions are constructed, view these documents at the raw XML level using (for example) curl. Michael Kay Saxonica On 19/12/2012 11:13, Benito van der Zander wrote: > Hi, > > btw. has anyone a regular expression matching exactly the allowed > anyURIs of XSD 1.0? > > I tried to make one by translating the BNF in RFC 2396 and 2732 to > regex, by having a regex for every token, and substituting them > everywhere the token is used in the BNF. > > But the resulting regex: > > ((((([a-zA-Z][a-zA-Z0-9+-.]*:)?((//(((([a-zA-Z0-9-_.!~*''();:&=+$,]|%[a-fA-F0-9]{2})*@)?((([a-zA-Z0-9]([-a-zA-Z0-9]*[a-zA-Z0-9])?.)*[a-zA-Z]([-a-zA-Z0-9]*[a-zA-Z0-9])?.?)|([0-9]+(.[0-9]+){3})|\[(([0-9a-fA-F]{1,4}(:[0-9a-fA-F]{1,4})*)?|([0-9a-fA-F]{1,4}(:[0-9a-fA-F]{1,4})*)?::([0-9a-fA-F]{1,4}(:[0-9a-fA-F]{1,4})*)?)(:[0-9]{1,3}(.[0-9]{1,3}){3})?\])(:[0-9]*)?)?|([a-zA-Z0-9-_.!~*''()$,;:@&=+]|%[a-fA-F0-9]{2})+)(/([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*(;([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*)*(/([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*(;([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*)*)*)?)|(/([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*(;([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*)*(/([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*(;([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*)*)*)))|(([a-zA-Z0-9-_.!~*''();@&=+$,]|%[a-fA-F0-9]{2})+(/([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*(;([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*)*(/([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*(;([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*)*)*)?))([?]([;/?:@&=+$,\][a-zA-Z0-9-_.!~*''()]|%[a-fA-F0-9]{2})*)?)|([a-zA-Z][a-zA-Z0-9+-.]*:([a-zA-Z0-9-_.!~*''();?:@&=+$,]|%[a-fA-F0-9]{2})(([;/?:@&=+$,\][a-zA-Z0-9-_.!~*''()]|%[a-fA-F0-9]{2}))*))?(#(([;/?:@&=+$,\][a-zA-Z0-9-_.!~*''()]|%[a-fA-F0-9]{2})*))? > > > is just horrible. > (and it might not even work so well with unicode) > > Benito > > > On 12/19/2012 10:31 AM, Michael Kay wrote: >> The validation rules for xs:anyURI in the XSD 1.0 specification are >> notoriously troublesome, and it is not surprising that different >> implementors interpret them differently. >> >> This is what XSD 1.0 says: >> >> >> The ·lexical space· of anyURI is finite-length character sequences >> which, when the algorithm defined in Section 5.4 of [XML Linking >> Language] is applied to them, result in strings which are legal URIs >> according to [RFC 2396], as amended by [RFC 2732]. >> >> Note: Spaces are, in principle, allowed in the ·lexical space· of >> anyURI, however, their use is highly discouraged (unless they are >> encoded by %20). >> >> >> The "Note" here suggests that Sedna is wrong to reject the value (it >> also suggests that your query is wrong to supply it, but that you >> should be able to get away with it). >> >> The "algorithm" referred to in this rule is basically the escaping of >> special characters such as space. >> >> Note that in XSD 1.1, the spec gives up trying to define what's valid >> in an xs:anyURI and what isn't - all strings are now valid in the >> lexical space of xs:anyURI. >> >> Michael Kay >> Saxonica >> >> On 19/12/2012 09:11, Robby Pelssers wrote: >>> Hi all, >>> >>> >>> I tested following Xquery with Sedna and Zorba: >>> >>> declare function local:getPipUri($id as xs:string) as xs:anyURI { >>> xs:anyURI(concat("http://www.nxp.com/pip/", $id)) >>> }; >>> >>> local:getPipUri("CX24483 14LZ") >>> >>> >>> Sedna throws an exception: >>> 2012/12/19 10:07:09 database query/update failed (SEDNA Message: >>> ERROR FORG0001 >>> Invalid value for cast/constructor. >>> Details: The value does not conform to the lexical constraints >>> defined for the xs:anyURI type. >>> Query line: 6, column:4 >>> ) >>> >>> >>> http://www.zorba-xquery.com/html/demo happy returns >>> "http://www.nxp.com/pip/CX24483 14LZ" >>> >>> So how does the xs:anyURI cast work? Is the developer supposed to >>> encode the String before passing it to xs:anyURI or is the anyURI >>> function supposed to do this? >>> >>> Thx in advance, >>> Robby >>> >>> _______________________________________________ >>> http://x-query.com/mailman/listinfo/talk >>> http://x-query.com/mailman/listinfo/talk >>> >> >> _______________________________________________ >> http://x-query.com/mailman/listinfo/talk >> http://x-query.com/mailman/listinfo/talk >> > > > > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk >

The value does not conform to the lexical constraints defined for the xs:anyURI type

Wed, 19 Dec 2012 03:13:00 GMT

Hi, btw. has anyone a regular expression matching exactly the allowed anyURIs of XSD 1.0? I tried to make one by translating the BNF in RFC 2396 and 2732 to regex, by having a regex for every token, and substituting them everywhere the token is used in the BNF. But the resulting regex: ((((([a-zA-Z][a-zA-Z0-9+-.]*:)?((//(((([a-zA-Z0-9-_.!~*''();:&=+$,]|%[a-fA-F0-9]{2})*@)?((([a-zA-Z0-9]([-a-zA-Z0-9]*[a-zA-Z0-9])?.)*[a-zA-Z]([-a-zA-Z0-9]*[a-zA-Z0-9])?.?)|([0-9]+(.[0-9]+){3})|\[(([0-9a-fA-F]{1,4}(:[0-9a-fA-F]{1,4})*)?|([0-9a-fA-F]{1,4}(:[0-9a-fA-F]{1,4})*)?::([0-9a-fA-F]{1,4}(:[0-9a-fA-F]{1,4})*)?)(:[0-9]{1,3}(.[0-9]{1,3}){3})?\])(:[0-9]*)?)?|([a-zA-Z0-9-_.!~*''()$,;:@&=+]|%[a-fA-F0-9]{2})+)(/([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*(;([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*)*(/([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*(;([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*)*)*)?)|(/([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*(;([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*)*(/([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*(;([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*)*)*)))|(([a-zA-Z0-9-_.!~*''();@&=+$,]|%[a-fA-F0-9]{2})+(/([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*(;([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*)*(/([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*(;([a-zA-Z0-9-_.!~*''():@&=+$,]|%[a-fA-F0-9]{2})*)*)*)?))([?]([;/?:@&=+$,\][a-zA-Z0-9-_.!~*''()]|%[a-fA-F0-9]{2})*)?)|([a-zA-Z][a-zA-Z0-9+-.]*:([a-zA-Z0-9-_.!~*''();?:@&=+$,]|%[a-fA-F0-9]{2})(([;/?:@&=+$,\][a-zA-Z0-9-_.!~*''()]|%[a-fA-F0-9]{2}))*))?(#(([;/?:@&=+$,\][a-zA-Z0-9-_.!~*''()]|%[a-fA-F0-9]{2})*))? is just horrible. (and it might not even work so well with unicode) Benito On 12/19/2012 10:31 AM, Michael Kay wrote: > The validation rules for xs:anyURI in the XSD 1.0 specification are > notoriously troublesome, and it is not surprising that different > implementors interpret them differently. > > This is what XSD 1.0 says: > > > The ·lexical space· of anyURI is finite-length character sequences > which, when the algorithm defined in Section 5.4 of [XML Linking > Language] is applied to them, result in strings which are legal URIs > according to [RFC 2396], as amended by [RFC 2732]. > > Note: Spaces are, in principle, allowed in the ·lexical space· of > anyURI, however, their use is highly discouraged (unless they are > encoded by %20). > > > The "Note" here suggests that Sedna is wrong to reject the value (it > also suggests that your query is wrong to supply it, but that you > should be able to get away with it). > > The "algorithm" referred to in this rule is basically the escaping of > special characters such as space. > > Note that in XSD 1.1, the spec gives up trying to define what's valid > in an xs:anyURI and what isn't - all strings are now valid in the > lexical space of xs:anyURI. > > Michael Kay > Saxonica > > On 19/12/2012 09:11, Robby Pelssers wrote: >> Hi all, >> >> >> I tested following Xquery with Sedna and Zorba: >> >> declare function local:getPipUri($id as xs:string) as xs:anyURI { >> xs:anyURI(concat("http://www.nxp.com/pip/", $id)) >> }; >> >> local:getPipUri("CX24483 14LZ") >> >> >> Sedna throws an exception: >> 2012/12/19 10:07:09 database query/update failed (SEDNA Message: >> ERROR FORG0001 >> Invalid value for cast/constructor. >> Details: The value does not conform to the lexical constraints >> defined for the xs:anyURI type. >> Query line: 6, column:4 >> ) >> >> >> http://www.zorba-xquery.com/html/demo happy returns >> "http://www.nxp.com/pip/CX24483 14LZ" >> >> So how does the xs:anyURI cast work? Is the developer supposed to >> encode the String before passing it to xs:anyURI or is the anyURI >> function supposed to do this? >> >> Thx in advance, >> Robby >> >> _______________________________________________ >> http://x-query.com/mailman/listinfo/talk >> http://x-query.com/mailman/listinfo/talk >> > > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk >

The value does not conform to the lexical constraints defined for the xs:anyURI type

Wed, 19 Dec 2012 01:31:29 GMT

The validation rules for xs:anyURI in the XSD 1.0 specification are notoriously troublesome, and it is not surprising that different implementors interpret them differently. This is what XSD 1.0 says: The ·lexical space· of anyURI is finite-length character sequences which, when the algorithm defined in Section 5.4 of [XML Linking Language] is applied to them, result in strings which are legal URIs according to [RFC 2396], as amended by [RFC 2732]. Note: Spaces are, in principle, allowed in the ·lexical space· of anyURI, however, their use is highly discouraged (unless they are encoded by %20). The "Note" here suggests that Sedna is wrong to reject the value (it also suggests that your query is wrong to supply it, but that you should be able to get away with it). The "algorithm" referred to in this rule is basically the escaping of special characters such as space. Note that in XSD 1.1, the spec gives up trying to define what's valid in an xs:anyURI and what isn't - all strings are now valid in the lexical space of xs:anyURI. Michael Kay Saxonica On 19/12/2012 09:11, Robby Pelssers wrote: > Hi all, > > > I tested following Xquery with Sedna and Zorba: > > declare function local:getPipUri($id as xs:string) as xs:anyURI { > xs:anyURI(concat("http://www.nxp.com/pip/", $id)) > }; > > local:getPipUri("CX24483 14LZ") > > > Sedna throws an exception: > 2012/12/19 10:07:09 database query/update failed (SEDNA Message: ERROR FORG0001 > Invalid value for cast/constructor. > Details: The value does not conform to the lexical constraints defined for the xs:anyURI type. > Query line: 6, column:4 > ) > > > http://www.zorba-xquery.com/html/demo happy returns "http://www.nxp.com/pip/CX24483 14LZ" > > So how does the xs:anyURI cast work? Is the developer supposed to encode the String before passing it to xs:anyURI or is the anyURI function supposed to do this? > > Thx in advance, > Robby > > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk >

The value does not conform to the lexical constraints defined for the xs:anyURI type

Wed, 19 Dec 2012 01:11:55 GMT

Hi all, I tested following Xquery with Sedna and Zorba: declare function local:getPipUri($id as xs:string) as xs:anyURI { xs:anyURI(concat("http://www.nxp.com/pip/", $id)) }; local:getPipUri("CX24483 14LZ") Sedna throws an exception: 2012/12/19 10:07:09 database query/update failed (SEDNA Message: ERROR FORG0001 Invalid value for cast/constructor. Details: The value does not conform to the lexical constraints defined for the xs:anyURI type. Query line: 6, column:4 ) http://www.zorba-xquery.com/html/demo happy returns "http://www.nxp.com/pip/CX24483 14LZ" So how does the xs:anyURI cast work? Is the developer supposed to encode the String before passing it to xs:anyURI or is the anyURI function supposed to do this? Thx in advance, Robby

Sequence of Nodes Comparison

Wed, 05 Dec 2012 00:49:50 GMT

On 05/12/2012 04:59, Kunal Chauhan wrote: > Hi, > > I tried the way you suggest, but it works for me in xquery editor. > when I integrate it with java it returns true all the time. > > don't know why it happens ? > Because you are doing something wrong. If you want help in discovering what you are doing wrong, you will need to tell us more precisely what you are doing. Michael Kay Saxonica

Sequence of Nodes Comparison

Tue, 04 Dec 2012 07:37:24 GMT

let $i := (ABC, DEF, XYZ) let $j := (DEF, XYZ, ABC) return every $x in $i satisfies some $y in $j satisfies deep-equal($x, $y) : ) (a) that's O(n^2) (b) it will return true if the first list is empty and the second contains anything at all (or nothing). At the very least you need to check the lengths are equal; but even then, there's a potential problem with duplicates. Michael Kay Saxonica

Sequence of Nodes Comparison

Tue, 04 Dec 2012 07:26:37 GMT

On 4 December 2012 15:14, Kunal Chauhan wrote: > Hi, > > I want to compare two list of nodes. > Comparison should be based on QName, attribute and value. > Node's position is sequence doesn't matter. > > for example, > List A > ABC > DEF > XYZ > > List B > DEF > XYZ > ABC > > > When I compare both the lists it should show equal. let $i := (ABC, DEF, XYZ) let $j := (DEF, XYZ, ABC) return every $x in $i satisfies some $y in $j satisfies deep-equal($x, $y) : ) -- Andrew Welch http://andrewjwelch.com

[ANN] RXQ v0.1 - RESTful MVC with XQuery 3.0 annotations for MarkLogic

Sun, 28 Oct 2012 12:26:39 GMT

..great news, thanks for the links! Christian ___________________________ > having fun with Adam Retter's RESTXQ > > src at https://github.com/xquery/rxq > > -Jim Fuller > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk

[ANN] RXQ v0.1 - RESTful MVC with XQuery 3.0 annotations for MarkLogic

Sun, 28 Oct 2012 12:23:40 GMT

having fun with Adam Retter's RESTXQ src at https://github.com/xquery/rxq -Jim Fuller

exist xquery search

Thu, 25 Oct 2012 05:26:22 GMT

>Also the > performance is really bad. Your query can be made much more efficient yet. > I haven't fully done an index of the exist-db yet. Indexes made a huge difference in eXist, but you need to get your query correct first, so that you know which indexes you need. -- Adam Retter skype: adam.retter tweet: adamretter http://www.adamretter.org.uk

exist xquery search

Thu, 25 Oct 2012 05:24:20 GMT

Im not quite sure what the context of your query is, but this really does not look right to me. I would try inverting the order of execution, you can often use the set operators like union or intersect to bring together faceted queries - e.g. let $base := if($person) then //foo/bar[contributions/person/@val = $person] else //foo/bar return let $next := if($other) then //foo/bar[other = $other] else //foo/bar return subsequence($base intersect $next, $off, $num) Another option is actually to build your predicates as a string using concatenation, and then use util:eval to evaluate the query. On 25 October 2012 12:37, Michael Jones wrote: > Hi, > > I'm trying to write a faceted search with exist and xquery. What I have so > far is: > > xquery version "1.0"; > declare namespace request="http://exist-db.org/xquery/request"; > declare namespace xs="http://www.w3.org/2001/XMLSchema"; > declare option exist:serialize "method=xml media-type=text/xml > omit-xml-declaration=no indent=yes"; > > let $label:= request:get-parameter("l",'0') > let $dateTo:= request:get-parameter("dt",'0') > let $dateFrom := request:get-parameter("df",'0') > let $person := request:get-parameter("p",'0') > let $officesHeld := request:get-parameter("o",'0') > let $off := request:get-parameter("off",'0') > let $num := request:get-parameter("num",'10') > > return > > { > subsequence(//foo/bar[ > > (: label :) > (if ($label = '0') > then ( > * > )else( > label/@val = $label > )) > > and > (: person :) > (if ($person = '0') > then ( > * > )else( > contributions/person/@val = $person > )) > and > (: offices held :) > (if ($officesHeld = '0') > then ( > * > )else( > contributions/offices_held/@val = $officesHeld > )) > ],$off,$num) > } > > > On my local machine this runs fine but on my server I get FORG0001: > xs:string(0) is not a sub-type of xs:double [at line 18, column 9]. Also the > performance is really bad. Is there a better way to do a faceted search? I > want to say, if there is a parameter in the URL that matches $person then > search for a person that matches something similar to the value of the > person element. And if the parameter isn't in the url don't search for it, > the way I thought about getting around that is by putting in *, and then > building up a search query based on that. But this seems really inefficient. > I haven't fully done an index of the exist-db yet. But can anyone see a > better way to do this search? > > Thanks > > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk -- Adam Retter skype: adam.retter tweet: adamretter http://www.adamretter.org.uk

moving an element from last child to next sibling

Wed, 24 Oct 2012 00:43:14 GMT

> Now I wonder whether something like this is feasible using xquery 3.0 > features. Maybe not worth the effort, given the existence of xslt, > but at least you could imagine defining a map of XPath to function, > iterating over a tree, matching patterns and calling functions... > I think that with maps* and higher-order functions you could do something quite powerful; however the resulting code might be very cryptic to the uninitiated. * Sadly, maps are not in XQuery 3.0, though John Snelson has shown how they can be implemented using higher-order functions... Michael Kay Saxonica

moving an element from last child to next sibling

Tue, 23 Oct 2012 19:30:20 GMT

On 10/23/2012 10:02 AM, David Sewell wrote: > > Speaking as someone who wrote a lot of pseudo-templates in XQuery > before MarkLogic added an XSLT 2.0 parser to their product, this is > one area where XSLT is a lot more pleasant to use, if that's a > possibility. > > David Hear, hear - we abandoned using xquery for transformations as well for that reason. When I was still struggling with that, I found myself trying to write a pattern-matching system (basically something like xslt implemented in xquery), but it was too difficult in XQuery 1.0. Now I wonder whether something like this is feasible using xquery 3.0 features. Maybe not worth the effort, given the existence of xslt, but at least you could imagine defining a map of XPath to function, iterating over a tree, matching patterns and calling functions... -Mike

moving an element from last child to next sibling

Tue, 23 Oct 2012 07:02:06 GMT

There are at least a couple of different approaches to this via the typeswitch strategy, but I think the simplest would be: 1. In your function for closer, recurse over the child nodes as usual (which I assume will output a element, or whatever you transform it to), then process your postscript children: for $ps in $node/tei:postscript return {$ps/@*, eccoparse:recurse($ps)} 2. Extend your postscript function so it returns null if the postscript is a child of : declare function eccoparse:postscript($node as element(tei:postscript)) as element()* { if ($node/parent::tei:closer) then () else {$node/@*}{eccoparse:recurse($node)} } Speaking as someone who wrote a lot of pseudo-templates in XQuery before MarkLogic added an XSLT 2.0 parser to their product, this is one area where XSLT is a lot more pleasant to use, if that's a possibility. David On Tue, 23 Oct 2012, Martin Mueller wrote: > I have used the xquery typeswitch function to transform elements from a TEI > file, but I am stymied by a task involving the following fragment: > > > Your ever affectionate WOODVILLE. > >
P.S. You have a house, within a mile of York; where we > have spent many happy days—"Days of ease, and nights of > pleasure." Who knows but we may there recover our juve‑nile tastes and > passions! impossible! As well when advanced in life, might we hope to > reco‑ver our youth, in those fields where we once were young.—But > is that house untenanted? Will you be our host? Or have you lett, or lent > it?
> > > > I want to move the element from its position as the last child > of into the position of right sibling of so that the > desire output would look like this: > > > Your ever affectionate WOODVILLE. > > > >
P.S. You have a house, within a mile of York; where we > have spent many happy days—"Days of ease, and nights of > pleasure." Who knows but we may there recover our juve‑nile tastes and > passions! impossible! As well when advanced in life, might we hope to > reco‑ver our youth, in those fields where we once were young.—But > is that house untenanted? Will you be our host? Or have you lett, or lent > it?
> > > > How do I do this? In a typeswitch function the different tasks relating to > elements are carried out by subsidiary function. Here is the postscript > function that simply passes through the element: > > declare function eccoparse:postscript($node as element(tei:postscript)) as > element() > { > {$node/@*}{eccoparse:recurse($node)} > }; > > > > I know how to various things that would change the postscript element but > leave it in its current place. But how do I put it in another place without > changing anything in it? Is this a task that should be done at the level of > the parent element? > > > > I'll be grateful for any advice. > > > > > > Martin Mueller > > Professor emeritus of English and Classics > > Northwestern University > > > > > -- David Sewell, Editorial and Technical Manager ROTUNDA, The University of Virginia Press PO Box 400314, Charlottesville, VA 22904-4314 USA Email: http://x-query.com/mailman/listinfo/talk Tel: +1 434 924 9973 Web: http://rotunda.upress.virginia.edu/

moving an element from last child to next sibling

Tue, 23 Oct 2012 06:36:41 GMT

I have used the xquery typeswitch function to transform elements from a TEI file, but I am stymied by a task involving the following fragment: Your ever affectionate WOODVILLE.
P.S. You have a house, within a mile of York; where we have spent many happy days—"Days of ease, and nights of pleasure." Who knows but we may there recover our juve‑nile tastes and passions! impossible! As well when advanced in life, might we hope to reco‑ver our youth, in those fields where we once were young.—But is that house untenanted? Will you be our host? Or have you lett, or lent it?
I want to move the element from its position as the last child of into the position of right sibling of so that the desire output would look like this: Your ever affectionate WOODVILLE.
P.S. You have a house, within a mile of York; where we have spent many happy days—"Days of ease, and nights of pleasure." Who knows but we may there recover our juve‑nile tastes and passions! impossible! As well when advanced in life, might we hope to reco‑ver our youth, in those fields where we once were young.—But is that house untenanted? Will you be our host? Or have you lett, or lent it?
How do I do this? In a typeswitch function the different tasks relating to elements are carried out by subsidiary function. Here is the postscript function that simply passes through the element: declare function eccoparse:postscript($node as element(tei:postscript)) as element() { {$node/@*}{eccoparse:recurse($node)} }; I know how to various things that would change the postscript element but leave it in its current place. But how do I put it in another place without changing anything in it? Is this a task that should be done at the level of the parent element? I'll be grateful for any advice. Martin Mueller Professor emeritus of English and Classics Northwestern University -------------- next part -------------- An HTML attachment was scrubbed... URL:

Invitation to connect on LinkedIn

Fri, 19 Oct 2012 08:29:26 GMT

LinkedIn ------------ I'd like to add you to my professional network on LinkedIn. - Naveen Naveen Hanumara Software Developer at Detica London, United Kingdom Confirm that you know Naveen Hanumara: https://www.linkedin.com/e/vuwohj-h8hgff4f-3o/isd/9161410241/uQwFakjN/?hs=false&tok=1xEmtoYKixvls1 -- You are receiving Invitation to Connect emails. Click to unsubscribe: http://www.linkedin.com/e/vuwohj-h8hgff4f-3o/uDkLrgTRH42D5Lxbr_d17aeXvE/goo/talk%40xquery%2Ecom/20061/I3065200479_1/?hs=false&tok=0hRZBjI-axvls1 (c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA. -------------- next part -------------- An HTML attachment was scrubbed... URL:

deduplicating information in XML files

Fri, 19 Oct 2012 04:05:55 GMT

Hi, I'm currently trying out a pure XSLT solution. As an add-on, I'd like to mention I like where Zorba is going although I did not have the time to use it yet. I really need to take a closer look once I have time at the documentation. Thx for the tip by the way. Robby -----Original Message----- From: Helena Galhardas [mailto:http://x-query.com/mailman/listinfo/talk] Sent: Wednesday, October 17, 2012 12:19 PM To: Robby Pelssers Cc: http://x-query.com/mailman/listinfo/talk; xquery-discuss; Bruno Martins; Daniela Florescu Subject: Re: deduplicating information in XML files Dear Robby, Zorba XQuery processor currently supports a data cleaning module (look for data cleaning in http://www.zorba-xquery.com/html/modules) that we may want to try. In principle, the requirements associated to your data de-duplication problem can be addressed by writing an XQuery program that invokes some of the functions available in this data cleaning module. We would appreciate your feedback if you decide to do so and please let us know if we can help somehow. Thanks. Best Regards, Helena Galhardas On Oct 12, 2012, at 1:02 PM, Robby Pelssers wrote: > Hi all, > > This time I have a rather challenging task at hand. Let me first > describe the use case. We have lots of product information stored in > XML. Some of that information describes . Technical applications . > Features and benefits . Technical summary > > One of the problems is a lot of products had e.g. the same features > and benefits as they are of the same product family or group. But as > we stored that info per product it got duplicated. Now we want to > deduplicate that info by generating DITA maps and topics (both are > just XML). Now for simplicity let's assume we generate the following > content for product1 and product2. The goal is to get from INPUT to > OUTPUT by checking if the body of the linked topics are duplicates, > next create 1 generic topic and rewrite the links in the map to point > to that single topic. I have XSLT / XQuery (XMLDB) and Java at my > disposal to get the job done. I'm not sure what will be the easiest > way to get the job done. Keep also in mind that my INPUT will contain > a few 1000 files (maps and linked topics) and I will need to > deduplicate the whole set ;-) > > Thx upfront for any input, > Robby > > INPUT > > Product1_map.xml > > > > Product1_FandB.xml: > > > product1 > > >
Suitable for high frequency applications due to fast switching characteristics
>
Suitable for logic level gate drive sources
> > > > Product2_map.xml > > > > Product2_FandB.xml: > > > product2 > > >
Suitable for high frequency applications due to fast switching characteristics
>
Suitable for logic level gate drive sources
> > > > Expected output: > > Product1_map.xml > > > > > Product2_map.xml > > > > > FandB_1.xml: > > > > > >
Suitable for high frequency applications due to fast switching characteristics
>
Suitable for logic level gate drive sources
> > > > > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk

deduplicating information in XML files

Wed, 17 Oct 2012 03:18:36 GMT

Dear Robby, Zorba XQuery processor currently supports a data cleaning module (look for data cleaning in http://www.zorba-xquery.com/html/modules) that we may want to try. In principle, the requirements associated to your data de-duplication problem can be addressed by writing an XQuery program that invokes some of the functions available in this data cleaning module. We would appreciate your feedback if you decide to do so and please let us know if we can help somehow. Thanks. Best Regards, Helena Galhardas On Oct 12, 2012, at 1:02 PM, Robby Pelssers wrote: > Hi all, > > This time I have a rather challenging task at hand. Let me first describe the use case. We have lots of product information stored in XML. Some of that information describes > . Technical applications > . Features and benefits > . Technical summary > > One of the problems is a lot of products had e.g. the same features and benefits as they are of the same product family or group. But as we stored that info per product it got duplicated. Now we want to deduplicate that info by generating DITA maps and topics (both are just XML). Now for simplicity let's assume we generate the following content for product1 and product2. The goal is to get from INPUT to OUTPUT by checking if the body of the linked topics are duplicates, next create 1 generic topic and rewrite the links in the map to point to that single topic. I have XSLT / XQuery (XMLDB) and Java at my disposal to get the job done. I'm not sure what will be the easiest way to get the job done. Keep also in mind that my INPUT will contain a few 1000 files (maps and linked topics) and I will need to deduplicate the whole set ;-) > > Thx upfront for any input, > Robby > > INPUT > > Product1_map.xml > > > > > Product1_FandB.xml: > > > product1 > > >
Suitable for high frequency applications due to fast switching characteristics
>
Suitable for logic level gate drive sources
> > > > Product2_map.xml > > > > > Product2_FandB.xml: > > > product2 > > >
Suitable for high frequency applications due to fast switching characteristics
>
Suitable for logic level gate drive sources
> > > > Expected output: > > Product1_map.xml > > > > > Product2_map.xml > > > > > FandB_1.xml: > > > > > >
Suitable for high frequency applications due to fast switching characteristics
>
Suitable for logic level gate drive sources
> > > > > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk

deduplicating information in XML files

Fri, 12 Oct 2012 05:02:40 GMT

Hi all, This time I have a rather challenging task at hand. Let me first describe the use case. We have lots of product information stored in XML. Some of that information describes . Technical applications . Features and benefits . Technical summary One of the problems is a lot of products had e.g. the same features and benefits as they are of the same product family or group. But as we stored that info per product it got duplicated. Now we want to deduplicate that info by generating DITA maps and topics (both are just XML). Now for simplicity let's assume we generate the following content for product1 and product2. The goal is to get from INPUT to OUTPUT by checking if the body of the linked topics are duplicates, next create 1 generic topic and rewrite the links in the map to point to that single topic. I have XSLT / XQuery (XMLDB) and Java at my disposal to get the job done. I'm not sure what will be the easiest way to get the job done. Keep also in mind that my INPUT will contain a few 1000 files (maps and linked topics) and I will need to deduplicate the whole set ;-) Thx upfront for any input, Robby INPUT Product1_map.xml Product1_FandB.xml:     product1
Suitable for high frequency applications due to fast switching characteristics

Suitable for logic level gate drive sources
Product2_map.xml Product2_FandB.xml:     product2
Suitable for high frequency applications due to fast switching characteristics

Suitable for logic level gate drive sources
Expected output: Product1_map.xml Product2_map.xml FandB_1.xml:
Suitable for high frequency applications due to fast switching characteristics

Suitable for logic level gate drive sources

[ANN] XML Prague 2013 Call for Papers

Wed, 10 Oct 2012 03:42:45 GMT

XML Prague 2013 is now welcoming submissions for presentations on the following topics: Digital books and publishing: The role of XML in single-source publishing in the era of tablets, smart phones, and eBook readers. Semantic web: Beyond mere structures. Expressing semantics in data formats and communication protocols. XML vocabularies: A deep dive into industry specific usage of XML. XML efficiency: High-speed processing, compact serialization and storage, processing of big data volumes. XML birthday: Do we need new syntax, data model or both or is XML just fine after 15 years? For more information on CFP http://www.xmlprague.cz/call-for-papers/ on behalf, XML Prague Committee 2013 -- -- XMLPrague 2013, Feb 8-10 Sponsored by XML editor

incorrect syntax?

Tue, 02 Oct 2012 08:51:12 GMT

Do I sense an International Obfuscated XQuery Code Contest [1] [2] in the offing? -- Ron [1] http://www.ioccc.org/ [2] http://en.wikipedia.org/wiki/International_Obfuscated_C_Code_Contest On 10/2/2012 1:38 AM, Andrew Welch wrote: > On 2 October 2012 09:30, David Carlisle wrote: >> On 02/10/2012 08:56, Andrew Welch wrote: >>> >>> ha that's great (if a little contrived): >>> >>> declare default function namespace "x"; >>> declare function return ($x) { $x+1 }; >>> return (23) >>> >>> returns 24 >> >> >> Yes that is contrived, I think it's clearer if you write it like this >> >> declare default function namespace "return"; >> declare variable $return := 23; >> declare function return ($return) { $return+1 }; >> return ($return) > > That is indeed much clearer, thanks David. > > > ;) > >

incorrect syntax?

Tue, 02 Oct 2012 01:38:30 GMT

On 2 October 2012 09:30, David Carlisle wrote: > On 02/10/2012 08:56, Andrew Welch wrote: >> >> ha that's great (if a little contrived): >> >> declare default function namespace "x"; >> declare function return ($x) { $x+1 }; >> return (23) >> >> returns 24 > > > Yes that is contrived, I think it's clearer if you write it like this > > declare default function namespace "return"; > declare variable $return := 23; > declare function return ($return) { $return+1 }; > return ($return) That is indeed much clearer, thanks David. ;) -- Andrew Welch http://andrewjwelch.com

incorrect syntax?

Tue, 02 Oct 2012 01:30:07 GMT

On 02/10/2012 08:56, Andrew Welch wrote: > ha that's great (if a little contrived): > > declare default function namespace "x"; > declare function return ($x) { $x+1 }; > return (23) > > returns 24 Yes that is contrived, I think it's clearer if you write it like this declare default function namespace "return"; declare variable $return := 23; declare function return ($return) { $return+1 }; return ($return) ________________________________________________________________________ The Numerical Algorithms Group Ltd is a company registered in England and Wales with company number 1249803. The registered office is: Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom. This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. ________________________________________________________________________

incorrect syntax?

Tue, 02 Oct 2012 00:56:32 GMT

> But if you say > > declare default function namespace "x"; > declare function return ($x) { $x+1 }; > return (23) > > that does seem to return 24 for at least one processor that I tried, which > seems truly bizarre (to me, anyway) ha that's great (if a little contrived): declare default function namespace "x"; declare function return ($x) { $x+1 }; return (23) returns 24 but add a let: declare default function namespace "x"; declare function return ($x) { $x+1 }; let $foo := 1 return (23) returns 23 (tested using Saxon HE 9.3.0.5.)

incorrect syntax?

Mon, 01 Oct 2012 21:11:32 GMT

On 10/1/2012 7:22 PM, Michael Sokolov wrote: > Sorry, I think I neglected to include a let before a couple of the > returns. I thought that might be the case. > But my main point was the unusual (and probably unfamiliar to > people used to other languages) change in the interpretation of > parentheses when they follow the return keyword and when they follow the > return function. That is confusing. The other thing that confuses people is that functions don't use the "return" keyword and instead just return the result of evaluating the contained expression. > Admittedly the idea of defining a function with the same name as a > keyword is contrived and ill-advised, right up there with C++ operator > overloading. It just occurred to me on reading Michael Kay's comment > 'There is no function called "return"' that there actually could be one. Agreed. -- Ron

incorrect syntax?

Mon, 01 Oct 2012 19:22:03 GMT

Sorry, I think I neglected to include a let before a couple of the returns. But my main point was the unusual (and probably unfamiliar to people used to other languages) change in the interpretation of parentheses when they follow the return keyword and when they follow the return function. Admittedly the idea of defining a function with the same name as a keyword is contrived and ill-advised, right up there with C++ operator overloading. It just occurred to me on reading Michael Kay's comment 'There is no function called "return"' that there actually could be one. Mike Sokolov On 10/1/2012 8:55 PM, Ronald Bourret wrote: > This is actually very straightforward. "return" is a keyword, used in > FLWOR expressions and a few other places. There is no standalone > "return" in XQuery. Thus: > > let $x:=0 return (23) > > is a valid (if uninteresting) FLWOR expression that is equivalent to > the even less interesting (but still valid) expression: > > (23) > > And a standalone "return" is illegal: > > return (23) (: error :) > > Where you have included parentheses below, you are calling a function > named "return" and XQuery works as expected. It's a bad idea to name a > function using a keyword as a name, but XQuery allows it. If you > replace "return(...)" with "foo(...)" in the expressions below, the > intended meaning will be clear. > > The last two XQuery expressions should return errors (and do in the > online Zorba XQuery processor I tried them in). As noted above, this > is because there is no standalone use of the "return" keyword -- > either the processor you are using has a bug or you haven't shown us > the entire expression. > > Thanks, > > -- Ron > > On 10/1/2012 5:34 PM, Michael Sokolov wrote: >> On 10/1/2012 10:48 AM, Michael Kay wrote: >>> There is no function called "return". Just remove the keyword. >>> Depending on the context, you might need to remove the outer curly >>> braces as well. >>> >>> It's a little confusing because you can say >>> >>> let $x:=0 return 23 >>> >>> but you can't say >>> >>> return 23 >> >> Actually if you really start to dig, it becomes a lot confusing >> >> you can say >> >> let $x := 0 return (23) >> >> but in that instance return is not a function call; the parentheses here >> are constructing a sequence (of one item) >> >> But if you say >> >> declare default function namespace "x"; >> declare function return ($x) { $x+1 }; >> return (23) >> >> that does seem to return 24 for at least one processor that I tried, >> which seems truly bizarre (to me, anyway) >> >> yet >> >> declare default function namespace "x"; >> declare function return ($x) { $x+1 }; >> return 23 >> >> returns 23 >> >> while >> >> declare default function namespace "x"; >> declare function return ($x) { $x+1 }; >> return return(23) >> >> returns 24 >> >> -Mike Sokolov >> >> >> _______________________________________________ >> http://x-query.com/mailman/listinfo/talk >> http://x-query.com/mailman/listinfo/talk

incorrect syntax?

Mon, 01 Oct 2012 17:55:20 GMT

This is actually very straightforward. "return" is a keyword, used in FLWOR expressions and a few other places. There is no standalone "return" in XQuery. Thus: let $x:=0 return (23) is a valid (if uninteresting) FLWOR expression that is equivalent to the even less interesting (but still valid) expression: (23) And a standalone "return" is illegal: return (23) (: error :) Where you have included parentheses below, you are calling a function named "return" and XQuery works as expected. It's a bad idea to name a function using a keyword as a name, but XQuery allows it. If you replace "return(...)" with "foo(...)" in the expressions below, the intended meaning will be clear. The last two XQuery expressions should return errors (and do in the online Zorba XQuery processor I tried them in). As noted above, this is because there is no standalone use of the "return" keyword -- either the processor you are using has a bug or you haven't shown us the entire expression. Thanks, -- Ron On 10/1/2012 5:34 PM, Michael Sokolov wrote: > On 10/1/2012 10:48 AM, Michael Kay wrote: >> There is no function called "return". Just remove the keyword. >> Depending on the context, you might need to remove the outer curly >> braces as well. >> >> It's a little confusing because you can say >> >> let $x:=0 return 23 >> >> but you can't say >> >> return 23 > > Actually if you really start to dig, it becomes a lot confusing > > you can say > > let $x := 0 return (23) > > but in that instance return is not a function call; the parentheses here > are constructing a sequence (of one item) > > But if you say > > declare default function namespace "x"; > declare function return ($x) { $x+1 }; > return (23) > > that does seem to return 24 for at least one processor that I tried, > which seems truly bizarre (to me, anyway) > > yet > > declare default function namespace "x"; > declare function return ($x) { $x+1 }; > return 23 > > returns 23 > > while > > declare default function namespace "x"; > declare function return ($x) { $x+1 }; > return return(23) > > returns 24 > > -Mike Sokolov > > > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk

incorrect syntax?

Mon, 01 Oct 2012 07:29:35 GMT

On 01/10/2012 15:19, Gleb Gawriljuk wrote: > I cannot see where my error lies. I am just executing the return function That is your error. Xquery does not have a return function. Without seeing more context it's not clear what the query should be. David -- google plus: https:/profiles.google.com/d.p.carlisle ________________________________________________________________________ The Numerical Algorithms Group Ltd is a company registered in England and Wales with company number 1249803. The registered office is: Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom. This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. ________________________________________________________________________

incorrect syntax?

Mon, 01 Oct 2012 07:25:03 GMT

Hi Gleb, Could the prefix in front of the return call be missing? (e.g., local:return, depending on how you defined this function) By default (if you have not changed it), the default function namespace is the builtin one (also available through fn:), so just typing "return" will look up among builtin functions (fn:return, which as far as I know does not exist). Does this help? Kind regards, Ghislain On Oct 1, 2012, at 4:19 PM, Gleb Gawriljuk wrote: > Hey everyone, > > I have the following query which I use as a string in Saxon 8.9: > {return( > if ( > not(doc('path.xml')/Student/StudentID = doc(path.xml')/RentNote/StudentID) and > not(doc('path.xml')/Buch/BuchID = doc('path.xml')/RentNote/BuchID) > ) > then error() > else > ) > } > > However I receive the follwoing error: > > > I cannot see where my error lies. I am just executing the return function which holds a xpath expression. Can anybody help? > > Kind regards, > Gleb > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk

Looking for help restricting results per input?

Mon, 24 Sep 2012 01:59:21 GMT

On 24 September 2012 07:47, Jeremy Botto wrote: > let $keywords := ("keyworda", "keywordb", "keywordc") > for $keyword in $keywords, > $v in doc('test')//document/item > where $v/quote contains text {$keyword} > return ( > {$v/comment} > {$v/buyer}) > > There are three things I am trying to add to this query: > > 1) I'd like to get only two results per $keyword in $keywords, but I am > currently getting 20-30 results per keyword. You've got a "cartesian cross product" in your for expression.... is that really what you want? > 2) I'd like to search for case-insensitive keywords. Covert both items to lower-case() before comparing, or use your xquery vendors custom extensions. > 3) Because I am trying to receive only 2 results, I want to prioritize > results whose 'quote' element also contain round braces "(" and ")". Use order by - if if the quote contains round brackets return 1 else return 0, then sort by number descending. -- Andrew Welch http://andrewjwelch.com

[xml-dev] XQuery 3.0 implementations vs the XQuery 3.0 Test Suite

Wed, 19 Sep 2012 10:12:56 GMT

Jim, I expect Zorba to report results by the end of the year, hopefully 100%. We implement all the features, including the optional ones. Best Dana On Sep 17, 2012, at 6:55 PM, Jim Melton wrote: > Gentle friends, > > The XML Query WG, jointly with the XSLT Working Group, are nearly ready to several several of the "3.0" suite of specifications from Last Call Working Draft to Candidate Recommendation. The exceptions are Serialization 3.0, which will be submitted for a second Last Call comment period, and XSLT 3.0, which has not yet entered the Last Call phase. (The documents being considered for advancement are XQuery 3.0, XQueryX 3.0, XPath 3.0, XDM 3.0, and F&O 3.0.) > > We already have in place a very substantial test suite for XQuery 3.0, although we do not claim that it is as complete as we wish it to be. We are currently in the process of reviewing the test suite to determine what additional tests are needed to ensure that we can determine our specs to be implementable as required by W3C policies. > > The purpose of Candidate Recommendation is, as implied above, to determine whether the specs are implementable, particularly that each feature can be implemented by two or more implementations compatibly. Therefore, as documents are transitioned to Candidate Recommendation, a Call for Implementations is issued. Implementations respond to that call by submitting their results from running the test suite and by reporting bugs they've discovered as a result. > > When we transition to Candidate Recommendation, we are required to indicate a date through which we will accept test suite results and other comments before we consider a further transition to Proposed Recommendation. At this point, we honestly cannot predict whether implementors will require two weeks, two months, or two quarters before they're able to submit results. > > If you are responsible for an XQuery 3.0 implementation, please respond to this message with your best estimate of how long from, say, mid-October 2012 it will be until you are able to submit test suite results. > > Many thanks! > Jim > > ======================================================================== > Jim Melton --- Editor of ISO/IEC 9075-* (SQL) Phone: +1.801.942.0144 > Chair, ISO/IEC JTC1/SC32 and W3C XML Query WG Fax : +1.801.942.3345 > Oracle Corporation Oracle Email: jim dot melton at oracle dot com > 1930 Viscounti Drive Alternate email: jim dot melton at acm dot org > Sandy, UT 84093-1063 USA Personal email: SheltieJim at xmission dot com > ======================================================================== > = Facts are facts. But any opinions expressed are the opinions = > = only of myself and may or may not reflect the opinions of anybody = > = else with whom I may or may not have discussed the issues at hand. = > ======================================================================== > > _______________________________________________________________________ > > XML-DEV is a publicly archived, unmoderated list hosted by OASIS > to support XML implementation and development. To minimize > spam in the archives, you must subscribe before posting. > > [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/ > Or unsubscribe: http://x-query.com/mailman/listinfo/talk > subscribe: http://x-query.com/mailman/listinfo/talk > List archive: http://lists.xml.org/archives/xml-dev/ > List Guidelines: http://www.oasis-open.org/maillists/guidelines.php >

Replacing an attribute

Fri, 07 Sep 2012 08:22:52 GMT

> Yes. I saw that If I write an XSLT stylesheet, then I can call that > from marklogic and it all works good... > I am not too sure, if XSLT is a good approach or if Xquery is a better > way of doing things? > Generally, XQuery is better than XSLT for extracting specific information out of an XML document, and XSLT is better at making small changes to a document while leaving most of the content unchanged. Or to put it another way, XQuery is better at query and XSLT is better at transformation. (XQuery Update is an alternative, though, if available). Michael Kay Saxonica

Simple (I thought) Xquery giving run-time error.

Fri, 13 Jul 2012 08:20:41 GMT

It seems like you might have too many '/*' steps. For example, if you evaluate $models/* in the body, I think you should get the empty sequence. $models appears to bind to the sequence of elements so $models/* would select element children of each but there aren't any. I would try changing your line to the following: {$models/{local:bindModel(local:defineModelRoot(.),"",xs:QName('group'))}} Josh On Jul 13, 2012, at 7:41 AM, Ihe Onwuka wrote: > Given this in modelNames.xml > > > > 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 html="http://www.w3.org/1999/xhtml"; > declare namespace ev="http://www.w3.org/2001/xml-events"; > > declare variable $configDir as xs:string :="config"; > > declare variable $models as element()* > :=doc(concat($configDir,"/modelNames.xml"))/*/*; > > declare function local:bindModel($x,$y,$z) {$x}; > > declare function local:capitalise($str) > { > concat(upper-case(substring($str,1,1)),substring($str,2)) > }; > > declare function local:defineModelRoot($model as element()) > { > element {concat('b2b:',local:capitalise($model/text()))} > {element xf:bind {attribute repeat > {local:getBindingFileName($model)}}} > }; > > declare function local:getBindingFileName($model as element()) as xs:string > { > concat($model/@singular,'Bindings.xml') > }; > > {$models/*/> id='{text()}Case'>{local:bindModel(local:defineModelRoot(.),"",xs:QName('group'))}} > > > The idea of the line that says > > {$models/*/> id='{text()}Case'>{local:bindModel(local:defineModelRoot(.),"",xs:QName('group'))}} > > is for the direct constructor to be evaluated for each model > element in $models. The two substitutions I am hoping for is the > text() element in the AVT for the id attribute of the case element and > the . in local:defineModelRoot, which is meant to pass the context > model element as a parameter to local:defineModelRoot. > > Is my understanding of what I should expect incorrect. If so I would > appreciate an explanation rather than just a solution. > > thanks. > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk

Simple (I thought) Xquery giving run-time error.

Fri, 13 Jul 2012 08:18:08 GMT

Your problem is that the initialization of $models goes down two levels below the document node, so it is bound to a sequence of Model elements, so when you do $models/* you are selecting the children of the Model elements, but there are no child elements to select. Remove 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://www.b2b.net/plants"; > declare namespace xf="http://www.w3.org/2002/xforms"; > declare namespace html="http://www.w3.org/1999/xhtml"; > declare namespace ev="http://www.w3.org/2001/xml-events"; > > declare variable $configDir as xs:string :="config"; > > declare variable $models as element()* > :=doc(concat($configDir,"/modelNames.xml"))/*/*; > > declare function local:bindModel($x,$y,$z) {$x}; > > declare function local:capitalise($str) > { > concat(upper-case(substring($str,1,1)),substring($str,2)) > }; > > declare function local:defineModelRoot($model as element()) > { > element {concat('b2b:',local:capitalise($model/text()))} > {element xf:bind {attribute repeat > {local:getBindingFileName($model)}}} > }; > > declare function local:getBindingFileName($model as element()) as xs:string > { > concat($model/@singular,'Bindings.xml') > }; > > {$models/*/> id='{text()}Case'>{local:bindModel(local:defineModelRoot(.),"",xs:QName('group'))}} >

Simple (I thought) Xquery giving run-time error.

Fri, 13 Jul 2012 07:41:50 GMT

Given this in modelNames.xml 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 html="http://www.w3.org/1999/xhtml"; declare namespace ev="http://www.w3.org/2001/xml-events"; declare variable $configDir as xs:string :="config"; declare variable $models as element()* :=doc(concat($configDir,"/modelNames.xml"))/*/*; declare function local:bindModel($x,$y,$z) {$x}; declare function local:capitalise($str) { concat(upper-case(substring($str,1,1)),substring($str,2)) }; declare function local:defineModelRoot($model as element()) { element {concat('b2b:',local:capitalise($model/text()))} {element xf:bind {attribute repeat {local:getBindingFileName($model)}}} }; declare function local:getBindingFileName($model as element()) as xs:string { concat($model/@singular,'Bindings.xml') }; {$models/*/{local:bindModel(local:defineModelRoot(.),"",xs:QName('group'))}} The idea of the line that says {$models/*/{local:bindModel(local:defineModelRoot(.),"",xs:QName('group'))}} is for the direct constructor to be evaluated for each model element in $models. The two substitutions I am hoping for is the text() element in the AVT for the id attribute of the case element and the . in local:defineModelRoot, which is meant to pass the context model element as a parameter to local:defineModelRoot. Is my understanding of what I should expect incorrect. If so I would appreciate an explanation rather than just a solution. thanks.

XML & XQuery @ NoSQL Now! 2012

Wed, 11 Jul 2012 08:59:58 GMT

Hello gang, This year edition of the NoSQL Now! 2012 will feature several talks related to XML & XQuery topics. We have listed the ones related to the Zorba XQuery Processor at http://www.zorba-xquery.com/html/entry/2012/07/10/NoSQL_Now We hope to see you there! William

XQuery Update Facility and unwanted whitespace

Tue, 10 Jul 2012 01:00:23 GMT

Andrew has answered the whitespace questions. It's a Saxon (not an Oxygen) restriction that XQuery 3.0 and XQuery Update can't currently be used together in the same query. It happened that way because both are implemented as extensions to the "core" XQuery 1.0 parser, built using subclassing. (Done that way partly because of the code separation between different Saxon editions). We need to fix this mechanism, which is becoming pretty unmanageable with the number of different language dialects supported. Ideally, I suppose, we should make a complete break and move to a bottom-up table driven parser; but XQuery parsing is so fragile with the number of context-dependent decisions that need to be made, it's a risky change to contemplate. Michael Kay Saxonica On 09/07/2012 19:45, Joe Wicentowski wrote: > Hi all, > > I'm having a problem with query I wrote that makes use of the XQuery > Update Facility. The problem is that unwanted whitespace inserted > into the results of my query. Here is my source XML (a TEI-like > list), the query in question, and the output showing the unwanted > whitespace: > > source.xml: > ----------------- > > See Middle East > Middle East 68 > > > fix-ids.xq: > -------------- > let $doc := doc('source.xml') > for $item-id at $count in $doc//item/@xml:id > let $new-id := concat('in', $count) > let $new-target := concat('#', $new-id) > let $targets := $doc//ref[@target = concat('#', $item-id)]/@target > return > ( > (: fix @xml:ids :) > replace value of node $item-id with $new-id > , > (: fix @targets :) > for $target in $targets > return > replace value of node $target with $new-target > ) > > output: > ---------- > > See Middle East > > Middle East 68 > > > > Note that while the query only modifies attribute values, the results > of the query are somehow re-indented. (Specifically, in the source, > there was no whitespace between and , but in the > results, is on a new line. > > Is this a serialization issue? Is there a way for me to declare some > options that will prevent the unwanted whitespace from being inserted? > > I'm not sure whether this is a general XQuery issue or an > implementation-specific issue, so let me know if this isn't the right > forum for this question. I'm using oXygen 13 in XQuery Debugger mode > with Saxon EE-XQuery 9.3.0.5. > > (On a related note, I see that XQuery 3.0 has new support for > serialization options -- > http://www.w3.org/TR/xquery-30/#id-serialization -- but oXygen doesn't > seem to allow combining XQuery 3.0 with XQuery Update Facility and > Saxon EE. This forum post instructs users to disable XQuery 1.1/3.0 > support in order to use XQUF: > http://www.oxygenxml.com/forum/topic6615.html.) > > Thanks, > Joe > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk >

XQuery Update Facility and unwanted whitespace

Mon, 09 Jul 2012 14:12:04 GMT

Hi Andrew, > What is you "strip whitespace" set to? It sounds like it's set to "all"... Great point - I had actually been fiddling with that setting earlier before your I emailed the list. Setting it back to "none" or "ignorable" is much better: See Middle East Middle East 68 I couldn't get it to put on a new line, but that's no biggie. So, in sum, the combination of unticking 'format transformer output' and setting 'strip whitespace' to 'none' or 'ignorable' yields quite nice results. Thanks very much, Andrew. Joe

XQuery Update Facility and unwanted whitespace

Mon, 09 Jul 2012 12:53:49 GMT

On 9 July 2012 20:35, Joe Wicentowski wrote: > Hi Andrew, > >> In the XQuery options (in oXygen) untick 'format transformer output' > > Thanks for that suggestion. That's definitely preferable, in that it > doesn't introduce new whitespace, though it does strips out all > whitespace between nodes -- which is fine with me: What is you "strip whitespace" set to? It sounds like it's set to "all"... -- Andrew Welch http://andrewjwelch.com

XQuery Update Facility and unwanted whitespace

Mon, 09 Jul 2012 12:35:47 GMT

Hi Andrew, > In the XQuery options (in oXygen) untick 'format transformer output' Thanks for that suggestion. That's definitely preferable, in that it doesn't introduce new whitespace, though it does strips out all whitespace between nodes -- which is fine with me: See Middle EastMiddle East 68 To sum up, I guess this was an oXygen/Saxon-specific issue, but it applies to all XQuery results in oXygen, not just those queries that use the XQuery Update Facility. Ah, whitespace. Life would be so boring and straightforward without you. Thanks again, Joe

XQuery Update Facility and unwanted whitespace

Mon, 09 Jul 2012 12:02:22 GMT

> Is this a serialization issue? Is there a way for me to declare some > options that will prevent the unwanted whitespace from being inserted? > > I'm not sure whether this is a general XQuery issue or an > implementation-specific issue, so let me know if this isn't the right > forum for this question. I'm using oXygen 13 in XQuery Debugger mode > with Saxon EE-XQuery 9.3.0.5. In the XQuery options (in oXygen) untick 'format transformer output' -- Andrew Welch http://andrewjwelch.com

XQuery Update Facility and unwanted whitespace

Mon, 09 Jul 2012 11:45:23 GMT

Hi all, I'm having a problem with query I wrote that makes use of the XQuery Update Facility. The problem is that unwanted whitespace inserted into the results of my query. Here is my source XML (a TEI-like list), the query in question, and the output showing the unwanted whitespace: source.xml: ----------------- See Middle East Middle East 68 fix-ids.xq: -------------- let $doc := doc('source.xml') for $item-id at $count in $doc//item/@xml:id let $new-id := concat('in', $count) let $new-target := concat('#', $new-id) let $targets := $doc//ref[@target = concat('#', $item-id)]/@target return ( (: fix @xml:ids :) replace value of node $item-id with $new-id , (: fix @targets :) for $target in $targets return replace value of node $target with $new-target ) output: ---------- See Middle East Middle East 68 Note that while the query only modifies attribute values, the results of the query are somehow re-indented. (Specifically, in the source, there was no whitespace between and , but in the results, is on a new line. Is this a serialization issue? Is there a way for me to declare some options that will prevent the unwanted whitespace from being inserted? I'm not sure whether this is a general XQuery issue or an implementation-specific issue, so let me know if this isn't the right forum for this question. I'm using oXygen 13 in XQuery Debugger mode with Saxon EE-XQuery 9.3.0.5. (On a related note, I see that XQuery 3.0 has new support for serialization options -- http://www.w3.org/TR/xquery-30/#id-serialization -- but oXygen doesn't seem to allow combining XQuery 3.0 with XQuery Update Facility and Saxon EE. This forum post instructs users to disable XQuery 1.1/3.0 support in order to use XQUF: http://www.oxygenxml.com/forum/topic6615.html.) Thanks, Joe

fn:doc not returning data

Mon, 09 Jul 2012 09:10:28 GMT

Hi Daniel, XQIB does not support the doc function - the XQIB way of accessing an XML document is to send a GET request over the Web with the EXPath http-client module (possibly to the same server). An example is given here: http://www.xqib.org/js/RESTCallCourses_source.html I hope this is helpful? Kind regards, Ghislain On Jul 9, 2012, at 4:15 PM, Daniel Oneil wrote: > I'm trying to use XQIB to get data from an XML file using the fn:doc function. > The following link leads to a Source Forge forum where I posted my code and a link to the books.xml file. > https://sourceforge.net/projects/mxquery/forums/forum/633155/topic/5412690 > > Kurt Cagle successfully used the fn:doc function in his example. > http://www.stylusstudio.com/xmldev/201101/post20010.html > > The post at the Source Forge forum describes the problem and various attempts. Any assistance would be appreciated -- thanks. > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk

fn:doc not returning data

Mon, 09 Jul 2012 07:32:17 GMT

Daniel Oneil wrote: > I'm trying to use XQIB to get data from an XML file using the fn:doc > function. > The following link leads to a Source Forge forum where I posted my code > and a link to the books.xml file. > https://sourceforge.net/projects/mxquery/forums/forum/633155/topic/5412690 > The post at the Source Forge forum describes the problem and various > attempts. Any assistance would be appreciated -- thanks. What is the location of the HTML file with the XQuery script in relation to that local XML file? Is the HTML file also loaded from the local file system? Does the Firefox or Chrome error console show any security errors like "access to ... denied"? -- Martin Honnen --- MVP Data Platform Development http://msmvps.com/blogs/martin_honnen/

simple map operator

Mon, 09 Jul 2012 03:30:44 GMT

Thank you, Michael, I see that this is a syntactic categorisation and that the semantics of the definition does not carry as much weight as the order of precedence. When the order of precedence changes in the next draft, will "/" and "//" become map operators? Waiting to have syntax and semantics linked up again, in the next edition of your book, Jens On Jul 9, 2012, at 11:26 AM, Michael Kay wrote: > > A!B is a RelativePathExpr in the BNF grammar, but so are 29, count($x), and (1 to 10)[3]. > > Similarly, the way the grammar works, "a and b" is an instance of OrExpr, and 2+2 is an instance of ValueComp. > > So you need to distinguish the names of productions in the grammar, which affect the precedence of expressions, from the semantics of the operators appearing in those expressions. Generally productions are named after the lowest-precedence operator that is allowed to appear in the expression. > > In fact, since XPath 3.0 was last published, we have decided to change the precedence of the new "!" operator to be lower than the precedence of "/", so this will change. > > As for my book, see the discussion of the terminological problems around the phrase "path expression" on the first page of chapter 9; also see page 523. In common parlance, a "path expression" is an expression that uses the "/" operator, just as an "or expression" is one that uses the "or" operator; but that doesn't correspond to the BNF symbols PathExpr and OrExpr. > > The term "sequence expression" is used as a chapter heading in my book, as a convenient title for the set of constructs I chose to describe in that chapter, but it is not a term that appears in the XPath language specification itself. > > Michael Kay > Saxonica > > > On 09/07/2012 09:43, Jens Østergaard Petersen wrote: >> Thanks, Michael, >> >> If the simple map operator "does not locate any special nodes within trees, but works on sequences of items you specify by expressions", does that not make it into a sequence expression in the terms of Michael Kay's Reference, Chapter 10 (which also has "/" as a simple mapping expression when it works on atomic values)? Also, the draft defines a path expression as something that "can be used to locate nodes within trees", so I still wonder what the meaning behind this categorisation is. >> >> Cheers, >> >> Jens >> >> On Jul 9, 2012, at 10:01 AM, Michael Seiferle wrote: >> >>> Hi Jens, >>> >>> they are relative, such that each step (E1 ! E2) will serve as the input sequence E'1 for the next operation (E'1 ! E'2), hence: >>> >>>> >>>> hello >>>> world >>>> and >>>> hello >>>> universe >>>> /bar ! (: here we locate each child of :) >>>> upper-case(.) ! (: we return a sequence of their text() in upper-case :) >>>> substring(.,2,string-length(.)) (: we return a sequence of the upper case text and strip the first character :) >>> the map operator redefines the context items (inner focus) for each subsequent operation. >>> >>> So it does not locate any special nodes within trees, but works on sequences of items you specify by expressions, for example: >>>> (1 to 5) ! (. + 1) ! (. * 2) >>> will work as well and returns (4, 6, 8, 10, 12). >>> >>> Hope this helped to clear things up a little :-). >>> I guess others on this list will correct me if I got something wrong. >>> >>> Kind regards >>> >>> Michael >>> >>> >>> >>> Am 09.07.2012 um 09:41 schrieb Jens Østergaard Petersen: >>> >>>> Hi, >>>> >>>> Can anyone explain to me why the XQuery 3.0 simple map operator is a relative path expression? Which nodes within trees does it locate? >>>> >>>> Thanks in advance for any enlightenment, >>>> >>>> Jens >>>> _______________________________________________ >>>> http://x-query.com/mailman/listinfo/talk >>>> http://x-query.com/mailman/listinfo/talk >> >> _______________________________________________ >> http://x-query.com/mailman/listinfo/talk >> http://x-query.com/mailman/listinfo/talk >> > > > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk

simple map operator

Mon, 09 Jul 2012 02:26:50 GMT

A!B is a RelativePathExpr in the BNF grammar, but so are 29, count($x), and (1 to 10)[3]. Similarly, the way the grammar works, "a and b" is an instance of OrExpr, and 2+2 is an instance of ValueComp. So you need to distinguish the names of productions in the grammar, which affect the precedence of expressions, from the semantics of the operators appearing in those expressions. Generally productions are named after the lowest-precedence operator that is allowed to appear in the expression. In fact, since XPath 3.0 was last published, we have decided to change the precedence of the new "!" operator to be lower than the precedence of "/", so this will change. As for my book, see the discussion of the terminological problems around the phrase "path expression" on the first page of chapter 9; also see page 523. In common parlance, a "path expression" is an expression that uses the "/" operator, just as an "or expression" is one that uses the "or" operator; but that doesn't correspond to the BNF symbols PathExpr and OrExpr. The term "sequence expression" is used as a chapter heading in my book, as a convenient title for the set of constructs I chose to describe in that chapter, but it is not a term that appears in the XPath language specification itself. Michael Kay Saxonica On 09/07/2012 09:43, Jens Østergaard Petersen wrote: > Thanks, Michael, > > If the simple map operator "does not locate any special nodes within trees, but works on sequences of items you specify by expressions", does that not make it into a sequence expression in the terms of Michael Kay's Reference, Chapter 10 (which also has "/" as a simple mapping expression when it works on atomic values)? Also, the draft defines a path expression as something that "can be used to locate nodes within trees", so I still wonder what the meaning behind this categorisation is. > > Cheers, > > Jens > > On Jul 9, 2012, at 10:01 AM, Michael Seiferle wrote: > >> Hi Jens, >> >> they are relative, such that each step (E1 ! E2) will serve as the input sequence E'1 for the next operation (E'1 ! E'2), hence: >> >>> >>> hello >>> world >>> and >>> hello >>> universe >>> /bar ! (: here we locate each child of :) >>> upper-case(.) ! (: we return a sequence of their text() in upper-case :) >>> substring(.,2,string-length(.)) (: we return a sequence of the upper case text and strip the first character :) >> the map operator redefines the context items (inner focus) for each subsequent operation. >> >> So it does not locate any special nodes within trees, but works on sequences of items you specify by expressions, for example: >>> (1 to 5) ! (. + 1) ! (. * 2) >> will work as well and returns (4, 6, 8, 10, 12). >> >> Hope this helped to clear things up a little :-). >> I guess others on this list will correct me if I got something wrong. >> >> Kind regards >> >> Michael >> >> >> >> Am 09.07.2012 um 09:41 schrieb Jens Østergaard Petersen: >> >>> Hi, >>> >>> Can anyone explain to me why the XQuery 3.0 simple map operator is a relative path expression? Which nodes within trees does it locate? >>> >>> Thanks in advance for any enlightenment, >>> >>> Jens >>> _______________________________________________ >>> http://x-query.com/mailman/listinfo/talk >>> http://x-query.com/mailman/listinfo/talk > > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk >

simple map operator

Mon, 09 Jul 2012 01:43:12 GMT

Thanks, Michael, If the simple map operator "does not locate any special nodes within trees, but works on sequences of items you specify by expressions", does that not make it into a sequence expression in the terms of Michael Kay's Reference, Chapter 10 (which also has "/" as a simple mapping expression when it works on atomic values)? Also, the draft defines a path expression as something that "can be used to locate nodes within trees", so I still wonder what the meaning behind this categorisation is. Cheers, Jens On Jul 9, 2012, at 10:01 AM, Michael Seiferle wrote: > Hi Jens, > > they are relative, such that each step (E1 ! E2) will serve as the input sequence E'1 for the next operation (E'1 ! E'2), hence: > >> >> hello >> world >> and >> hello >> universe >> /bar ! (: here we locate each child of :) >> upper-case(.) ! (: we return a sequence of their text() in upper-case :) >> substring(.,2,string-length(.)) (: we return a sequence of the upper case text and strip the first character :) > the map operator redefines the context items (inner focus) for each subsequent operation. > > So it does not locate any special nodes within trees, but works on sequences of items you specify by expressions, for example: >> (1 to 5) ! (. + 1) ! (. * 2) > will work as well and returns (4, 6, 8, 10, 12). > > Hope this helped to clear things up a little :-). > I guess others on this list will correct me if I got something wrong. > > Kind regards > > Michael > > > > Am 09.07.2012 um 09:41 schrieb Jens Østergaard Petersen: > >> Hi, >> >> Can anyone explain to me why the XQuery 3.0 simple map operator is a relative path expression? Which nodes within trees does it locate? >> >> Thanks in advance for any enlightenment, >> >> Jens >> _______________________________________________ >> http://x-query.com/mailman/listinfo/talk >> http://x-query.com/mailman/listinfo/talk >

simple map operator

Mon, 09 Jul 2012 01:01:21 GMT

Hi Jens, they are relative, such that each step (E1 ! E2) will serve as the input sequence E'1 for the next operation (E'1 ! E'2), hence: > > hello > world > and > hello > universe > /bar ! (: here we locate each child of :) > upper-case(.) ! (: we return a sequence of their text() in upper-case :) > substring(.,2,string-length(.)) (: we return a sequence of the upper case text and strip the first character :) the map operator redefines the context items (inner focus) for each subsequent operation. So it does not locate any special nodes within trees, but works on sequences of items you specify by expressions, for example: > (1 to 5) ! (. + 1) ! (. * 2) will work as well and returns (4, 6, 8, 10, 12). Hope this helped to clear things up a little :-). I guess others on this list will correct me if I got something wrong. Kind regards Michael Am 09.07.2012 um 09:41 schrieb Jens Østergaard Petersen: > Hi, > > Can anyone explain to me why the XQuery 3.0 simple map operator is a relative path expression? Which nodes within trees does it locate? > > Thanks in advance for any enlightenment, > > Jens > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk

simple map operator

Mon, 09 Jul 2012 00:41:30 GMT

Hi, Can anyone explain to me why the XQuery 3.0 simple map operator is a relative path expression? Which nodes within trees does it locate? Thanks in advance for any enlightenment, Jens

Invitation to connect on LinkedIn

Tue, 19 Jun 2012 03:56:38 GMT

LinkedIn ------------ I'd like to add you to my professional network on LinkedIn. - Alice Alice Wei Technical Consultant at Indiana University Bloomington, Indiana Area Confirm that you know Alice Wei: https://www.linkedin.com/e/xnupbm-h3muyo7o-28/isd/7546757883/m_IXhCbP/?hs=false&tok=1ClHTo3ERgPBg1 -- You are receiving Invitation to Connect emails. Click to unsubscribe: http://www.linkedin.com/e/xnupbm-h3muyo7o-28/kDd-YG5BG4ZUACXjkyk-G9jZp24/goo/talk%40x-query%2Ecom/20061/I2558502205_1/?hs=false&tok=2vCMZQeY1gPBg1 (c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA. -------------- next part -------------- An HTML attachment was scrubbed... URL:

[ANN] BaseX 7.3

Mon, 18 Jun 2012 09:47:04 GMT

Hi everyone, we are glad to announce a great new release of BaseX, our XML database and XPath/XQuery 3.0 processor! Here are the latest features; - Many new internal XQuery Modules have been added, and existing ones have been revised to ensure long-term stability of your future XQuery applications: http://docs.basex.org/wiki/Module_Library - A new powerful Command API is provided to specify BaseX commands and scripts as XML: http://docs.basex.org/wiki/Commands#Basics - The full-text fuzzy index was extended to also support wildcard queries: http://docs.basex.org/wiki/Full-Text - The simple map operator of XQuery 3.0 gives you a compact syntax to process items of sequences: http://docs.basex.org/wiki/XQuery_3.0 - BaseX as Web Application can now start its own server instance: http://docs.basex.org/wiki/Web_Application - All command-line options will now be executed in the given order: http://docs.basex.org/wiki/Startup_Options - Charles Foster's latest XQJ Driver supports XQuery 3.0 and the Update and Full Text extensions: http://xqj.net/basex/ As usual, your feedback is welcome. More infos can be found on http://basex.org. For those of you in the Northern Hemisphere, we wish you a nice summer! No worries, we'll stay busy.. Christian BaseX Team, 2012

Strong data checking on @xml:id?

Fri, 08 Jun 2012 16:00:06 GMT

The relevant statement in the spec is XQuery 3.7.1.1 clause 5: "If the attribute name is xml:id, then xml:id processing is performed as defined in [XML ID]. This ensures that the attribute has the type xs:ID and that its value is properly normalized. If an error is encountered during xml:id processing, an implementation MAY raise a dynamic error [err:XQDY0091]." So yes, the effect is to some extent implementation-defined. Saxon never raises XQDY0091. It does apply normalize-space() to the value, but unless you are validating the result tree, it doesn't complain if the value isn't a valid NCName. I'm not sure why I made this decision; it's conformant with the spec, but my feeling today would be that validating the value (and reporting an error) would be preferable. Michael Kay Saxonica On 08/06/2012 18:55, David Sewell wrote: > Working within MarkLogic, I just got bitten by a server error caused > by lexically invalid @xml:id in the input data. Boiled down, this was > the offending query: > > let $in := > return element out { > attribute id { $in/@xml:id } > } > > MarkLogic complains: XDMP-LEXVAL: xs:ID("-ptr") -- Invalid lexical > value "-ptr" > > So it is obviously trying to cast '-ptr' as xs:ID and failing. But I > notice that Saxon doesn't throw an error in this case. Either processor > is happy if I wrap string() around $in/@xml:id. > > I'm just wondering if this is an implementation-dependent matter, or > what the specs might say about such a case. > > David S. >

Strong data checking on @xml:id?

Fri, 08 Jun 2012 12:21:59 GMT

Yes that's because the id table is validating ... Simple case is the XML is schema invalid. It needs to be fixed. Some processors will choke others may not. But its still bad XML. ---------------------------------------- David A. Lee http://x-query.com/mailman/listinfo/talk http://www.xmlsh.org > -----Original Message----- > From: http://x-query.com/mailman/listinfo/talk [mailto:http://x-query.com/mailman/listinfo/talk] On > Behalf Of G. Ken Holman > Sent: Friday, June 08, 2012 2:48 PM > To: http://x-query.com/mailman/listinfo/talk > Subject: Re: Strong data checking on @xml:id? > > At 2012-06-08 18:35 +0000, David Lee wrote: > >I belive the issue is that of validation. > >MarkLogic is a validating XQuery parser so is validating xml:id > >against the standard XML schemas. "-ptr" is not a valid xml:id > > > >Saxon HE (I presume you are using HE), otoh, is not a validating > >XQuery engine. > > Maybe so, but I did discover recently that Saxon HE does not load the > id() table when the token is not a valid xml:id value: > > t:\ftemp>type david.xq > let $in := document { } > return ( 'Result with ''abc'':',count($in/id('abc')) ), > let $in := document { } > return ( 'Result with ''-ptr'':',count($in/id('-ptr')) ) > > t:\ftemp>xquery david.xq > Result with 'abc': 1 Result > with '-ptr': 0 > > t:\ftemp> > > I hope this is helpful. > > . . . . . . . . Ken > > > -- > Public XSLT, XSL-FO, UBL and code list classes in Europe -- Oct 2012 > Contact us for world-wide XML consulting and instructor-led training > Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm > Crane Softwrights Ltd. http://www.CraneSoftwrights.com/q/ > G. Ken Holman mailto:http://x-query.com/mailman/listinfo/talk > Google+ profile: https://plus.google.com/116832879756988317389/about > Legal business disclaimers: http://www.CraneSoftwrights.com/legal > > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk

Strong data checking on @xml:id?

Fri, 08 Jun 2012 11:48:11 GMT

At 2012-06-08 18:35 +0000, David Lee wrote: >I belive the issue is that of validation. >MarkLogic is a validating XQuery parser so is validating xml:id >against the standard XML schemas. "-ptr" is not a valid xml:id > >Saxon HE (I presume you are using HE), otoh, is not a validating >XQuery engine. Maybe so, but I did discover recently that Saxon HE does not load the id() table when the token is not a valid xml:id value: t:\ftemp>type david.xq let $in := document { } return ( 'Result with ''abc'':',count($in/id('abc')) ), let $in := document { } return ( 'Result with ''-ptr'':',count($in/id('-ptr')) ) t:\ftemp>xquery david.xq Result with 'abc': 1 Result with '-ptr': 0 t:\ftemp> I hope this is helpful. . . . . . . . . Ken -- Public XSLT, XSL-FO, UBL and code list classes in Europe -- Oct 2012 Contact us for world-wide XML consulting and instructor-led training Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm Crane Softwrights Ltd. http://www.CraneSoftwrights.com/q/ G. Ken Holman mailto:http://x-query.com/mailman/listinfo/talk Google+ profile: https://plus.google.com/116832879756988317389/about Legal business disclaimers: http://www.CraneSoftwrights.com/legal

Strong data checking on @xml:id?

Fri, 08 Jun 2012 11:35:21 GMT

I belive the issue is that of validation. MarkLogic is a validating XQuery parser so is validating xml:id against the standard XML schemas. "-ptr" is not a valid xml:id Saxon HE (I presume you are using HE), otoh, is not a validating XQuery engine. ---------------------------------------- David A. Lee http://x-query.com/mailman/listinfo/talk http://www.xmlsh.org > -----Original Message----- > From: http://x-query.com/mailman/listinfo/talk [mailto:http://x-query.com/mailman/listinfo/talk] On > Behalf Of David Sewell > Sent: Friday, June 08, 2012 1:55 PM > To: http://x-query.com/mailman/listinfo/talk > Subject: Strong data checking on @xml:id? > > Working within MarkLogic, I just got bitten by a server error caused by > lexically invalid @xml:id in the input data. Boiled down, this was the > offending query: > > let $in := > return element out { > attribute id { $in/@xml:id } > } > > MarkLogic complains: XDMP-LEXVAL: xs:ID("-ptr") -- Invalid lexical value "-ptr" > > So it is obviously trying to cast '-ptr' as xs:ID and failing. But I > notice that Saxon doesn't throw an error in this case. Either processor > is happy if I wrap string() around $in/@xml:id. > > I'm just wondering if this is an implementation-dependent matter, or > what the specs might say about such a case. > > David S. > > -- > David Sewell, Editorial and Technical Manager > ROTUNDA, The University of Virginia Press > PO Box 400314, Charlottesville, VA 22904-4314 USA > Email: http://x-query.com/mailman/listinfo/talk Tel: +1 434 924 9973 > Web: http://rotunda.upress.virginia.edu/ > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk

Strong data checking on @xml:id?

Fri, 08 Jun 2012 10:55:20 GMT

Working within MarkLogic, I just got bitten by a server error caused by lexically invalid @xml:id in the input data. Boiled down, this was the offending query: let $in := return element out { attribute id { $in/@xml:id } } MarkLogic complains: XDMP-LEXVAL: xs:ID("-ptr") -- Invalid lexical value "-ptr" So it is obviously trying to cast '-ptr' as xs:ID and failing. But I notice that Saxon doesn't throw an error in this case. Either processor is happy if I wrap string() around $in/@xml:id. I'm just wondering if this is an implementation-dependent matter, or what the specs might say about such a case. David S. -- David Sewell, Editorial and Technical Manager ROTUNDA, The University of Virginia Press PO Box 400314, Charlottesville, VA 22904-4314 USA Email: http://x-query.com/mailman/listinfo/talk Tel: +1 434 924 9973 Web: http://rotunda.upress.virginia.edu/

Help with an XQuery function

Tue, 15 May 2012 10:28:44 GMT

Perfect. Thank you everyone. I was a bit confused about using the string-join function, but I just looked it up and it makes sense now. So, I can call the following with my function, as Liam mentioned: string-join(local:xpath($someNode), '') Or I can use the new built-in function, as David mentioned, replacing any unwanted strings, like so: replace(fn:path($name),'\[1\]|Q\{\}','') It seems like I have a lot more to get used to with XQuery, but I think that I understand things a little bit better now. Thanks again, Mark -----Original Message----- From: Liam R E Quin [mailto:http://x-query.com/mailman/listinfo/talk] Sent: Tuesday, May 15, 2012 12:48 PM To: Custer, Mark Cc: xquery-discuss Subject: Re: Help with an XQuery function On Tue, 2012-05-15 at 11:29 -0400, Custer, Mark wrote: [..] > This works, but I was wondering if it could be written better (and I > imagine that someone already has written a concise XQuery function to > do this). It might be easier to write it recursively, but clear is better than concise. > Also, I'm not entirely sure why, but when I run the above function, > I get the following result: > > /a /b /c[3] This is because you construct a sequence of strings. Use string-join( your-function(), "") to fix that. Or it might be, string-join("", your-function()), I never remember, which suggests it's the opposite of the other languages I use :-) Liam -- Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.org/ Ankh: irc.sorcery.net irc.gnome.org freenode/#xml

Help with an XQuery function

Tue, 15 May 2012 09:48:14 GMT

On Tue, 2012-05-15 at 11:29 -0400, Custer, Mark wrote: [..] > This works, but I was wondering if it could be written better (and I > imagine that someone already has written a concise XQuery function to > do this). It might be easier to write it recursively, but clear is better than concise. > Also, I'm not entirely sure why, but when I run the above function, > I get the following result: > > /a /b /c[3] This is because you construct a sequence of strings. Use string-join( your-function(), "") to fix that. Or it might be, string-join("", your-function()), I never remember, which suggests it's the opposite of the other languages I use :-) Liam -- Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.org/ Ankh: irc.sorcery.net irc.gnome.org freenode/#xml

Help with an XQuery function

Tue, 15 May 2012 09:12:40 GMT

On 15/05/2012 17:02, Custer, Mark wrote: > Thanks for pointing out the XQuery 3.0 functions, Matthias! > > fn:path is indeed supported, but I want a function that will do the same > as fn:path, minus any of the values of “[1]”. Plus, since my current > crop of documents don’t have any associated namespaces, the processor > that I’m using prepends “Q{}” before each path. So, with the previous > a/b/c example, I get the following: > > /Q{}a[1]/Q{}b[1]/Q{}c[3] > > But all I want is: > > /a/b/c[3] > > I’ll try working on it again later. Thanks again, > > Mark sounds like replace(path(),'\[1\]|Q{}','') will do what you want. David -- google plus: https:/profiles.google.com/d.p.carlisle ________________________________________________________________________ The Numerical Algorithms Group Ltd is a company registered in England and Wales with company number 1249803. The registered office is: Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom. This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. ________________________________________________________________________

Setting the document URI on constructed nodes.

Sun, 13 May 2012 09:26:34 GMT

At 2012-05-13 10:19 -0400, I wrote: >I cannot think of any way in the spec to specify the document URI of >a temporary in-memory tree, because I don't think that is meaningful >in the general case. > >However, when I've chained transformations in the past, I've >sometimes needed to preserve the input document URI along all of the >steps (because there have been relative URI addresses in the data) >and so I've very simply used xml:base= on the document element of >the temporary tree (unless the document element already has an >xml:base= attribute). > >Remember that from a syntax perspective, the root document file >entity of an XML document must contain the document element, so >base-uri(/*) is always the same as document-uri(root()) when there >is no xml:base= already there on the document element. > >So, when I create a temporary tree I use: > > > >... and when I ask for base-uri(/*) I get "...whatever...". > >In my work I would do something along the lines of: > >let $d := doc("input.xml") return >element {$d/name(.)} > { > attribute xml:base { "...whatever..." }, > $d/@xml:base, (:in case there already exists one:) > "rest of the processing" > } Actually, two mistakes in throwing together that example. I was asking for the name of the root node (not the document element) and I wouldn't hard-code the xml:base value. Rather I'd use the document-uri() function to preserve the URI of the input file, or even shorten it further by using base-uri() on the document element so as to accommodate any existing xml:base= attribute: let $d := doc("input.xml") return element {$d/*/name(.)} { attribute xml:base { base-uri($d/*) }, "rest of the processing" } >I hope this helps. > >. . . . . . . . . . . Ken > >At 2012-05-13 13:58 +0000, David Lee wrote: >>I noticed somewhat of a hole in XQuery ... hoping I am wrong. >>I can find no way to set the base URI of a constructed document e.g >> >>document { } >> >>such that fn:document-uri() would return it. >> >>It seem this is one of those properties that must come from the >>outside environment. >>I know if I were to store the document to a file then re-read it, >>likely the XML processor would pick it up ... I also know how to do >>this programmatically in API's like say Saxon. >>But it seems missing from XQuery itself. My guess is that since >>XQuery doesnt support storing documents it was thought unimportant >>to set the document URI. >> >>Why I ask ? >>I'm still looking at Streaming XDM formats, including pure >>in-memory streaming. >>But it seems like I cannot directly encode and pass on a document >>(or base) URI through XQuery by itself to the output. So any >>constructed documents would have none or undefined URI's to the >>receiver. this leads me to think I need a meta encoding for XDM >>much like proposed at Balisage (XDML). basically passing the URI >>information as seperate XDM values and a convention for >>interpreting them. This seems like it could not be done in pure >>XQuery however because the target even if it got say a sequence ( >>"uri" , document ) has no way to apply the uri to the document >>using XQuery so it must be done by external code. >> >>Thanks for any commentary. >>-David -- Public XSLT, XSL-FO, UBL and code list classes in Europe -- Oct 2012 Contact us for world-wide XML consulting and instructor-led training Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm Crane Softwrights Ltd. http://www.CraneSoftwrights.com/q/ G. Ken Holman mailto:http://x-query.com/mailman/listinfo/talk Google+ profile: https://plus.google.com/116832879756988317389/about Legal business disclaimers: http://www.CraneSoftwrights.com/legal

Setting the document URI on constructed nodes.

Sun, 13 May 2012 07:19:47 GMT

I cannot think of any way in the spec to specify the document URI of a temporary in-memory tree, because I don't think that is meaningful in the general case. However, when I've chained transformations in the past, I've sometimes needed to preserve the input document URI along all of the steps (because there have been relative URI addresses in the data) and so I've very simply used xml:base= on the document element of the temporary tree (unless the document element already has an xml:base= attribute). Remember that from a syntax perspective, the root document file entity of an XML document must contain the document element, so base-uri(/*) is always the same as document-uri(root()) when there is no xml:base= already there on the document element. So, when I create a temporary tree I use: ... and when I ask for base-uri(/*) I get "...whatever...". In my work I would do something along the lines of: let $d := doc("input.xml") return element {$d/name(.)} { attribute xml:base { "...whatever..." }, $d/@xml:base, (:in case there already exists one:) "rest of the processing" } I hope this helps. . . . . . . . . . . . Ken At 2012-05-13 13:58 +0000, David Lee wrote: >I noticed somewhat of a hole in XQuery ... hoping I am wrong. >I can find no way to set the base URI of a constructed document e.g > >document { } > >such that fn:document-uri() would return it. > >It seem this is one of those properties that must come from the >outside environment. >I know if I were to store the document to a file then re-read it, >likely the XML processor would pick it up ... I also know how to do >this programmatically in API's like say Saxon. >But it seems missing from XQuery itself. My guess is that since >XQuery doesnt support storing documents it was thought unimportant >to set the document URI. > >Why I ask ? >I'm still looking at Streaming XDM formats, including pure in-memory >streaming. >But it seems like I cannot directly encode and pass on a document >(or base) URI through XQuery by itself to the output. So any >constructed documents would have none or undefined URI's to the >receiver. this leads me to think I need a meta encoding for XDM >much like proposed at Balisage (XDML). basically passing the URI >information as seperate XDM values and a convention for interpreting >them. This seems like it could not be done in pure XQuery however >because the target even if it got say a sequence ( "uri" , document >) has no way to apply the uri to the document using XQuery so it >must be done by external code. > >Thanks for any commentary. >-David > -- Public XSLT, XSL-FO, UBL and code list classes in Europe -- Oct 2012 Contact us for world-wide XML consulting and instructor-led training Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm Crane Softwrights Ltd. http://www.CraneSoftwrights.com/q/ G. Ken Holman mailto:http://x-query.com/mailman/listinfo/talk Google+ profile: https://plus.google.com/116832879756988317389/about Legal business disclaimers: http://www.CraneSoftwrights.com/legal

5 summer interns for the FLWOR Foundation

Mon, 07 May 2012 11:45:38 GMT

Dear all, The XML community has spend oozes of time building languages, technology and platform software, that are at this time sufficiently mature. It's time now to build more killer apps in order to make people aware of what could be achieved using this technology. The FLOWR foundation is looking for 5 summer interns with XML, XQuery, database and application development knowledge, with creativity and initiative, to build a series of XML-only information intensive web applications. The position offers between 3 and 6 month of competitive salary (length depending of the complexity of the application to be developed), and it is located in Palo Alto, CA, the heart of Sillicon Valley (part of the internship can be done remotely, but not entirely). In addition to the XML technologies, the internship will provide in depth knowledge in database cloud computing, NOSQL, full text search, complex optimization of large information processing platforms. Please contact me for more information. Finally, if anybody on this mailing list has an interesting idea about such an application, we are more then happy to investigate financing the development (in open source only ! ). Best regards Dana

talk

Sat, 28 Apr 2012 22:32:31 GMT

hello talk all of the goals you have set for yourself are reachable stop what youre doing http://t.co/GA6RznIL

[ANN] BaseX 7.2.1: The Spring Edition

Fri, 27 Apr 2012 08:35:45 GMT

Dear all, once more, we are proud to announce a new version of BaseX! And once more, we can provide you with a whole bunch of new features: * Our value indexes now support string-based range queries: http://docs.basex.org/wiki/Indexes#Value_Indexes A big thank you to our sponsors who made this possible! * Our new XQJ API is based on Charles Foster's implementation. It fully utilizes the client/server architecture: http://xqj.net/basex * Import of XQuery modules has been simplified: http://docs.basex.org/wiki/Repository * Simplified invocation of Java code from XQuery: http://docs.basex.org/wiki/Java_Bindings * Full support for the XQuery 3.0 Regular Expressions syntax: http://www.w3.org/TR/xpath-functions-30/#regex-syntax * Updating functions can now return values: http://docs.basex.org/wiki/Database_Module#db:output * Unified handling of document and database URIs: http://docs.basex.org/wiki/Databases#Access_Resources * Pinning of opened database replaced by filesystem locking: http://docs.basex.org/wiki/Transaction_Management#Locking * REST, RESTXQ, WebDav: concurrency issues fixed As usual, we are looking to your feedback. Have fun, Christian BaseX Team http://basex.org

XML and the US Congress

Mon, 23 Apr 2012 12:30:04 GMT

In addition to NIEM.gov, Wikipedia has a very good NIEM overview page: http://en.wikipedia.org/wiki/National_Information_Exchange_Model As for agency adoption, you can get an idea from the 13 "domains" currently participating in NIEM: https://www.niem.gov/faq/Pages/what-domains-are-currently-participating-in-niem.aspx The US Federal CIO Council published a report in June 2010 that some may find informative: AGENCY INFORMATION EXCHANGE FUNCTIONAL STANDARDS EVALUATION: Adoption and Use of the NATIONAL INFORMATION EXCHANGE MODEL https://www.niem.gov/documentsdb/Documents/Other/AssessmentReport.pdf For those wanting to see how exchanges are modeled and implemented in NIEM, I recommend a 4-article series written by Priscilla Walmsley, a very familiar name to many of you: Creating a NIEM IEPD http://www.ibm.com/developerworks/xml/library/x-NIEM1/index.html Finally, the NIEM Naming and Design Rules share similarities with other NDRs such as those for UBL and UNCEFACT standards. https://www.niem.gov/documentsdb/Documents/Technical/NIEM-NDR-1-3.pdf Standards such as ISO/IEC 11179 (parts 4 & 5) and CCTS were leveraged too. Ken Sall Data Architect / Sr. XML Data Analyst 202-261-9045 (office) 410-952-2076 (cell) http://x-query.com/mailman/listinfo/talk > -----Original Message----- > From: http://x-query.com/mailman/listinfo/talk [mailto:http://x-query.com/mailman/listinfo/talk] On > Behalf Of daniela florescu > Sent: Sunday, April 22, 2012 4:02 PM > To: Michael Sokolov > Cc: XQuery Talk ML; Andrew Welch > Subject: Re: XML and the US Congress > > MIchael, > > while XML isn't obviously the panacea for the world's evil, I don't > think anybody can deny the fact that a uniform use of XML through the > IT layers would allow MUCH more information to flow among participants. > > And that can be golden in many circumstances... > > Best > Dana > > > > On Apr 22, 2012, at 12:56 PM, Michael Sokolov wrote: > > > I love how her eyes light up when she says "XML" as if - how could it > be simpler for those poor, underfunded state and local governments? > All they have to do is put XML behind, under and through the PDF! > Maybe we've hit on the solution for underfunded government programs at > last - just interlard them with XML - and hey presto! - you've got > compliance, or whatever it was she's supposed to be talking about. > > > > -Mike > > > > > > On 4/20/2012 3:34 PM, daniela florescu wrote: > >> :-) > >> > >> http://pinarbilgin.wordpress.com/2011/08/13/what-ginger-hears/ > >> > >> > >> On Apr 20, 2012, at 12:14 PM, Andrew Welch wrote: > >> > >>> On 20 April 2012 18:36, daniela florescu wrote: > >>>> > http://www.youtube.com/watch?v=P65skr3OiXk&feature=plcp&context=C4a > >>>> b6fefVDvjVQa1PpcFNiJcNuH75TWCzgaADQ6XFKPxMyj5siNfc%3D > >>> I heard "blah blah blah embed xml in this pdf blah blah"... > >>> > >>> > >>> > >>> -- > >>> Andrew Welch > >>> http://andrewjwelch.com > >> _______________________________________________ > >> http://x-query.com/mailman/listinfo/talk > >> http://x-query.com/mailman/listinfo/talk > > > > _______________________________________________ > > http://x-query.com/mailman/listinfo/talk > > http://x-query.com/mailman/listinfo/talk > > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk

XML and the US Congress

Mon, 23 Apr 2012 01:07:32 GMT

I thought the best bit was her waving a piece of printed paper and saying "this is a PDF". But when she said it had XML behind it, I was disappointed that she didn't turn it over and show us that there were angle brackets printed on the other side of the sheet. Mike On 22/04/2012 20:56, Michael Sokolov wrote: > I love how her eyes light up when she says "XML" as if - how could it > be simpler for those poor, underfunded state and local governments? > All they have to do is put XML behind, under and through the PDF! > Maybe we've hit on the solution for underfunded government programs at > last - just interlard them with XML - and hey presto! - you've got > compliance, or whatever it was she's supposed to be talking about. > > -Mike > > > On 4/20/2012 3:34 PM, daniela florescu wrote: >> :-) >> >> http://pinarbilgin.wordpress.com/2011/08/13/what-ginger-hears/ >> >> >> On Apr 20, 2012, at 12:14 PM, Andrew Welch wrote: >> >>> On 20 April 2012 18:36, daniela florescu wrote: >>>> http://www.youtube.com/watch?v=P65skr3OiXk&feature=plcp&context=C4ab6fefVDvjVQa1PpcFNiJcNuH75TWCzgaADQ6XFKPxMyj5siNfc%3D >>>> >>> I heard "blah blah blah embed xml in this pdf blah blah"... >>> >>> >>> >>> -- >>> Andrew Welch >>> http://andrewjwelch.com >> _______________________________________________ >> http://x-query.com/mailman/listinfo/talk >> http://x-query.com/mailman/listinfo/talk > > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk >

XML and the US Congress

Sun, 22 Apr 2012 15:16:58 GMT

On 4/22/2012 4:02 PM, daniela florescu wrote: > MIchael, > > while XML isn't obviously the panacea for the world's evil, I don't think anybody can deny the fact that a uniform use > of XML through the IT layers would allow MUCH more information to flow among participants. > > And that can be golden in many circumstances... > > Best > Dana > Oh I completely agree. A standardized XML format (is it NEIM?) will be far more useful in many ways than mere PDFs, I'm sure. I just think it's a bit funny how the effort required from the information *providers* tends to get glossed over. I don't really know much about the adoption of this standard - I just know that starting from PDF, generating useful XML is a nontrivial task. -Mike

XML and the US Congress

Sun, 22 Apr 2012 13:33:09 GMT

Another note: She is advocating NEIM. It is a set of standards for tags within an XML document. On Apr 22, 2012, at 3:02 PM, daniela florescu wrote: > MIchael, > > while XML isn't obviously the panacea for the world's evil, I don't think anybody can deny the fact that a uniform use > of XML through the IT layers would allow MUCH more information to flow among participants. > > And that can be golden in many circumstances... > > Best > Dana > > > > On Apr 22, 2012, at 12:56 PM, Michael Sokolov wrote: > >> I love how her eyes light up when she says "XML" as if - how could it be simpler for those poor, underfunded state and local governments? All they have to do is put XML behind, under and through the PDF! Maybe we've hit on the solution for underfunded government programs at last - just interlard them with XML - and hey presto! - you've got compliance, or whatever it was she's supposed to be talking about. >> >> -Mike >> >> >> On 4/20/2012 3:34 PM, daniela florescu wrote: >>> :-) >>> >>> http://pinarbilgin.wordpress.com/2011/08/13/what-ginger-hears/ >>> >>> >>> On Apr 20, 2012, at 12:14 PM, Andrew Welch wrote: >>> >>>> On 20 April 2012 18:36, daniela florescu wrote: >>>>> http://www.youtube.com/watch?v=P65skr3OiXk&feature=plcp&context=C4ab6fefVDvjVQa1PpcFNiJcNuH75TWCzgaADQ6XFKPxMyj5siNfc%3D >>>> I heard "blah blah blah embed xml in this pdf blah blah"... >>>> >>>> >>>> >>>> -- >>>> Andrew Welch >>>> http://andrewjwelch.com >>> _______________________________________________ >>> http://x-query.com/mailman/listinfo/talk >>> http://x-query.com/mailman/listinfo/talk >> >> _______________________________________________ >> http://x-query.com/mailman/listinfo/talk >> http://x-query.com/mailman/listinfo/talk > > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk

XML and the US Congress

Sun, 22 Apr 2012 13:02:23 GMT

MIchael, while XML isn't obviously the panacea for the world's evil, I don't think anybody can deny the fact that a uniform use of XML through the IT layers would allow MUCH more information to flow among participants. And that can be golden in many circumstances... Best Dana On Apr 22, 2012, at 12:56 PM, Michael Sokolov wrote: > I love how her eyes light up when she says "XML" as if - how could it be simpler for those poor, underfunded state and local governments? All they have to do is put XML behind, under and through the PDF! Maybe we've hit on the solution for underfunded government programs at last - just interlard them with XML - and hey presto! - you've got compliance, or whatever it was she's supposed to be talking about. > > -Mike > > > On 4/20/2012 3:34 PM, daniela florescu wrote: >> :-) >> >> http://pinarbilgin.wordpress.com/2011/08/13/what-ginger-hears/ >> >> >> On Apr 20, 2012, at 12:14 PM, Andrew Welch wrote: >> >>> On 20 April 2012 18:36, daniela florescu wrote: >>>> http://www.youtube.com/watch?v=P65skr3OiXk&feature=plcp&context=C4ab6fefVDvjVQa1PpcFNiJcNuH75TWCzgaADQ6XFKPxMyj5siNfc%3D >>> I heard "blah blah blah embed xml in this pdf blah blah"... >>> >>> >>> >>> -- >>> Andrew Welch >>> http://andrewjwelch.com >> _______________________________________________ >> http://x-query.com/mailman/listinfo/talk >> http://x-query.com/mailman/listinfo/talk > > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk

XML and the US Congress

Sun, 22 Apr 2012 12:56:39 GMT

I love how her eyes light up when she says "XML" as if - how could it be simpler for those poor, underfunded state and local governments? All they have to do is put XML behind, under and through the PDF! Maybe we've hit on the solution for underfunded government programs at last - just interlard them with XML - and hey presto! - you've got compliance, or whatever it was she's supposed to be talking about. -Mike On 4/20/2012 3:34 PM, daniela florescu wrote: > :-) > > http://pinarbilgin.wordpress.com/2011/08/13/what-ginger-hears/ > > > On Apr 20, 2012, at 12:14 PM, Andrew Welch wrote: > >> On 20 April 2012 18:36, daniela florescu wrote: >>> http://www.youtube.com/watch?v=P65skr3OiXk&feature=plcp&context=C4ab6fefVDvjVQa1PpcFNiJcNuH75TWCzgaADQ6XFKPxMyj5siNfc%3D >> I heard "blah blah blah embed xml in this pdf blah blah"... >> >> >> >> -- >> Andrew Welch >> http://andrewjwelch.com > _______________________________________________ > http://x-query.com/mailman/listinfo/talk > http://x-query.com/mailman/listinfo/talk

XML and the US Congress

Fri, 20 Apr 2012 12:34:15 GMT

:-) http://pinarbilgin.wordpress.com/2011/08/13/what-ginger-hears/ On Apr 20, 2012, at 12:14 PM, Andrew Welch wrote: > On 20 April 2012 18:36, daniela florescu wrote: >> http://www.youtube.com/watch?v=P65skr3OiXk&feature=plcp&context=C4ab6fefVDvjVQa1PpcFNiJcNuH75TWCzgaADQ6XFKPxMyj5siNfc%3D > > I heard "blah blah blah embed xml in this pdf blah blah"... > > > > -- > Andrew Welch > http://andrewjwelch.com