<p>Hee-hee, too bad Kopete's author didn't know about the "no bad associations in other languages" guideline -- here, in Bulgaria, Kopete means "buy!", in *imperative* form. It also looks *a lot* like "Kopele", which means "son of a bitch". Not to mention that here Kexi is sometimes used as a derogatory term for a fat guy. >_<
</p>
<p>Anyway, I here are my suggestions (feel free to calmly ignore my K-ism, Aaron):</p>
<p>Kuerist, Patternist, Kondukt, Konquerier, seeK, oaK, looKfor, investiKate, Kolumbus, Kontent, reKuest, FlowtraK, Akcessance, Tranceform, Transq, struKt, taKe, xtraKt</p>
<p>Notes: </p>
<p>Konquerier (con-query-er) could be either very confusing or very enchanting. Dunno.</p>
<p>Kolumbus associates rightly, since the parser is like a sailor in the middle of the XML ocean.</p>
<p>reKuest is twofold. It has the feeling of "ya" (yet another) in things like yacc (since you'll RE-do the job of creating a XPath parser YetAnother time). Also, what feels like the main thing here is the "Kuest", which has a certain... adventure feeling to it, if you understand what I mean.
</p>
<p>About FlowtraK... well, the parser kinda like tracks the XML flow.</p>
<p>"access" derivatives are particularly nice, since "access" summarizes both original points - "change" and "navigate". Hence Akcessance.</p>
<p>I hope it's obvious that Tranceform is pronounced "Transform".</p>
<p>Transq feels cool, and signifies Transquery. Word-end q isn't patented by Compaq, you know ;) .</p>
<p>struKt describes that we're changing/navigating a *structure*. Besides, it feels a tad geeky, what with the C keyword "struct".</p>
<p>The parser "takes" things from the parsee, so enter, taKe.</p>
<p>Maybe the parser can be said to "extract" things from XML somewhat, so xtraKt might work.</p>
<p>In the end, I don't see how the current name KXForm is bad or too general. I'd stick with it.</p><br><br>
<div><span class="gmail_quote">On 5/28/06, <b class="gmail_sendername">Adriaan de Groot</b> <<a href="mailto:groot@kde.org">groot@kde.org</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Sunday 28 May 2006 02:19, Aaron J. Seigo wrote:<br>> On Saturday 27 May 2006 07:38, Frans Englich wrote:
<br>> > On Friday 26 May 2006 22:00, Aaron J. Seigo wrote:<br>> > > that said, the XPath/XQuery/XSLT frameworks are built on top of the<br>> > > KHTML / WebCore stuff, correct? does it then make sense to tie the name
<br>> > > in with that set of software?<br>><br>> instead of hooking into the "web" part, what about "<something>Core". we<br>> have WebCore, JavaScriptCore .... XMLCore? CoreXML? you might have
<br>> something better for the <something> part, but by following this name<br>> scheme we get something that provides a theme.<br><br>This is about data query and transformation; can we do something about that?
<br>Taxons might make sense here, Core Compass perhaps for the steering and<br>searching thing. Or call it "Brownian" for the random motion.<br><br>> > What list is better? kde-devel?<br>><br>> kde-promo =)
<br><br>Replying here anyway.<br><br>--<br>KDE Quality Team<br>GPG: FEA2 A3FE<br>_______________________________________________<br>kde-quality mailing list<br><a href="mailto:kde-quality@kde.org">kde-quality@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-quality">https://mail.kde.org/mailman/listinfo/kde-quality</a><br></blockquote></div><br>