[
Lists Home |
Date Index |
Thread Index
]
- From: Len Bullard <cbullard@hiwaay.net>
- To: Tim Bray <tbray@textuality.com>
- Date: Thu, 30 Mar 2000 19:43:04 -0600
Tim Bray wrote:
>
> At 10:46 AM 3/30/00 +0100, Kay Michael wrote:
> >
> >I really think you need to distinguish between a query engine and a search
> >engine. Query engines answer questions like "find me all documents that have
> >an <xyz> element as the third grandchild of an <abc> element". Search
> >engines answer questions like "have you got anything about the causes of
> >hyperinflation in inter-war Germany?"
>
> I think what you're talking about would normally be called an Information-
> Retrieval (IR) system. Such a system is distinguished from traditional
> search engines in the general case in that nobody has ever successfully
> built one that, in the general case, works.
>
> (putting on my asbestos underwear) -Tim
Ouch! Flame to fungus?
Generalized IR should fall easily out of markup. The trick is to ask
the
the namespace, not the tree.
If I have to know position, how can I ask a question of a
tree I've never seen. But, if I have a namespace, I can
ask for names in it:
? germany interwar hyperinflation causes
should return the aggregate of treelocs to
branches like that; an XLink if you like.
It really should be *made* that simple to state.
The user gets that and it works on a little screen. :-)
Long obscurely syntaxed paths are too hard for most
users to learn. They have to be able to name
and return branches. Use the XML namespace.
Little schemas but lots of them, iconic
and at about the complexity that emerges
using relational tables.
len (glossingOverNaturalLanguageParsing)
***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************
|