: Kendall Shaw
Cc: BaseX
Subject: Re: [basex-talk] Somewhat unusual question
Hi Kendal --
If you don't stick to attributes, it's not hard to represent that kind of
relationship graph in XML:
karen
linda
sarah
Hi Kendal --
If you don't stick to attributes, it's not hard to represent that kind of
relationship graph in XML:
karen
linda
sarah
wendy
cindy
This way you can have a lot of elements (edges in the relat
On 2/25/17, 12:55 PM, "Liam R. E. Quin" wrote:
On Sat, 2017-02-25 at 10:02 +, Kendall Shaw wrote:
> It’s interesting to me to know what sorts of applications seem like
> they would be a good match for XQuery’s data model but turned out not
> to be in some case.
I agr
On Sat, 2017-02-25 at 10:02 +, Kendall Shaw wrote:
>
[...]
> The original post was asking for examples of ways that XQuery is a
> good solution for an unknown problem.
Unknown to us at least... yes.
> Generally, if I found myself think that technology x is the solution
> to every problem, I
Hi,
I was following this thread last week but couldn't chime in yet as I was
inundated with work. I am, in a sense, lucky to be able to spend about 2/3 to
3/4 of my time on XQuery and XSLT. It used to be just XSLT but we started using
XQuery more and nowadays it's predominantly XQuery (with Ba
We users of BaseX probably all agree that it and XQuery are super and powerful.
XML ,like RDF, is not a perfect match for every problem. Wordstar is however
the solution to every problem.
Kendall
On 2/25/17, 1:28 AM, "meumapple" wrote:
XML offers an elegant yet simple tree structure. You
On 2/24/17, 7:15 PM, "Liam R. E. Quin" wrote:
On Fri, 2017-02-24 at 18:07 +, Kendall Shaw wrote:
> For example, a program that regulates flow of water in a garden
> sprinkler is probably not a good match for xquery and an xml
> database.
Funnily enough, sensors these days
XML offers an elegant yet simple tree structure. You can find a way to express
in XML the kinds of relationships you mention by simply using a different
strategy (using not a parent element but, for example, attributes).
In general, every format has limitations (so this is not an XML-related
p
I do not think this an argument to
Il giorno 25 feb 2017, alle ore 00:05, Kendall Shaw
ha scritto:
A more interesting example, maybe: If you compare XPath with this SPARQL
fragment:
?x foaf:knows/foaf:name ?name .
All of my friend’s friend’s friend’s friend’s friend’s etc., with arbitrary
On Fri, 2017-02-24 at 18:07 +, Kendall Shaw wrote:
> For example, a program that regulates flow of water in a garden
> sprinkler is probably not a good match for xquery and an xml
> database.
Funnily enough, sensors these days often report results using EXI, and
an embedded XQuery engine might
A more interesting example, maybe: If you compare XPath with this SPARQL
fragment:
?x foaf:knows/foaf:name ?name .
All of my friend’s friend’s friend’s friend’s friend’s etc., with arbitrary
depth, who know my friend with name x.
Friends are not limited to having 1 “befriender” in the way tha
For example, a program that regulates flow of water in a garden sprinkler is
probably not a good match for xquery and an xml database.
On 2/24/17, 2:20 AM, "meumapple" wrote:
Hi Kendall,
I do not agree. A few considerations. If data are XML, I find it difficult
to use a different
Hello Marco,
I'm sure your thinking like this: look at it from the customer's point
of view. They will view the
s/w as a means to a enabling them to get their product to the consumer
more cheaply or quickly or to allow them to reach more consumers.
>From that viewpoint here's a few points to consi
Hello Marco,
I think Max is spot on, that the main objection of business people is
that XQuery is not exactly mainstream stuff. Nobody will be questioned
if you buy Oracle and your project in the end fails - Hey, you bought
the established market leader, what could go wrong? But you use a
relative
lto:mgaer...@arcor.de>>,
"basex-talk@mailman.uni-konstanz.de
<mailto:basex-talk@mailman.uni-konstanz.de>"
<mailto:basex-talk@mailman.uni-konstanz.de>>
Subject: Re: [basex-talk] Somewhat unusual question
To put it mildly, I disagree. I think the greatest mistake one ca
Hi guys,
thank you all so much for the great feedback.
This one in particular feels like a crucial point and it's why I'm
currently collecting all possible feedback also from students, stagers
and other technicians that are somehow representative of entry-level to
basic staff.
Nice to see that
Hello Max,
I think business decisions follow that path to avoid ending up in
a niche area where it would be terribly difficult to employ a
replacement once a/the developer has left.
Perhaps also pointing out that there are standards and perhaps
that it's not too difficult to learn would help to a
Hi,
I really like this thread! Keep the arguments coming! ;-)
I am not saying that XQuery is just another query language. But if
somebody (who has never heard anything about XQuery) is asking about
your technological choice then telling them that XQuery is so special
and unique is counter-product
lt;mailto:basex-talk@mailman.uni-konstanz.de>"
mailto:basex-talk@mailman.uni-konstanz.de>>
Subject: Re: [basex-talk] Somewhat unusual question
To put it mildly, I disagree. I think the greatest mistake one can make is call
XQuery a query language. I prefer to say that it is an i
To put it mildly, I disagree. I think the greatest mistake one can make is call
XQuery a query language. I prefer to say that it is an information language. If
this appears to be an incomprehensible statement, this reflects the novelty of
the concept of an "information language". A book should b
Hi Kendall,
I do not agree. A few considerations. If data are XML, I find it difficult to
use a different language from XQuery. It is possible, of course, but much much
more complex (why doing that?!). But native XML files are not the entire story.
You can transform, for example, all of text da
What the application is makes all the difference. If the purpose does not have
to do with XML and XML in a database, then XQuery and BaseX is less likely to
be appropriate.
Kendall
On 2/23/17, 12:36 PM, "basex-talk-boun...@mailman.uni-konstanz.de on behalf of
Maximilian Gärber" wrote:
Hi
Hi Marco,
from my experience, the best way to handle these types of arguments is
to make clear that there is nothing 'special' about XQuery. It is a
query language.
If you have to compare BaseX to something that most Java developers
will know, I'd use Hibernate and HQL, a library and DSL that is
Hello Marco and all,
There was a similar question asked on the xquery-talk mailing list two
years ago: "what are the prime factors behind the resistance to adopt
XQuery or it's derivatives". Here's a direct link to that thread [1].
Around the same time there was many similar topics about othe
-Message d'origine-
De : basex-talk-boun...@mailman.uni-konstanz.de
[mailto:basex-talk-boun...@mailman.uni-konstanz.de] De la part de Marco Lettere
Envoyé : mercredi 22 février 2017 13:43
À : BaseX
Objet : [basex-talk] Somewhat unusual question
Hi to everyone,
probably this is not the
Hello Marco,
I don't really get why you want to exclude languages which you call
"lower level of abstraction", at least to me the architectural reasons
are not obvious at all. In the wild when I see XML handling applications
which are not XQuery/XSLT I would say they are mostly Java, C# or python
Hi to everyone,
probably this is not the right place for such a discussion but the BaseX
communitiy is the one I'm better introduced to and the one I trust the
most. So I hope that this somewhat unusual excursus will anyway be of
interest to some of you.
As for myself I fell in love with XQu
27 matches
Mail list logo