I just stumbled across this experimental Query language for XML, called XCerpt.  It is example-based variable binding, and looks very much like Prolog queries over a triples database, or like Redland's QBE would look if they used RDF/XML syntax instead of triples.  Such query syntaxes seem popular for graph queries, but I'm not sure if they are really the best for users. 

In any case, the paper on XCerpt was interesting.  Although XQuery is not as "imperative" as the paper wants you to believe, XCerpt really does blur the line between "data" and "code" more than XQuery does.  It makes you want to use it, because it hints seductively that code and data are really the same thing.

[Better Living Through Software]

(SOURCE:"sjoerd")-This is great: now you can have a real time vanity search of your name available as an RSS feed.
e.g. http://www.feedster.com/rss.php?q=%22roland%20tanglao%22 is an RSS feed showing all posts with links to Roland Tanglao (I assume that putting a phrase in quotes causes the whole phrase to be searched for like Google. Couldn't find any docs confirming this so this is only a guess for now).
<quote>
Scott Johnson (maker of Feedster) mailed me to say that the search results already are available in RSS. It's the XML icon at the bottom of the result page. That's just great!
</quote> [Roland Tanglao: KLogs]

Bottom-up vs. top-down taxonomy is an old, ongoing KM struggle. But the emerging architecture of business process automation may help us cut that Gordian knot. XML documents, produced and consumed by Web services but also by people running a new generation of XML-savvy applications, will be the currency of the information economy. Richly structured, easily captured, and embedded in well-defined business contexts, they'll be a godsend for tools that mine knowledge from documents. Full story at InfoWorld.com

Here's Edwin Khodabakchian's take on InfoPath, an example of the kind of "XML-savvy application" I had in mind:

Infopath is a kind of Blog++: the manipulated data is rich and structured (expense report, travel request, hotel reservation, employee review), meaning that when the data is published back to the server can be processed by an array of services, processes, agents. [Collaxa's Take]

Exactly. Collaboration tools have to move heaven and earth to mine knowledge and infer social networks from email traffic. While it is notionally private, many email exchanges -- "here's the revised version with the changes we discussed" -- are really semi-public in scope. The same holds true for many voice interactions. ... [Jon's Radio]

Top XML Mar 16 2003 4:43PM ET [Moreover - XML and metadata news]

.net Mar 14 2003 4:09PM ET [Moreover - Webmaster tips]