RE: [Fwd: Implementation of XML QUERY]

[Scott Hinkelman <srh@us.ibm.com>]

David,
Again, your mail tool is misquoting people. That was not my comment.

Scott Hinkelman, Senior Software Engineer
XML Industry Enablement
IBM e-business Standards Strategy
512-823-8097 (TL 793-8097) (Cell: 512-940-0519)
srh@us.ibm.com, Fax: 512-838-1074



David RR Webber <Gnosis_@compuserve.com>@compuserve.com> on 01/24/2001
09:31:09 PM

To:   Scott Hinkelman/Austin/IBM@IBMUS
cc:   mark.hale@interwoven.com, ebxml-regrep@lists.ebxml.org
Subject:  RE: [Fwd: Implementation of XML QUERY]



Mark,

I'm a believer!!!  I totally agree that the kind of high level form
driven interfacing is what we need.

Having implemented these in the past - users are adept at
using these - but NOT at writing SQL queries or understanding
lowlevel XML path syntax.

I think we need to conpromise - I was accused of attempting
to re-invent query language for daring to believe in Google
style approach.

So here's my further thought - implementors can build Google
style interfaces ON TOP of our middle layer query methods
where are middle layer are prescribed methods(valuelists).

If we position this right we can just about run with this being
a neutral approach while exposing enough of a flexible
query structure.  Personally I am not above providing
AND, OR, NOT, EQUAL, and GT, LT on pulldown lists of
connectors for nouns and values.  If this is re-inventing a
query language - well them I'm guilt - but seems to me
to be about as basic and obvious as you can get and
that every query language ever invented (except APL)
uses these - so what's to invent?

DW.
=====================================================

Message text written by Scott Hinkelman
>I strongly
encourage disbelievers in the ability to use ad hoc query against content
to
try out a wonderful ad hoc query interface already in place:  go to
www.google.com, type "Enterprise Class Content Management" in the entry
field, and hit return.  What is missing is a well defined partner profile
that comes up to do business (I would certainly hope this is achieved in
ebXML).  Notice that I can find someone that can do ECCM without having to
know anything about taxonomies.  Also note that we also have to deal with
the plethora of information that will be available when core components
come
on-line.

We can also visit classical decision theory that suggests that heterarchies
support creativity in early stages of a business life-cycle, which in my
opinion, is the time in which we can foster the growth of new
opportunities.

I am agreement that the discussion about one query syntax over another has
gone on too long.  What I disagree on is the ad hoc versus structured query
debate.  There are plenty of use cases that support both.
<